I've seen a few "can't scale many-to-many" Java/C things in my career... it's all about how you put things together. I don't think Java and C can go faster than light either ;-).
And then you are in segmentation fault hell.
Sun had to rewrite the entire JVM in 2003 with a new memory model, later adopted in C++11 (and still the current C++ memory model) which failed for C++ because this model only works well if you have a VM with GC.
C# is just a plain Java copy after Microsoft got sued for J++ in 1998.
All other languages have problems with concurrency and threads that make them unsuitable for anything really.
So again, Java is the ONLY language/VM you can use on the server and on the client you still want a combination of C(++) and Java for performance + ease of use (avoid segmentation fault hell that no person should suffer).
If you saw bad Java code then that is not the fault of Java.
FWIW, I'm also pretty sure this type of comment (and therefor my comment?) are against the rules, but I've been rate limited for like 90% of my time here because I don't use burners to get into fights so dafuq do I care.
Anyway, hope you have a Good Friday. If it makes you feel better, you're much lower on the crucifixion scale than the even providing it's name.
"While I'm on the topic of concurrency I should mention my far too brief chat with Doug Lea. He commented that multi-threaded Java these days far outperforms C, due to the memory management and a garbage collector. If I recall correctly he said "only 12 times faster than C means you haven't started optimizing"." - Martin Fowler