• e0qdk@reddthat.com
    14·
    3 days ago

    I have some interest in trying to take that on if it’s really unmaintained now. I use mlmym and want to make sure we continue to have an interface that works w/o JS. I have relevant web programming experience, but not with Go specifically.

    @nnrx@lemmy.world FYI, if you’re still here.

      • Admiral Patrick@dubvee.orgEnglish
        272·
        4 days 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
          4·
          3 days 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.

        • rglullis@communick.news
          2·
          3 days ago

          Their justification is that pre v1.0, you can break whatever you want whenever you want.

          They are not wrong. If you are developing an application against a backend that clearly states “we are following semver. This version is not 1.0, therefore no API is guaranteed to be stable”, and you go on to write a client for it anyway, you don’t get to complain later when they make breaking changes.

          Alternatively, you can just stop relying on their ad-hoc APIs and push for them to implement Lemmy with focus on the ActivityPub API. That is already an standard and if you come up to them with issues against their AP implementation, they will be a lot more likely to listen to you.

        • seeigel@feddit.orgEnglish
          35·
          4 days 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.

            • wizardbeard@lemmy.dbzer0.comEnglish
              8·
              3 days ago

              I’m just a scripting monkey for a systems engineering/admin team, but I have one system integration that is being fireman carried by a ton of my code. I’ve since learned that there are entire consulting companies built off selling a slightly expanded version of what I’ve one man army’d together. Maybe I overestimate my skill, but I feel qualified to talk about large projects and long term sustainability.

              I’m convinced that people who talk about things like backwards compatibility as if it’s super difficult just aren’t willing to try. I won’t say shit like that is super easy, but it’s not black magic.

              I think there’s a lot of programmers out there more interested in building shit than ensuring any sort of quality, that it’ll be maintainable longer than the next code review, or in thinking about any downstream effects of their code beyond the limited scope they’re developing in. Stuff like backwards compat is largely just another design pattern in a sea of them that you learn through experience. But you have to try it to learn what works and what doesn’t. Go try folks.

  • IcyToes@sh.itjust.works
    86·
    4 days ago

    Playing devils advocate. Lemmy isn’t reddit and the only reason people used old reddit was because new reddit was unusable to them.

    As with new context and new front ends that Lemmy has, no one with the technical skills seems to care about this enough and blaming Lemmy Devs for not tiptoeing around unmaintained software so development grinds to a halt isn’t fair. It’s like saying “they don’t want to support it, and I don’t, but you shouldn’t spend your free time doing so”.

    • Blaze (he/him) @lemmy.dbzer0.comOP
      16·
      4 days ago

      Lemmy isn’t reddit and the only reason people used old reddit was because new reddit was unusable to them.

      The comment in the OP shows that at least one person cares.

      Mlmym also has the “show images” button that the default Web UI doesn’t

      no one with the technical skills seems to care about this enough

      That’s what this post is trying to solve

      blaming Lemmy Devs for not tiptoeing around unmaintained software so development grinds to a halt isn’t fair.

      I’m not blaming the Lemmy devs (I should rephrase if the post comes as such), the goal of this post was mainly to find someone interested in keeping mlmym up-to-date, not to blame anyone

    • tigeruppercut@lemmy.zip
      12·
      3 days ago

      New lemmy isn’t nearly as bad as new reddit, but I still prefer old because it’s more compact. The formatting on new vs old displays 7 vs 12 posts on one screen, which feels like a lot of wasted space. I know, first world problems and all that

    • magnetosphere@fedia.io
      5·
      3 days ago

      Lemmy isn’t reddit and the only reason people used old reddit was because new reddit was unusable to them.

      If “because new reddit was unusable to them” is a polite way of saying “because new reddit is a bloated, buggy, and worthless coding disaster” then I agree completely.