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.
(
2 comments
| on HN
)
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
What do you mean by "more robust model relationships" if it's not something that's solved by Ember and Ember Data?