> A complete web framework has client-side components that facilitate two-way communication to/from the server, data binding, HTML5 history state-based page/vie

> A complete web framework has client-side components that facilitate two-way communication to/from the server, data binding, HTML5 history state-based page/view swapping, etc. In other words, the type of stuff being addressed by Angular, etc. < What you describe sounds very much like Plato's shadows (search for "Allegory of the Cave") when compared to a native application. Web browsers aren't operating systems. They weren't and still aren't designed to be general application execution environments.