Not mine, stole it.

It was just a pun, cuz Arch is popular, I use Void actually 😊.

Same 😊.

Alpine is an advanced user distro. I’m sure there are workarounds for the broken stuff.

Yes, you are correct, reliable is the term needed there 👍.

Yeah, but no glibc 🤷… some of us need it, and I can’t chroot all the time.

It’s so freaking stable, it’s boring 😂.

It’s more like Arch than Endeavour though, just a heads up. Very little GUI things, especially the installer and all that. Well, the installed is TUI, so It’s not that hard to be honest.

Rolling release and stable. And no systemd… not by choice though, they’re not purists, you just can’t build it for musl.

Yep, believe it or not, it’s probably the most stable rolling release distro out there. I’ve used it for the past 4, 5 years or so, not once has it broken.

There are 2 main reasons why this is. One, they don’t roll with bleeding edge, they opt for stable, so cutting edge is more like it. And two, they don’t have something like the AUR. There is only the main repo and that’s it. The approval process for new packages is quite strict and it has to fulfil a lot of requirements, among which the software has to not just build, but also run on i686, x86_64, ARMv5/6/7 and ARM64. And not just on glibc, but also on musl. So basically, all that, times 2. Sometimes it may take up to a year to get new packages approved by the maintainers, depending on how big the package is and how integrated in the system it is.

Yep, I use it as a desktop OS. Why is it baffling?

Oh, come on, I use Void too, it was just a play on Void 😁.

Stability as well. It’s probably the most stable rolling release distro out there.

I know, it was just play on Void 😊.

Nah, it’s just play 😊.

It’s better than Arch if you ask me, I use it on all my rigs.

They’re still waiting to be mainstreamed into the kernel. The process of integrating drivers into the kernel is complicated. Coding practices of the coder that wrote the driver play a large part in that. Buggy or badly written code will not get accepted. Not all of these drivers have the code quality that is required in order to be merged with the kernel.

What’s the deal with Nebraska? Are people from there like really polite and helpful?

Yeah, I know, that’s why the kernel with the drivers is not more than 150MB. Otherwise, you’d have the Windows situation where driverpacks compressed with 7z (LZMA2, solid archive, 273 word dictionary size and 2GB decompression memory, which requires about 128GB of RAM to compress) take about 30GB.

You have to pack the driver from each manufacturer because of signatures, even though they might even be the same with other drivers in the pack… but, REV differs and oh well, the driver installer doesn’t recognize that driver as a valid one for that device.

It’s mind boggling just thinking that things like this depend on the effort of one or two guys… while on the other hand, it’s not so uncommon that a team of engineers and developers fails to deliver a working (mostly) bugfree product.

I think management is who is responsible for the shitty decisions, as always… and, in general, just holding the team back.

Damn… now that’s a wholesome moment 🥹.