Login or register your account to reply
Martijn Insane. Huge respect for Winer, but he seems to be arguing that library authors are not allowed to deprecate functions. And that is definitely not for the best. If you stick with SemVer it means you must increase the major version number for every API breaking change. And the minor version must only be increased if the changes are backwards-compatible. SemVer may very well be the best way any library creator can communicate breaks, and if you as library user pin to a specific major version nothing will break.
6y, 40w 1 reply
John Olinda On the other hand, it is a problem for users when companies or developers simply pull the rug out from under them. I think the best solution is to be very hesitant to add new features and to consider whether future users will latch onto something that you're not really interested in maintaining.
6y, 40w reply
Mark Dain I stopped updating software due to this; not so much removed features but new bugs that kept breaking stuff. Eventually I got so fed up I just turned off auto updating.
6y, 40w reply
👽 Lucian Marin I silently updated the SSL certificate on Sublevel so we won't experience any breakage.
6y, 40w reply