Earlier quoted context omitted.
Kotlin can never replace Java as long as the JVM is relevant. This is like trying to replace C on UNIX, C# on .NET, Erlang on BEAM, or JavaScript on the browser.
I agree on the first 3... and most probably that's why I very strongly disagree on the last part. The way the languages "match" the environment in the first 3 examples is almost reciprocal to the way the language is a mismatch in the last one... "it just happened". Also seeing those first 3 environments even listed with the last one somehow does not seem fitting... but is still a nice pictures of current "Zeitgeist"…
Although I think if WebAssembly becomes a success, we will get the revenge of plugins.