Wait, what?

http://www.indeed.com/jobtrends?q=scala%2C+groovy%2C+clojure...

apparently the matching algorithm isn't particularly smart... those are just the job postings that have the word "go" in it?

http://www.indeed.com/jobanalytics/jobtrends?q=scala%2C+groo...

edit: yeah, it isn't intended to be programming specific: "Indeed.com searches millions of jobs from thousands of job sites. This job trends graph shows the percentage of jobs we find that contain your search terms."

Indeed is unusable for the points made here.

Under the graphics you have the links to the respective jobs. Just check for yourself what these "Go" jobs [1] and the "Scala" jobs [2] are. "Haskell" jobs are also interesting.

And more: don't forget that currently even Php ads feature the infamous "experience with functional programming (Lisp, Clojure, Haskell) is a plus" line.

[1] http://www.indeed.com/q-Go-jobs.html

[2] http://www.indeed.com/q-Scala-jobs.html

Or C# http://www.indeed.com/jobtrends?q=scala%2C+groovy%2C+clojure...

> EDIT 26/10/13: I felt it important to only compare 2nd generation JVM languages. IMO it’s not fair to include the Java language itself because it dwarfs adoption of 2nd gen languages due to its omnipresence in the industry for over 20 years.

The article has just been edited with the above note.

I think the lead by Groovy from 2009 to last year should be ignored because job ads for Groovy programmers want them to use it as well as Java, but those for Scala programmers want them to use it instead of Java.

The list was limited to languages that developers actually like. Java is widely used, but not particularly popular as evidenced by recent polls here on HN.

OK, but how many programmers have experience in Java vs. (say) Clojure or Scala? The number of potential candidates also matters

In my experience it's pretty easy to find Java developers who can be productive in Scala. They already know the class libraries and the tooling/JVM.

I call BS here, the tooling for Scala sucks and without strict coding conventions and familiarization with said conventions you can get lost quickly.

The tooling argument can go both ways. For instance Visual Studio + Resharper is much much better than any option for Java. The Java profilers are nearly useless when compared to something like Red Gate and the integration with Sql Server on the MS stack makes database programming much easier.

The Microsoft build ecology is a little bit more mixed bag, but when compared to the explosion of choices for Java between Ant/Maven/Ivy etc. I'm not sure which I prefer.

As far as languages, working in C# makes working in Java so painful. C# makes so many better language/library decisions. The problem is that the JVM is a very compelling target platform (much more so than being stuck on Windows).

With those constraints Scala is a very nice language to use. In fact I dread every minute I have to spend in Java. Further everyone I know personally who has spent time in Scala feels the same way. I've literally never met anyone in person who prefers Java to either C# or Scala from a language point of view.

IDE for Scala sucks, mostly because Java developers are spoiled with Intelij IDEA and, to some degrees, Eclipse. It is still very usable. If you don't care about IDE, that is a non-issue.

What other Scala tools you're referring to? Scala can reuse almost all popular Java tools.

Also, can you elaborate on strict coding convention? do you mean operator overloading?

The IntelliJ Scala plugin is actually very good. We didn't have any strict conventions, just code reviews and good taste. Our devs didn't have any major trouble, but your experience may be different.