One of the slides shows &quot;Rails is still the best choice for entire classes of apps.&quot;<p>&quot;Best&quot; is of course usually subjective, and this could spawn huge internet arguments back and forth about the relative merits of various solutions. But I think there&#x27;s perhaps an objective argument to be made that this isn&#x27;t true now, and won&#x27;t be true with Rails 5 and beyond.<p>I own a web + mobile app dev shop (Infinite Red). Our background is Rails, and some on our team have been using Rails since pre-1.0 (Steve Kellock, for example wrote the first Rails guides, and his name still appears on the website). We have loved Rails (and Ruby) for a long time.<p>But the concurrency and scalability difficulty of Rails isn&#x27;t just an opinion. As we&#x27;ve built larger and larger applications on Rails, the amount of effort put into making Rails scale gets disproportionately high. Not to mention server costs.<p>Yes, it&#x27;s totally possible to scale Rails. No, not every Rails app needs to scale to Twitter-level. We get that; we&#x27;ve been doing both for years.<p>When we discovered Elixir&#x2F;Phoenix [cue the groans, sorry] it felt like we kept the magic of Ruby on Rails while (in a single stroke) we also made a giant leap forward in concurrency, scale, and reliability. In my opinion, this is the direction the Rails community would be better off going. We felt so strongly about this that my partner Ken Miller wrote a piece titled &quot;Phoenix is Rails 5&quot;. <a href="https:&#x2F;&#x2F;shift.infinite.red&#x2F;phoenix-is-rails-5-f6d28e57395#.1z9pas7co" rel="nofollow">https:&#x2F;&#x2F;shift.infinite.red&#x2F;phoenix-is-rails-5-f6d28e57395#.1...</a><p>We don&#x27;t need Ruby on Rails to be great again. It&#x27;s done its job and we&#x27;re all better for it and grateful for it. We don&#x27;t have to become Node.js developers and abandon all the things we love about Ruby and Rails. We have a better alternative: Elixir&#x2F;Phoenix.