Rants
Questions
Soapbox
Best Practices
Apply today for a FREE subscription to CIO Magazine!
Tue, Oct 14, 2008 19:11 EDT

|
Posted by: Esther Schindler in Best Practices Topic: DevelopmentBlog: Developer Wisdom
Current Rating: |
Koders.com sees an increase in Ruby code searches as a sign of the scripting language's growing popularity. But is that what it means? Esther Schindler isn't so sure.
Black Duck Software just released data from its Koders.com search engine, and reports that "more Koders.com users are searching for Ruby code than ever before." According to their analysis, Ruby is now the fourth most requested language on Koders.com, after Java, C/C+ and C#. "The number of Ruby searches has increased by more than 20 times since 2004 and has surpassed alternatives, such as PHP, Python and Perl," the company says. (If you aren't familiar with the company: as they point out, "Tens of thousands of software developers use Black Duck's Koders.com daily to find open source code and other downloadable code.")
That's interesting. But I'm not sure that I'd agree with the company's conclusions that Ruby use is significantly on the rise. The thing is... I'm not sure I'd disagree, either. Because the Ruby community is a little strange.
I'm not speaking of the relative virtues of the Ruby language or Ruby on Rails; rather, I'm thinking of the behavior of its developers. Because—speaking as someone who has carefully watched pageviews for software development articles for several years—I know that anything I publish related to Ruby will always get plenty of attention from the Ruby community. (You're reading this, aren't you? See?) The whisper of a paen to Ruby (or even more exciting, any criticsm) attracts more Ruby devotees faster than black flies find a picnic in Maine.
But that doesn't mean Ruby is popular; it only means that it's an active and interested developer community. That speaks well (most of the time) for the passion of its users. But a party doesn't have to be large to generate a lot of noise; it just needs a big set of speakers and a loud rock and roll band.
The contrasting statistic is this: Ruby use really isn't all that much. According to Evans Data, which asks developers twice a year about their favored programming languages, only eleven percent of North American developers use Ruby today, for any part of their work. (It probably goes without saying that most developers use more than one language; this statistic reflects those who spend any of their time programming in Ruby.) About two thirds use JavaScript in any guise, just for comparison, but somehow that doesn't generate the same kind of passion.
Black Duck's Comparison of Language Searches
According to the folks at Black Duck, JavaScript has gone from 3 percent of all Koders language-specific searches in 2004 to 4 percent recently. Ruby is 5 percent. "There are 1.3 Ruby searches for every JavaScript search. JavaScript has moved up over time and is also ahead of PHP, Python and Perl," I was told. The graph they provided shows Perl, Python, Ruby, PHP and JavaScript searches and how they have fared relative to each other over time.
I am reminded of a message posted in a PC Magazine CompuServe forum in the late 1980s or early 1990s by the magazine's then-editor Bill Machrone. PC Magazine had just done its first, huge customer satisfaction research study, saying straight-up which PC brands were great and which were crap (in the eyes of the purchasers). If I recall correctly, they had something like 25,000 responses; it was a huge number, anyway.
As Machrone pointed out, at first glance it looked as though the best company
As VP of Development & Technology for FiveRuns, I have the chance to live deeply in the Ruby community. From that POV, I have another take on the data: collaboration is assumed in the community, i.e. it's baked in from the start and the increase in Ruby code searches is a side effect of that collaboration. In other words, Ruby developers have a strong tendency towards collaboration and this shows up as more frequent searches so they can find the right people and projects to work with.
I regularly see this collaboration - it ranges from loose & occasional to frequent and close. In the community, and at FIveRuns, we see this as a great feedback loop - course corrections occur regularly because of these collaborations and the right people are in the right place to solve the tough problems.
Certainly this isn't unique to Ruby - there are other communities where this is baked in. However, it is one of the beauties of the Ruby community and contributes to the quality of the results and growth we've seen.
I think the main problem, that soon or late everybody see, is that the interpreter is a dog slow crap ...