BURN

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.

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

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

I find that Java is overly Verbose, but it’s much better than the alternative of underly verbose.

Java really follows the single class for single functionality principle, so in theory it makes sense to have these located in different classes. It should probably be abstracted to a shared method, but it shouldn’t be in the same file.

At least to me this looks like simplicity, but I’ve been writing Java in some capacity since 2012.

It seems to be more language focused than hard to PR against the main repo.

Java is much more widely known than Rust, which means a much larger pool of developers. I never contributed to the original Lemmy server because I couldn’t wrap my head around a full production scale rust project. I’ll very likely contribute to this because I work with production Java code daily. Im sure I’m not the only other dev who has run into this.

Also maybe there’s just too many disagreements with the Lemmy owners, who are a bit extreme for a lot of people.

That’s why I like Java too. The fact that it’s so strict means I have to think about projects in a certain way and can’t just wing my way through it like Python.

Legacy Java software is a massive pain in the ass. No arguments there. I’ve been migrating an app from Java 11->17 for the last 2 months and it’s a versioning mess. So many libraries deprecated and removed that don’t have easy replacements.

It’s great because things don’t break when they’re running, but the problem is upgrading.

Version management does seem to have become better with the last couple versions

+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.

Have you ever worked with Apple SDKs? They’re kinda a mess. They’d still need a dedicated team to build, support and manage the app, and they clearly don’t feel it’s worth it.

It’s still 4-5 full time developers at least. Probably a full few teams also including marketing, legal and a few other departments.

Pilots and sports car owners too. Tbh I think pilots just like to go fast, on the air or on the ground

I’d guess it’s mostly just a low volume set of use cases. So few people are on iVision (my new name for this) that it doesn’t make sense to devote development time to it.

Same problem the windows phones had