Don’t call it a comeback: Java is still champ
The only problem Java has is experienced C programmers don&#x27;t build servers from scratch with it yet.<p>Once they take that responsibility, the debate will be over because:<p>&quot;While I&#x27;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 &quot;only 12 times faster than C means you haven&#x27;t started optimizing&quot;.&quot; - Martin Fowler <a href="https:&#x2F;&#x2F;martinfowler.com&#x2F;bliki&#x2F;OOPSLA2005.html" rel="nofollow">https:&#x2F;&#x2F;martinfowler.com&#x2F;bliki&#x2F;OOPSLA2005.html</a><p>&quot;Many lock-free structures offer atomic-free read paths, notably concurrent containers in garbage collected languages, such as ConcurrentHashMap in Java. Languages without garbage collection have fewer straightforward options, mostly because safe memory reclamation is a hard problem...&quot; - Travis Downs <a href="https:&#x2F;&#x2F;travisdowns.github.io&#x2F;blog&#x2F;2020&#x2F;07&#x2F;06&#x2F;concurrency-costs.html" rel="nofollow">https:&#x2F;&#x2F;travisdowns.github.io&#x2F;blog&#x2F;2020&#x2F;07&#x2F;06&#x2F;concurrency-co...</a><p>&quot;Inspired by the apparent success of Java&#x27;s new memory model, many of the same people set out to define a similar memory model for C++, eventually adopted in C++11.&quot; - <a href="https:&#x2F;&#x2F;research.swtch.com&#x2F;plmm" rel="nofollow">https:&#x2F;&#x2F;research.swtch.com&#x2F;plmm</a><p>This combined with the fact that Java doesn&#x27;t crash and you can easily hot-deploy the classloader (maybe 100 lines) means nothing can compete that doesn&#x27;t copy everything Java does VM + GC (hello C#, please don&#x27;t downvote).<p>To use anything else (than JavaSE without heavy deps.) on the server is madness.