Coolify will be great, 6 months ago however I experienced so many bugs around docker deployments I just couldn't trust it for production. Hopefully the new hires will make continued progress because there are some pretty great workflows possible. Already though, it is extremely cool to run your own platform
I moved my profile folder into Librewolf, done. The only thing that's bugging me is the 'LibreWolf: Always store cookies/data for this site' option on the navbar padlock dropdown, it only appears for me in private windows, regardless of my 'Delete cookies site/data...' option.
It's annoying because I contributed UX to this librewolf feature a few years ago (because I really wanted it), its finally landed but I can't use it - it was the blocker to adopting the more strict privsec model that librewolf offers by default (it solves the 'cookie exceptions are a pain to manage' problem. Obviously something to do with my kitchen-sink Firefox profile folder copy, but for now I guess I'll just carry on with cookies persisting and at some point rebuild a fresh librewolf profile if I want to adopt their defaults.
So there's at least that, if this ambigious license stuff (and recent ad company purchases) bothers you, you can probably just copy your profile into Librewolf's profile folder, rename, and have done something about this perceived issue without a major disruption
I contributed UX for a 'save cookies for this site' dropdown feature in the navbar, a poc was made which looked good, but it got lost in other work and eventually didn't land in a release that I'm aware of. Shame because that one feature would make it practical to use the recommended clear cookies behavior by default except for particular sites and overall boost everyone's privacy and security because I'm pretty sure most people turn it off after getting sick of logging in. After a couple of months I went back to Firefox and hardened it making it basically the same as LF but not being a month behind in updates. I guess I'll revisit the project now
I am sorry to hear this, however I would not be surprised if someone in the OpenCore/Hackintosh space has (or will produce) a fix, because those systems are sometimes particularly sensitive to updates
This definition of helping me (a user} navigate could be interpreted in many ways, from the obvious all the way through to sending Mozilla my data so they can "improve Firefox" and therefore help me through giving them my information. This signals intent against my interest, regardless of whether that actually is there intent. The 'help' in particular is extremely suspicious and ambiguous
it was done on an 13900k system with 128gb ram. I bet the performance would be very different on other systems. and by my calculations the next frame would only take like maybe an hour or so to render. so that means that actually, hilariously, if anyone wanted to really dig in and make the engine faster - which I suspect it can be done by multiple orders of magnitude, truly - then actually I'd say 30fps types-only-doom is possible in the next maybe year or two. the TAS-style keyboard controls will work, but one problem is definitely going to be "how do you refresh a screen" which is a problem I didn't attempt to tackle other than to say you could (with what I already built) just hover your mouse over another type that contains the information for frame 2.
Fascinating. Just for fun, comparable compute (by cpumarks) to your 13900k for 30 fps would be 39,600+ 96-core AMD EPYC 9655Ps. Bravo on the project success!
you know what's funny, I also have a threadripper rig (which is my main development rig) and it ran _slower_ than on the 13900k. Like. by a lot. and while that surprised me at first, it's makes a lot of sense because this is Node.js in the end (i.e. the TypeScript typechecker runs within Node.js) and that means it's single threaded. So single-threaded perf is all that matters.
That figures. It was fun though to pretend it would scale across processors. Were you tempted to fork the typescript compiler in this project to add some optimizations or something crazier like gpu acceleration for rendering or parallel workloads?
Reminds me of the guy on Youtube obsessed with optimizing Mario64 code, he found really interesting things like how removing optimizations made the game faster - presumably because the very basic tooling the original developers had made it hard to measure things across the board, and also not making the most of the powerful hardware architecture.
I evaluated reactive databases for a client side app recently - what a mess to be found there. Node polyfills in the browser? No thanks. So yes, there is a need and I hope this could be an option in the future.
