I use PHP daily. The only thing that seems overly magical on a cursory glance is Livewire, but I’ll probably end up using Solid for the frontend anyway.

colden the relations with Israel

I thought this was a forum for Linux discussion, not promotion of fascists

What did they realize that they open sourced their product a decade too late for anyone to actually revive it?

dozen = 12 + 1; // one extra for the baker!

I got mad at this when I first saw it but then I remembered there’s some code at work that defines an hour as 50 minutes

Statistically, this makes your code better

Yeah…. I’ve definitely been the next guy on a couple bad regexes that I wrote

When versioning and feature flags are too hard: just use git and hope for the best

My old senior used to do this before he got laid off and now I’m charge of code that’s littered with old commented out code and no way to know why it was commented out.

Then it breaks years after you’ve left and someone has no choice but to touch it

I often use comments as ways to say, “I know this is cursed, but here’s why the obvious solution won’t work.” Like so:

/**
 * The column on this table is badly named, but
 * renaming it is going to require an audit of our
 * db instances because we used to create them
 * by hand and there are some inconsistencies
 * that referential integrity breaks. This method
 * just does some basic checks and translates the
 * model’s property to be more understandable.
 * See [#27267] for more info.
 */

Edit: to answer your question more directly, the “why not what” advice is more about the intent of whether to write a comment or not in the first place rather than rephrasing the existing “what” style comments. What code is doing should be clear based on names of variables and functions. Why it’s doing that may be unclear, which is why you would write a comment.

So this is admittedly the first genocide I’ve followed this closely in real time. Is it normal for them to just… announce what they’re doing the entire time? The general who drafted the plan posted it on YouTube? What?

Writing plain old JavaScript without a library or framework is nice while you’re learning. Too many people will learn a single framework and not have any idea what the underlying APIs are, so the transferable skills are minimal.

Companies doing austerity internally to own the clean energy enjoyers

I can’t imagine just opening a giant PR without having extensive contact and coordination with the maintainer. Almost any amount of incremental safe steps would be preferable to a giant PR, even with extensive communication. I once introduced fully strict typescript into a vanilla js codebase and it took dozens of small PRs to do so. It was made more complicated by the fact that it was a library, but still. The communication made the entire process smooth and let everyone be confident the changes were correct along the way. If I’d done it all at once without any coordination, it would have been faster for me, but at the cost of the maintainer’s sanity and time.