I felt like I entered some time wrap, was this written in 2007/2008? Can't believe someone writing this in 2013 since so much of the arguments are from those da

I felt like I entered some time wrap, was this written in 2007/2008? Can't believe someone writing this in 2013 since so much of the arguments are from those days. That rails shops with more than 9 months of development are festering piles of magic code is not news. Let's take a step back and ask why would anyone write a new Rails app in 2013. When rails came out in 2003/4 (yes it is now a decade) it was really neat. However things have changed dramatically as far as client/server capabilities are concerned and it is wise to revisit assumptions. Key points 1. Javascript is now anywhere from 20 to 50 times faster than it was in 2003. 2. Javascript is supremely better than ruby in building UI and DOM manipulation. It is even faster in doing straight computations. 3. Clients are now 10 times more powerful (approx. memory/cpu-core wise) and even mobile phones have more memory/capability than a desktop computer of 2003. 4. Rails remains the slowest and least efficient server side language by a huge margin. 5. Mobile/Tablets have their own UI/View concepts and work best with a server API that just serves json type data. So why would you bottleneck your application through a rails server. Best to have your server be a provider of services (security, data store, integration with backend etc). Most computation and UI manipulation is probably better done in javascript. What is that rails provides that say PHP cannot provide in this new way of doing things. It feels like with, say, AngularJS + server API (not doing everything) we are much better served by having computation distributed in the right way.