So, 6 MUSL bugs for all of Gentoo?
And three of them are the same just for different versions of MUSL. And reading the bug report, it seems like a commit has been created and is awaiting review.
If all that is true, we have our answer. MUSL works with everything.
The default allocator is very slow but it can be changed. Chimera Linux, for example, uses mimalloc which is very fast.
My distro is based on MUSL. I seem to remember finding something that would not build on it but I do not recall what that is. In addition to the thousands of packages I am using, I have compiled hundreds of applications. Compatibility is very high.
Certainly it is clear the “most applications” work with MUSL.
That is, the source code does.
gcompat is when you want to run something that is already a binary that wants to call into Glibc. I try to avoid that so I cannot comment much.
There is the odd time I have had a binary built for Glibc that I could not avoid. For example, bootstrapping .NET or the version of vcpkg that the Ladybird browser uses in its build system. To be honest, in those cases, I just reach for Distrobox and drop into a distro that has Glibc natively, like Arch. Or I might use a RHEL Distrobox for a commercial binary meant to target that distro.
Clearly running a binary without one of the dependencies it was built against is a problem no matter what library you are taking about. But if we are just asking what works on MUSL, I would say almost everything.
I can almost guarantee that the problem you encountered was an outdated archlinux-keyring that meant you did not have the GPG keys to validate the packages you were trying to install. It is an annoying problem that happens way too often on Arch. Things are not actually screwed up but it really looks that way if you do not know what you are looking at. One line fix if you know what to do.
It was my biggest gripe when I used Arch. I did not run into it much as I updated often but it always struck me as a really major flaw.
Half of them probably will. People are like that.
Many times, I have seen people switch tech because something is missing or has changed…and they switch to something that also does not have it. Boggles my mind.
It could be that /dev/sdb2 really does not exist. Or it could be mapped to another name. It is more reliable to use UUiD as others have said.
What filesystem though? Another possibility is that the required kernel module is not being loaded and the drive cannot be mounted.
Nothing that uses apt is remotely bullet-proof. It has gotten better but it is hardly difficult to break.
pacman is hard to break. APK 3 is even harder. The new moss package manager is designed to be hard to break but time will tell. APK is the best at the moment IMHO. In my view, apt is one of the most fragile.
COSMiC has made Iced and Smithay stronger. Now Niri is based on Smithay. I for one are happy they spent their time on something other than GNOME.
GNOME has been shedding market share to KDE and now COSMIC is going to take a chunk of the rest.
Sour grapes.
Unbelievably ignorant take.
Arch and its forks are, in my view, the BEST options for a daily use desktop.
FreeBSD has made a real laptop push recently and 15.1 is supposed to offer KDE out of the box.
Depending on your hardware, it is really viable now.
Wayland has improved a lot in the last few years. And yes, there are and have been differences in hardware.
I think the biggest difference is likely to be software though. Primarily in two ways.
First, a lot of people are using older software. Not to pick on Debian but it is a good example. A Debian Stable user may be using NVIDIA drivers that are literally years older than what an Arch user is using. Paired with Wayland compositors and XDG portals that are older as well. So when they talk about Wayland (even today), they are really describing the experience from years ago. Alma Linux probably falls on this camp.
Second, what use cases are well supported on Wayland still varies from compositor to compositor. Somebody using Plasma 6 may experience that pretty much everything just works. Somebody using Sway may find that some uses cases are still immature.
Put these together and you have a lot of NVIDIA on Debian people telling you things don’t work and a lot of AMD on Fedora people wondering what they are talking about.
Today, Wayland and Xorg are more “different” than better or worse. If you are happy with Wayland, migrating to Xorg would probably feel like a real step back and there would be all kinds of issues and deficiencies. But, for some, the reverse can still be true. Wayland still has a few gaps.
Finally, they ARE different. Which means that if you insist on trying to make Wayland work exactly like X11, it is easy to make it seem like it is not working, even if Wayland can do exactly what you need in some slightly different way.
The important thing to acknowledge though is that more than half of Linux desktop users run Wayland now. And the majority of new users start in Wayland and will never switch. So X11 is the weird one now. And while Xorg is about as good as it is ever going to be, Wayland gets better every day.