2 ms·
Seriously imagine the consequences of this "eat or be eaten" approach. What it incentivizes is not feature development per se, but fragmentation for the sake of
by tEem21 5d ago
Seriously imagine the consequences of this "eat or be eaten" approach. What it incentivizes is not feature development per se, but fragmentation for the sake of it. This in turn leads to less attentation toward maintaining the shared base of the fragmented forks, as it has been superseded with features X and Y in different, probably incompatible forks.
- wmf 5d agoMy point is that the original maintainer can defuse the forks by including the same features. That leaves users no reason to bother using the forks.
- j2kun 5d agoIt's a good point, and it also depends on the feature being good and sensible and in demand enough to push users away from the default. And then it incentivizes people to make good forks, like neovim vis-a-vis vim.