4 ms·
It doesn't matter what the common language is, if library developers enjoy breaking changes like they seem to, they'll make them. They'll just remove features,
by eternityforest 3y ago
It doesn't matter what the common language is, if library developers enjoy breaking changes like they seem to, they'll make them. They'll just remove features, change the way stuff works, or make trivial changes like renaming stuff...
Android has API levels where they don't do that, but that's because Google can afford to provide almost everything themselves.... random npm and pypi contributors don't seem interested in keeping compatibility.
So some kind of smart version system or container or something seems to be needed.
Although, I think in a perfect world our standard libraries would be rich enough that we would not need many libraries, and the ones we did need would mostly only be a few hundred lines at most, and we'd basically never have libraries depending on other libraries or any tangled webs like that.
- nerdponx 3y agoMaybe I'm just spoiled in Python, but library devs in the Python ecosystem seem highly disciplined in this respect. Packages tend to be forward-compatible for years, even with very active development cycles, and breaking changes tend to be treated carefully and announced with plenty of advance warning. That said, I don't understand this mentality that libraries can never change. Eventually things need to change. It's impossible to predict all future requirements.