Except it isn’t: https://en.wikipedia.org/wiki/Sugar_cube
Except it isn’t: https://en.wikipedia.org/wiki/Sugar_cube
That’s not how they became billionaires in the first place though. Being banned I mean.
Similarly, how the kilogram is the SI unit for weight, not the gram.
Everyone in metric zone fails as well to guess weights of a few grams :) best I can do is estimate 1/4 kilos


Also a good solution but you will end up in a container anyway once the requirements will become too old to be satisfied on a current OS.
That might be - but depending on the platform, that container is trivial or not necessary at all (e.g. wine on Linux still runs 16 bit executables with just a config file). Also, until then, I can continue to run the game without worry. E.g. Unreal Tournament 99 still worked out of the box (last I tested) on Debian 12 - haven’t tried it yet on Debian 13.


Why ? Any technical reason beside your dislike for containers, in this specific scenario ?
Because jailing a container is even harder than jailing an application. “But a container is already jailed” you’ll say - I don’t trust any jail that I can’t choose & configure myself.
If the publisher only give you the server binary (and all the dependencies) there is way to be sure that the next OS update does not break something, assuming you are able to run it in the first place.
The source code you say ? Fine, when the copyright end, after 70 years, they will release it in the public domain, until then… good luck, laws are on their side.
How about: document the requirements for the execution environment (in industry this is called an interface definition document), based on which the gaming community can then generate their own container configs if they like, but no one has to run stuff in a container.


I firmly disagree that this would be a good use case. Allowing this kind of container shenanigans would introduce more incompatibilities than it solves.


Pardon my French but would you please kindly fuck off with “container solutions”? Cheers.


idiots…


The rule should be “if you get caught using LLMs or caling them ‘AI’, you’re a dipshit and will never ever be let near the Kernel again.”


About fucking time.


I am pretty sure I borrowed it in the same way from someone else. Don’t think I am witty enough to have come up with that myself, but I don’t recall where I saw it.


Iran isn’t threatening the rest of the world though, and Magastan has killed several orders of magnitude more people on every continent. Including its own citizens.
Also, Magastan is directly responsible for the Iranian regime coming to power in the first place. So these atrocities committed are also blood on Magastan hands


Well - I mean - it’s a war. Fair game to self-defend against the aggressor.


please don’t link to Nazi platforms!


Haha. Great summary.


This just keeps happening with npm, from the news I’ve read. Almost like npm devs are not qualified to maintain code.


That sounds like written by some dumbass vibe-coder who actually believes their LLM is “smart”.
Human selfishness.