3 ms·

TIOBE index for December 2013 says otherwise: http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html http://www.tiobe.com/index.php/content/paperinfo/

TIOBE index for December 2013 says otherwise: http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html http://www.tiobe.com/index.php/content/paperinfo/tpci/index.... Ruby dropped 3 spots from this time last year (currently #13); if it is dying, it's dying slowly. For my work on the JVM, Scala in comparison is way down at spot #31; Groovy #47, and Clojure doesn't even break the top 50. Meanwhile F# is kicking some serious azz, soaring 27 spots in a single year to #20, impressive. Ruby should be just fine for the next several years, assume will drop down into the 20s as the static typing + FP movement takes root in the enterprise. 2014 should be a fun year for the JVM: Java 8, Scala 2.11, a possible Kotlin release, and whatever Groovy and Clojure have planned.

dham 13y ago
I used to look at the TIOBE index all the time, until I saw Visual Basic .NET jump a bunch of spots this year. I then started to question either TIOBE index or the people that are using Visual Basic.NET
- kamaal 13y ago
  Not sure what to say about TIOBE. It bases its results on search engine trends. They can't really tell the difference between Ruby(The stone) and Ruby(The language). Or Python(The snake) and Python(The language).
mountaineer 13y ago
Ruby is still holding its own in he HN hiring trends too[1] [1] http://www.ryan-williams.net/hacker-news-hiring-trends/2013/december.html http://www.ryan-williams.net/hacker-news-hiring-trends/2013/...
steveklabnik 13y ago
TIOBE results for Ruby won't be the same just quite yet, because December 25 is the traditional Ruby release date. Ruby will get a lot of press over the next week that's still in December, but wouldn't be counted yet.
vorg 13y ago
> and whatever Groovy and Clojure have planned Groovy's roadmap just added version 2.3, featuring "_Traits_", which were actually originally announced for version 2.2 [1], but were delayed so Codehaus could get a release of Groovy out the door in time for selling seats to their annual December GrailsXchange conference in London. In June last year, Codehaus/Pivotal had also announced a new meta-object protocol for Groovy version 3.0 [2] to come after version 2.1, but that was postponed early this year to make way for version 2.2. I don't think Groovy really has anything "planned" as you put it, rather they're reacting to external conditions. [1] http://groovy.329449.n5.nabble.com/Adding-Trait-to-Groovy-td5715831.html http://groovy.329449.n5.nabble.com/Adding-Trait-to-Groovy-td... [2] http://groovy.329449.n5.nabble.com/Groovy-3-tt5710334.html http://groovy.329449.n5.nabble.com/Groovy-3-tt5710334.html

dham 13y ago

I used to look at the TIOBE index all the time, until I saw Visual Basic .NET jump a bunch of spots this year. I then started to question either TIOBE index or the people that are using Visual Basic.NET

kamaal 13y ago
Not sure what to say about TIOBE. It bases its results on search engine trends. They can't really tell the difference between Ruby(The stone) and Ruby(The language). Or Python(The snake) and Python(The language).

mountaineer 13y ago

Ruby is still holding its own in he HN hiring trends too[1] [1] http://www.ryan-williams.net/hacker-news-hiring-trends/2013/december.html http://www.ryan-williams.net/hacker-news-hiring-trends/2013/...

steveklabnik 13y ago

TIOBE results for Ruby won't be the same just quite yet, because December 25 is the traditional Ruby release date. Ruby will get a lot of press over the next week that's still in December, but wouldn't be counted yet.

vorg 13y ago

> and whatever Groovy and Clojure have planned Groovy's roadmap just added version 2.3, featuring "_Traits_", which were actually originally announced for version 2.2 [1], but were delayed so Codehaus could get a release of Groovy out the door in time for selling seats to their annual December GrailsXchange conference in London. In June last year, Codehaus/Pivotal had also announced a new meta-object protocol for Groovy version 3.0 [2] to come after version 2.1, but that was postponed early this year to make way for version 2.2. I don't think Groovy really has anything "planned" as you put it, rather they're reacting to external conditions. [1] http://groovy.329449.n5.nabble.com/Adding-Trait-to-Groovy-td5715831.html http://groovy.329449.n5.nabble.com/Adding-Trait-to-Groovy-td... [2] http://groovy.329449.n5.nabble.com/Groovy-3-tt5710334.html http://groovy.329449.n5.nabble.com/Groovy-3-tt5710334.html