4 ms·
No the expectation is that users of projects stop assuming SemVer is followed by every projects. > pushing breaking changes at a yearly rate. That’s a horrible
by byroot 5y ago
No the expectation is that users of projects stop assuming SemVer is followed by every projects.
> pushing breaking changes at a yearly rate. That’s a horrible developer experience.
That's your opinion. I much prefer these bite sized yearly changes to much bigger changes over longer periods. e.g. Ruby with this strategy never had the big divide Python 3 had with its much larger change.
- astrowilson 5y agoYou may not believe this, but there are other ways of versioning software beyond breaking things every year and doing whatever Python 3 did.
- byroot 5y ago> You may not believe this You may not need to be confrontational... > there are other ways of versioning software I'm sure there is. But some features and other improvements sometimes require to deprecate and remove some older features. Each project will chose its own tradeoff between bringing the improvement faster vs keeping compatibility longer.