[martinaglv]

Rails is a great framework. But posts like this and the one discussing how the team made product decisions around their caching strategy [0] and the horrible hacks that they did to make it work, for me are telltale signs that Rails is not the right tool for building web apps anymore.

Web development is evolving, as it ever has, and I believe that the next step is pushing the view layer to the client, and caching data, not html, on every step of the way. The major hurdle here is SEO, but I hope that when the right framework comes, it will offer an elegant solution to this problem.

[0] http://37signals.com/svn/posts/3112-how-basecamp-next-got-to...

[ds_]

I wouldn't say SEO is a major hurdle, there is prerender.io (http://prerender.io/getting-started#ruby) and countless other services which help (I made one).

[artellectual]

what criteria is used to define if something is a hack? or a feature? I mean if there is a pattern that works for some people and provides secure and clean way to achieve a goal how can you say that its a hack? I mean where do you draw the line between a 'hack' or 'beautiful implementation' I would like to know.