creshal

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.

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

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.

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

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.

apt-mark manual has allowed the same functionality in apt since forever and probably inspired apk's copy of it :)

They're unsure because a lot depends on the legal status of children born to non-citizen parents in the US after a executive order tried to revoke birthright citizenship: https://www.bmj.com/content/390/bmj.r1538

If that EO was legal, then sharing the data is, too. If it wasn't, then it's probably a privacy violation, but the CMS isn't allowed to make that call themselves, they have to rely on court decisions for it. And challenging EOs is not trivial.

Since they're operating in Europe it's trivial to split manufacturing into 3+ places that are within an hour drive but also in 3+ distinct jurisdictions that are part of the same free trade zone, so no tax authority can have a full picture either. And you'll never get, say, French and German tax authorities to voluntarily talk to each other.

No, it's a generic android keyboard and works with all apps. But you need a keyboard like it (arrow keys, ctrl, etc.) for termux to not be a total PITA to use.

(Android has full physical keyboard support, so with it you can use Ctrl+A/Ctrl+X/Ctrl+V in all input fields. Usually a lot faster than fumbling with the touch equivalents that keep randomly bugging out…)

> People will say "small marketing websites are dead with SS or Wix about", but it's not true. Most small businesses just don't want to learn how!

Even if they want to, they have approximately 500 other problems to deal with that are more urgent.

Just figure out how you handle support after the initial project phase: It's a lot easier to get a small business to spend $1000 on a website than to get them to spend $100/year for the constant trickle of small changes they'll inevitable need later.

A few pharaos remain only known for being so poor architects that their hastily built temples needed renovations after only 2-3 generations.

> Just that what it means to be a good engineer has changed again.

And not even by much, 1/2/4 have always been signs of good engineers.

Openbox isn't limiting me, Wayland still has no advantages for what I do with desktops.

Eh, kinda. Work forces me to have Jira, Confluence, Gitlab, Copilot, the other Copilot formerly known as Outlook, the other other Copilot formerly known as Teams, as well as Slack of course, and a dozen other webslop apps open… and it still all fits in <8GB RAM.

Which is a lot worse than the <1GB you'd get with well-optimized native tools, but try running Win11 with "only" 8GB RAM.

Indeed. Much of a modern Linux desktop e.g. runs inside one of multiple not very well optimized JS engines: Gnome uses JS for various desktop interactions, and all major desktops run a different JS engine as a different user to evaluate polkit authorizations (so exactly zero RAM could be shared between those engines, even if they were identical, which they aren't), and then half your interactions with GUI tools happens inside browser engines, either directly in a browser, or indirectly with Electron. (And typically, each Electron tool bundles their own slightly different version of Electron, so even if they all run under the same user, each is fully independent.)

Or you can ignore all that nonsense and run openbox and native tools.

Wherever it they're finding people in charge of canteen menus.

Coffee was around in Ethiopia and Yemen before that, but it didn't really spread in the Muslim world before 1500, and didn't spread from there to Europe until even later.

And coffee didn't make the jump until around the same time, either. No wonder Europeans wanted to be anywhere on the planet except Europe.

It really depends on how you tackle gradual typing on a project level. The easiest way to sabotage is a "any new code must be fukly type checked" requirement, because it often means you also need to add type hints to any code you call, which leads to Optional[Union[Any]] nonsense if you let juniors (or coding assistants) go wild.

As always, no fancy new tech is a substitute for competent project management.

That'd be even more reason for them to have a solid PR plan prepared, to grind down opposition and gaslight everyone into giving up. Leaving all messaging about the issue to upset users is the worst way to handle it. Even just closing the issue would've been less damaging at this point.

HDD load times compared to......?

No. Please try reading more carefully.

Yeah, that's what I was trying to get at. Sony was extremely deceptive in how they marketed the PS5 to devs, and the Helldivers dev don't want to admit how completely they fell for it.

HD2 started as playstation exclusive, and was retargeted mid-development for simultaneous release.

So the PS5's SSD architecture was what developers were familiar with when they tried to figure out what changes would be needed to make the game work on PC.