3 ms·
> Google Trends is not the place to be looking. It isn't. Author here. That is why I wrote the post and included many more sources, stackoverflow insights, Ti
by berkes 5y ago
> Google Trends is not the place to be looking.
It isn't. Author here. That is why I wrote the post and included many more sources, stackoverflow insights, Tiobe, rubygems.org, github etc. I'm sorry If I did not put this forward more clearly. The initial graph was mostly a hook, and not so much proof, as I mentioned in the first paragraph.
I presume you did not read the article, but if you did, could you help me write better articles next time, by showing me how I could put this point more forward? I did include it in the first paragraph, but maybe that gets overlooked?
- cutler 5y agoYes, I read the whole article but as you were going for Google Trends as your opener I thought I'd counter with job stats which you didn't really dwell on much in the rest of the article. Point taken, however, that a lot of Rails jobs are probably legacy code. I think the major factor in the relative decline of Ruby and Rails is that microservices are better served by languages with first-class support for async or concurrency.