3 ms·
Instead of fixing old problems that the entire community agrees with wild consensus, they insist on spending time creating new problems. Perhaps we should stop
by kristopolous 6y ago
Instead of fixing old problems that the entire community agrees with wild consensus, they insist on spending time creating new problems.
Perhaps we should stop whining and start fixing them. And then if the developers refuse to accept things people have been wanting for well over a decade then we can fork it and simply abandon them like any other archaic unusable thing of the past. We've all asked very politely long enough.
This is open source, we don't have to put up with this, that's the whole idea behind it. Closed source solutions from 23 years ago shouldn't still be running circles around the current stuff. We should all be embarrassed.
- wruza 6y agoYou can fork code, but neither a development, support nor maintenance process. The truth is that there is no fork, Neo.
- kristopolous 6y agoSo someone implements all the features that a massive number of people want, people use it, but then you think there will be no interest in maintaining it? Sorry, I don't buy that.
- selfhoster11 6y agoIf the fork is closer to the final result that most people want, it's a no-brainer that developers, maintainers and the community will follow. There's no incentive to stay behind. It's worth studying the case of OpenOffice.org and MySQL. Both of these weren't satisfactory to the community for <reasons>, so the community forked them and did all the high-demand feature implementation on the fork. Now the original projects that were forked from are near-ghost towns.
- akerro 6y agoLike Mint failed to fork Ubuntu? Or Ubuntu failed to fork Debian? Or LibreOffice failed to fork OpenOffice? MariaDB MySQL?