3 ms·
PulseAudio took ages to get to a stable and reliable state. There are still warts (try and make your machine act as a bluetooth audio receiver. It's horribly
by Twirrim 10y ago
PulseAudio took ages to get to a stable and reliable state. There are still warts (try and make your machine act as a bluetooth audio receiver. It's horribly ugly.)
systemd wasn't reliable or fit for purpose for servers when it got shoehorned in to everything.
When it comes to production servers you need stable and reliable. Not new and shiny. You're ideally rarely having anything happen on the server other than "run this software"
- digi_owl 10y agoSadly there are two definitions of server floating around these days. There is the classical "box in the corner sending and receiving data over the network". And then there is the new "bunch of software in a container in the cloud somewhere". And with the latter definition, stable and reliable seems to be of lesser importance in the eyes of the faithful. This because they can just fire off a new instance of the container if the existing one falls over (Uptime by machinegun as i like to think of it). http://www.commitstrip.com/en/2015/07/08/true-story-fixing-a-self-ddos/ http://www.commitstrip.com/en/2015/07/08/true-story-fixing-a...
- marcosdumay 10y agoOn either case, a fault means that at least one person will get a bad interaction with your service. And usually a few. On either case, respawning time and scalability are limited by data coherence needs.