Not just Ukrainians. Uyghurs, Syrians, Kurds, Georgians, Quirimli, Chechens… the list goes fucking on.
The most vile shit they introduced into discourse around Gaza is the notion that genocide is a competition. “More people dead in n days in Gaza than in n months in Ukraine” is a statement that achieves only two goals: devalue human suffering and reveal the messenger to be a morally bankrupt psychopath.
Individual rights get eroded if people don’t keep the good fight. The hope for a system that can prevent the amassing of power in the hands of a few through no effort by the many is entitled childishness personified.
Welcome to the world of SPAs. Where every little thing needs its own application.
Damn it, we even have HTML tags that are impossible to employ in their entirety without use of JavaScript. <dialog> is infuriating and is literally two attributes away from not needing JavaScript.
Except on Chrome. Dialog is broken on Chrome and you will have to clean up with JavaScript after chrome’s own half assed implementation.
If you’re a software engineer, you’re applying an engineering process to the field of software development. Adding a shopping cart to a blog can be a perfectly sound solution to the problem at hand.
Engineering becomes more important at scale, but scale itself doesn’t define engineering.
Sorry, but you don’t get to claim groupthink while ignoring state of Apache when Nginx got released.
Apache was a mess of modules with confusing documentation, an arsenal of foot guns, and generally a PITA to deal with. Nginx was simpler, more performant, and didn’t have the extra complexity that Apache was failing to manage.
My personal first encounter was about hosting PHP applications in a multiuser environment, and god damn was nginx a better tool.
Apache caught up in a few years, but by then people were already solving different problems. Would nginx arrive merely a year later, it would get lost to history, but it arrived exactly when everyone was fed up with Apache just the right amount.
Nowadays, when people choose a web server, they choose one they are comfortable with. With both httpds being mature, that’s the strongest objective factor to influence the choice. It’s not groupthink, it’s a consequence of concrete events.
Don’t learn Elixir to replace Ruby. Learn it to enjoy OTP and BEAM.
I would love to join a cool company that’s willing to accept a dev that can transition fast. However, most of Elixir job listings I find are gambling or crypto. And I ain’t gonna touch those.
When the specific goal is something I can do manually, and it’s not pressing, I would rather spend time learning how to make a tool to do it. I might not need the tool ever, I do use the knowledge picked up on those forays every day.
Thorium reactors have a cleverly dumb failsafe. If reactor control fails, there’s a plug that melts and drains the contents into a container that’s not fit for runoff neutron generation.
That’s an example of a failsafe that fits its purpose. It’s still possible to fuck it up, but it would take a lot of effort to do so.
Safety features should work if everything else fails. Their failure mode can’t be “fuck it, it didn’t work”. Which is directly opposite to the failure mode of a subscription based service.
Right, because Amsterdam, as we all know, is such a shithole in that regard.
You’re the obsessed one in this case.