Simon Ritter

This is correct but all OpenJDK binaries provided by Oracle via jdk.java.net will only have updates for six months (until the next JDK release). There is no concept of an LTS for these binaries.

Sure, but public updates for JDK 8 end next January, at which point you will need to pay to get security patches and bug fixes just like JDK 11.

Yes, but Kotlin applications compile to bytecodes, which run on the JVM (as does Scala). There is no difference between JDK 11 for Java, Kotlin, Scala or any other bytecode compiling language.

Azul (full disclosure, I work for them) still provide support for 32-bit versions Java on Windows (and Linux). Check out our website for more details, https://www.azul.com/downloads/zulu/zulu-windows/

Of course, the simple solution to reducing long GC pauses is to use a JVM where the collector does not support the concept of a full STW compacting collection, i.e. the Zing JVM from Azul :-).

Sure, for web applications almost everyone uses HTML5, CSS and Javascript. However, your comment was that Java has poor performance, which it does not. You provide no evidence to back up your argument. You claim that nobody uses it and I give you Twitter as an example. Now you claim that people like Twitter are not worried about performance; you couldn't be further from the truth. I know several of their JVM engineers and performance is exactly what they focus on. I work with many clients using Java in high-frequency trading systems where latency (and therefore the performance of Java) is absolutely paramount. As a single example look at LMAX, which is written in Java. They chose Java precisely because of the performance and scalability they could get from it. Ever heard of Cassandra? That's written in Java and used for many high-performance applications. Feel free to provide some sort of counter-argument to this beyond, "Java is not good at performance".

If you read (and understood) my response, I gave you one example of why it is completely unreasonable to make the statements you do about Java performance. Just one example, I can easily provide more. Nobody prefers bytecodes and a VM over native code? Are you serious? Ever heard of a small company called Twitter? All of that is run on the JVM.

Oh here we go, another ignoramus claiming that Java is slow, awful and nobody in their right mind should use it for serious applications. Sorry, but Java is the most popular programming platform on the planet for many reasons, performance being just one of them. As a simple example allocating memory in C is significantly slower than in Java. Just look up how Java uses pointer bumping in the young generation (which is approximately 6 machine instructions) compared to all the work that happens when you call malloc(). Your response is almost as bad as this article (and less comprehensible).

You're absolutely right; that was a typo on my part. Elements in the stream will either be taken (takeWhile) or dropped (dropWhile) while the Predicate test() method returns true, not until it return true. Apologies for the confusion.