2 ms·
I think, in part, it’s because people want shiny tools and lots of new features but nobody wants their code to break when upgrading to a new version. Such is th
by elteto 3y ago
I think, in part, it’s because people want shiny tools and lots of new features but nobody wants their code to break when upgrading to a new version. Such is the duality of backwards compatibility. That leads to lots of churning with people working on scratching their own itches instead of “fixing” existing tools, because a lot of times that fixing implies breaking compatibility and upstream won’t merge the changes.
- throwaway894345 3y agoMoreover, whenever I’ve offered up a solution that scratches my itch, people complain that I should have focused on improving the current thing, but typically the maintainers of the current thing aren’t interested and have different priorities (probably very understandably!). When I can fix my problem by contributing upstream, I do so but it’s often prohibitively difficult.