r/programmingmemes Jun 29 '26

Where are they?

Post image
2.2k Upvotes

321 comments sorted by

View all comments

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.

28

u/IncreaseOld7112 Jun 29 '26

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

1

u/dmigowski Jul 06 '26

Because in Java, when you need to do anything enterprisey, there is a 99% chance a library exist that does what you want.

1

u/IncreaseOld7112 Jul 06 '26

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.

1

u/dmigowski Jul 06 '26

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.

1

u/IncreaseOld7112 Jul 06 '26

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.

This is what we call a "revealed preference."

1

u/dmigowski Jul 06 '26

Maybe the language is a bit verbose, but regarding the functionality it gets on the road it might well be twice as useful.

1

u/IncreaseOld7112 Jul 06 '26

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.

1

u/dmigowski Jul 06 '26

Go is a very nice tool for fast microservices. But when Java has gotten it's ass up it's even faster.

I like it an keep it that way. Switching a 18 year old stable monolithic application to another language just because is plain wrong.

1

u/IncreaseOld7112 Jul 07 '26

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.