Ask HN: What do you want in a javascript MVC framework.
For a project I'm considering making or extending a javascript MVC framework. What features or design aspects would you want in one? I personally want more robust model relationships and less boilerplate.
3 comments
[ 3.1 ms ] story [ 16.3 ms ] threadThe problem is analysis paralysis. Take a look at http://todomvc.com/ and note "Scroll down for 30+ more framework apps in Labs"
30+ more???? 30+ more?????????
What do you mean by "more robust model relationships" if it's not something that's solved by Ember and Ember Data?
I would argue that the ones we have are way too model heavy, and makes all kinds of presumptions what a model is.
Stuff that does not belong in a javascript MVC framework: -Bindings -Routes -Templates -Coffeescript