Hi Andrew, On Fri, Oct 7, 2011 at 1:34 PM, Andrew <[email protected]> wrote: > Do you know where I can find articles/statistics on Ruby adoption
It's going to be difficult to get good data. The biggest reason, IMHO, is that companies that do adopt RoR are going to be doing so for the productivity. If it works, they're not going to talk about it. That's what 'strategic advantages' are all about. Keep your mouth shut and hope your competitors don't figure it out. If you're convinced that you need hard data then I'd recommend looking for secondary indicators: growth of hosting providers is one. How many are there today vs. 2 years ago. Do they say anything about customer base? What about financial condition? There are tertiary indicators as well. Of those hosting providers, how many moved into new digs this year? They moving up? Or scaling back? I doubt very seriously that the leg-work will pay off (see below for why) but it would be an interesting exercise. If you do undertake it, I'm sure you'll be able to find a publisher who'll pay you a small amount (way out of proportion if you do the per-hour calculation, so don't ;-) ) to publish it. > and how I can convince my co-worker(s) that Ruby is the way to go? You probably can't 'convince' them. The choice isn't so much rational as it is personal preference. There are, IME, two ends to the programmer-preference spectrum: Java and Rails. The spectrum is most easily characterized by the individual's tolerance for delay in the gratification / feedback loop. I liken the Java end to the guys who build the huge, elaborate domino knock-down displays. Please understand that I am not criticizing at all; simply making an observation on human nature. The domino guys get a big dose of gratification when the dominoes all fall. But it's not about the dominoes falling. It's about the validation that all the setup steps were done perfectly. It's the validation that counts. If the dominoes all fell because the ground shook, there'd be no joy. So if I were you (embarked on organizational change) I'd ignore the developers who've already expressed a preference for Java. Focus on the ones that may be more attracted to a rapid-feedback model. Introduce them gently; perhaps via your local ruby brigade. Get them around some folks who are clearly having more fun than them. In any event, they'll get some free pizza ;-) Good luck and best regards, Bill -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
