I didn't start using Ruby (or Rails) until this year. The language is nice and makes my top 3 language list. That said, I find both Python/Django and Node.js b

I didn't start using Ruby (or Rails) until this year. The language is nice and makes my top 3 language list. That said, I find both Python/Django and Node.js both more productive than Rails for quickly building API-driven web-apps. More so this has to do with Rails, which has a number of warts and a tendency to require excessive configuration for all its pretty much patently false 'convention over configuration' spiels, than it does with Ruby. If there's a problem with Ruby, it's the inseparability of it and Rails. As things like node make using non-JS languages server side less appealing, use of Rails will decline, making Ruby decline. The main reason this hasn't happened is that there's not a standard groupthink-do-it-all toolkit for building things with node yet. And even when it does happen it will take years and years to go away. Just look at PHP. I'm going to go ahead and say it: Ruby will be the new PHP... And yes, I think it's fair to assume that Ruby usage is vast majority tied to Rails.