4 ms·

> They reject it because they're inherently conservative Not just that. They reject Ruby because 1. It's very slow and continues to be very slow despite all t

by laureny 13y ago

> They reject it because they're inherently conservative Not just that. They reject Ruby because 1. It's very slow and continues to be very slow despite all the performance work being done on it (nod to JRuby). 2. It's just hard to hire Ruby developers, who are getting more scarce every year. These are the symptoms of a dying language.

subsection1h 13y ago
> It's just hard to hire Ruby developers, who are getting more scarce every year. Citation? Why would Ruby developers be getting more scare? Are they retiring earlier than Java developers?
- laureny 13y ago
  > Citation? http://www.indeed.com/jobtrends/ruby%2C+java.html http://www.indeed.com/jobtrends/ruby%2C+java.html > Why would Ruby developers be getting more scare? Are they retiring earlier than Java developers? Ruby developers have always been a tiny fraction of the number of Java developers, and that fraction has been steadily decreasing, while the Java developer pool keeps increasing (Android helped quite a bit growing that population).
  - ksec 13y ago
    I think it is actually the Ruby Pool is increasing much faster then there are Ruby Devs.
lobster_johnson 13y ago
> 1. It's very slow Benchmarks these days show Ruby 1.9/2.0 as being a wee bit faster than Python, and it's improving. That's still much slower than Java, of course, but then that's a bad comparison; Ruby and Python are better comparisons.
- pkolaczk 13y ago
  It is also still much slower than Groovy and Scala, being at the same time similarly or even less expressive and having worse tooling. Therefore I can't see any reason to move from e.g. Java to Ruby. When Java is not expressive enough I'd consider using Groovy/Scala/Clojure.
jmagoon 13y ago
If you provided sources, I would maybe think this was something beyond a personal axe you have to grind. Seeing as how you've fit the classic "respond to every post" argumentative style.

by laureny 13y ago

subsection1h 13y ago

> It's just hard to hire Ruby developers, who are getting more scarce every year. Citation? Why would Ruby developers be getting more scare? Are they retiring earlier than Java developers?

laureny 13y ago
> Citation? http://www.indeed.com/jobtrends/ruby%2C+java.html http://www.indeed.com/jobtrends/ruby%2C+java.html > Why would Ruby developers be getting more scare? Are they retiring earlier than Java developers? Ruby developers have always been a tiny fraction of the number of Java developers, and that fraction has been steadily decreasing, while the Java developer pool keeps increasing (Android helped quite a bit growing that population).
- ksec 13y ago
  I think it is actually the Ruby Pool is increasing much faster then there are Ruby Devs.

lobster_johnson 13y ago

> 1. It's very slow Benchmarks these days show Ruby 1.9/2.0 as being a wee bit faster than Python, and it's improving. That's still much slower than Java, of course, but then that's a bad comparison; Ruby and Python are better comparisons.

pkolaczk 13y ago
It is also still much slower than Groovy and Scala, being at the same time similarly or even less expressive and having worse tooling. Therefore I can't see any reason to move from e.g. Java to Ruby. When Java is not expressive enough I'd consider using Groovy/Scala/Clojure.

jmagoon 13y ago

If you provided sources, I would maybe think this was something beyond a personal axe you have to grind. Seeing as how you've fit the classic "respond to every post" argumentative style.