It's not that there are breaking changes, but that breaking changes were introduced in a patch release.
Re:Htmx 2.0.4 Released
by intalentive on Saturday December 14, 2024 @12:41AM
(#42414920)
How is Python a disaster?
I'm not fine with breaking changes in a patch bump, otherwise it means versioning is useless
Re:Htmx 2.0.4 Released
by PhilippGille on Saturday December 14, 2024 @03:29AM
(#42415550)
In addition to what the siblings say, in case parent isn't aware of semantic versioning: https://semver.org/
Re:Htmx 2.0.4 Released
by sethammons on Saturday December 14, 2024 @05:43AM
(#42416154)
Backwards 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.
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.