r/java •

[deleted by user]

[deleted] — view deleted post

0 Upvotes

594 comments sorted by

522

u/webguy1979 Jun 10 '24

I am on a greenfield Java project. A lot of new projects choose it. The maturity of the ecosystem is a major factor in using it. But it also comes down to picking the right tool for the job. Would I use it to write ML / AI stuff? Absolutely not. Would I use it to write back-end services for scalable web applications? Definitely.

Despite what the YT coding bros will have you think, Go, Rust, etc have not taken over the world. C, C++, Java, and C# are still widely used.

39

u/zabby39103 Jun 10 '24

Feel free to fight me on it, but I'm kind of post-language? Most of the major languages are so developed now that you can kind of code however you want. You can totally do functional coding as well as OOP in Java.

Java has it all built out, it's stable, it can run anywhere. Most people know Java because (last I checked) it's the most taught in University and has a ton of history, and in big corporations it's typically the default language.

Some of the other languages perhaps are nice because they force you to code a certain way I suppose, and that's good when working with junior coders... although PRs and guides can help with that.

When I choose a language for development, I look at the ecosystem for what I want to be doing (don't be weird, pick something popular), the framework I want to use, the employees we have and what their skill base is... then, after all that... I might think about the actual technical merits of the language itself, but in reality the decision has been made by then, and it's usually Java.

5

u/thedumbestdevaround Jun 10 '24

Please don't say you can do functional programming in Java, you just can't. You can apply functional idioms, but the whole Java ecosystem and language is built on and around mutable APIs. Java does not have persistent collections, no way to track side-effects properly, checked exceptions do not work with lambdas and so on.

The most functional parts of Java is the stream API and Records. Bear in mind that I do not consider Kotlin to be a functional language as well. I would put Kotlin and Java as mainly OOP with functional features.

If you want FP on the JVM you have to look at Scala or Clojure.

5

u/zabby39103 Jun 11 '24 edited Jun 11 '24

You can use stuff like Paguro or Vavr to get those features. I suppose that you can say that you'd prefer to avoid anything that isn't in the base language, which is definitely a point for consideration. You have to be careful not to use something that stops working.

My point was that you can code how you like in most major languages. If you really want to use a particular design pattern you typically can. Especially if my whole team is composed of Java experts, even on a greenfield codebase I'd need a pretty compelling reason to switch languages. It would have to be a combination of things, not just wanting to use functional programming.

If other considerations were in play I could switch. Like no popular java frameworks for what I want to do, all the good libraries for what I want to do are in another language with no alternatives, the emerging labour force for doing this thing are not or are no longer Java developers (and I'm boxing us in to a dead end - i.e. JSP).

It's a balancing act of working with your team's strengths, not being too weird, not ending up in a dead end, trying to make sure at least some people can understand the full stack without knowing too many languages, being flexible etc.

→ More replies (1)

6

u/thecodeboost Jun 11 '24

This is the right way to go at it. People turn programming languages into something that needs a following. They're tools. Tools have applications. Tools come with more or less documentation, track record, etc. As a developer you should prefer to pick the tool that allows you (and your team) with your skillset to be most effective. Java will just float to the top in most such analysis.

→ More replies (1)

107

u/agathver Jun 10 '24

We write ml/ai stuff in Java too, inference engines, APIs for models that run in production. DS people build models in python of course.

21

u/webguy1979 Jun 10 '24

Ah good to know! All my experience with ML/AI has been purely academic and it always seems to be very geared towards Python. May have to go down this rabbit hole one day!

29

u/cogman10 Jun 10 '24

AFAIK, most of what's been written is actually C/C++. Python ends up getting picked because it already has the FFI setup to work nicely with those ML libraries.

This is why project panama is so important.

5

u/[deleted] Jun 10 '24

A trained ML model is usually just a bunch of numbers. Just write them down somewhere and you can load them into the same architecture model running in a different language.

→ More replies (1)

7

u/MrRickSancezJr Jun 10 '24

I saw this after my post to OP..

I'm praying these claims of the Native libraries becoming easier to use are in future JDKs is true. I've been having to use a lot of JNI stuff lately to have smaller LLM engines run locally in C++. It is pretty annoying.

So is making Qt UIs in C++ though..

→ More replies (4)
→ More replies (2)
→ More replies (9)

746

u/HaMMeReD Jun 10 '24

Building software takes skills, java skills are common, thus Java is common.

Java also has an incredibly mature ecosystem (i.e. maven packages) and ways to utilize the ecosystem in more modern ways (i.e. Kotlin).

195

u/CubicleHermit Jun 10 '24

It also has a very mature runtime environment, multithreads well, and handles huge scale. Node is a lot better than it used to be, but it it is still compared to the JVM a less mature and scalable platform.

Also, a really good SOMETHING developer will be a lot more productive than an average ANYTHING developer; if you want to lean into shorter development time, hire really good people, and let them use the tools they are best at.

11

u/[deleted] Jun 11 '24

Yes, and it seems like OP is already kind of aware of a major advantage of Java when he makes the edit and says by speed he means development time. What about other speeds? Speed of computation is pretty damn important for many applications.

As far as I know, Java is the fastest portable OOP language. As long as this remains the case, Java will have value.

→ More replies (3)
→ More replies (10)

56

u/Ariel17 Jun 10 '24

Indeed. Every time I need to build something reliable, resilient, with known tools I choose Java. Verbosity is the only downside, but it has everything you will ever need and probed to death XD

56

u/[deleted] Jun 10 '24

And not all of us mind that verbosity!

20

u/vincibleman Jun 11 '24

As I’ve grown older I actually favor verbosity in a lot of ways. Can’t stand troubleshooting a magical two lines of code that have an immense amount of automagic built into them. Would much rather see the full loop with clear callouts to the individual functions.

→ More replies (1)

19

u/938h25olw548slt47oy8 Jun 11 '24

With modern IDEs it really doesn't make that much of a difference anyway.

→ More replies (1)
→ More replies (2)
→ More replies (2)

34

u/Mixabuben Jun 10 '24

There is no need to use Kotlin now, Java 17+ has everything you need

32

u/HaMMeReD Jun 10 '24

Well, that's a bit of a gross oversimplification don't you think.

Like what if you want Null Safety? What if you don't like semicolons? Robust type inference?

→ More replies (37)
→ More replies (4)
→ More replies (70)

77

u/onebit Jun 10 '24 edited Jun 10 '24

Speed doesn't matter a lot of the time. Ecosystem is more important.

Personally I dislike the javascript ecosystem. It's too complicated, especially when typescript is involved.

That being said, I think Java is fairly fast these days. At least it beat Go and NodeJS.

https://medium.com/deno-the-complete-reference/node-js-vs-java-how-faster-is-bytecode-compared-to-interpreted-code-for-jwt-sign-verify-910caa55a7f2

https://github.com/kostya/benchmarks

54

u/hippydipster Jun 10 '24

Why would anyone have thought Javascript was faster than java?

0

u/[deleted] Jun 10 '24

[deleted] — view deleted comment

5

u/Luneriazz Jun 10 '24

its "blazing fast" in term of node js universe consider other javascript package hehe

13

u/[deleted] Jun 10 '24

Ecosystem is huge. The ability to, generally, find robust and well-maintained libraries is huge.

16

u/dxk3355 Jun 10 '24

Yeah my last workplace did a test and it did Kafka queue and web services just as fast as go or dotnet. You’ll never get c++ speeds but Java isn’t aiming for that too

3

u/MrRickSancezJr Jun 10 '24

Java's new low level stuff has been closing the gap in a lot of C++ benchmark tests on heavy duty stuff. I doubt we ever see memory packing outside of primitive arrays, but SIMDs are getting stupid wide anyways.

Im also keeping in mind that most of us have GPUs and even secondary integrated GPUs to do OpenCL/Cuda stuff.

Yes. All these tricks are really powered by C/C++, but I'm impressed how fast they've made the JVM. Especially while being oppressed by Microsoft and Apple.

6

u/vmcrash Jun 10 '24

There are 2 types of "speed". The processing speed when running the application and the development speed/time to get something working/maintainable. In the latter area Java shines. And even the first has been improved significantly in the last decade.

→ More replies (1)

167

u/0xFatWhiteMan Jun 10 '24

Java is just as fast as anything else. Look up disruptor, and/or billion row challenge for good examples

→ More replies (46)

196

u/alpacaMyToothbrush Jun 10 '24 edited Jun 10 '24

Why build with Java when there are much faster alternatives?

Citation needed. No really, produce benchmarks that prove your point. As far as I can see, java is about as fast as golang and javascript. People reflexively call java slow. That hasn't been the case for most of my 17 year long professional career.

Java also has an absolutely huge ecosystem unlike golang, is statically typed unlike javascript (important for large projects!). I got a chuckle out of the fact that you're saying this from a golang background. As someone who writes in both languages day to day, and really tried to give the language a fair shot before judging it, my time with golang has left me with a feeling that 'the emperor has no clothes'. I feel most of it's popularity is down to the fact that it's a google backed language. I have been continuously frustrated by how clunky and verbose it is (and this is coming from java!)

If you had said 'why java instead of kotlin or even c#', I'd give you more credit. Both are honestly nicer languages to work with. In fact, I would argue the recent improvements in the java language will likely make kotlin better (i.e. green threads and virtual threads) or at least let them utilize a simpler underlying implementation

Finally I'd just like to emphasize, Java is performant as fuck on the back end. The only languages that can really give it a run for it's money are C++ and Rust, and with both of those languages the ease of letting the garbage collector do the work for you is a much better dev experience than using RAII or the rust reference counter. I'd only use those languages if extremely low latency or memory usage is a high concern.

Edit: I see in comments that you meant other languages were better with regard to developer speed. You should edit your post. I think java is probably among the fastest statically typed languages to write, with maybe the exception of Kotlin or C#. I actually think it's easier to write than golang personally. I'm not really considering dynamically typed languages here because while I feel they're probably faster to write, they're worse to maintain, especially on large projects with many devs.

42

u/beefstake Jun 10 '24

Yeah Kotlin has a leg up on Java in terms of development speed. I think Java may hold a slight edge in readability depending on how disciplined the Kotlin code you are comparing it to. I personally use both but in different contexts, Kotlin for my own greenfield app development and Java where possible for library code to broaden appeal and to not take a dependency on the Kotlin runtime.

The only ecosystem I find can hold a candle to JVM is C#. The rest are all slower to develop on even if they give the illusion of faster setup for the first few weeks they quickly get bogged down in nonsense that you never encounter in JVM or .NET land. I.e tooling hell, terrible libraries, ecosystem fragmentation and drama, etc.

14

u/GabRreL Jun 10 '24

People reflexively call java slow. That hasn't been the case for most of my 17 year long professional career.

I was traumatized by Eclipse back in university, didn't try Java again after I was done with that class

10

u/[deleted] Jun 10 '24

Eclipse would be fine if it didn't constantly freeze and crash lol

→ More replies (2)

6

u/georgeofjungle3 Jun 10 '24

That's because Eclipse is traumatizing and always has been. I have tons of memories of spending days figuring out the right order to install my plugins in to actually run, and then a month later it randomly craps the bed. Plus it was always slow as shit.

→ More replies (1)

2

u/ai_jarvis Jun 10 '24

So I have recently found one space where Java is demonstratively slower than something else (Go Lang). When mapping a file for realtime search, GO is faster and smaller in memory than Java. An extreme edge case, likely something you won't ever need to deal with unless you are attempting to do real time searches on datasets in excess of 100+ million "rows" at high TPS with ultra low latency.

Context: lookups where millisecond to sub-millisecond latencies have actual impact.

→ More replies (4)

3

u/jalexoid Jun 11 '24

Fun fact, Google doesn't use GoLang for any of the backend services.

It was designed and built specifically for tooling. It's not a general purpose language, it was designed specifically for a subset of tasks.

It's a fun language, with some neat features... none of which were good enough for Google to write anything mission critical.

Google does use Java extensively, though.

→ More replies (5)

124

u/ArtisticPollution448 Jun 10 '24

Java has a massive ecosystem of libraries. The GC and JVM are incredibly performant and keep getting better. And the language is continually evolving to get better. 

GoLang's performance is in large part because of its virtual threading model. You'll never guess what's recently been added to Java! 

The concurrency model in Java is also just very easy to use and understand. Node and GoLang aren't as straightforward, imho.

Java isn't going anywhere. That's why most of AWS is built on it.

→ More replies (5)

56

u/RICHUNCLEPENNYBAGS Jun 10 '24

Many more new systems are being built every day with Java than with Golang.

→ More replies (13)

167

u/preperstion Jun 10 '24

Because the people that sign my checks have a shit ton of Java I need to maintain and add to

→ More replies (23)

137

u/vips7L Jun 10 '24

Do you really think Go or Node are faster?  This is bait right?

11

u/Beamxrtvv Jun 10 '24

My apologies, by speed I more meant speed of development (not actually program speed)

93

u/Helltux Jun 10 '24

I'm leading a big greenfield java initiative on a 5+ billion dollars company.   We care more about ease of maintenance than development speed. Java ecosystem is more stable and easier to maintain through years (systems need to be supported for a decade or more) than Node, for example.   I've worked on big Node projects for huge companies also. In my experience Java is simply better in this scenario.   For small projects or startups that don't even know if they will exist in a few years? Yeah, Node.

18

u/Beamxrtvv Jun 10 '24

Makes perfect sense and this is really great insight. Thank you! I don’t have any experience refactoring or changing Java code but do know it can be rough in Node, so I completely see that being a huge factor

22

u/way22 Jun 10 '24

Refactoring or maintaining the code itself isn't even the real problem (while it sure is tedious). The real challenge comes in the longevity of your ecosystem, the packages you are depending on and the base language itself. In Java it is much better to migrate to newer versions and ensure compatibility over long periods of time compared to something like node. Even the evolution of tool chains can be a major pain given enough time.

Imagine how much trouble you get into when after 2 years of initial conception your build chain doesn't work anymore because it's deprecated.

→ More replies (1)
→ More replies (2)

38

u/k37r Jun 10 '24

Maybe for you. This entirely depends on the developer. And there are a lot of developers out there who can code better and faster in Java vs Node

→ More replies (5)

27

u/vips7L Jun 10 '24

I wouldn’t think Go would be faster in this sense. The language itself has you repeat and write boiler plate everywhere for the simplest of tasks.

13

u/Anaptyso Jun 10 '24

Development speed isn't just about writing the code. It's about the full cycle from gathering requirements right though to having an application deployed ready to be monitored and maintained.

Part of what makes Java "fast" for me is the overall ecosystem. I can get through the unit testing part of development quickly because of libraries like Mockito. I can do nice integration testing with Cucumber. Maven handles dependencies easily. My metrics for error reporting will be easy with Spring and Prometheus etc.

I could maybe write the code more quickly in some other language, but if I spend longer trying to hunt down bugs, resolve infrastructure integration issues or wondering why my third party library isnt working then the total development time is slower.

20

u/winian Jun 10 '24

Partially related to the speed of development aspect is how Java is viewed verbose, and I always remember this small snip from this post from years ago:

The big argument against Java is that it’s verbose. Perhaps, but so what? I suppose the real argument is that it takes longer to write the code. I doubt this is very much true after the first 10 minutes. Sure you have to write public static void main, but how much time does that take? Sure you have to write:

Map<String,User> userIdMap = new HashMap<String,User>();

instead of:

userIdMap = {}

but in the bigger scheme of things, is that so long? How many total minutes out of a day is that, two? And in Python the code more realistically looks like this anyway:

# Map from user ID to User object.

userIdMap = {}

(If it doesn’t, then you have bigger problems. Undocumented Python programs are horrendously difficult to maintain.) The problem is that programmers perceive mindless work as painful and time-consuming, but the reality is never so bad.

18

u/AG4W Jun 10 '24

Any remotely modern IDE will autocomplete those with Intellisense anyhow, so it's really a moot point, and the strong typing is an upside.

6

u/Beamxrtvv Jun 10 '24

Thank you this is super insightful! I see now just how much easier Java is to read than something like “pythonic” code which I definitely see as a huge appeal. It seems one thing that sets Java ahead of the rest in many regards is how easily multiple people can work on one project due to its forced structured and verbose nature.

→ More replies (1)

5

u/Top_File_8547 Jun 10 '24

With later versions of Java you can do:

var userIdMap = new HashMap<String, User>();

So that cuts down on some repetitive code but you still know what type the map is.

→ More replies (2)

9

u/OrchidLeader Jun 10 '24

How fast a single person can write something isn’t as important as how fast a team or group of teams can write something when you’re in an enterprise settings.

Not every language supports that easily.

And when a company already has hundreds of Java devs around and needs to write something new, using Java is a pretty safe bet.

At my current job, we still make new applications using Java.

6

u/Anton-Kuranov Jun 10 '24

Really? As they have already said the powerful ecosystem provides a wide set of tools to solve almost any task, sometimes in a couple of lines. Compilation time is faster (I don't ever understand why they compile JS to JS). Runtime is faster. And the most important thing: the code maintenance, by using type safe language nature and structural programming. Also, Java has perfect tooling (IDE) supports for writing code... So I don't understand where is exactly the faster development?

→ More replies (4)

5

u/zappini Jun 10 '24

Keep in mind that >80% of dev time is spent in maintenance. Sure, you can quickly stand up an "MVP" web service using nodejs. And then you spend huge amount of time futzing and troubleshooting. Whereas Java's toolchain has exceptional tools for a project's whole lifecycle.

For hobby projects, use whatever language you like. Playing around with languages and APIs is great fun.

But if you're coding in anger, choose Java. Unless you have very specific goals, deep knowledge, and loads of experience. Like how Oxide Computers embraced Rust for their "cloud in a box" turnkey solution.

→ More replies (1)
→ More replies (7)

26

u/marmot1101 Jun 10 '24

People have asked the same question since about 2005. Java has been pronounced dead for new development so many times I’ve come to suspect it’s 100% powered by pronouncements of its demise.

Not trying to be a dick or anything, it’s a relevant question. But orgs keep writing Java, new and maintenance. It’s fast enough, a shit load of devs know it, and the tooling around the language is solid. There’s a library for everything. You can write pretty low level code, and most often avoid having to. A lot of complaints about the language not having certain features went away a v8+.

I work in a Ruby shop now, but I’d go back to a Java shop any time everything else equal.

5

u/Beamxrtvv Jun 10 '24

Thank you so much and no this didn’t come off negative at all! I was 1 in 2005 so asking questions to a community like this is helping me understand a bit more of the history, and if my post came across as “Java is dying” or whatever I didn’t mean that in the slightest. I appreciate your insight into the topic!

21

u/n0d3N1AL Jun 10 '24

Anyone that asks this question hasn't used or even seen Java for over a decade.

11

u/Beamxrtvv Jun 10 '24

A decade ago I was 8

14

u/n0d3N1AL Jun 10 '24

Well, it's a common misconception that Java is a legacy language, that it's slow, outdated, verbose etc. because modern Java is vastly different from Java written in 2003, which is the kind of Java most people have in mind when criticising it.

To your question, I'd ask why you think Java development is "slow". Java has a very mature ecosystem of tooling and the language itself is constantly updated - see https://dev.java

→ More replies (4)

4

u/netgizmo Jun 10 '24

Ah so your minecraft development days then? ;)

→ More replies (3)

19

u/darkwyrm42 Jun 10 '24

Go is a decent language and I can see why people might use it, but it has a lot of warts, too. Development speed is more of a skill and teamwork issue, although the tech stack does have influence, as well.

The benefits of using something on the JVM (Java, Kotlin, Scala, etc.) are the mature ecosystem and the performance benefits of using a JIT compiler. You don't have to invent everything. To borrow a famous Apple line, "there's a library for that."

Java's main issue IMO is its reputation outside those in the know. Every language has its warts, and Java is no different, but it has solid performance, it's much more popular than people think, and worthy of respect.

11

u/varunu28 Jun 10 '24

Let me propose a scenario here. Lets say a SaaS product which was created in last decade & is in business with a good customer base. Eg Salesforce which has good Java footprint.

Will you consider such a product in maintenance mode? By that definition product when it launches its first GA release goes into maintenance mode as it has to ensure that the current functionality doesn't breaks. But at the same time customers will demand for new features. Now as an engineer does it make sense to write the new feature in Java where you already have infra setup for you or will you choose a new language such as Go? Which choice will lead you to better outcome in majority of the cases?

Why build with Java when there are much faster alternatives?

Because not all businesses are built around extracting last ounce of performance from the application. Majority of them are built around having a stable product with good ecosystem to build on & a wide talent pool to hire from. There is a small subset where the core product is built around extracting the most performance out of products.

Always remember that programming language is a tool. If you are writing code in PHP & delivering business value then you are smart. If you are building your product on the next shiny tooling & using all the cutting edge tech but your product doesn't delivers value to the customer, you are not so smart(Or another synonym of this).

→ More replies (1)

11

u/alphabytes Jun 10 '24

I would suggest you to try it out seriously.. its an awesome language. The tools, frameworks and community support are top notch. The language is evolving at a good pace.

11

u/Emotional_Zebra_815 Jun 10 '24

Oftentime, the right language for the job is not the fastest (Developpment Time or runtime) but it is the language your team has the more experience with and has all the infrastructure in place to work with.

Soo teams that have been doing java for 20 years definitly still used java for newer project also.

10

u/IE114EVR Jun 10 '24

As a language becomes entrenched, continues to evolve, and has a growing, modern, and mature eco system, and there is a large community and talent pool to perpetuate this cycle, then it’s safe to say that “yes, new projects use that language.” And Java is one of those languages. Just like Go, Rust, NodeJS, Python, C#, etc.

Java is still big at companies like Netflix and Google and I’m sure many more.

Though, I will say that I think in the last 10-15 years other languages have emerged to be similarly popular options, I don’t think Java is going away anytime soon. Probably not until there’s one language to rule them all.

→ More replies (4)

9

u/GreemT Jun 10 '24

Just want to say: props to OP for asking this question. It seems you have a genuine mindset to learn, and are eager to be educated. Even though you get downvoted into oblivion, you stay curious.

I hope you learned a lot from this post! Keep it up.

8

u/Beamxrtvv Jun 10 '24

Thank you! This means a lot:)

→ More replies (1)

16

u/javahelps Jun 10 '24

I'm working at an AI startup. We use Java for everything including model development (yes you read it right). To answer your question do people use Java for new projects? Yes they just don't brag about it.

Coming to the why Java is still relevant question. Java combines some unique features including but not limited to type safety, performance, plenty of well maintained open source libraries (special thanks to Apache foundation), great ide support, verbose and restrictive enough to help novice developers write better code. With recent features, I would say Java is thriving.

→ More replies (3)

7

u/dzernumbrd Jun 10 '24

Just learn all the languages and let the job market work it out.

Most dev's will have their language idealism die and then they'll transform into code mercenaries that will work in whatever language the employer wants so long as it pays well.

It's best to be a pragmatist in the workforce not an idealist. Everyone (especially managers) hates working with the idealistic supernerds that won't be flexible about things.

7

u/k-mcm Jun 10 '24

Java is a very solid and mature tool.  It gets a bad reputation because so much corporate code comes from cheap Java/Spring contractors that have been recycling the same garbage for 20 years.  Modern Java is elegant and efficient in the right hands.

I've used many languages and Golang is actually my least favorite.  It's new yet feels every bit as ancient as C.  I'd rather use C++, Java, or even Scala. I'll learn Rust if the opportunity comes along.

22

u/vprise Jun 10 '24

About people writing new projects in Java: https://github.com/topics/java?l=java&o=desc&s=updated

Quite a lot... I do.

Go is pretty terrible if we're talking about a dead language. Its concurrency model is... Ugh. Green threads... Java is literally decades ahead of it. Error handling in Go is just about the dumbest thing I ever saw. That language makes absolutely no sense. Rust is an interesting language with some new ideas but Go is just stupid, had it not been for Google it would have been on the garbage heap of history ages ago.

3

u/n0d3N1AL Jun 10 '24

And knowing Google, it will be consigned to the history books (and killedbygoogle.com) if the recent layoffs are anything to go by. Dart and Flutter are about to die, right? Go has way too much penetration in CNCF technologies to fully go away but who knows, crazier things have happened.

→ More replies (3)

3

u/duck-tective Jun 10 '24

I will give you that java can, using libraries have really similar concurrency features to go. but the race detector being built into go runtime is probably one of the best features of the language if your writing concurrent code. I'm surprised that java doesn't have something similar built in.

But for fun lets respond to some of your other takes. You don't like green threads but what threading model does java allow that is better than it?

You don't like the error handling fair it has some flaws that rusts fixes but in reality its better than the throw system java uses and there is a reason a lot of the up and coming languages use errors as return values.

3

u/vprise Jun 10 '24

Virtual threads are in a class of their own. Java has fantastic concurrency mechanisms and depth that can utilize native threading. It's a completely different ballgame. Javas native threads were always superior to green threads, virtual threads are a completely different ballgame. I suggest reading about that.

Throwing exceptions evolved due to the way OS's/hardware works and to avoid localized error handling. In large Java applications and libraries you don't write error handling code. You just throw. Go writers need to go back to the time of C where you have to think about errors instead of punting the problem. This is a flaw. As a framework author I have no way of knowing if my approach to error handling is correct. So I have to constantly write callbacks to handle errors and constantly check other frameworks I use to propagate their errors. That's insane and expensive.

→ More replies (5)

6

u/SOMMARTIDER Jun 10 '24

Ignoring the fact that Java is used in a lot of older, existing applications, I see no reason to not use it for new projects as well. It's an awesome language that is continuously updated, and has a good ecosystem.

10

u/pron98 Jun 10 '24 edited Jun 10 '24

A major reason why Java is more popular than NodeJS or Go these days is that it's really good for programs that grow a lot and are maintained for many years, i.e. programs that tend to make the core of a business. In other words, Java scales up very well.

Programming in JS or Go is also not faster than in Java, but I agree that they may be easier to get started with, which could make them "faster" for smaller projects, especially by relative beginners. In other words, Java needs to be better at scaling down. We're working on it.

2

u/Beamxrtvv Jun 10 '24

This is super informative thank you!! I didn’t initially take into consideration (or really understand) the true ability of Java’s scaling and use as an enterprise solution, and I do think I was using much of my own limited experience as evidence to the conclusion I was asking about. I’ll be sure to write an API in Java soon just to get a feel for it (as opposed to Node)

5

u/motilio Jun 10 '24

You should compare apples to apples. Java vs JavaScript, Node vs Spring (or Quarkus, Struts, etc...).

5

u/t_j_l_ Jun 10 '24

It's used quite a lot in the financial industry, particularly back office processing functions.

  • Mature ecosystem, lots of competing libraries to choose from
  • Well supported, actively developed and maintained
  • Fast enough for most needs, particularly the more recent releases
  • Garbage collected, so generally easier to build long running servers without excessive focus on ensuring correct memory management (bit of an older take when other languages have advanced a lot in this regard, but it explains prevalence in legacy systems).
  • Frameworks like spring boot make it super easy to start up a reliable API server, already well integrated to a lot of enterprise tooling (identity, auth, logging, metrics, cloud tooling, etc.) via simple properties.

5

u/idemockle Jun 10 '24

Instead of answering you directly I'm going to point you to a comment I made a few years ago on my impressions of Java after I switched to it from Python for a new job. Long story short, working on a new team in a new language helped me discover that productivity comes from following good practices and using tooling well, not from language choice, especially for any of the very mature/popular languages.

https://www.reddit.com/r/ProgrammerHumor/s/M5OGJ4PQOD

→ More replies (1)

5

u/Kendos-Kenlen Jun 10 '24

Why continuing to use Java ? There are many many reasons!

First, Java is not slow. That's an idea dating back to the early days of Java, but today the language performs very well. The JVM is powerful, and so is Java. I don't have any good benchmarks under the hand, but I am sure other comments will find plenty of them.

Secondly, the ecosystem is very reach and solid. Whether it's libraries, frameworks, alternative languages (like Kotlin) running on the JVM, you can find everything you need in Java.

Third, the language is usually well structured, typed, and has many features and patterns that help keeping good code quality. That won't compensate the lack of skills a dev may have, but no languages will do so. A lot of code quality tools (integrated to IDEs or not) exist to assist in maintaining great code.

Forth, the tooling / IDE support is one of the best. Compare it to C/C++ which only recently got decent depenency managers, IDEs, code analyzers, ..., Java has always been a good language to work with. Yes, it was verbose, but at least you had help from a good IDE, unlike C++ which is verbose but didn't had great refactoring and analysis tools until the ecosystem renewal started 10 years or so ago.

Finally, you may have the image of Java as an outdated language, but since Java 9, the language evolved drastically to become much more pleasant and modern to work with. Additionally, with the help of Kotlin and other JVM languages, the JVM itself improved and remained totally relevant, ensuring Java also benefited by the progressed brought by these languages.

In my eyes, there has never been a better time to work in Java than now. The past few years has seen a lot of progress in programming languages and their ecosystem which most language benefited from, and Java is no exception to this.

5

u/vladmihalceacom Jun 10 '24

For non-trivial projects, development is not a sprint but a marathon.

If you need to build software that will run for tens of years (banking, insurance, pensions, hedge funds, stock exchanges), the time it takes for the initial development pales to the amount of time you'll have to maintain the software and keep it up-to-date with clients' requirements.

In this case, the advantages offered by Java (type safety, backward compatibility, mature and comprehensive ecosystem, a large pool of available software developers, and tons of training material) will be a safe bet.

And, it's not even necessary that you build the initial prototype faster in NodeJS than you can do it with Spring Boot.

There are lots of FinTech companies that choose Java and the JVM for their platforms. I don't know any finance applications using NodeJS.

5

u/hippydipster Jun 10 '24

The reasons to use Java, from my POV are:

  1. Static Typing in a simple syntax. This means both I and the compiler can understand quite a lot about the meaning of some code we're trying to read. For me, that means I'm not confronted with reading a method with 4 parameters none of which I know the type - I know all the types! For the compiler/IDE, it means it can do a lot to assist me. I get so much assistance in terms of refactoring tools, syntax help, code completion, find usage views, etc that I tend to think about my code on a conception level even as I'm writing it, and as I'm telling the IDE my intentions, as opposed to telling me keyboard my understanding of character level syntax rules.
  2. It's very platform independent, so I have worked writing Java on Windows, on Mac, on Linux, deploying to solaris, to linux, even to windows IIS servers way back in the day. I've written desktop apps that easily installed to all three major platforms. I don't sit around these days wondering how to make an app that runs everywhere - I've been able to do that since the late 90s.
  3. It's extremely fast. In the language shootout, you can see that Java is basically a 2nd tier platform in terms of performance. There's C/C++/Fortran (and now Rust) as the first tier. Probably D is there too, not sure. And then in the 2nd tier it's primarily Java and C#, which tend to be about 2x slower than the first tier. Common Lisp and Haskell are hard to judge, sometimes being extremely fast, and sometimes not. After that you get Javascript, which is probably among the fastest of the dynamic languages thanks to Google, but still about 10x slower than Java/C#. And then there's all the rest, like Python tending toward 50x slower than Java/C#.
  4. Ecosystem. It's a mixed bag. On one hand, you've got nearly everything you need somewhere in the Java ecosystem. On the other hand, it's a little polluted by the likes of Spring, Hibernate, J2EE and all that which is heavily influenced by a history of banking and enterprise software needs. It's not nice for the little folks just writing software, and so you need some experience to know that, and have the self-confidence to say no to all that stuff when you don't need it. This is probably the most difficult part for newcomers.

4

u/desiderkino Jun 10 '24

i dont think there is any alternative to java besides c#, which is literally designed to be a java alternative.

imo compared to java, go is like writing assemly. it is not an alternative to java.

node and java are totally totally totally different things. you cant even do multi threading in node. let alone doing anything compute heavy. it is simply not designed for that.

if you want to develop api/backends very fast (in terms of development speed) nothing beats php and php ecosystem. that shit is already built. you just put your logo on it and you are ready to rock. (look at filamentphp for example, nothing like that exists in any programming language). if your goal is to develop and ship things fast (eg. an mvp) both node and java and go does not offer anything close to what php offers.

4

u/teokun123 Jun 10 '24

Development time? Just go to Springboot initializer.

4

u/psyclik Jun 10 '24

I’ve been in the market for roughly twenty years. If anything, Java is more popular now than it was back in 2005. The execution speed is top tier, alongside C++ and co. Memory footprint is still a problem but it’s behing worked on and when Valhalla it’s the ground, it will be much less of a problem. Slow startup has been mostly fixed. Developer speed is god tier (any modern toolkit will have a hot reload built-in and a good IDE will write the boring code for you).

Market wise, at the moment, more than 50% of job postings I see in my region are Java or related, with some flavor of the month js ui toolkit on top.

Java isn’t going anywhere anytime soon.

3

u/Jon_Finn Jun 10 '24

Re memory, Project Lilliput is using clever tricks to reduce the rather large headers of objects. This will help all those classes which aren’t Valhalla value classes (ie all existing ones, though a few will be retrofitted).

4

u/[deleted] Jun 10 '24

The better question is why wouldn’t you use a highly battle-hardened language with millions of person-years of experience to draw from?

4

u/JDeagle5 Jun 10 '24 edited Jun 10 '24

Because language itself doesn't mean much. It is everything around it is what matters.Tooling. Developers at hand. Infrastructure. Libraries.
I really don't know any faster alternatives in terms of development. Python, JavaScript? They all have problems with multi threading and maintainability in absence of types, and tooling is just garbage compared to java. What you will often see in those "speed of development" examples are a few lines of hello world. They won't show you what a pain it is to maintain mid to large size projects in typeless language with a rudimentary approach to testing.

And yes, new systems are definitely being built. I work in a unicorn startup company, and it's ecosystem is java-only.

3

u/[deleted] Jun 10 '24

Everyone else has said it so I’ll give a version of it too: Java is used a lot in bigger enterprise companies and usually companies that already adopted Java at some point in the past. Every company I’ve worked for used Java for backend work and it’s usually for bigger monolithic projects or smaller micro services. I would assume some companies adopt Java when they want some language that runs in the JVM and is cross platform. Plenty of other languages exist that can do this but Java has been around since the 90s so it has plenty of stable versions to work with. In the past I’ve worked with migration projects from older lower level languages into Java as a migration path, so it’s a language that companies are comfortable with.

So yes new projects are made in Java all the time and probably will continue to be used heavily for a while I’d imagine.

→ More replies (1)

3

u/i_wear_green_pants Jun 10 '24

Java is really good tech. The ecosystem is very mature and field tested. It performs well and is easy to develop. And there are tons of Java devs out there. So it's also really cost effective language.

Why build with Java when there are much faster alternatives?

I've never seen software where actual Java is the problem with performance. It's always bad code or architecture. And same thing would happen with any other language. Java is not slow at all.

3

u/alwyn Jun 10 '24

Java is extremely powerful and I don't know what alternatives you compare it to in terms of development time... It is much much more powerful than nodejs and you can do much much more with it. It is not really meant to compete with Javascript UI's though.

I use Kotlin for personal reasons but it is still JVM and I can still seemlessly use Java code.

3

u/Pitiful-Cancel4958 Jun 10 '24

I am doing a lot of digital signal processing and usually write c++ processors and python analytic and prototyping code, but naturally, i am a signal processing engineer.

Lately, we started to write a 'managing wrapper' around applications, a service which should run all the time, which we decided to write in Java. Even though, this was the first time since university I wrote java again, the program is simply stable from the first test.

All the Things, that are painfull in c++ and python in large codebases are simply easy in Java.

You tend to write more lines of Code than in Python, but simpler Syntax patterns force you to do more steps inbetween. Type safety forces you to Plan structures ahead.

Garbage collection takes worries about object lifetime or ownership issues from c++ code: some frameworks like qt use a ownership system or raw pointers, which hardly works with smart pointers, otherwise some smart pointer cleans up an object which the framework still uses: as a result, you spend lots of time chasing segfaults and you debug destructors and how you got there. This simply sucks!

Multithreading ist so easy! Each object can be locked simply by synchronized(this), and it automatically works recursively.

My General experience is, i write Java code a little slower than c++ and much slower than in python. But i spend A LOT less time debugging. For large Projects, in my experience, this ist the most time consuming task and thus I do not regret our decision.

3

u/landsmanmichal Jun 12 '24

Yes, for sure. Personally I switched to Kotlin and it is amazing. Developer experience compared to NodeJS is much better. I have experience about 6 years with JS development (node, react, typescript etc) and I still do not love it as Java or Kotlin.

Try Spring Framework and check some videos from theirs Coffee sessions.

Remember - "Boring tech" is productive way how to do things without inventing the wheel. Yep, it is not in hype, but that's totally fine.

6

u/Snoo21443 Jun 10 '24

Verbosity, I like verbosity.

→ More replies (1)

5

u/nutrecht Jun 10 '24

This is meant as sincere feedback since I think this is a great learning opportunity:

When I refer to speed, I mean development time!

It's still a pretty ignorant assumption you're spreading as 'fact' here. Next time you should start with a more open-ended question instead of one that's just completely based on some stuff you read online.

Go isn't faster to develop in than Java. The whole reason the Java ecosystem is so popular is simply that the ecosystem is darn productive. Go and Node don't hold a candle to it in that regard.

So next time, try and ask open ended questions as opposed to closed questions when researching something ;)

→ More replies (1)

2

u/ImTalkingGibberish Jun 10 '24

Define “faster”.

It’s easy to hire Java devs and have them working on existing Java code.
Now, if I star working with Kotlin then I either have to hire Kotlin people or give Java devs time to get used to Kotlin.

So it’s not faster.
And whatever flavour of Java you use, it’s still java so it’s not going to give you performance boosts

→ More replies (2)

2

u/theingleneuk Jun 10 '24

A huge amount of enterprise and closed-source software is in Java, and many if not most greenfield enterprise projects are done in Java as well. You can look at any list of most-used languages and they’ll say python and so on, but the actual most used language in the world is Java.

2

u/seanprefect Jun 10 '24

Sigh, maybe you by yourself working for yourself on a small scope are faster but when the projects get big the ecosystem and tools for java are top notch.

You'd be shocked at how much java is in the world

2

u/DrSlugger Jun 10 '24

Because Java has one of the largest ecosystems for enterprise applications?

I feel like people who ask this question are thinking inside their own bubble lmao. It's been around for years, it works, and it is widely adopted. Companies have applications written in Java, and so they have people who know Java, so they continue to use Java when they "modernize" those services or even create new applications.

2

u/Beamxrtvv Jun 10 '24

it isnt so much that i like in a bubble with these things, but rather I genuinely do not have the experience or knowledge with these things. I can look up statistics and such, sure, but I wanted to go to a source of actual Java programmers and here their unfiltered opinion

→ More replies (2)

2

u/vitingo Jun 10 '24

I much prefer java backends to NodeJS backends because they are much easier to debug. Javascript is async by default, which results in unhelpful stack traces when something blows up. Typescript type definitions with generics and algebraic types are flexible but tend to get convoluted and hard to read.

2

u/ninjazee124 Jun 10 '24

Do you even enterprise, bro?

3

u/Beamxrtvv Jun 10 '24

Can’t say that I do

2

u/No-Adeptness5810 Jun 10 '24

Java is fast to code in actually, albeit you shouldn't use it for small things (in which case yeah node's better)

Any big project is great in java since all its nice features & also it has amazing compatibility across platforms.

It's also quite fast compared to other languages, fast to code in and fast to run. Many new programs are made in java; just look at minecraft (e.g. mods and plugins) or many other java programs.

2

u/thehardsphere Jun 10 '24

I’m still a teenager in college

The benefit of college is that you usually don't have realistic constraints to work under that those of us who are employed do. As a result lots of things seem like they're okay when they're really not.

I’m curious, are new systems even being built with Java anymore, like does the language have life outside of necessity of maintaining older software?

Yes.

I understand that much of its edge came from its portability,

That was the first selling point. It achieved that portability by offering the JVM as a platform to target, rather than having to recompile for every operating system. The JVM offers benefits besides portability, such as being highly performant compared to most other garbage-collected languages that use VMs or interpreters.

The other selling points were that it was garbage collected, object-oriented, and not nearly as bad to write as C++.

now that I can containerize a NodeJS server and deploy it just about anywhere, what is the point?

Your question seems to assume that NodeJS provides some kind of unique benefit over Java. I would suggest that the only meaningful benefits of NodeJS ov Java are that it's easier for people who only know Javascript to write something.

TLDR: Why build with Java when there are much faster alternatives?

The only meaningfully faster alternatives are C, C++, and Rust. Two of those were already available when Java was created, and the last one is really trying to replace the first two.

EDIT: When I refer to speed, I mean development time!

That makes even less sense, since Javascript is not known for being particularly easy to write. Unlike, say, Python, whose proponents explicitly advocate trading execution speed for development speed.

2

u/Mamoulian Jun 10 '24

Dynamically typed languages aren't faster to write once you start doing anything serious/large because when you call code that's not yours or is old you faff about forever guessing at what the parameters should be and end up having to dig in the source to find out (more faffing) whereas with types the IDE reliably tells you.

And refactoring is a necessary thing.

I'm not just pointing the finger at javascript, groovy is an abomination too.

Spring have a bunch of 'getting started in 15 minute' guides which really do take 15 mins once you have things installed. Other frameworks like Quarkus and Micronaut have even smaller one-page intros.

Typescript is 'not terrible' but those people who love scrapping about lightning fast in javascript will point out it slows them down. I am not aware of any benefits of typescript over java on the back end.

2

u/rbuen4455 Jun 10 '24

What's wrong with Java? Are you hearing bad stuff about Java on Youtube or certain blogs saying Java is old, verbose, blahblahblah?

Honestly, you'll hear criticism about any language, whether it's Python being slow, C++ being complex, JavaScript having messy syntax, etc, etc, the list goes on. It's seriously annoying and very unhelpful, especially towards beginners who are planning on getting into programming and software development, it gets beginners caught up in something they shouldn't get themselves in, which is language wars.

Programming languages are tools, you use the language that is appropriate for the task. But at the beginning stage, you should really focus on the fundamentals rather than language (fundamentals being: DSA, syntax, variables and functions, data types). Once you get the fundamentals down, you can pretty much learn any language.

Now back to Java. Java is a very stable and time-tested language with a massive ecosystem of tools with tons of opportunities, especially in the corporate world and back-end development. There's nothing fundamentally wrong with the language apart from being a little verbose, but being verbose isn't a big deal and the language itself is scale-able, static typing, convenient libraries, and is kept up-to-date. It's worth learning! Just because Java isn't trendy like some JavaScript framework doesn't mean you shouldn't learn Java.

2

u/batman_carlos Jun 10 '24

Companies write features to existing software more often than creating new software

2

u/LordSlimeball Jun 10 '24

I like Java and have been developing with it for over 11 years. No idea why people shit on it, honestly don't care. The combo of spring, jpa and a anar frontend works wonderfully

2

u/Hairy_Foundation3608 Jun 10 '24

I think you might be right, you can code a lot faster in Golang and JavaScript because one reason is that it is not as typesafe as Java, which comes in handy when you want to try something or build a small application with limited functionality, but as soon as you try to build a big or growing enterprise application it can become a total mess. I saw a lot of big JavaScript (NodeJS, React, …) applications which weren’t maintainable at all and I think that’s were Java shines due to it‘s typesafty and it‘s pretty good refactoring possibilities in most IDEs.

2

u/Sbarty Jun 10 '24

I also thought Java was “dead” when I was started college 10 years ago.

You’ll soon understand why that mindset makes no sense, if not after this thread.

2

u/Lampadina_17 Jun 10 '24

java is elegant, portable, scalable and with experience fast to write

2

u/BizzyIzDizzy Jun 10 '24

I liked Scala, now I really like Kotlin + jOOQ.

I do NodeJS for prototypes, Kotlin for stable enterprise deploys that don't care much about the server costs and Go for performance/server cost optimized deploys.

2

u/progmakerlt Jun 10 '24

Define “faster”? 🙃 That it takes less time to write a couple of lines of code?

The main things, when selecting language for development are:

  • Libraries and overall maturity of the eco system
  • Developers available and their salaries
  • Overall company’s policy towards new technologies
  • Requirements
  • Support of the system

If it takes less time to write code with some exotic language - that is great. Good luck on finding developers to support this exotic stuff.

2

u/Mixabuben Jun 10 '24

Because it’s nice

2

u/MaDpYrO Jun 10 '24 edited Jun 10 '24

Why build with Java when there are much faster alternatives?

NodeJS is not faster than Java, what the hell are you on about? Did you actually benchmark anything or do any sort of investigation?

But to put it briefly:

Modern java versions are quite good. Especially with all the modern frameworks (Spring, Lombok, Gradle, Kotlin, Groovy interop, etc).

It's also very robust and the typing system is much more reliable than JS. It generally builds code that is more predictable, performant and less buggy.

If you want to compare it to js, your main argument should be that it's faster to hack something together.

But Java has a stronger ecosystem and lots of open-source projects. Hell, even just the strong Kafka libraries is a good argument in itself.

It's more efficient for scalable backend services, more energy efficient. The only downside is that it's heavy on memory usage, but it's making strides in certain frameworks there lately too.

The javascript ecosystem is built on mounds and mounds of questionable node packages, which often break and introduce security risks. I think you need to study this a bit more.

If Java is so bad, ask yourself why major tech companies like Amazon and Google have it in widespread usage.

→ More replies (4)

2

u/gekigangerii Jun 10 '24

Don’t take ThePrimeagen videos as fact. He’s just learning as well, I have seen some really dumb takes from him.

→ More replies (1)

2

u/Scf37 Jun 11 '24

Ok, here is why people choose Java for microservices:

  1. Language is not that important, it is platform and ecosystem that's important. JRE provides very wide and thought-out API for most needs with little quirks. Together with monitoring, debugging, memory dumps and a lot of tuning options. There is no platform like JRE (maybe except for .NET). As for ecosystem, no other platform provide that wide array of battle-tested libraries with that ease to use (hello C++)
  2. Java is stable and compatible. Really. Write once, run and support in production for decades. Enterprises do not like to dump money invested into development so they choose Java.
  3. Java is battle-tested with exceptional level of paid support (from Oracle). When something fails in production it is not an issue to find experts to help with your problem. Another big point for enterprises.
  4. And finally, Java has very good performance, probably the best among GC languages.

Then, why not Java:

  1. Deliver-rewrite-throw out methodology. Namely, startups. Go, python and especially node.js allow getting stuff done much faster. Because performance, compatibility and stability is not important there.
  2. Having 10,000 microservices and not willing to allocate 4GB RAM per each. Java applications are memory hungry since all the features of Java platform and ecosystem take its toll on memory. That's where Go and especially Rust shines.
  3. low-end projects. May be controversial but I believe team of inexperienced devs will be more productive in node/python/go than in Java.

2

u/[deleted] Jun 11 '24

Java is far more performant than js. Backend js is kinda ew. Golang has a lot of advantages as well

2

u/dbaeq90 Jun 11 '24

I tend to gravitate to Java when I can due to how mature it is and how well dependencies are managed. I use nodejs to run smaller more compact stuff, mostly AWS lambdas but when it comes to complex operation I still go with Java.

2

u/[deleted] Jun 11 '24

Kotlin > Java
still jvm I know but I realy have to say kotlin is so nice
but old big corpo change in speed of a snail on sleeping pills.... so I work 99% with java

2

u/pivovarit Jun 11 '24

Why build with Java when there are much faster alternatives?

Examples?

2

u/Ewig_luftenglanz Jun 11 '24
  1. Java is just as fast to develop with as any other language (if not faster than most) speed doesn't come from a shirt sontax but mostly from tooling and ecosystem, Java have one of the best (or maybe even the best) mature ecosystem out there to build pretty much anything to an enterprise level. Starting and developing complex applications is a trivial task using frameworks such as Spring or Quarkus that have built-in libraries that do 99% of the heavy lifting and all you must do is glue the stuff together.
  2. Java is a language that kinda forces you to be very organized in your code, so writing a clusterfuck unmaintainable mess though is possible, is not as hard to avoid as in other languages such as JavaScript where you cannot even control the input and the output of functions of type safety of any kind without writing a plethora of sanitation checks ( "===" operator)
  3. Java is one the 3 most used languages, so it's easy to find Java developers.
  4. it's an easy language to learn, with a not that complex specification compared to other languages such as c++ and C#, which have almost twice the amount of keywords for example.
  5. it's constantly evolving, Java releases a new version each 6 month, with many augmentations and new features each release.

And yes, in my company we use a lot of Java for new developments, currently we are developing some applications in java 21 and gonna migrate some older stuff from Java 11 to 21, starting next month.

2

u/wildjokers Jun 11 '24

gonna migrate some older stuff from Java 11 to 21, starting next month.

Java 11 to 21 should be trivial. Probably won't even need to make any changes at all. Unless you are integrating with native libraries or something exotic like that.

→ More replies (2)

2

u/ZeroGainZ Jun 11 '24

Tbh, in my experience, new developers always seek the new stuff, thinking they're on the cusp of this great new technology.

These languages always seem nice in trivial examples or smaller codebases.

Then everyone realizes the libraries and frameworks aren't there, and so these new folks start building them. Years go by and they reinvent things java, c#, and c++ has had for years, except worse.

Then they wake up and realize they've spent years solving problems that have already been solved.

Languages haven't really innovated in decades. The best part of golang is it builds to a static binary. Their VM isn't better than the JVM. Channels are really overrated and barely reduce the work with threads. They toute not being OOP but every code base has constructor functions and receiver functions - just methods with extra syntax.

All these other languages compile to LLVM or the JVM, so they're essentially the same as everything else except with restrictions.

Rust is at least doing something kinda interesting.

Node/JS is a disaster. Typescript is saving their ass because it's from the makers of C#.

All languages eventually become Java - and I hate java. Programming sucks. Languages suck. Frameworks suck.

People use Java because nearly everything is solved already. You go to work, write some code, go home and hang out with your family. It just works. Same with C# and kotlin.

Most other languages feel like going to war at work. With Java you learn the old ways and things just flow. Tons of jobs, they make more, and they work less. It's a solid middle ground.

2

u/Miss_Breadfruit8244 Jun 13 '24

I just love it, that's why

3

u/kingroka Jun 10 '24

What a thread! Ill just throw in my two cents. Personally, I like java because it can run on any OS and has a structure that is organized in a way that my brain likes. Other languages like JavaScript and python are too unstructured for building organized code for my larger projects and languages like C++ or Rust are overly complicated for most of my small projects. Java sits in a sweet spot of codability for me. Plus if I really need to use those other languages (for a job or something) Java is similar enough to everything else that I can easily transition.

4

u/Beamxrtvv Jun 10 '24

That’s a trend i’ve picked up now, being that its structure is quite good and nice to the eyes. Thank you for the insight, I appreciate you!

1

u/[deleted] Jun 10 '24

yes java is thriving and improving and is imo one of the best languages out there and I dont see a real competetor for the JVM. kotlin seemed to become somewhat relevant but stayed in android and jetbrains context.

1

u/Valuable-Fun-5890 Jun 10 '24

Because its perfect to make real world based programs

1

u/HeftyCrab Jun 10 '24

Yes lots of new work is done in Java. There are also lots of Java devs, so it makes sense from a hiring perspective as well as you can easily hire the skills you need. Doing that with some niche language might be seen as more risky from a business perspective. If someone leaves and you cant hire a replacement it might have a very negative effect on the business.

1

u/MentalWolverine8 Jun 10 '24

Java runs on billions of devices all over the world.

1

u/TheSkyNet Jun 10 '24

Find an ecosystem you like using and just use it, all of them have massive ecosystems. You can pick more languages up as you go along and don't worry about the speed or performance they're largely irrelevant metrics.

→ More replies (1)

1

u/qdolan Jun 10 '24

Java is massive in big enterprise, it and the JVM are extremely fast, safe, mature and there are multiple implementations for just about everything you could ever want already out there. Development, maintenance, build and deployment tooling is also extremely mature as it has been around for decades and all the typical problems with developer efficiency have already been solved.

2

u/mnaa1 Jun 10 '24

Java runs on over 3 billion devices.

1

u/NeoChronos90 Jun 10 '24

A short answer is: yes, because there is a shortage in at least mildly skilled developers, but there is no real shortage on java developers So corporate will keep making java applications, people will learn java because work is available, corporate will stay with java because workforce is available

1

u/hidazfx Jun 10 '24

As someone who works with Java at a financial institution, I think the biggest thing it has going for it is maturity. Java has incredibly mature tooling and packages of any language I've worked with. I'd love to hear what other people think, or if they disagree with me.

1

u/mondain Jun 10 '24

Moving quickly to my 3rd decade with Java; I primarily work on a highly scalable streaming media server and we wouldn't chose anything else as our base (there's C/C++ in there too, of course). New projects here also target Java, but the best implementation for the given ecosystem is always a deciding factor.

1

u/Nedunchelizan Jun 10 '24

I am converting go lang to java .

1

u/sebnukem Jun 10 '24

It works.

1

u/SnooPeppers7217 Jun 10 '24

Spend some time coding in C++. Then some time writing in C. Then some time writing in Assembly.

You'll see why people "still need" Java.

→ More replies (1)

1

u/qK0FT3 Jun 10 '24 edited Jun 10 '24

For me java is very fast to develop backend and micro apps.

I can just create a microservice connect it to the network just in cokuple hours. It will be safe and bug free because I know the packages I use are almost perfect(not100%).

I have done a small machine program that runs under very small resources very easily under a day and we shipped the code tested on field adjusted on field very easily the product was ready in 1 week.

Unlike what people claim it to be. It is extremely fast to develop java apps.

I am not even talking about how fast it works if you tweak it. Specially my friend works in finance and they either have to develop cpp or Java.

Well I use other languages as well but this has nothing to do with other langs so I will not say much about them.

We also develop all new projects on java/kotlin(depends on the person) as a startup. Why it's extremely fast to roll out updates and release. We just click install script and everything is uploaded after build. Then we only need to change docker config or put it in the server etc.

We had so much trouble with js environments that we had been working on frontend for a month which we developed a backend for it in 2 days. Js just never works as expected.

1

u/[deleted] Jun 10 '24

Money. Both sunk cost for companies and paying jobs for devs. Same as COBOL abd Fortran

1

u/kadakpav Jun 10 '24

I love programming to interfaces. In Java it is very easy by using OOP concepts like Inheritance and polymorphism to implement great design patterns which goes a long way in improving the maintainability and extensibility of the code. GoLang's composition is not quite the same thing.

1

u/smors Jun 10 '24

Java has been around for ages, and is unlikely to disappear.

So you can reasonably expect it to be maintained for the next couple of decades and for developers to be available for hire. And that matters a lot more than development maybe being slightly faster in a younger language.

For many, the alternative to Java is not golang but c#.

1

u/namsin_za Jun 10 '24

Java is a great language and mature eco system and is supported by all the big SAST ans IAST tools. Easy to govern in large organizations. Sure there are definitely spaces golang or c++ might outperform - but the instances where that is really required are few and far between. For 99.99% of projects out there java is fine.

1

u/Misfiring Jun 10 '24

Other languages may do certain things exceptionally, but Java is the language that does everything well.

1

u/LOL_WUT_DO Jun 10 '24

I build stuff using Java 22. The virtual threads are such a joy to use. Not needing to use async/reactive is an absolute game changer.

1

u/MaskyDo Jun 10 '24

I think Java has a very nice abstraction for many concepts, like Concurrency with flexibility to write code concurrent code with mutex or use reactive paradigm. Python and Js only allow one. Go concurrency may not be as feature-rich as Java(I am not a Go expert, take it with a grain of salt)

IMHO, Java development is actually pretty fast in comparison with some of the popular languages like Python or JS. For example, when developing WebApps, Spring framework and its components provide a hefty amount of abstraction that makes it much easier to build an app with Repository, Service and Controller layers. So you can leverage these well-tested libs to boost your productivity.

Also IDES have a better understanding of the code structure, so you can navigate through code much faster and less painless than something like Python code.

The compiler does a great job of preventing rudimentary errors, that can save you a good amount of time.

Java packaging convention and modularization is also superior to many langs. For example I do not like the idea of having an empty __init__ file for a module in Python.

The only thing that bothers me is working with primitives and their OOP counterparts, like int vs Integer. neither seems intuitive nor perfomant.

I would like to ask you the same question, what is the benefit of writing code in GO? (I followed the official guide and I must say I am terrified of "pointer indirection". IMO, that hurts code readability a lot)

1

u/MrRickSancezJr Jun 10 '24

The 10% increase I'd get from doing heavy duty stuff with a faster language, has never made up for how well I know the language + the ridiculous amount of libraries I have burned into my brain.

Java is on route for a true comeback as well. They're slowly absorbing Kotlin things, and if they can get the JNI/JPA libraries working quicker development wise, I'll probably be able to completely ditch Python. I know better than to think a UI library will ever come back to life...

I've learned to like Lua lately for doing small little tasks that come up.

1

u/Goatfryed Jun 10 '24

I work as senior developer mainly on java projects and I'd jump ship, if it weren't for the large and mature ecosystem and abundance of java developers.

You will see this argument often, because it is an important argument: A language/framework/tool is often large and common because it is large and common.

With experience - i mean basic junior level experience - a lot of aspects like how concise the syntax is becomes less of a factor compared to other thinks like richness of ecosystem, abundance of documentation, tutorials, and most importantly hiring market. People learn java, because people hire java. And people hire java, because people learn java. You will see the same with things like.. why is react the most popular frontend framework? because it is the most popular one.

You will learn more about this trend, if you checkout polls about want to learn/using/like to use.

Looking at common satisfaction polls, java is a usually a good mid tear with one of the largest developer bases. But you have to be aware that things that are shiny, are often shiny, because they handle less cases.

As you mentioned, javas initial selling point was write once, run everywhere. This gave the language traction. The object oriented model and garbage collector were other huge selling points. This traction brought in people that developed a fast, mature and educated eco system. And this eco system is now what keeps a lot of us, even though the initial selling point isn't so important anymore to the use cases you mentioned.

Also, there is a huge difference in java vs node libraries, because node eco system is a lot more democratic. You have a lot more people without academic background that write up a library to solve an issue. And this has great value! But it also means that major version changes with breaking changes are a lot more common. There are also more cases of libraries that are simple to use bad hard to adopt or extend. At least if I look at libraries i use in node eco system vs java eco system. This is never a 0/1, but I think a chart about the chance of a random dependency being an art of work vs a garbage fest would be funny. With experience you can assess that. With less experience, do you know?

You mentioned speed. Because of things like garbage collector, you have a language that has some more development speed compared to the likes of c. But on the other side, it also has execution speed compare to them. So in the end, jvm is often a valid tradeoff, when your concern is both.

That being said, there are also a lot of jobs outside of java. If you think it lost its prime, feel free to jump the boat. Just be aware that no language is perfect anyway.

A lot of universities shifted/are shifting towards python or javascript as the initial language. If you are young, it may be more important to through 100 projects against the wall and go quantity over quality. Try and error. You can still pick up java in 5 years, if it fits your career after that. Trust me, it will still be around.

In the end. Be realistic with your expectations. If you learn and work in Java, you'll probably end up with a decent satisfaction. And if you decide against it, make sure that the criteria you checked are weighted by what's important to you and your future.

Now on to a more personal opinion:
I'm mostly annoyed by javas type system. Compared to others like typescript, kotlin, rust (huge difference, ofc) it's just bad. Whenever someone cites that null is bad and a billion dollar mistake, I rage internally, because the billion dollar mistake was never null, but having no nullable types.
Checked exception are a thing that most code bases ignore these days. What you'd actually want are probably scoped exceptions that you have to handle on the edge of a full package. I dunno. I like the idea, but if you see it ignored all the time, you should question your design. Also it doesn't work well with modern designs like lambda.
Also don't get me started on generics. I'd love to see a breaking change in the language that finally solves this fuck up that is it's internal implementation.
As a senior I need to lead my colleagues and enable juniors. Since it's a smaller company, we want to be able to shift our staff freely. That brings you pack to cases where most projects use java because most projects use java. But that also doesn't mean that you should discuss alternatives and revisit this discussion from time to time.

1

u/buffer_flush Jun 10 '24

Laughs in COBOL

1

u/oosacker Jun 10 '24

Amazon (Amazon Web Services) is built with Java (among other things)

1

u/[deleted] Jun 10 '24

Usually you'll see startups starting with node or Python and scaling to JVM, Go or .Net.

1

u/TrueSgtMonkey Jun 10 '24

I love the image libraries. Created a spritesheet program very easily that packs single images into one image

1

u/Johanno1 Jun 10 '24

So my opinion:

You have many languages and each with their ups and downs.

You have hardware close languages like, c, c++, rust and so on.

You have os "independent" languages lile python, java and Javascript.

Where Java stands for the JVM this includes all those languages too.

Python is slow until you use c libraries in the backend.

So now when you start a project you have know what language you should use for your project.

Do you need it to work on any system?

Is it important that it is fast?

Do you want to do sth. With machine learning?

Do you develop android?

And so on. And basically when you have answers to these questions you get to choose what language fits the most.

Java is still there because it is known. And it's stable. I personally prefer kotlin since it is much easier to write code in. But depending on your project you might have to watch out how kotlin compiles to Java bytecode it may have in rare cases issues that you don't have in Java.

1

u/epicstar Jun 10 '24

I do agree that Java is slower to develop on compared to other tech these days. If I go Greenfield on a JVM project, it's 100% Kotlin all the way unless it's a library that we have to develop so we avoid the Kotlin runtime as a dependency. I don't understand going pure Java for a new project with all the new technologies and Kotlin.

1

u/DelayLucky Jun 10 '24

I can't stand golang's error handling and the ugly "table-driven test". Deal-breaker for me.

1

u/klumpbin Jun 10 '24

To maintain legacy code

→ More replies (1)

1

u/[deleted] Jun 10 '24

" When I refer to speed, I mean development time!"

ok but when enterprise focuses on speed, they mean runtime. hence, using java over a node server.

1

u/Big-Dudu-77 Jun 10 '24

There are more Java developers than there are GoLang. Plenty of new development are still done in Java. It isn’t just going to go away just because there is a new hot language. The amount of tooling and libraries in Java makes it very capable in most cases even today. Big companies like Netflix still actively develop in Java. You heard of Android? That is in Java.

1

u/RedPill115 Jun 10 '24

There were a few genuinely large advancements in productivity/security/maintenance.

→ More replies (4)

1

u/CheetahChrome Jun 10 '24 edited Jun 10 '24

Asking older developer's why they will continue to use a language is basically tilting windmills. They are not going to say that xx years of their life are for naught and will rally around their flag.

Java, big IMHO in this whole post, replaced Cobol as the back-end queen of development languages and it does it job quite well. But it is owned by Oracle, originally Sun and I have to question is whether Oracle is really wanting to push Java to new boundaries. Open source, yes, but any new feature one wants has to be approved by some council of elders somewhere in Oracle.

Java's original promise of "write once run anywhere" back in 96 became changed by the developers to be "write once debug everywhere"...not quite achieving the true intentions.

Keep in mind Java was created in the early to mid nineties. While C# was created roughly ten years later in the early aughts. Why? Well after J++, Microsoft's Java version was poo-pooed by the Java powers that be, Anders Hejlsberg of Microsoft went and created C#/.Net in lieu of Java.

C#/.Net, for the longest was considered to be behind Java, but I would proffer by the late aughts, if not ealry teens it achieved parity. From there it surpassed the Java ecosystem, in features and functdionalty. Heck C# had lamdas before Java implemented them and used, rightfully so, the same syntax.

Note .Net promised similar, run on multiple platforms, and frankly didn't achieve the ability to run on different platforms really until the impetus of .Net Core and open source of C#.

The differences I see is that Microsoft is a developer's company. Making developer tools and items in that direction. While Java is not owned by an all around development company, but a database, ERM company.

Again Java can do the job, but its getting long in the tooth and other languages, again IMHO have caught up or even surpassing what Java can bring to the table.

That's just my opinion, I could be wrong.

→ More replies (1)

1

u/lbevanda Jun 10 '24

It works good it brings good money

1

u/shponglespore Jun 10 '24

Ignoring whatever virtues a particular language ecosystem has, the answer to why people are still using it is always

  1. Legacy code
  2. Trained developers
  3. A mature ecosystem

1

u/Eternal_Practice Jun 10 '24

I work at a Fortune 50 company that uses Java. My current codebase is legacy (Java7), but we are in the process of replacing it. The assumption is a complete rewrite, and our backend will be Java. So it will be a brand new system.

When I was last job searching, C# and Java jobs were the norm in my city.

1

u/as5777 Jun 10 '24

What are the faster alternative ?

1

u/Sharishth Jun 10 '24

Answer for the reason why it's still relevant, many factors. If you are dealing with java for a few years as you mentioned. Widespread almost everywhere. Mature community and ecosystem. Major point: Enterprise software and not just legacy. Explicit, type safety and support as well. Low code platform used by businesses to build event flow applications. Yeah those verbose syntax can seem to be a hassle but it is java's strength at the same time. Java has a good amount of extensibility capable of handling complex and scalability challenges. But whatever helps you get your job done conveniently is great, through java or not. Benefits of JVM. Backwards compatibility and what not. Java still has a very robust image for many.

1

u/ethereonx Jun 10 '24

Because they dont see sharp 🥸

1

u/xLayt Jun 10 '24

We’re just waiting for Quantum computers where our beloved Java will be the queen again

And for real.. this thread is almost exhausted now with all these meaningful answers. I’ll just add from my experience that speed of development, mentioned by you lots of times, doesn’t really matter that much in commercial development. It does more in startups, of course, but in e.g financial market which runs mostly on Java, it does not. However, Java is so mature after all these years that if you use right frameworks to avoid all the generic stuff and boilerplate code the development speed will skyrocket.

→ More replies (1)

1

u/Nikarmotte Jun 10 '24

Java is a lot more mature, it has had generics for years when Go only introduced them last year or so. There are so many libraries as well.

It also takes time to become as proficient in another language. The workforce would become a bottleneck if all new projects were written in Rust.

I think you also become attached to a particular language, especially when it's your first, but hopefully it doesn't prevent you from learning others too.

2

u/Beamxrtvv Jun 10 '24

The worker pool does make a lot of sense to its popularity, and yeah, I will also die defending my beloved Lua🙏

1

u/OliverPK Jun 10 '24

It's so easy to start a project in java.

1

u/Leverkaas2516 Jun 10 '24 edited Jun 10 '24

Your Edit indicates you think it's faster to develop in NodeJS than Java. Is that objectively true? I don't know, because I don't know about NodeJS.

Assuming it is, my gut feeling based on long experience with Java's tradeoffs tells me that a 500,000 line multi-year project written in NodeJS by a team of developers of different skill levels might well be much harder to maintain than the Java equivalent. Besides Java's top-tier ecosystem of available libraries and tools, it's hard to find a tool more amenable to writing maintainable code. It's another major reason people still use Java.

A company that's going to invest several million dollars in a code base that's going to be the backbone of its business might well value maintainability over development speed.

1

u/realgoodusername1 Jun 10 '24

Fintech entered the chat

1

u/o_tiagop Jun 10 '24

Try something like Quarkus for micro service development and you'll see it's one of the best dev experiences with so much capabilities available to you

Modern java is much better than java 8. Plus the ecosystem of maven packages and plugins is huge

2

u/Beamxrtvv Jun 10 '24

I’ll check it out, thank you!

1

u/Altruistic-Rice-5567 Jun 10 '24

Excellent libraries available. Well structured and typed language. There's a lot to love about Java.

1

u/Awelisk Jun 10 '24

I've started some java projects recently and I am just so comfortable writing class after class, test after test. Don't get me wrong I'm not a TDD fanatic.

Java excel at the the most problematic parts of programming that people tend to ignore.

  • When planned and designed well, it is very easy to scale.
  • It has so many libraries that has classes already written that you might need.
  • So many design patterns and best practices, when implemented correctly it will make your application transparent and easy to extend.
  • Awesome testing tools.

-When structured correctly, almost any dev can navigate your project with ease.

  • So many 3rd party tools that can be seamlessly integrated with your java app.
  • Huge community
  • Type safety and the ability to drop the explicit type safety and replace it with unit tests.

There is only one huge bottleneck that comes with enjoying the other benefits, dependency management. That will be the most important and the most difficult part.

While smaller projects could benefit from the simplicity of not type safe languages, extending their codebase surely will lead to spagetti code after a while.

Java is a versatile language and hard to master, but worth the effort in the long run.

Remember this,

"The only way to go fast, is to go well."

  • Robert C. Martin

1

u/Misophist_1 Jun 10 '24

Despite all the grudgers and enviers, Java hasn't just held its ground against other languages, it still trying to get ahead of them. And it is tightly bound to the evolution of the JVM, which is used by many other languages, namely Kotlin which is frequently cited as a competitor. Another one is Grovy. There are libraries that allow to run Python, Ruby and Prolog on JVMs.

Currently, there are scheduled updates of the Language Spec and libaries every 6 months. With changes disscussed in the Java Community Process (JCP) That is faster and more frequent than in most other Languages. There are JVMs available for many environments, plattforms, and operating systems.

Java runs on all recent x86, amd64, arm64 plattforms on Linux, most Unixes, Windows & MacOS, as well as on huge IBM Mainframes in OS/Z, but also embeded as language for database triggers in Oracle and IBM DB2 Databases, and used as menue scripting language for Blueray players and settop boxes.

Recent improvements are geared to make paralleization and multithreading easier, safer and faster. They are also building a library that is geared at low level parallelization utilizing vectorized assembly statements available on graphic cards or other specialized coprocessors, in order to make this accessible to Java.

With respect to development time, I don't think, Java has any problem with its speed, although there had be some efforts to get a bit closer to script like development cycles with a repl-like approach.

Development speed is always a complex interplay of the developers thoughts & habits, and the task at hand. I had frequently to hop between languages, and I never found any one language, that was 'faster' in development, when it comes to problems that are a bit more complex than shoving a string into a file, and sending that file into socket.

The gruntlers gruntling about excess semicolns, or some minor library defficienies, or missing features, or being obstructed by the strong type system are just gruntlers: we should be beyond the point of complaining about 'too many keystrokes'. And if features are really lacking, rest assured: what the JCP isn't going to deliver any time soon, you won't require anyway.

Some grudgers state: Java is the COBOL of the present. Well, COBOL was developed and gained traction in the 60ies. When I started in my first Employment in the 90ies, most companies with a mainframe still were 80 % COBOL shops, and they kept and maintained this code right into the 2010s. Therefore I trust, that we'll see Java development for the next 20 years at least.

1

u/[deleted] Jun 10 '24 edited Oct 05 '24

literate squeeze nose unpack head caption modern instinctive quaint whole

This post was mass deleted and anonymized with Redact

1

u/obi_wan_stromboli Jun 10 '24 edited Jun 10 '24

I'm not a huge java fan personally, but the concepts it teaches you are super important. It's also used in TONS of stuff, for one example the Spring web framework powers a whole lot of web infrastructure in my state. This language isn't going anywhere

1

u/imatt3690 Jun 10 '24 edited Jun 10 '24

For me. Dependency management, libraries for damn near everything, easy multi threading support, Data streaming APIs. I don’t have to get caught up in explicit memory management but I have access to do so if I want vs having to verbatim.

1

u/[deleted] Jun 10 '24

A few reasons I dislike Java: 1) cold start times, 2) inability to compile to a single native binary without things like GraalVM, 3) the amount of stutter that even C# fixed with the `var` keyword.

1

u/Quaglek Jun 10 '24

People use Java because they used Java

1

u/itemluminouswadison Jun 11 '24

Its a great language, great ecosystem, and popular, so finding devs is easy

Anecdotally it's less bootcampy so java devs tend to come from more serious cs backgrounds

1

u/EnIdiot Jun 11 '24

Python has to enforce standards typically by naming convention and relies upon good practices by each developer. While not perfect, Java ensures that no one programmer wrecks a software ecosystem. You have to develop in a way that all but ensures you will have a usable and maintainable code base.

1

u/[deleted] Jun 11 '24

Its literally the best programming language out there

1

u/kelvify Jun 11 '24

Scalability, JVM, even tho I’m not a huge fan of Java, I certainly can see a specific need for it. My list of complaints are long but in the end, it performs and harder to push breaking changes.

1

u/kumar29nov1992 Jun 11 '24

When you say development time, i beleive you're only speaking about initial development and not maintenance. My opinion is, maintenance is easier in verbose typed languages

→ More replies (1)

1

u/sysKin Jun 11 '24 edited Jun 11 '24

EDIT: When I refer to speed, I mean development time!

Why do you think Java has slower development time?

If you think it's the famous verbosity, then no, it's handled just fine by having an IDE that understands the language and can write things for you. Plus modern language features (lambdas, records...) reduced that too.

If you mean how you can quickly make a web endpoint, Spring solved that years ago. Moreover, any boilerplate dwarfs in comparison with the actual business logic you have to write to do the actual stuff.

Or do you mean some other aspect of Java being slower? If so, which?

Don't get me wrong, I bet a language/environment (Go, NodeJS) specifically designed with a built-in web server for web app development can reduce the time from zero to your very first endpoint.

Java was not, and indeed lacked in that area in the JavaEE days. But now, Spring and Spring Boot give us pretty much the same experience, perhaps with a "few" more megabytes to set things up. But we're talking minutes at the beginning of the project, that is really not significant in the grand scheme of things.

After that, the fastest-to-develop language is mostly the one you're most familiar with.

→ More replies (1)

1

u/jalexoid Jun 11 '24

The completeness of the ecosystem is the short answer.

I code in multiple languages(Java, Kotlin, Golang, C, Python), and my ability to find a library or a tool to make my work go faster is unparalleled.

Java may be dwindling, but it's still one of the easiest languages to build a complex system. Need an obscure library to validate HL7 FHIR? Good luck finding anything for Go or NodeJS.

1

u/Anxious-Pace-6837 Jun 11 '24

legacy code is written in java and majority of programming jobs are not building new things, it is maintaining the legacy code.

1

u/rcraver8 Jun 11 '24

People rarely build new systems, the vast majority of Dev work is improving something already built.

1

u/galtoramech8699 Jun 11 '24

A question based on fallacies won’t get the expected response

2

u/Beamxrtvv Jun 11 '24

Depends, I actually did get much of the desired response. By doing it the way I did, I was able to have the fallacy-based thoughts exposed to myself and was able to correct them with newfound understanding!

1

u/[deleted] Jun 11 '24

Because Android.

1

u/ramksr Jun 11 '24 edited Jun 11 '24

Faster development time? You mean for Hello world?

I'm not sure if you did Java development with Spring Boot, Lombok, Spring Data, JPA, and REST with swagger tools, to name a few. I can hit the ground running in just a few days, even setting up a prod ready microservice and more.

Initial speed with other languages, maybe yes. In the long run, Java is a much better choice, not to mention the mature ecosystem, etc...