It’s a draft spec.
6 is probably finalised and being implemented.
7 is probably late stage finalisation.
So 8 can be started to be drafted.

If it doesn’t squidge like a folded ketchup packet under a toilet seat, it’s not doing shit.
You want it dripping to the case to couple the cases thermal mass. Leaking out of the case and onto the floor is better than liquid nitrogen.

Or, the bill fails.
But all of its objectives get packaged attached to other bills that are actually required to be passed.
So you get some random bill about the shape of car exhausts which suddenly requires OS providers to verify users ages

Venlafaxine (SNRI).
Took a couple weeks to settle into side effects, and about half a year to dial up the dosage (with side effects being a few days to a week after dosage changes).

But it was pretty immediate. I think a big part was the act of treating it, the act of getting help.
Had a lot of ups & downs, took a while to “trust” it, to recognise it working. And building the habit of taking meds helped maintain a schedule.

Well, no. But then it gets rejected, and further PRs that also fail the check will likely get you banned from contributing.

The human is responsible.
If the code or PR fails, the human has to own that.
If the human fails to own that, the human gets banned

As a non-american, the speed with which trump has dismantled international relations and the lethargic (even non-existant) reaction of the “checks and balances” that should prevent such things says to me:
If America has done it once, America can do it again.
It can spend 30-50 years building strong relationships, or it can devastated them in 1-2 years.
Seems better to work without America, and let America do it’s own thing.
If America wants to join in, fine. But it’s gonna be on the world’s terms, not Americas.

Yeh, AI as an assistant/tool. Not as a replacement

2026 Debian Vs 2001 windows?
Or 2001 Debian Vs 2001 windows?

Cause 2001 Debian 2.2 was like 4MB ram, maybe 16 if you are really going for it!
https://groups.csail.mit.edu/mac/projects/omnibook/boot-floppies/current/doc/ch-hardware-req.en.html

So yeh, let’s continue comparing apples and oranges.
FreeRTOS is bloatware cause we were able to orbit a sphere that could reflect radio waves with a bunch of tubes and a handful of germanium.

What the fuck is this “windows xp Vs modern Debian” shit?

That poor insomniac dyslexic atheist that stayed up all night wondering if there was a dog

Yeh, JSON will compress well.

This is already possible using an autounattend file.
https://schneegans.de/windows/unattend-generator/ is fantastic.
Use Microsoft’s Media Creation Tool to create a windows installer USB, add the XML file to the root of the USB disk, reinstall windows exactly how you want it.

(If you are feeling fancy, download the windows iso, and repack it with the autounattend.xml file in it, then drop it onto a Ventoy USB stick)

That’s not a big financial incentive.
Microsoft will remove stuff when it actually gets in the way.
If it’s easier to leave in and not have to touch dozens of other programs/services then they will.
They might mark it as depreciating, and start planning a suitable replacement. They might just mark it as depreciating and kick the can down the road.
When enough services that relied on that depreciating thing have been touched due to other updates, then they might look at actioning the depreciation.

But if it doesn’t actively break the thing they are currently working on, the cost overhead or ripping it out is insane.
There might be other dev teams working on features that now rely/leverage the thing marked as depreciating. But the thing getting marked as depreciating happened towards the end of the other teams new feature development cycle. At which point actually depreciating the thing might invalidate that other teams entire project.
And maybe the rip it out, and it turns out one of their large clients (or a large amount of the user base) was relying on it.

Addressing technical debt is always hard to justify, but it always makes a better project.
If management doesn’t care about a better project, they will prioritise features and things that make money

But maybe they have the lowest crash rate?
So like, crashes cost money right? Someone is responsible. Someone has to pay.
But if everyone dies in an inferno, then nobody is responsible. Who can pay? They’re all dead! What medical bills? What repairs? It’s all a write off.
Sounds like a high mortality rate with low accident rate is an absolute profitable win! Free market baby!

Mumble is fantastic.
I designed and implemented a very complex voice system for an old guild. Like 100 people, 8 groups of 15, group leader’s private chat, priority speech all that. It worked so well, and never failed.
This was many many years ago, to be fair.
I wish it’s positional audio was more supported.

When ctrl+v is disabled to “prevent brute force bots” or something ridiculous

Yeh, I have passkeys in bitwarden.
I get it. Once they become ubiquitous, you click “login” your password manager prompts you to select account, and you are in.
No password that can be leaked, incorrectly stored, brute forced.
Corporations can pre-register company service passkeys for new users.
It’s like mTLS, except staged.

And then some kid buys a used raspberry pi or wipes an old computer and circumvents it all anyway.

So these “os reporting age bands” laws are useless then.
Cause either the parents are being responsible, at which point there are many parental tools for network and device control.
Or they aren’t being responsible, and the kid can easily bypass it or just buy their own device.

So that means that kids can’t buy computers?
Can’t buy a cheap used raspberry pi or old laptop/desktop in order to set up as a server?

It works out as O(regex^n)