My guess is some combination of:

  * Python -> Java jump (e.g. CS1=Python, CS2=Java) is difficult.
  * First real world job in Java in a larger enterprise with lots of older baggage
  * And by a few handful, related to sound technical reasons in their niche area

For me, the jump from Java -> C/C++ in university was hard and I still don't have a good handle on those latter languages. In my first job out of school I was handed a massive C++ library to build an application around with no mentorship and I failed spectacularly. I reacted similarly to the negative Java hate: "Why would anyone use this?"

For me now, as a principal eng, building a greenfield project with Java 17+ now is extremely enjoyable. Interestingly, we've had some HTML/CSS/JS bootcamp devs with no prior coding background succeed in doing Java. And we've had some Python/C university devs struggle. Sample size is too small to be meaningful, I just thought it was interesting.

Both GPU support and SIMD CPU support are being worked on in OpenJDK projects, there are talks on them from last year's JVM language summit - https://youtube.com/playlist?list=PLX8CzqL3ArzW90jKUCf4H6xCK...

Thank you. It looks like there is still a lot of work to do.

> What is with Java hating crybabies here? Your mothers didn't love you enough?

We were forced to use Java and then switched languages and saw the light. Simple as that. Doesn't mean that Java is useless but coders are entitled to have strong opinions when their day-to-day is impacted so heavily by it.

Same reason I allow but don't necessarily approve of Rust, emacs, nix, etc. evangelism. Is it annoying? Sure, but those people all have a basis for their gripes for the most part.

> We were forced to use Java and then switched languages and saw the light.

Other languages will do a better job in various ways, certainly, but in my opinion Java remains a pretty good middle-of-the-road language.

If you want to go deep on high-performance computing, or functional programming, or type-safety, or low-level programming, then Java isn't going to win at any one of these. It's still broadly successful in what it's trying to achieve: a fairly fast, very portable language and virtual machine with various features to help the programmer deal with code-defects and achieve correctness, generally preferencing these (and portability) over performance where necessary. It also generally commits to backward compatibility.

There is no one language to rule them all. It's more a matter of Pareto efficiency.

Who forced you to use Java and why?

What did you see in the light? Don't full a Fermat's Last Theorem on us please...

Java is only fun when leveraged via Clojure.

Can you please not take HN threads into programming language flamewar, or any flamewar? We're trying for the opposite here.

If you wouldn't mind reviewing https://news.ycombinator.com/newsguidelines.html and taking the intended spirit of the site more to heart, we'd be grateful.

Of course. If this was my intent, I would have also replied to the comments. I was just curious about the massive phenomena rapidly appearing under this post.

In addition I'm also frightened if the same anti-Java bias prohibits similarly interesting content to appear on the front page.

HN discusses plenty of interesting Java content and you're certainly welcome to post more!

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...

These are all fine motivations but they make threads worse not better by starting unrelated meta flamewars, especially when written in a goading tone (crybabies, etc). The way to make crappy threads better is to downvote and flag lame comments and by writing on-topic, nonmeta comments.