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.
Why Java though ? Like really ? It’s… Better than any other compiled language ?
Because modern Java is an OK language with a great ecosystem to quickly build web backends. And there are lots of java devs which means more potential contributors.
Exactly. It’s also using Spring Boot, Hibernate, and Lombok. It looks just like projects at work. It might be the first fediverse project I contribute regularly to.
+1 same
I tried to contribute to Lemmy, spent a few hours really confused by rust and gave up. I can meaningfully contribute to a Java/Spring project, not a rust one.
Ah, yes. How about he kitchen sink and another 5000 dependencies to make Java bareable to code in? Actually lets skip Java cos it’s an over-engineered cluster-fuck that considers verbosity a virtue.
If you don’t want to contribute, don’t. Do you think being a hater is helpful?
It sooooooooothes my soul. 🙂
Hello world in Java = 500 lines of code.
Hello world in Rust = 3 lines of code.
Java is over-engineered corporate bullshit used by banks and Android development. Nobody programs Java for the fun of it.
Hello World is < 10 lines in Java. Just say you don’t know the language and go away.
Java runs the majority of corporate software out there, and it is very good at what it’s built for.
I’ll take Java over Python/Rust any day of the week
Removed by mod
And yet it’s still a better option than 90% of languages out there.
Trendy languages are great until they break something or lose support. Java is consistent, and that’s the most important part.
You sound like some Java dev personally offended you so much that you can’t separate the language from a person you hate for completely irrelevant reasons.
Like I said, I’ll take Java and extreme OOP over Python/Rust/Go any day of the week because it’s actually readable code instead of a clusterfuck of hundreds of methods in one file
The only reason you don’t like Rust is it’s the first language in a long time that’s threatened the dominance of C, the bedrock of programming. If it can do that then Java is going to be under threat too. Go failed cos it’s a shit language and Python isn’t even the same category. Java is more readable than Python? You’re having a laugh or you’ve never seen a friggin line of Python in your life.
Python:
for i in range(1, 10): print("Hello: ", i)Java:
import static java.lang.*; public class BentJavaClass { public static void main (String args[]) { for(int i=1;i<11;i++){ System.out.println("Java is shit: " + i); } } }10 lines vs 2. And you think Java is more readable?
Back in the day Java couldn’t even handle concatenating strings and numbers and needed you to fucking convert the integer into a string beforehand (
String.valueOf()). I see it only took you about 20 fucking years to figure out something most other languages had out of the box.What’s with all the unnecessary braces? The semicolons? Punctuation causes blindness and coldsores. Java is a cancer and it’s devs should be shot and their bodies piled high before being tipped into the sea.
Ok, so now build an api that can handle 100k iops with a cache, db calls and everything else, and tell me how simple that is in Python.
Java and Python, like any programming languages don’t do everything well. They do a few things well, and most things adequately. Python is great for scripting and small applications, but once you’re hundreds of files into a corporate software project it becomes near unreadable. Java is great for large scale applications but suffers if you want to make a single purpose app.
I’d also argue that yes, the Java is more readable at scale. Everything is explicitly typed, braces are so much better than indents (is something 20 indents or 21 idents deep, I never know), semicolons are useful for delineating ends of statements.
It sounds like your only expose was Java in uni and have never worked with anything at scale.
You don’t know because you’re a mongoloid who’s never heard of an IDE or a well configured text editor. Stop blaming your own inadequacies on tools and accept the fact you’re a shit dev.
Like I said - Python and Java are different categories so I agree they aren’t competing. But you do know Dropbox, Netflix and Reddit are built in Python don’t you?
However, Rust and Java are competing and that scares you. Because Rust has all the benefits of Java with none of the downsides. The only benefit Java has (like COBOL) is inertia. Even Google want rid of Java and it’s why they created Kotlin.
Java has reached it’s zenith and s in decline. It’s only a matter of time before tech debt and new concepts kill the language off and it goes the way of COBOL and Fortran.
Just accept it with grace and stop fighting the inevitable.
BS
Java devs are the reason humanity will never have FTL drives.
Oh right, that’s a much less moronic take. Well done genius
Probably because everyone knows it and its more predictable
Predictable in what sense?
If you say the function should only recieve one argument and returns always boolean. It is predictable to only allow the wanted args and forces you to return a boolean.
For example in a less predictable programming language e.g. Python: I can do all above but python does not stop anyone to put more or less arguments to a function, or a developer not adding typehints or not complying to them and return a string instead of a boolean.
But i had it wrong rust is similar to java on that part.
But still it is a lot more popular and easier to start with. So there will be a lot more contributor to sublinks than lemmy ever had.
Well in that sense Rust is even more predictable than Java. In Java you can always get back exception that bubbled up the stack. Rust function would in that case return Result that you need to handle somehow before getting the value.
That i dont understand? How can it be a result that i need to handle? If its not correct than java will throw an error. ( As expected, shit in shit out )
It’s a great and probably the best error system I’ve seen, instead of just throwing errors and having bulky try catch statements and such there’s just a result type.
Say you have a function that returns a boolean in which something could error, the function would return a Result<bool, Error> and that’s it. Calling the function you can choose to do anything you want with that possible Error, including ignoring it or logging or anything you could want.
It’s extremely simple.
If I except a boolean, there is an error and get a Result, is Result an object? How do I know if I get a bool or error?
You always get a Result. On that result you can call
result.unwrap()(give me the bool or crash) orresult.unwrap_or_default()(give me bool orfalseif there was error) or any other way you can think of. The point is that Rust won’t let you get value out of that Result until you somehow didn’t handle possible failure. If function does not return Result and returns just value directly, you (as a function caller) are guaranteed to always get a value, you can rely on there not being a failure that the function didn’t handle internally.Here’s some examples written on my phone:
match result { Ok(bool_name) => whatever, Err(error_type) => whatever, } if let Ok(bool_name) = result { whatever } if result.is_ok() { whatever } let whatever = result.unwrap_or_default(); let whatever = result?;And there’s many other awesome ways to use a Result including turning it into an Option or unwrapping it unsafely. I recommend you just search “Rust book” on your search engine and browse it. Here’s the docs to the Result enum.
It’s probably got the best library/tooling ecosystem of any language out there. Certainly dwarfs Rust in that regard. Easier to find devs. Reasonably efficient thou not as much as Rust and typically less memory efficient. It’s a perfectly good suggestion for a project like Lemmy. I’d reach for Java or Go before Rust for a project like this but you know, that’s just me.
You see, Go would’ve been a better option than Java.
It would have been a good option. As is Java. If you want to do it in Go, go ahead.