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.

    • Dessalines@lemmy.mlEnglish
      0·
      11 months ago

      After working in java for over a decade, I will never use another garbage-collected language if I can avoid it again. I still have nightmares about debugging memory build-ups and having to trace down where to do manual garbage collection. I remember my shop eventually just paid for 32 GB ram servers, and java filled those up too.

      Rust doesn’t have these problems because its not a garbage collected language like java or go, and has an ownership-based memory model that’s easy to work with.

        • Dessalines@lemmy.mlEnglish
          1·
          11 months ago

          Garbage collection is by nature imperfect, its impossible for it to always be correct about when and what things to free up in memory. The best option is to not use a garbage collected language.

      • kaffiene@lemmy.worldEnglish
        01·
        11 months ago

        That wasn’t a memory safety issue, that was a what the fuck were you thinking design issue. It would have been batshit in any language