Presenting the JavaScript that can produce a client-side application could be by today's site developing standards, a little strict, because frameworks and libraries open the door, to applications ready for everyone.
However, that I work in this somewhat strict environment may have to do with old school experience, where a language would be known inside out before moving on to another.
Plus, I don't quite fit into, what I'd consider as the genius category, at least not with programming, but maybe with a talent for markets.
So, I'm taking a look at some javascript code,which is evolving into how an application could be structured, client-side, but there is need to rethink the security of applications at the client.
There is also a matter of why XML or XHTML verses HTML, and on that behalf, knowing everything evolves, including code and applications, when common sense prevails.
To clarify how common sense or what common sense is about, I have the idea that through contenteditable, an HTML feature, with the help of XML, we can deprecate forms. However, and example of common sense prevailing, is when with HTML they added document tags, such as section, header, footer, in part having to do with expected document yet site structure.
How the above demonstrates common sense, is we grew into the decision, as a result many documents and sites built on the same bases. Thus, common sense.
The difference with deprecating forms, is that there has been a try to change form applications with the appication of XML, also through XPath, and XQuery, and maybe even through JSON methods, but they might all fall short of an application's interpretation.
JavaScript, as I have discovered recently, provides code which has cut down enormousely on JavaScript itself. In short, some pretty sensible ideas. Add a client and server encrypted application strategy and we have a fairly powerful update.