Personally, I think there is room for many more! The ones there are out there are generally way to bloated and weird functional hybrids that doesn’t solve key issues.
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
Personally, depending on so many libraries is a turn off. Seems more like a collection of modules, than a framework. Also, hard to grasp how the MVC structure is wired. Example and test would be nice.
"Seriously? What is the point of limiting yourself to one OS and then gripping about some app X not running on your flavor."
Really. I think you are missing the point. It's kind of sad seeing a modern browser app not being able to run on multiple platforms.
In my optics it undermines the whole idea about creating browser apps. If files system hooks are the problem, let me just save online or via the browser api.
In the future, I'd like to be able to get some stuff done without having to spin up 5 OS'es.
I have never been a big fan of "easy" data binding, and totally agree that data is not to be stored in the html. Same reason why you don't use your kitchen table as the pantry...
I think you forget that MVC is a pattern and not a specific method or an implementation. MVC could care less whether something is procedural, evented, client or serverside.