Akito is right about me. Dont know about ‘expert’… I would call it having lots of practice.
I will venture an opinion on Void. I cant compare with Arch, as I have never used Arch
My Void has never crashed in about 3 years. I do regular updates, as required for a rolling release distro
I actually have 3 Voids at the moment…my main one with Xfce, one with KDE which was quite an effort to setup, and one with the Lumina desktop which is an experiment.
I have only had one issue. It was with the xbps package system. The bluez package and a number of other related packages would not update. I got a swift answer by posting a bug report. All I needed to do was delete the package and reinstall it.
The Void Handbook/Manual is well written and covers most areas of installing and running Void. It is not as comprehensive as the Arch documentation.
You would have to learn the runit init system. That is the only choice of init system in Void. It is very simple… the learning curve is about half an hour… The Handbook covers it. You will need to understand runit, because when Void installs packages , it installs any daemons involved, but the package system does not start the daemon. You have to start it by hand or set it up,to start automatically on boot. Not complicated… it is only a one line command to start a daemon.
I dont know what happens in Arch, but in most distros when you install a package, it just works. Not so in Void, you have to start daemons by hand. So when you first boot a new Void installation, there will,be very few daemons running… You may need to start a daemon to get network cards running, for example. The install will setup the primary internet connection for you, but any others will require configuring and daemons.
The install itself is like BSD. It is different but easy enough to understand. Be carefil if you have more than one disk. It is possible to choose the rignt partition name for the root filesystem, and have it written on the wrong disk… because when the install starts what is sda and what is sdb seems to be random.
Void will quite happily share a disk with other distros in a multiboot scene. When you install is does not want to collar the whole disk. One of my Voids is the controlling distro for grub on one disk. I did that to see what it is like having the grub configuration in a rolling release distro. It has been OK so far, but I have only had it for 6 months.
Some people say that with a rolling release distro one should do a system backup before every upgrade. I dont do it that regularly. Void seems to be rather well managed in that respect.
If you have the disk space, when trying any new distro, it would be better to leave your current distro in place and do the new install in a new partition, and do a multiboot. Then , at least, if there is trouble, you have another linux to boot back to.
If you decide to do it and get stuck, there is help.