Sublinks Aims to Be a Drop-In Replacement for Lemmy - programming.dev
programming.dev
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.

Link to the thread: https://programming.dev/post/8969747

Hello everyone, I’ve followed this thread yesterday and noticed a few very negative reactions towards the choice of Java. I follow Java evolution from far away, but it seemed like it was evolving in a good direction since the last few years, and that performance-wise it would make sense for the back-end of a Lemmy-like platform.

Is it indeed the case? I was just curious to see that much negativity towards one of the most popular languages.

  • RonSijm@programming.dev
    9·
    11 months ago

    Now as for the “Java bad”, I’m kind of guilty of it too. I very much dislike how academia is obsessed with UML diagrams.

    I’m kind of guilty of that too - in mindset - I just don’t go around and shitpost about Java.

    My dislike for Java also came from academia, since I had to use it in school. Though my main problem was just the general tool chain of Java. Like we had to use Eclipse or NetBeans. And then we had to write stuff in “JavaBeans” When instead of a normal “Person” class, you’d have to have a “PersonBean” and everything was so weird. And all the packages and references would constantly break or be missing, both in the project and even in the IDE itself…

    After moving to C# and using Visual Studio, NetBeans just feels like you’re trying to build a house with a rock instead of hammer, on an already crooked foundation.

    Though that was a long time ago. I assume things have improved. But I never really had any reason to go back to Java

    • asyncrosaurus@programming.dev
      51·
      11 months ago

      C# will definitely spoil Java for you. Even modern Java, there’s just no going back from the .Net ecosystem without feeling like you’re timetraveling 10 years.