

3·
7 days agoEven if we assume every patch to an existing bug is perfect and doesn’t cause other issues somewhere else.
This still only applies if the kernel stays static/not adding features or support for new hardware.
He/Him 🏳️🌈 🏴☠️
Linux Nerd [Artix BTW] and Gay Furry. Anti-Ai.


Even if we assume every patch to an existing bug is perfect and doesn’t cause other issues somewhere else.
This still only applies if the kernel stays static/not adding features or support for new hardware.
I REALLY don’t understand this part. Not requiring disclosure is one thing (that I already don’t approve of).
But out right stating you shouldn’t be open with users and contributors just goes against I want in an open-source project. It’s already got me looking into Sway.
I also feel a bit bitter since I literally donated money to a project I assumed wasn’t huffing the Ai Jenkem and I could keep using and recommending in good faith for the foreseeable future.
You apparently can limit programs memory cap using cgroups. I haven’t tried it however.
Wouldn’t be the first…or 5th time I’ve seen Minecraft max out ram.
Me and some friends managed to crash a guys 64Gig server rack because the modpack my friend made had a bad memory leak.