• Admiral Patrick@dubvee.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      2 months ago

      Yep, and that’s how we do API versioning at work. One app is on like API v9 now, and I think we support back to v5 or maybe even v4.

      Their justification is that pre v1.0, you can break whatever you want whenever you want. But when you’ve got a large community of people developing for the ecosystem over several years, it’s kind of a slap in the face to keep breaking the API. I appreciate that 0.19.0 - 0.19.11 has been fairly stable, but breaking v3 while also rolling out v4 is just inexcusable.

      I get that v3 will eventually need to be deprecated and apps move to v4, but you’d think they’d put all their breaking changes in v4, let v4 stabilize and run concurrently with v3, and then drop v3 a few versions down the line. Except a few paid apps, I don’t think most of us are doing this full time and have other things to deal with.

      But what do I know? It’s not like I do this for a living. Oh, wait…

      • can@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        In a comment one of the main devs mentioned worst case scenario that they could be supporting 0.19 for a long time so they’re trying not to rush 1.0.

      • seeigel@feddit.org
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        2 months ago

        It’s open source. If somebody wants to fix v3, they could submit patches.

        It’s unfortunate that v3 is stalling but nobody is paying the devs so they can prioritize however they see fit.

        I also think that right now developing missing features is more important than old APIs.