It was really refreshing to read this response. Somehow it turned into &quot;I prefer framework X over Rails because....&quot; and Rails is lame because [fill in the reason here]. I&#x27;ve never even heard of Phoenix before this thread.<p>I guess Rails is stodgy and old. Technology changes very frequently sometimes too frequently. Less than 2 years ago everyone was getting on the Angular bandwagon. Now the conversation I&#x27;ve been having with employers is &quot;Yeah we&#x27;ve decided that React is going in a better direction so we&#x27;re replacing it with React.&quot;<p>Think about all that wasted code and time learning how to use the new framework so you can get what out of it? A few more miliseconds performance? Better more visually pleasing syntax? Learning the new hot thing? Does anyone ever think about the Return on Investment (ROI) relationship between learning something new, how hard it will be to learn that new technology and then figure out what you are gaining from using this new thing? Once you spend all that time trying to scale the steep learning curve for Angular or Ember or whatever new tech comes down the pike do you ever wonder &quot;what did we gain by learning this new technology? was it worth the trouble learning it? What benefit did it provide once you know how to use it?&quot;<p>I guess Rails is getting long in the tooth, but for the most part it does what I need it to do. It&#x27;s predictable, it&#x27;s readable, it&#x27;s organized, and best of all I&#x27;m just competent enough to use it. I&#x27;ve hit the wall trying to learn it and overcome most of the pitfalls and aggravations while using it. It&#x27;s just blowing my mind how eager many programmers are always pursuing the next technology. I&#x27;m all for change but only if the change is worth the aggravation. I don&#x27;t know if Rails 5 is a big improvement but really it&#x27;s good enough for most of what I need it for.