thevegetarian

Ruby the language isn't bad, but the VM is very primitive.

That's a lot like arguing that since my C++ code hasn't segfaulted or leaked memory in 10 years that garbage collection in Java is essentially pointless. I also don't see much need for classes in that new-fangled C++ thing since my assembler code has a "solid" feel to it and has worked reliably for years. Being too lazy to initialize registers correctly is not a reason to add more features.

Very important feature that. I usually choose my language based on such important considerations. Busy deleting my Scala code as I write this and rewriting it into Java code 5-10 times the size so I don't have to suffer from being confused between null and None. Something in the back of my head tells me it has something to do with the infamous null pointer exception...

Commonly used and popular are not the same thing. I happen to know a number of developers who hate Java, but code in Java for a living. By popular I mean number of developers who actually enjoy using the language. There are better ways to measure usage e.g. job ads on indeed.com.

The popularity of a language is important. If developers don't like a language they won't use it. Look at Ruby a few years ago as an example of a popular language which was hardly used which became on of the most widely used scripting languages in modern times.

According to Wikipedia work on Nice slowed around 6 years ago... http://en.wikipedia.org/wiki/Nice_(programming_language)

Xtend and Ceylon faring extremely badly, Kotlin only slightly better. Looks like a 2 horse race with Scala and Clojure in front.

Not so fast... Clojure also getting some votes.