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?
Western "Democracies"
That poor insomniac dyslexic atheist that stayed up all night wondering if there was a dog
Yeh, JSON will compress well.
It's the "wall and make them pay for it" it's the "tarrifs and make them pay for it" now its "war and make them pay for it".
Yeh, but it's serverless! Where else do the private API keys go, other than in the web page?
\s
Thank you for reminding me I still haven't bought a new water bottle after I lost my last one!
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)
Surely you can't be serious!
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!
Well the point is that he should never have been the headline to start with.
And now all the sponsors have pulled out, because they don't want to be associated with a festival that is promoting a person like Kanye.