Main Content

Rails is Obsolete (But So's Everything Else)

About the Talk

September 18, 2010 5:45 AM

San Francisco, CA

San Francisco, CA

Back in the old days, you submitted a form to some URL and you got back some HTML. These days, you probably didn't hit submit, your URL probably didn't change, and what you got back was probably JSONā€”but you never saw it because it came in asynchronously in the background. Best practices around web applications are changing fast, driven by new browser standards, sophisticated JavaScript libraries and super fast JavaScript implementations. Why would a web framework design from 2004 still be appropriate? What can we be doing to adapt, or reinvent, our approaches to building web apps?

Ratings and Recommendations

Avg. Rating

Average based
on 1 rating

comments powered by Disqus