- cross-posted to:
- fediverse
- fediverse@kbin.social
- fediverse@lemmy.ml
- cross-posted to:
- fediverse
- fediverse@kbin.social
- fediverse@lemmy.ml
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.
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.
Any recent CS grad is obsessed with rust, trust me. It’s not hard to learn either with that background.
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.
Yeah, same boat. I’m continuously learning new shit with C# and I’m starting to understand Angular after all these years. I could switch back to Java with few issues.
I would love to learn Rust, but there’s no time right now.
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.
Once you know a few languages and the principles for how a computer works moving to a new one is easy. Don’t think of it as being a “Java developer”, but a programmer. It’s just a tool.
We did not learn languages at uni, but concepts. You use the same data structures and algorithms.
I think you’d be surprised, try picking up rust for some advent of code challenges. If you know Java Streams and C/C++ lower level programming all that you’re missing is some pattern matching.
I know Java and I am learning C#, I don’t feel like I can just send a few hours and be at the same level as I am with Java. There are a lot of things I do not know or understand yet with C#.
Anyone can quickly learn how to solve some code challenges in a new language.
It’s a completely different story to learn how to write long lived enterprise scale programs that can grow with multiple independent contributors. This takes a lifetime to learn. More people have more experience to do it with Java.
That feeling when you’re not a recent CS grad anymore 😭
I never even heard of rust when I graduated in 2016.
deleted by creator
If I were to guess, it’s not recent grads making those posts. I got the sense those comments were coming from people who had been around for a while. Folks who are now senior enough to be trapped in draining meetings all day, and have to manage a family a night.
The work day and home life can get longer and more exhausting the further the older you get.
Sure, twenty-five years ago, when Sun was pushing their language hard into colleges everywhere.
Now? Sun Microsystems doesn’t even exist, and everybody hates the JVM in an ecosystem where VMWare, Docker, and Kubernetes do the whole “virtual machine” model much better.
That was a long, long, long time ago.
Java has continued to be very popular after Oracle purchased Sun Microsystems.
Can’t say I agree. It feels like an almost even 50/50 split between Java and C# when I look at job postings.
I think rust is a very pragmatic choice, lemmy is decentralized, the security benefits are a necessity when it comes to self hosters donating hardware
Java is also memory safe
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.
Is that still a problem in newer java versions? I have to admit I have only written simple things in java.
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.
Wow. It’s amazing that anyone ever got anything to work in java. Must have never got used for anything
Ah yes, that explains the log4j fiasco
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
This is quite an outdated view I would say.
Perhaps, but a lot of devs wanted to contribute to a Java client, and that’s what they were saying.