6 ms·

I have a sneaking suspicion that Kubernetes is another Ruby on Rails waiting to happen: https://trends.google.com/trends/explore?date=all&geo=US&q=ruby%20on%20

• WrtCdEvrydy 8y ago
  Good for me, I must made about 500,000 from moving Rails to other more modern stacks... I'll learn Kubernetes just as it dies off and start moving people's shit to whatever's next.
  • james_s_tayler 8y ago
    That has to be one of the best strategies out there. So long as you just read the trends right.
    • WrtCdEvrydy 8y ago
      Best of both worlds, I can paid to learn the new tech and the old tech...
  • danmaz74 8y ago
    Out of curiosity, which more modern stacks were those?
    • WrtCdEvrydy 8y ago
      Most NodeJS with ReactJS frontends. Some of them had already started doing React for frontend and just need the backend work.
      • quickthrower2 8y ago
        Smart move. They’ll have to hire you again in 5 years tome for another migration.
      • danmaz74 8y ago
        React for a js front end makes a lot of sense. But, for the back end, what advantages did they expect by moving to node - besides having the same language in the back end?
        • kolme 8y ago
          Code reuse. For example you can use the same React components for (pre-) rendering pages on the backend so the site feels quicker to load.
          • danmaz74 8y ago
            You can pre-render React with Rails too (and other frameworks).
• Aeolun 8y ago
  We’re still in the popular phase. https://trends.google.com/trends/explore?date=all&geo=US&q=ruby%20on%20rails,Kubernetes https://trends.google.com/trends/explore?date=all&geo=US&q=r...
• adjkant 8y ago
  The geographical map of Rails vs Kubernetes is quite interesting: https://trends.google.com/trends/explore?date=all&geo=US&q=ruby%20on%20rails,kubernetes https://trends.google.com/trends/explore?date=all&geo=US&q=r...