The Threadiverse is growing again, this time offering an effort to build a new Lemmy replacement from scratch, with API compatibility.

Seems like an interesting effort. A developer is building an alternative Java-based backend to Lemmy’s Rust-based one, with the goal of building in a handful of different features. The dev is looking at using this compatibility to migrate their instance over to the new platform, while allowing the community to use their apps of choice.

  • Melmi@lemmy.blahaj.zoneEnglish
    1·
    10 months ago

    It’s kind of ironic taking a project that’s already written in Rust and writing a replacement for it in Java.

    Usually things get ported to Rust, not the other way around.

        • 1984@lemmy.today
          1·
          10 months ago

          I mean, Java has faster developer speed since it’s much less complicated than Rust. But it will also use a lot more memory. That being said, I guess most of what happens in Lemmy is database queries anyway and that will go equally fast in Java.

          Rust is a very fast language but for a web app like Lemmy it’s probably not that important that it’s rust underneath.

          But I really dislike Java. Lots of issues with code only working on a specific JDK, and code being very ugly due to all classes and shit.

    • 0x1C3B00DA@kbin.social
      1·
      10 months ago

      That’s not applicable. Sublinks is using the same standard as Lemmy/kbin/mbin, i.e. ActivityPub. In a decentralized system based on an open standard, plurality of implementations is a good thing. We shouldn’t want lemmy to be the only one.

    • spaduf@slrpnk.net
      0·
      10 months ago

      This sentiment is so overplayed and seems especially out of place in the context of the fediverse.