exactly what rails has become to me. Models and API controllers that respond_to json. The client does the rest with Backbone, handlebars, css3 animations, ...
Same. I feel that for apps that are mostly server-side, Rails and Django are the way to go, especially CRUD apps. In the quickly emerging client-side app market, they often serve as an overly complex JSON api that requires too much configuration IMO.
While I like what Meteor is attempting to do by merging the client and server into one framework, I feel their approach is somewhat haphazard. Using it left a bad taste in my mouth, though t be fair I haven't done much beyond building a basic app for evaluation purposes. I'm currently evaluating Derby.js, and so far I'm liking it much more.
That said, convention has yet to be established for clientside apps, so either framework could fail. I do think that there is a niche for a framework that provides both the server and the client, however.
what I would like to see is a Rails type framework specifically geared towards building APIs. I like asset pipeline, give me that, I like gems, I like ActiveRecord, but take views, helpers and all that jazz. I will do that on the frontend thankyouverymuch
