5 ms·
What a lot of people don't seem to realise is Ruby was eating Python pretty badly around 2005-2010 as Rails and Github exploded and other things like Vagrant, P
by antod 4y ago
What a lot of people don't seem to realise is Ruby was eating Python pretty badly around 2005-2010 as Rails and Github exploded and other things like Vagrant, Puppet and Chef took over.
Ruby had all the mindshare and hype over Python back then. To me as a Python fan, it felt like Python had peaked and wasn't going to grow further.
Then Node came along and stole the bandwagon followers that had flocked to Rails. The Ruby community was mostly the Rails community, so this kinda capped the growth of Ruby.
Python though had lots of competing Web frameworks, and other use outside webdev incl core tooling for Linux distros etc. Ansible (and Salt to a lesser extent) came along and stole back share from Chef/Puppet. Less fashionable Python kept on trucking along and was well placed to pick up machine learning.
- pyb 4y agoVery interesting, thanks !
- jb_s 4y agoDid all the Rails people wind up being JS / Node developers? AFAIK the .NET MVC setup was pretty influenced by Rails, but don't think Rails people went to .NET
- antod 4y agoNo, a good number of Rails devs stayed around and it became more of a mature community, but the hype driven growth/mindshare was over. There is a certain loud percentage of webdevs driven by fashion, and that portion follow the latest fashion around around. Rails lost some to Node, Node lost some to things like Go and/or React as API backed SPAs grew. I really doubt many Rails devs went to .NET. In those days Ruby was pretty bad on Windows machines (might still be?), and nearly all Rails devs were Mac users. I never knew .NET MVC was Rails inspired - I always assumed it would've been closer in style to the older Java MVC frameworks Rails was keen to disrupt in the beginning.