3 ms·
> A traditional FOSS project is not limited in this way. The developers often just start a new major version and overhaul everything. And regular users hate th
by oblio 5y ago
> A traditional FOSS project is not limited in this way. The developers often just start a new major version and overhaul everything.
And regular users hate this.
Jamie Zawinski describes this funnily, eloquently and also offensively:
https://www.jwz.org/doc/cadt.html https://www.jwz.org/doc/cadt.html
> This is, I think, the most common way for my bug reports to open source software projects to ever become closed. I report bugs; they go unread for a year, sometimes two; and then (surprise!) that module is rewritten from scratch -- and the new maintainer can't be bothered to check whether his new version has actually solved any of the known problems that existed in the previous version.
But he's right, and that's why:
* regular application developers who don't care about ideology
* and mass market users
hate desktop Linux.
- jasonjayr 5y ago(don't click links to jwz.org, he hates news.ycombinator.com, you have to copy/paste so the Referrer doesnt' reflect this site.)
- throwaway984393 5y agoOh sure, that's 100% true. Patches often are applied by packagers when the upstream won't apply it themselves. But there's a big difference between patches for bugs and poor design limping on because we can't change it because people depend on it. Users just want stable software. Developers want software that works better and solves more problems. The compromise is for users to stick with old major versions. At some point that's no longer tenable, but at least this way the software is free. Certainly no worse than when the same thing happens but you're paying for it.