That's why I like LISP. Cut all the crap out and get back to the basics.

Agree with the wasted effort but IT has a very rich academic history in Computer Science. Current functional and reactive fads are a return to the 70s and 80s before OO poisoned the well. :-)

https://dzone.com/articles/11-concerns-for-the-java-ecosystem (#7)
In the context of this list of Java concerns, Java and the JVM have provided a phenomenally rich ecosystem in which to build software, the likes of which has not existed before. It is a natural progression to want to explore and evolve this ecosystem with different languages, be they Groovy, Scala, Clojure or Kotlin. There may well be some dead ends (JRuby? Jython?) but I cannot agree that this is wasted effort.

Agree +James Gemmell.  The JVM ecosystem has provided a rich enough runtime that we can return to those parts of Computer Science that were traditionally the bastion of academics. Clojure is a great example of putting Lisp into the hands of developers solving real world problems.  Though I wouldn't throw the OO baby out; it's just that most people do it wrong (Android source code is a great example of bad OOP)

After 5 years, I will come back to this record to see which language in your judgement right now is still alive, which has died.

Hmmm, you may have to export this record. Given G's rate of service attrition, I strongly doubt G+ will be around in 5 years time. ;-)

Everything you have said today wound be archived and let me chase you guys later :-P

Don't worry. The government are recording the... 'vibe' of this conversation anyway.

Isn't "the vibe" how Brandis defines metadata?

Exactly.