This brings to mind the memcached extension for PHP that was broken for years because nobody tagged a release even though it had been fixed for years. Many distros effectively shipped “master” because that was the only way.
I've been trying to live with KDE 5 on Debian 11 and Fedora for about half a year. I don't know if the signatories had this in mind, but on both OSes the GUI experience is a sad, bug-ridden quagmire that would make a your stereotypical Windows Power User from the early 00s OS wars die of laughter. Just a different sampling of bugs on each.
I hope there exists a stable release of KDE and the OS vendors learn to ship it.
But maybe I'll just resurrect my .fvwmrc from the 1990s while I wait.
TBH i tried KDE every now and then. But FVWM does its job, has good docs and it's customizable. And last but not least, does not load half of your hard drive in memory.
This isn't new. Remember red hat 7's gcc 2.96, famous for subtly miscompiling a lot of projects.
RH's problem was they supported an architecture that was new and had no backend in gcc 2.95, so they downloaded whatever unstable snapshot was available that day, and called it gcc 2.96
8 comments
[ 2.1 ms ] story [ 27.8 ms ] threadFuck it ship it!
Done is better than perfect!
Better to light a candle than curse the darkness!
perfect is the enemy of good!
I hope there exists a stable release of KDE and the OS vendors learn to ship it.
But maybe I'll just resurrect my .fvwmrc from the 1990s while I wait.
RH's problem was they supported an architecture that was new and had no backend in gcc 2.95, so they downloaded whatever unstable snapshot was available that day, and called it gcc 2.96
https://gcc.gnu.org/legacy-ml/gcc-announce/2000/msg00003.htm...