You're also missing the forest for the trees - if no-one maintained xscreensaver packages for distros, then there would be considerably fewer installs of it. Centralised package management is a very powerful feature, and without it, you're reduced to the Windows style of installing software: hunt around on the web for it, try and figure out if you're getting it from the official repo, try and figure out if the download is trustworthly, install it separately, hope it doesn't sideload malware, then maintain it personally as time goes on, and maybe even suffer every second tool having it's own self-updating service phoning home and nagging you (plus you may not even be able to easily uninstall the software if the author didn't offer that option). It's easy to do that for just one bit of software, but it's a real chore to do it for all your software.
Packaging is a difficult problem - the 80% use case is easy to solve, but the edge cases really require elegant forethought. It also seems that every distro has a different idea of what that 20% is...
> Really? Then what about this poor sap who had the misfortune of releasing one buggy minor version
Can't you do a minor do a minor version upgrade? Even the stable distros do updates all the time, just nothing major.
Ah, poor maintainer. Releasing software with a self-destruct timer is not an acceptable way to "tell people to upgrade".
If desktop packages like the XScreensaver is what makes your system unstable, then you have worse problems...
1. I use Arch Linux for my desktop and I like it.
2. I hate docker's repository systems (and other upstream packaging)
But this article writer sure is putting the maintainers on a pedestal.
More fundamentally, the maintainer is the primary line of defence and interaction between users and developers. Maintainers shield developers from uninformed users, allowing the devs to write software with less support overhead. Non-bugs are caught and filtered out. Low-quality bugs reported to the distribution's tracker often becomes a good bug when the maintainer reports it upstream.
...
Maintainers also shield users from developers, offering a layer of quality control...choosing a subset of the (subjectively) best software FOSS has to offer. Maintainers will disable features that they feel act in bad faith. Maintainers' greatest power is the ability to outright say "This is not good enough for our users"
Really? Then what about this poor sap who had the misfortune of releasing one buggy minor version, and is now forced to support that for the next 5 years even though the bug was fixed in the next version?
https://news.ycombinator.com/item?id=11452432
The maintainers actively tried to sabotage his attempts to tell people to upgrade to a new version in the name of 'consistency.'
Sure, consistency is great, but only if we (the maintainers) don't have to do any work (such as backporting). We offload all the supports to the developer and have him do support work for us. Then when he complains we will call him a whiner and laugh him off...