Wednesday, June 6, 2007

Why are there no Awk Jobs?

My buddy over on OReilly Ruby Blog posed the profound question why there are no Ruby jobs?.

Although I was shocked that Dice (for Chicago) just brought up 32 hits. Amazing, far more than the last time I checked. Compared to 41 for Python, 202 for Perl, 784 for Java, and 351 for C#. And don't forget awk. Five whole jobs in Chicagoland.

To quote:

I guess it could be a lot of things, any of the below or a combination might be to blame:

  • Lack of good marketing for non-web oriented Ruby
  • Assumption that Ruby is not general purpose as a side effect of the success of RoR’s marketing
  • Technical issues that I can’t think of that make it an inferior choice to other languages
  • Ruby adoption might be in nature slower than Rails adoption, but on it’s way
  • MRI isn’t robust enough for the ‘enterprise’, so companies are waiting on JRuby

Shitty documentation. Lack of decent built-in APIs. Rubyforge sucking big-time compared to CPAN or Cheese Shop. All the Japanese? Everything starting with R. Not coming default on Real OS's (OSX doesn't count, spare me). Being cute? Not being used in the application infrastructure of any Real OS's. (FreeBSD is an anomaly in that it doesn't require Perl, all the other distros I can think of Require at least Perl and some like Ubuntu, Python). All the crap about programming being fun? A significantly large number of Ruby-ists (or RoR-ists) that use OSX? Should I go on?

Alls of these equate to non-ENTERPRISE.

Waiting for JRuby? Please. That is so rich I almost spit my fruit bar onto the screen. And I think JRuby is cool. Maybe that nobody does any "real work" (meaning the pays $$, blogging doesn't count) in Ruby. Well, except maybe Matasano.

No comments: