Hackaday

A counter-movement to Linux distribution fragmentation is emerging through 'distroless' initiatives like Project Bluefin's Distroless and KDE's switch to BuildStream. The distroless approach uses a common base (Freedesktop SDK) with customization layers applied on top, similar to how FreeBSD handles specialized variants. This could reduce duplicated effort and fragmentation, though it risks reigniting debates over standardization issues like package managers that previously challenged the Linux Standard Base.

The Distroless Linux Future May Be Coming

<blockquote>
FreeBSD ‘distros’ like GhostBSD and NomadBSD are therefore essentially just specialized customizations that target a sub-group of FreeBSD users.
</blockquote>
Soooo… like 75% of current Linux “distros” (or more… anyone’s got a more accurate number? be my guest to post it). The way things are, every distinguishable distro has its own philosophy and way of doing things, their own package manager, their own repositories, thier own developer community, their own favourite tooling. I don’t see people throwing all that work and all those developed habits to the bin.
Linux’s evolution (as an OS, not as a kernel) was always based on a certain level of chaos and distros one-upping each other in different areas (Debian - high stability and predictability, Ubuntu/Mint/Fedora - user friendliness, Arch/Fedora - software freshness, Gentoo/LFS - extreme customization, etc. - this is more of a historical perspective as I stopped distro-hopping a few years ago). I don’t see this going away, as this is what was driving Linux as an OS for years.

Standardization through convenience is fine. But let’s be careful about the language we use. Calling it ‘the distroless future’ doesn’t describe what’s happening, it prescribes it. And there’s a difference between ‘we built something useful’ and 'this is destiny.

looks like brainless future is coming

We are essentially circling back to the FreeBSD model of a separated base system and userland, just with more complex tooling to manage the layers. It’s a great leap forward for stability until you need to <code>strace</code> a process and realize you have to rebuild your entire OS image just to install the debugger.