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.

you are viewing a single comment's thread
view the rest of the comments

[–] Ghostalmedia@lemmy.world 55 points 10 months ago (23 children)

Java instead of Rust is going to be a big thing for a lot of people who would like to contribute in their spare time. Yeah, Rust is cool, but every CS grad and their mother knows Java.

Back during the migration surge a few months ago, you commonly saw a LOT of comments from folks saying they would love to help eat away at the project’s backlog, but they just didn’t have the time or energy to learn Rust at the moment.

[–] Amaltheamannen@lemmy.ml 34 points 10 months ago (9 children)

Any recent CS grad is obsessed with rust, trust me. It's not hard to learn either with that background.

[–] Undaunted@feddit.de 20 points 10 months ago (5 children)

I'm not saying that rewriting he backend is a good choice, but for me specifically, I'd like Lemmy to be written in Java. Why? I'm a Java software engineer for nearly 7 years now and I'd like to contribute. Yes, I could learn Rust, like I did learn Go, C, C++ and other languages during my cs studies. But I really don't have the free time and motivation to do that after I already worked 8-10 hours at my computer. If I could use my existing Java knowledge to quickly fix some small bugs or whatever, I'd love to do that. But the hurdle to learn a new language (including other paradigms and best practices) just to contribute to this one project is just too high for me.

[–] Spzi@lemm.ee 9 points 10 months ago

Exactly this. It's often about finding the right balance between technically optimal, and socially feasible (lacking the right phrase here).

The nerds brimming with technical expertise often neglect the second point.

Oh - wow! I was about to complain about how https://join-lemmy.org/ is a shining bad example in this regard, talking about server stuff right away and hiding how Lemmy actually looks until page 3, but apparently they changed that and improved it drastically. Cool, good job!

Anyways.

For collaborative projects especially, it is important to strike a balance between tech and social aspects. Making poor tech choices will put people off. But making your project less accessible will also result in less people joining. It's crucial to find a good balance here. For many coming from the tech side, this usually means making far more concessions to the social side than intuitively feels right.

load more comments (4 replies)

load more comments (7 replies)

load more comments (20 replies)