4 ms·
> Changing the default behavior feels like a breaking change I'm fine with breaking changes personally. An adherence to maintaining backward compatibility alwa
by hipadev23 2y ago
> Changing the default behavior feels like a breaking change
I'm fine with breaking changes personally. An adherence to maintaining backward compatibility always is what leads to bloat and criticisms of "poor design" from HNers in the future.
Keep it slim, have one way to do things, and avoid the disaster that is js and python today.
- Spivak 2y agoIt's not that there are breaking changes, but that breaking changes were introduced in a patch release.
- intalentive 2y agoHow is Python a disaster?
- deleted 2y ago[deleted]
- izietto 2y agoI'm not fine with breaking changes in a patch bump, otherwise it means versioning is useless
- PhilippGille 2y agoIn addition to what the siblings say, in case parent isn't aware of semantic versioning: https://semver.org/ https://semver.org/
- sethammons 2y agoBackwards compatibility is a mainstay in Go and I don't experience bloat, and, I believe, such goals are a hallmark of good api design. Source: over the last 20 years, built several and used many large code bases that have used for years and years that had different teams and individuals regularly committing into them.