Hacker News new | ask | show | jobs
by skrebbel 976 days ago
The issue is that releasing breaking changes sucks for your users. A numbering scheme doesn’t really make it suck any less.
2 comments

Breaking changes are fine (and a lot of times completely necessary) as long as they are expected _for what you're trying to do_.

The numbering scheme is meant to give predictability to breaking changes or backwards compatibility, so if followed correctly, it absolutely should make it suck less.

> A numbering scheme doesn’t really make it suck any less.

Yes it does, because that "numbering scheme" tells my users when and if breaking changes happen.

It also allows them to avoid them. Don't want to keep up with the dependency? Make the version a hard requirement. Done.