5

anybody just love those oPeN sOuRcE libraries that COMPLETELY change their libraries syntax on a minor version change? like bro, do you even semver?

i've said it once and i'll say it again: open source will be the death of me

Comments
  • 5
    This has nothing to do with open source.
  • 0
    I have seen function calls change and perhaps some data structures between a 1.2 to 1.3 version. Bunch of stuff was deprecated. Annoying yes.

    What kinds of changes are we talking about?
  • 2
    then just buy a closed source library instead, where you won't get this problem for the sole reason of you _never_ buying an updated version of the library because money.
  • 1
    @tosensei I can tell you from experience that closed source libraries have the exact hame problem.
    Also, closed source doesn‘t mean it costs money. And open source doesn‘t mean it‘s free. It’s not related at all.
  • 0
    @Lensflare yeah, both are possible, but there _is_ a strong correllation.
  • 0
    In kotlin we got @Depracted to notify users about detraction if something
  • 1
    @rebokdev every language has something like @deprecated. That’s not the problem.
  • 0
    the quedtion is more about how much is depreated and why!
  • 0
    @max19931 every single function call... was horrible
  • 0
    @fullstackcircus by the way, what library exactly are we talking about, and what version jump?

    ...i wanna laugh at their incompetence
Add Comment