TwinkedIn

rose wrote: Wed Aug 27, 2025 5:56 pm

navi wrote: Wed Aug 27, 2025 5:55 pm

rose wrote: Wed Aug 27, 2025 5:34 pm Honestly yeah gentoo is probably my favourite distro in terms of versioning

Though I dont really see enterprise users using gentoo or alpine on their servers , in my opinion fedora would probably be the best and sanest choice there

fwiw blender studio's workstations and servers all run gentoo: https://studio.blender.org/tools/gentoo ... troduction

wtflip thats awesome .. there should be like enterprise support for gentoo so that more companies switch to it

chromeos is roleplaying as a gentoo distro:

https://www.chromium.org/chromium-os/packages/
https://www.chromium.org/chromium-os/bu ... -creation/

the same reasoning for both chromeos and blender studio, the fact you can customize the hell out of it and making arbitrary packages, even bumping overriding main ones is a big, big plus for very focused systems.

bleeding edge where you need to have a fix immediately (or backported,) while relying on stable versions everywhere else is pretty much needed in the real world.

ohh that reminds me of when ChromeOS flex was a new thing and I tried to get emerge working on it lol

but I mean, gentoo/portage as a distro build system makes a lot of sense, at work we use bitbake which is inspired by portage

lizzy wrote: Wed Aug 27, 2025 3:58 pm

i think it's this ideology that the less software changes, the more "stable" it is and hence the more outdated your software is the better - completely ignoring why software gets updates at all

debian also suffers from this to some degree

That is the reason it hates debinyan users! People being proud of how old and shitty their PRODUCTION environments are is simply disgusting.

i think it's largely like an enterprise/business thing (which makes sense for rocky). having your os be stable and rarely changing is a nice thing to have in those situations, so installing security updates or whatever don't break the application you're running on it, even if it does mean it's gets pretty old and crusty.

obviously for desktop usage this sucks ass and it doesn't make sense to do stuff like that there. but for servers i do see the appeal, especially if u have to run/maintain really old shit

the thing is that never changing isn't what makes something stable
a truly stable system would be able to update without completely dying, backported security patches are an awful coverup for an awful habit

rose wrote: Thu Aug 28, 2025 1:01 pm the thing is that never changing isn't what makes something stable
a truly stable system would be able to update without completely dying, backported security patches are an awful coverup for an awful habit

the problem here is a lot of software will silently break shit for no reason

yeah I mean stable updates on Linux are never going to be a thing lmao
truly everything loops back to Linux bad

A lot of FOSS software is made by hobbyist hackers who don't really care all that much for testing and quality assurance. Which is fine, because it's their choice what to do with their time.

When you look at FOSS projects that are developed professionally, such as Wine, Blender or OpenSUSE, you'll see that stability is less of an issue because they spend a lot of resources on QA.

of course, but projects like glibc not doing proper QA at times and doing random ABI changes that break everything can't really be excused with "its just hobbyists" imo

I agree, it's also a matter of attitude.

QA is for preventing breakage ahead of time, but even if you don't have QA you should still be treating regressions that break someone's use case as serious bugs to be fixed.