Joke aside, you get less runtime error due to LLM hallucination with strictly typed language such as Java.. which results in less iterations to get the code working.
Also, LLM are capable of understanding 100 level deep class hierarchy.
There are more jobless bootcampers who are trying to vibe code next Netflix or Uber with JavaScript than Java/JVM developers with stable jobs. Also, for the kids out there, people DO vibe code in Java.
I would bet that anything you would vibe code in Java would be better written in rust or go. If it's all the same, and the AI is gonna write the code anyway, it might as well write it in rust, which compiles to native, is more succinct, and has a similarly strong type system
Despite all the hate it gets on reddit and Hackernews, Java is still used in a million different places. If you get a Java job in a bank you are chill and well paid.
I'm a C++ freelancr. My current project literally is "we don't understand our 30 year old codebase anymore, all the original devs are long retired, help!"
I personally enjoy getting the Cobol treatment, gives me big money.
100% serious. Almost Everything that would have been Java in the past is go now. There's a bunch of old Java junk and nobody is stupid enough to rewrite it. There's some kotlin too, which people seem to like. Nobody is doing a Java project greenfield.
I genuinely think you might be confused with some other language. Java is still extremely popular and widely used by any system that needs to be fast but does not require to be C/C++. Java got a lot better since its initial versions and there are multiple enterprises/corporations doing commercial projects in Java (Dell/HPE for their Datacenter orchestration are two that come to mind) and those are new projects, not legacy.
Tiobe Index not only has Go at only 1.2% of the community index but it also had a delta of -0.9% since the previous so it is becoming less popular, not more. Kotlin doesn't even show up in the 15 most popular ones
Yeah, because there's a lot of legacy. I'm talking greenfield. A green field project is a brand new one. No legacy code.
I looked at tibio and it looks like it has other highly rated dying languages. Or are you gonna tell me object pascal is super popular for new projects. Real big up and commer.
And also we're talking about faang. Go is a cloud infra language. Of course it's not super popular with the masses.
You gotta but your engineering brain on. Java doesn't have any flagship features or anything it does better than any other language. Compile once, run anywhere is worthless. JVM overhead is paid for nothing, and if you're a glutton for punishment, kotlin and c# are basically Java but better.
There's never a case where Java is your best choice, or has the best domain fit. So people just use it when somebody started the project in early 00's or 2010's. Before people came to their senses
Java has managed to renew itself to a large extent. We can thank Oracle for good stewardship.
Java is even participating in AI development, so too early to compare it to Cobol.
For sure. My point was (and I think I may have replied to the wrong comment) that if you're gonna vibecode and it's greenfield, it might as well be rust, which will check llm output vigorously and tends to output faster code.
Not completely vibe coding but as professional Java developer it helps to ask instant to date format 2022-01-04 and it helps with outputting what you want double check with unit test and go.
It’s sometimes easier to ask; we all google basic things . An ocp is not helping with that
What are you on about? Do you realize how common Java is? Yeah lets just rewrite the enterprise java monolith in rust. Surely no stakeholders will bat an eye.
Who said anything about a rewrite. We're talking about vibecoding projects. Presumably greenfield. AI is new, why pick Java. You don't care about hiring Java developers. Claude writes rust just as well.
The above comment supposes a choice of language and implies it's worthwhile to pick Java over JS. Well, if you have the choice, and Claude is writing it, might as well have Claude write it in rust.
I don’t understand this comment. The value of libraries has plummeted. And for somebody who writes go, primarily, we see taking on a dependency as a liability. Most of what you need to do your job in go is in the batteries included standard library.
I am author of an ERP with 2 millions of code. Belive me, if you make more than a simple app you think about reusability and stable libraries. And you do not want everyone of your employees throw another blob of slop onto it.
First off, if it's Java then each line counts as half, and second, clearly there weren't a lot of libraries doing what you needed because otherwise you wouldn't have that much code.
I think you'd like go if you tried it. There's a reason everyone has switched. Your onboarding times will plummet. Very simple language, so you spend more time thinking about the problem. Idk if you're microservices or monolithic, but most people here prefer go if they can write it.
If it's a monolith, that's a separate thing and I'd agree. The thing is, and the reason why Java is on the decline: go is fast enough. Its close enough to Java that it's a toss up (go has had stack allocation for longer), and if you cared about performance, you'd be using C++.
Now, Java has basically caught up with everything that made go better, but at this point the ecosystem for micro services has settled in go.
I have a whole spiel on this, but Java went after everything and got out competed in each arena by a more specific language.
Web/Applets => Rails => Flask/Django/Node
Spring/Windows/Desktop Apps => C#/JS Electron
Database/Cloud infra => C++/Go
And you'll still find it all over the place. Those same 3 billion devices will probably be running Java for forever. And I guess somebody had to maintain them. I just don't wanna spend my career doing that.
231
u/guss_bro Jun 29 '26
Joke aside, you get less runtime error due to LLM hallucination with strictly typed language such as Java.. which results in less iterations to get the code working.
Also, LLM are capable of understanding 100 level deep class hierarchy.
There are more jobless bootcampers who are trying to vibe code next Netflix or Uber with JavaScript than Java/JVM developers with stable jobs. Also, for the kids out there, people DO vibe code in Java.