Well, to be honest, I've been daily driving alpinelinux for quite a while, first on an x86 desktop and nowadays on my apple silicon macbook.
In my experience alpine is a good fit from anything between an OCI container all the way up to a full fledged desktop or your server. But that's not all, you can have it running on your rpi or even your smartphone as architectures like arm are really a first-class citizen something relatively uncommon even with popular distros like arch which has only a fraction of its packages available for different architectures.
Alpine may come pretty bare-bones by default but don't let that fool you, its more than capable for at least anything a regular distro is if you know what to do with it. Even if you're a casual linux user you can get it setup in no time by using the setup-* commands that it ships with eg setup-desktop which takes care of setting up a desktop environment without you having to worry about dbus,seatd,compositors or things like that. Also their repositories are filled with almost any package someone would need and can always be coupled with complementary package managers like nix and flatpak in cases where apk isn't enough.
I love alpine and the aforementioned causes do justice a fraction of reasons, especially when considering things like running on a much leaner and modern c runtime musl instead of glibc, being systemd free and having a minimal dep, bare-bones/ bloat-free philosophy as it was originally intended for use on constrained embedded devices like routers. Its one of, if not the best distros available in my opinion, amongst nixos and gentoo which I deeply respect as well. That being said, one has to factor in the drawbacks some of these features like systemd-free and musl imply when assessing combatibility but I'm having trouble remembering cases where I've ran into deadlocks even on exotic setups like alpine on aarch64 architecture running natively on a M1 macbook with a custom kernel like asahi-linux or a sdm845 oneplus 6T smartphone with pmOS.
In my experience alpine is a good fit from anything between an OCI container all the way up to a full fledged desktop or your server. But that's not all, you can have it running on your rpi or even your smartphone as architectures like arm are really a first-class citizen something relatively uncommon even with popular distros like arch which has only a fraction of its packages available for different architectures.
Alpine may come pretty bare-bones by default but don't let that fool you, its more than capable for at least anything a regular distro is if you know what to do with it. Even if you're a casual linux user you can get it setup in no time by using the setup-* commands that it ships with eg setup-desktop which takes care of setting up a desktop environment without you having to worry about dbus,seatd,compositors or things like that. Also their repositories are filled with almost any package someone would need and can always be coupled with complementary package managers like nix and flatpak in cases where apk isn't enough.
I love alpine and the aforementioned causes do justice a fraction of reasons, especially when considering things like running on a much leaner and modern c runtime musl instead of glibc, being systemd free and having a minimal dep, bare-bones/ bloat-free philosophy as it was originally intended for use on constrained embedded devices like routers. Its one of, if not the best distros available in my opinion, amongst nixos and gentoo which I deeply respect as well. That being said, one has to factor in the drawbacks some of these features like systemd-free and musl imply when assessing combatibility but I'm having trouble remembering cases where I've ran into deadlocks even on exotic setups like alpine on aarch64 architecture running natively on a M1 macbook with a custom kernel like asahi-linux or a sdm845 oneplus 6T smartphone with pmOS.