HTML was originally for relatively static documents and still works relatively well in that domain. But for almost everything ELSE it turned into a convoluted m

HTML was originally for relatively static documents and still works relatively well in that domain. But for almost everything ELSE it turned into a convoluted mess, requiring UI rocket science to manage, and bloating up development. I observed it takes roughly 3x the staff to produce and maintain custom small and medium CRUD applications than the IDE's of the 1990's. Some claim the added flexibility and easier deployment[1] of web based applications is worth this 3x increase, but usually that's tech staff saying that, not business owners. They want get-it-done-on-budget, not eye candy, if given a clear choice. We have to come clean and admit that job security is keeping us technical people from being objective on this. A convoluted standard increases demand for specialists. I suggest the industry form 3 browser-based mini-standards: A) Art/Gaming/Charts/Entertainment, B) Document-oriented (current HTML may almost be good enough), an C) "productivity" oriented data and CRUD. That way each can focus on doing its niche right instead of trying to be one-size-fits-all. [1] With a good stateful GUI-markup-over-HTTP standard, we probably wouldn't need local installs to get decent GUI's.