Thread 105984567 - /g/ [Archived: 811 hours ago]

Anonymous
7/22/2025, 6:04:59 AM No.105984567
e8vtww90rzi91
e8vtww90rzi91
md5: 8f69b7f9fb347c725e316c59e361c1da🔍
Do you think it's worth using bleeding edge distros instead of having a sheltering system that decides what goes in or not with proper screening? Or is it futile anyway and any distro gives up to the pressure of using the latest packages? How would you describe the bleeding edge, and how would you describe stability? Which one do you prefer?
Replies: >>105984592 >>105985006
Anonymous
7/22/2025, 6:10:28 AM No.105984592
>>105984567 (OP)
my work machine is airgapped. so once i zero in on a work environment i lock it in.
i make a disk image and never touch it again

my internet facing machine ought to be up to date bc security and shit
never use bleeding edge because thats experimental versions unless they contain a feature you desperately need
thats using loonix 101
sage
7/22/2025, 7:13:57 AM No.105984815
Kind of depends. Bleeding edge distros sometimes have issues with packages.
Also if you need anything from big corporations like amd rocm or you need to build something, the supported system is usually pretty old.

But stable systems have issues too if you need some unkown project from github because those people usually use some bleeding edge distro.

I use debian stable and run anything that doesn't work in it in chroot / docker.
You might also want to have some newer distro like the latest ubuntu lts for dual boot.
Anonymous
7/22/2025, 8:00:52 AM No.105985006
>>105984567 (OP)
I prefer working on a stable fixed lts distro (debian/devuan, alma/rocky, slackware/salix, etc...), and setting up a chrooted environment (debootstrap, podman, etc...,) with more bleeding edge libs if i need to.
Anonymous
7/22/2025, 2:49:23 PM No.105987179
if you've got a reasonable amount of time to get dirty and "debug" stuff then sure. otherwise stick to a stable release and spend your free time on something else instead.