Learn More
Resend Email
18
LLAMS
8y

A word of advice to framework authors:
If I am currently using v2.5.5 of a library, and I update to 2.8.6, I would expect to maybe have to update a few deprecated method calls here and there.
I do not expect the entire API to be completely different, with half the classes totally renamed and restructured. Breaking changes should go into a new major version plz

undefined

updating libraries

pain in the ass
Favorite
Ranter
Comments
  • 1
    8y
    Weeeeell. Do they use the major minor patch system? If they don't, tough luck
  • 3
    8y
    So, in effect you're saying that every developer in the world today should switch their projects over to semantic versioning?

    For what it's worth, I'm a big supporter of semver, but it's not the answer to every type of software release, so it will never completely take over the world of versioning.
  • 5
    8y
    Breaking stuff with a minor version isn't the worst i've encountered, having breaking changes in a f-ing patch (Laravel and Lumen, sometimes they're not even mentioned in the release notes and/or upgrade guide (wtf), i've had to dig through the commit history on github to figure out why things were breaking).
  • 1
    8y
    After reading the last two comments, suddenly the history of jQuery releases springs to mind.. lol.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment