Don't be silly, this is the JS ecosystem. Why use your brain for a minute and come up with a 50 byte helper function, if you can instead import a library with 3912726 dependencies and let the compiler spend 90 seconds on every build to tree shake 3912723 out again and give you a highly optimized bundle that's only 3 megabytes small?

Scammers have no problem waiting 24 hours, so this doesn't protect incompetent people at all.

To be blunt: I don't care. Don't make their incompetence my problem.

> But putting my design hat on here: couldn't this be the whole approach?

No, because protecting users is just an excuse. The overreach is the goal.

Having worked in big tech, my money would be on Hanlon's Razor here -- "Never attribute to malice that which is adequately explained by incompetence"

It isn't adequately explained by incompetence. This is out of the playbook of boiling the frog. Nothing about this is new or unexpected. We have plenty of history about how these things go down. First they make installing device owner chosen software ridiculously laberous. Then they will remove the option altogether.

That includes school-issued Macs, so I don't see how that's an argument against Chromebooks.

And faking being sick so he could clap at Apple marketing events. He kinda lost me there.

He's looking back to a time when they were still special. When every keynote brought out a new, interesting product, feature, OS enhancement, etc. Back in the Steve Jobs era, it was still worth tuning in every year to see what was new.

The whole article is about how Apple is still special just like when he was a kid.

But anyway, I find it funny that author implies if a kid gets a MacBook Neo they will explore all the possibilities to use and customize it, but somehow the same kid won't try to push a Chromebook to its limit. It 100% matches my stereotype of how Apple fans view machines.

Yeah, you'd find out about it all in the newspapers a few hours later, and none if it was "clap to yourself in an empty room" impressive anyway. I was around back then and I didn't feel the need to act like a drug addict whenever Steve Jobs opened his mouth.

Were you a kid then too? :)

Lighten up. He was a kid and he knows how silly that was.

It's sick even if it was a kid. Being so brand washed should trigger a parent intervention.

OTOH, client Windows is the smallest and least important building block in it. Microsoft is helpfully also setting all their native apps on fire too and replacing them with webslop that runs equally poorly on MacOS, ChromeOS and Linux as it does on Windows 11, so the biggest concern is (A)AD integration and centralized management… and all three are decently manageable these days. If Microsoft didn't throw in the Windows licenses for free, more orgs would already be looking at ditching Windows 11, and if it keeps getting worse, even that won't look like a good deal any more.

> Maybe what bothers you is that you have a branch for tags, yeah, that's an extra level of indirection, but this lets you separate between user facing information in the master branch commits and developer facing information in the release branches commits.

That's such a marginal niche use case to build your entire organization around… why would you make this the default approach?

The standard is, for better or worse, gettext; it's good enough that any attempt to replace it runs into the problem that people can't agree on how much better an alternative needs to be to be worth migrating to; so you get a constant churn that so far hasn't seen any clear winner.

Depends on a lot of factors. LEO has high drag, but good radiation shielding, so if you've got a low enough orbit you can use most embedded hardware but need to compensate with bigger thrusters and bigger fuel tanks if you want it to survive "any length of time" without burning up from atmospheric drag.