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
    0·
    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
          0·
          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.

          • SorteKanin@feddit.dk
            0·
            10 months ago

            Java has faster developer speed since it’s much less complicated than Rust

            [citation needed]

            To give some context: Exception-based error handling is insanely complex. The error handling of Rust is much simpler to reason about. Finding out where errors happen is a lot simpler.

            The only Java dev I know is an older guy who started university with me at the same time - I was 20, he was 45. He knew Java, I didn’t. Java is not the future if you ask me.

    • somethingp@lemmy.world
      0·
      10 months ago

      Yeah this sounds like someone doesn’t know rust and instead of learning it they’re porting to Java? It might also be a way to capture an existing userbase as it’s still compatible with lemmy, but also adds features that might cause more people to use it. But being written in Java is an excuse to make it more difficult to migrate the additions back upstream to lemmy. Maybe they hope that this will eventually allow them to build out a private platform?