Eh, I don't see much of a need for a client side framework. Just client side templates. jQote2 <http://aefxx.com/jquery-plugins/jqote2/>works great for that. Submitting data via ajax is as simple as calling ajax('url',[data to be saved], ':eval'). Templates are the slowest part of a webserver (usually), and since pages can take a long time to load from template compilation, it makes sense to offload that to the client. As far as database access is concerned, you're going to be waiting on the server no matter what database you have, so no need to abstract that out, just make it async, which is what ajax is good at. Every client side MVC framework seem to be overkill anyway.
On Tuesday, April 2, 2013 12:41:10 PM UTC-7, Arnon Marcus wrote: > > Backbone is not comparable to any full-stack MVC - it's a mere, well. > "backbone" of an MVC framework... It's hideously verbose in boilerplate, > and by itself doesn't do much... "You" are doing most of the work with > backbone (which would be, again, mostly boilerplate...). For any sane > deployment, you have to gather a bunch of plugins (from variant degrees of > maturity/documentation/communities, and that don't necessarily play > together). > Marionette/Chaplin/Gepeto might be better, but I haven't researched them > very much... Knockback also seems interesting, but kind of an weird > abomination.... > > Angular is "SUPER"... It is genius... And has everything one might need, > but it's somewhat of a mystery... Learning it is like solving an enigma... > Directives? HTML-Compiler? Dirty-checking? On the client? Are you serious? > Wouldn't that be Sloooooowww in a big project? > And DOM templating? Is that wise? Given that the DOM is the most broken > API in the web stack? > It might be a glimpse of the future, but I'd rather wait for the real > thing (Shadow-DOM, Composable-Elements, HTML6...) > > > I think that for most web2py users, Ember would feel more "natural" > that basically any other framework out there... > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
