2 ms·
The only thing that would make this realistic is if open source developers prioritize backwards compatibility very highly. Of course, there will always be some
by jrochkind1 12y ago
The only thing that would make this realistic is if open source developers prioritize backwards compatibility very highly.
Of course, there will always be some bugs anyway. And it varies across language (or other open source affinity) communities. But in many communities, developers aren't really even _trying_ to ensure backwards compatibility.
If developers committed to backwards compatibiilty with successive versions for X number of years -- then you could update to the latest release for a number of years worrying less about breaking things, rather than needing to freeze the versions you use for that number of years.
Yes, this would significantly increase developer hours on open source projects. Nothing comes for free.
But wouldn't those developer hours be better spent centrally on ensuring backwards compatibility in the projects themselves; as opposed to every developer of every consumer of the project needing to deal with backwards incompatibility on every upgrade? Or every distro needing to backport patches? (This latter is more debatable, which is exactly why we have the status quo)