Rumors of Ruby’s Demise

Ruby is presented as still being the most programmer-friendly mainstream language the author has used. The post says that if developer joy matters, Ruby will stay competitive, and that pressure to build better implementations can also improve performance. It also suggests that future concurrency features from Matz would likely be well considered and easy to use.

Reading notes

#

• The author acknowledges bias because of long-term Ruby work and income from Ruby books and screencasts.
• He describes himself as a hacker rather than a Rubyist and says he values Ruby for being pragmatic and fun.
• He argues that concern about concurrency and scalability is overstated because only large organizations usually face those problems strongly enough to drive new languages.
• He says many programmers care more about development velocity than raw server capacity.
• He points out that some scaling gains come from rewriting components after the team understands the problem better, not from changing languages early.
• He compares choosing tools to using a pocket Leatherman first and bringing out the big toolbox only when needed.
• James Edward Gray’s anecdote says an all-Ruby SOA system handled a traffic spike to 40,000 requests per minute, then was being tuned further.
• The post warns against peer pressure to adopt new frameworks just because they are hot.
• It says new technologies usually solve specific problems, and similar surface traits do not mean two applications have the same problem.