Rather, we're seeing "the people in charge of all the procedures" (Govt employees, not airline employees) being grossly understaffed. It's a bit like "inbox zero"; you have a list of SOPs you want to observe, and you want absolute inbox-zero for completely every single procedure, to the letter, for something like flight control, spaceflight, etc.

If you cut staff, and still demand the same throughput, then the simple reality is balls are going to get dropped in the juggling - and at worst, if you refuse to accept that you don't have staff on hand to do it, and threaten to punish people who fail to keep up the same output with less staff, people are going to start lying about it.

And that - that, is the nightmare scenario. That creates what the Russians call "Vranyo": https://www.youtube.com/watch?v=Fz59GWeTIik

Thank god, this also hit the Russians incredibly bad, but yeah; people's perceptions of the production capacity of both countries is wildly, wildly overestimated.

The MIC basically had its budget slashed by ~80% or so after the cold war. Thousands of factories were permanently shuttered, hundreds of companies more or less ceased to exist - sometimes some of their engineers were aqui-hired by other firms, but by and large they just stopped working for the MIC in general.

https://www.youtube.com/watch?v=CqjvTKFufuk

This is what they called the "Peace Dividend"; when the Soviets collapsed, we no longer felt we needed a military that could repel a conventional assault from the Soviet Union (with all 700m citizens, and the heartland of industrial Europe (i.e. Germany, Poland, Czechia) backing them). We just, worst-case, needed to stop Russia and their 140m citizens.

They called it that because it unlocked a huge chunk of the budget that previously went to the MIC. A literal dividend of money.

I got to hear about how (name I won't doxx) was being told how he was gonna be okay when he was obviously bleeding to death from a gut wound that wouldn't stop. It's the kind of story you hear about soldiers in a warzone. 7 people got shot; he was the one who died before paramedics could stabilize him.

Mass shootings are barely newsworthy anymore. They plopped the usual couple of sentences about it, and didn't mention the political angle on it, probably for fear of death threats.

All these societal institutions, politicians, churches - everyone that's supposed to give a shit; they all just collectively shrugged. "So it goes", as Vonnegut would say.

-

It's that grotesquerie, that banality of people just pretending it's all social hysteria, or bothsides, or "it's not really happening" or any number of ways of just ... gaslighting it as not being real. That's what's so vile. It's a level of cowardice and dishonor I have no words for. At least own your deeds like actual men, don't weasel out of it like spineless worms.

In and among the nonsense there were a bunch of great promises, like pulling us out of China, getting massive infrastructure projects, resourcing a ton of our manufacturing from Mexico, maybe finally taking out the Ayatollah. Legitimately good shit!

So like; honestly if he was gonna do any of that, I'm game, man. We need it.

…

If I sit back and objectively look at it … he did a couple of tiny "token gestures", like saving a few hundred jobs at the Carrier plant, or whacking Soleimani. But for the most part … almost none of it got done, and not because of "Democratic obstruction", but because he just didn't even try. At all.

Really had me bummed, because damn if he wasn't -saying- all right stuff, but honestly I feel like I just got taken for a ride, you know? Like he said all that stuff just to get elected, and then just forgot about us.

Meanwhile Biden's doing: https://en.wikipedia.org/wiki/CHIPS_and_Science_Act

https://www.hhs.gov/about/news/2023/06/09/biden-administrati...

https://fortune.com/2023/04/17/biden-manufacturing-chips-com...

https://www.forbes.com/sites/alanohnsman/2023/12/08/watershe...

…

I don't care who delivers, but I do take note of who chose not to do so, and don't vote for them a second time. "Fool me once".

Needless to say it has batshit insane implications for memory bandwidth.

I've got an M1, and the load time for apps is absolutely fucking insane by comparison to my iMac; there's at least one AAA game whose loading time dropped from about 5 minutes on my quad-core intel, to 5 seconds on my mac studio.

There's just a shitload of text-processing and compiling going on any time a large game gets launched. It's been incredibly good for compiling C++ and Node apps, as well.

The "siren song" on those is the whole "if you're careful you can cancel" trick the users think they're pulling off. They may individually, but not in aggregate.

These cards are often much easier to get approved for.

It's like watching the stillborn OpenPandora or GP2x, and discovering that "devices bought almost exclusively to pirate SNES/SEGA games" have no devs writing games for their market because ... well ... you know ...

———

Woke: using OSS as a dev model because it's inherently more efficient/effective and leads to better software Broke: using OSS because "muh rights".

The app store is a condom (or a covid mask). It's not all about "you"; it doesn't matter a damned sight if YOU are careful, or if YOU are responsible. Other people can make god-awful decisions that screw you over, and you have no power to stop them. Or rather: the app store IS your power to stop them.

I can't count the number of times I've seen windows users get duped by phishing that gives a bad actor root access. If that's your family member, that's YOUR problem; it doesn't matter if you were super careful — if your 18 year old son fucks up because he just didn't realize he was getting hacked, well — you're liable. That's what regulations are about; just like the FDA, just everything else.

I like having a platform where there is no fear. Same reason I like vaccines, same reason I like food safety regulations, etc. It's about network effects.

———

The worst thing about all this stuff is: when tragedies like this happened back in the day (and I remember, clearly, friends having their drives get wiped by script kiddies) — you suffer in silence. You sob and cry about whatever happened to you, and try to "raise awareness" in the open-source community about how maybe we should do something better, and nobody listens.

A lot of this stuff in the OSS community reminds me of gun nuts and school shootings; people wring their hands when a personal tragedy happens, the solution is right in front of them should they dare to actually adopt it, but they refuse to adopt it because it's ideologically untenable. So they just pretend the problem never happened until it personally hits their own family — and the worst thing is watching their friends, around them, engage in the same denial.

The two "real consequences" are losing your data (drive wipes, randomware, etc), and financial fraud (someone getting your CC number or bank access). I personally know people who've been hit by this. It's heartwrenching when it happens.

Have the political will to adopt the solution.

---

The kind of programming people are agitating for in threads like these is emphatically NOT general-purpose programming. It's a very specific kind of proto-programming - being able to write direct inputs in exactly the kind of way you'd write software in the 1980s; a core example being the ability to write for a built-in BASIC interpreter, right on the commandline.

Plot twist: that shit's useless.

I grew up in that era, and that kind of programming is a toy. You can write gimmicky little things like outputting text in various colors, or at extraordinary expense, you can use these incredibly basic building-blocks to jerry-rig higher-level constructs to actually accomplish something meaningful.

It's an incredibly damning indictment that most of the successful pieces of software from that era started by bootstrapping their way out of having to do direct "dos/apple console" programming and wrote a high-level interpreter for something better so they didn't have to deal with that; every major title did something like its own virtual machine (c.f. lucasarts games), its own lisp interpreter, etc.

It doesn't teach you to program; it teaches you to bootstrap language interpreters — if you get incredibly lucky and figure that out on your own. The other "99% of space marines get attrited in training"; the other 99% of aspiring programmers from that era never figured that out, and gave up at the blinkenlights stage, without ever building an actual piece of software, or really getting their machine to actually do anything. I use that example to illustrate the absurdity: the WH40K trope is meant to be satire, because that level of attrition in any field is just a bafflingly wasteful way to elevate people to higher skillsets. Survivor bias may make heroes out of the tiny minority of people who actually made it (the Jordan Mechners of the world), but the cost in people who never "break through" isn't worth it.

I'd rather teach people to actually program. Teaching them to build the ingredients for programming (not the universal ingredients, but just the ingredients to enable it on one very particular kind of host medium) isn't it.

My regard to that "programming" era is: "rest in piss, you won't be missed".

Putin played the classic "tough on crime" authoritarian tack, except the crime wave was genuine, and huge. The routine street crime and killings were brought to a stop, and ... unfortunately he's been riding the popularity wave from that for at least 20 years. I mean — he didn't solve the high-level corruption of basically having a mafia class run things, which robs the average people of opportunity, but he did slam down on street crime, at least.

Credit for this is a bit misplaced, but it is a reason why he was unusually popular for quite a while.

In fact, the problem is chiefly that a certain group of assholes never upgrade their clients, ever, and disingenuously try to keep everyone on an old version of the protocol, because they don't see a need for new features. Period. I've been through this gauntlet with some long-running open-source projects, and basically these guys were like "plain text and command-line should be sufficient for everyone (and shame on you if it's not!)".

Of course, that's fine if you're a programmer, but then these guys were SHOCKED - shocked, I say, that people's whose primary working medium was images rather than text - you know, UI designers and artists - found it a struggle to work on their project and quickly gave up.

This kind of bigotry constantly stifles progress in the OSS community.

---

There's a damn good reason no federated service even comes remotely close to Discord, and it's because despite all of those features being developed for other clients, repeatedly, there is always heavy social pressure not to leave people out, so "newfangled" features get swatted down by communities, and people are forced to only use the features that everyone supports.

You can have IRC that supports pasting images just fine, but some asshole's client doesn't support it, so you're back to using a shithole solution like external pastebins or personal FTP servers, again. Otherwise you're dealing with a constant "I don't see anything! Why can't you just use something that works on my client!"

---

So no, "interoperability and open systems" doesn't mean all users can be happy. It's a trojan horse to let luddites force obsolete versions of the protocol on everyone because they don't want to update.

A lot of this stuff is UI-related; it's things that aren't a reskin, but they're a major shakeup of how the entire UI works, and would break all other clients using a framework.

The problem with "truly" federated protocols is that every design fuckup is preserved in amber for eternity.

Much of this was because real compression methods like zip simply weren't available during early decades of web development.

Obviously, if shrinking the code size is desirable, and you were building a library that did minification, you'd want to move on to also adding other, more dangerous changes that could change the meaning of the code, like removing unused CSS classes, doing DCE on javascript, etc, etc.

--

Since programming is a giant, decentralized soup of autodidacts, there's no "word of god" authority that can really say "this is the one true name of something". It's mostly just lingo that passes in and out of various communities, and a lot of times communities (as you're seeing in splintercell's comment) try to helpfully match themselves up and standardize so it doesn't degenerate into pure chaos.

I get pretty tilted when people complain about the banking system, because most of the "problems" they're complaining about are features. A really good metaphor is a programmer complaining about being forced to use a version control system, and wishing they could just dispense with all this pointless waste of time. "All this thing does is cause me trouble" — well, yeah, because you've never experienced the problems it utterly eradicated.

It's a Chesterton's fence issue at best. At worst, it's wolves repealing the laws that prohibit eating sheep.