[snitko]

What I'm saying is that a tool for webdev that wants to stand any chance of becoming popular must be able say to developers: here's the familiar MVC structure, you write your models, you create your views (hopefully out of set of widgets that are highly replaceable/customizable at any moment), we take care of talking to the server, saving your models to the storage and syncing between different instances of an app. Sure, there are problems to solve here, but since everybody does it their own way at the moment, I don't see no reason why we can't have a framework that solves them for you.