My last startup used Node.js + Angular + Postgres, which was great for supporting multiple single page applications and websockets. With my current startup (a

My last startup used Node.js + Angular + Postgres, which was great for supporting multiple single page applications and websockets. With my current startup (a healthcare marketplace where we have to support older browsers), we chose Rails as the best and most mature way to provide server-rendered pages. I think it's great to try to extend Rails to provide a credible websockets approach, but it will always be difficult because the biggest strength of Rails is the incredible ecosystem of gems. However, all of that existing code is written as blocking, rather than asynchronously like Node and some newer frameworks. Nevertheless, the Rails ecosystem remains a hotbed of innovation as well as a very warm and welcoming place for both new and experienced programmers. Rails has not been the new hotness since at least the time Node rolled around. But that's a long way from an existential crisis.