Well, reading comments was interesting. A lot of "we need a faster horse" thinking, and, sadly, a lot of "we don't care about the users" thinking too. By "we do

Well, reading comments was interesting. A lot of "we need a faster horse" thinking, and, sadly, a lot of "we don't care about the users" thinking too. By "we don't care about the users" I mean thinking purely from the developers perspective, not from "make it harder for the database easier for the user" POV. And you can substitute database with developer. For those hoping for the rise of web, I'd suggest a few points to consider. The most important: what advantages does this kind of approach have compared to native — and to think about that form user's perspective. Run the same app everywhere? Ok, but typical user does not switch platforms that often on the same kind of device. Switching desktop/mobile is another matter, but there is an alternative to running the same everywhere, e.g. Apple's continuity. Ease of updates: just go to the same URL and you get the version. Well ok, what if I don't like the new version? How do I keep the old one? And how big advantage is that (again, from users perspective) compared to app stores and auto updating, that is already there? I am afraid that in five years from now we will see the same we saw five years ago: throwing in half-baked features into browsers to keep them "on-par" with native APIs and endless search for THE framework. The trouble is, that while native have those frameworks at foundation, web tech basically requires them to be bolted on…