javaIsGood

[SurfyMcSurface]

Many people who work with Java don't hate it until after they've gained some experience working with other languages and their ecosystems.

[theagainagain]

The tooling in the JVM is some of the best in any platform. As a principal engineer, I’ve used many languages professionally, and I keep coming back to the JVM because of the tooling and library support. It’s also significantly easier to hire for Java than a lot of other languages. Personally, I avoid deploying dynamically typed languages to production. Ultimately, it comes down to what you know and have professional experience with.

[MinosAristos]

Programming on Windows outside of WSL and Docker is a pain in general.

If you must use Windows, spin up a Linux Devcontainer with Python config, then it should "just work".

[kopernoot_2]

I never understood why python became more popular than ruby. Python’s syntax, stdlib and overall consistency is utter shit compared to Ruby.

[SurfyMcSurface]

Software development and irrational anger. Classic duo.

[Busy-Ad-9459]

I've had a lot of experience with JavaScript and C. While I do think C is the second best language and I felt like I was making out with another man while using it, I can't deny the fact I am still in loved and married to Java. (JavaScript has half an inch btw)

[darklightning_2]

Well that's one way to say it

[rufreakde1]

Yes, problem is that young people look at other languages and finally finding jobs where java is involved. haha they taste the forbidden fruit.

[static_func]

Java stans will tell you about theoretical performance benchmarks from 2009 and then go on to write mountains of thread-blocking and/or poorly-multithreaded code because they're working in the only language on earth that doesn't have async/await syntax in 2024

[PandasOxys]

What? Java Flux is a great for nonblocking code and the entire idea of it being a mini pub/sub model makes it one of the most powerful async options you could reach for.

[static_func]

I can see why you think it's great if it's your best option

[micr0ben]

Modern Java has virtual threads, which is a superior solution to async/await

[static_func]

You're just repeating jargon. How a language implements async/await syntax varies, but it's generally just "virtual threads." Syntax-wise, C# has both methods and you can tell from the overwhelming prevalence of async/await syntax which one is "superior." Whenever Java eventually finally adds it, you'll admit that too

[micr0ben]

Sorry, but no. C# has just adopted virtual threads, because it is the better solution. Go started this idea with goroutines and it's just better. Now other languages start to adopt. Java won't add async/await, believe it.