376 karma · joined July 8, 2009
Firefox used to _stand_ for things that internet savvy folks cared about, and at least some of that would trickle down to make even the non-savvy user's browsing experience better.
Can't they just take Google's yearly $600,000,000 payment and build the best browser "for the user" while also addressing technical debt and organizational issues so it can continue as an open source project if/when the money ever dries up?
Edit: deleted distracting details that the comment below rightfully calls out.
This may not have any other real purpose than to be a piece of art. Or perhaps it's aimed at a narrow demographic of kids who are already decent programmers. However, it's also entirely possible that others will create a whole ecosystem of "unofficial" tutorials and libraries/frameworks around it.
Crosshair placement for things like leading shots? Or more for building a mental map of where the enemy is likely to poke their head up? I would think these things involve spatial imagery/memory. I do remember putting a tiny piece of post-it note on my monitor to act as a red dot sight in Killing Floor, but my guess is that'd help anyone headshot zombies better, not just us aphantasics.
On the OS side of things, when switching between activities, very rarely my last activity is to the right in the carousel rather than to the left. Because I can't predict when it happens, I can't mindlessly switch to my previous activity, which is surprisingly annoying.
You can launch a job(s) via command-line, config in Bash comments, REST APIs, linking to their library, and I think a few more ways.
I found it pretty easy to setup and admin. Scaling in the cloud was way less developed when I used it, so I just hacked in a simple script that allowed scaling up and down based on the job queue size.
What do you like better and for what use-case? Mine was for a group of researchers training models, and the feature I desired most was an approximately fair distribution of resources (cores, GPU hours, etc.).
And even within frameworks like Scrum, I don't think that "sprint" was ever intended to mean that programmers are supposed to be in permanent crunch mode.