41
I've used it as a daily driver for a few years now. Here are my thoughts on it:
Stability: Generally speaking, I've found it to be pretty rock solid for a rolling release distro. Over the years, it's only really broken a handful of times. Things that break tend to be the same as with any rolling release distro, e.g. pipewire came out which had no immediate impact on pulse, but over time more and more things started to require pipewire, so eventually forcing ones hand with switching.
Updates Being rolling release, everything is relatively up-to-date. The way they manage dependencies package updates with continuous integration is pretty clever and seems to help prevent things from breaking.
System Management Because of the decision to use runit, things are different from mainstream Linux distros. This isn't bad, just keep in mind you will need to learn to use a new set of tools to manage your system. There are some bits and pieces that bridge the gap, e.g. elogind means you get systemd type session management without needing all of systemd. For system logging, you will need to use socklog instead, which is a very different beast to systemd journal and classic syslogd. For everything else, the arch wiki is very useful for finding light weight utilities to help manage things.
Package availability There are definitely a plethora of options for packages. Because of how their package infrastructure works, it is rare that a package you want isn't available. And for those that aren't available, it's usually a small utility...one with an alternative that is available in the repository already.
User Contributions In void, there is no distinction between "official" and "user" contributed packages. Voids package infrastructure feels more like the AUR from the outset, but with github CI doing the heavy lifting of compiling the package for everyone once you've upstreamed package changes. The downside I've found is that the maintainers seem to be perpetually time/resource constrained. For any package changes that are moderately more complicated than "uprev package", "fix breakages" or "new package", I've found it a bit frustrating. A few years ago, I attempted to get some changes in for GHDL to enable backtraceing support, but after a few review comments, it just went silent on the maintainer side, so never got merged. After about a month of silence, github automatically closed the issue.
Documentation Their docs are pretty good for getting started. I've found them great for pointing out nuances and peculiarities of Void. It is definitely not as exhaustive and comprehensive as the arch wiki, but about 75-80% of the arch wiki is applicable across the board for all Linux distros anyway...