I don't see how Canvas or WebGPU is any different. People want a way to write high-performance UIs without all the complexity/legacy of the DOM. It makes everything more difficult, and because it makes things easier for browser developers isn't a valid justification to make the user experience worse. The users should drive the technology. I'm sorry this architecture you built almost 30 years ago isn't adaptive enough to meet the needs of your users. Instead they should create a new one for this use case (GUIs/applications) and keep it focused on documents.
> isn't adaptive enough to meet the needs of your users
I imagine if this conversation continues this will be quoted and argued against. My point is that it's not working well. People find workarounds to do amazing things with the browser, but they shouldn't have to. Give developers what they've wanted for 15 years. The various committees and working groups keep missing the mark, by a lot. See WASM, WebGPU shader language, etc., etc.. I'm sure it's more complicated than I realize, but if all you do is fail and disappoint, maybe your governance model and the people involved need some adjustment. Is anyone happy with WebGPU? Is anyone happy with Web Components?
> isn't adaptive enough to meet the needs of your users
I imagine if this conversation continues this will be quoted and argued against. My point is that it's not working well. People find workarounds to do amazing things with the browser, but they shouldn't have to. Give developers what they've wanted for 15 years. The various committees and working groups keep missing the mark, by a lot. See WASM, WebGPU shader language, etc., etc.. I'm sure it's more complicated than I realize, but if all you do is fail and disappoint, maybe your governance model and the people involved need some adjustment. Is anyone happy with WebGPU? Is anyone happy with Web Components?
/rant