[PaulDavisThe1st]

Even after all that, you still haven't made explicit the thing that needs to be explicit for any of this to make any sense:

    ".... for UI *IN A BROWSER*"

I know it's convenient to forget the millions of us who spent years and continue to spend hours implementing UIs outside of a browser context, but it certainly doesn't feel very polite.

[troupo]

1. I've already answered about "in the browser"

2. Even in the browser it's the worst possible system

3. The original comment I was replying to didn't make any references to "in the browser", and explicitly talked about things like QML and XIB which are very much not in the browser.

[PaulDavisThe1st]

Sorry, somehow I really misread your comment. Not sure how I was so wrong in my reading.

Needless to say I agree with everything you've written, and also appreciate the use of a DAW screenshot to make the point.

[troupo]

No worries :) DAWs have now become my go to example of complex interactive UIs :)

[PaulDavisThe1st]

That said, there are examples of these being implemented in-browser. Not sure how any just use the canvas/webgl vs. the DOM (I know examples that do each).

[CharlesW]

I don't think anyone's trying to be impolite or diminish What Came Before, but HTML is used for lots more than websites and browsers. (Examples that come to mind are email, desktop and mobile apps, ebooks, and digital signage.)

[troupo]

Yes. Unfortunately we've not inly settled for one of the worst systems, but we additionally further settled for limited subsets of it as well (email, ebooks)