[exabrial]

I freakin love SVG. Someday I hope we just end up with a browser standard:

* pluggable execution engine/memory model (WASM, JVM, CLR, etc)

* SVG output (binary or text)

From there, the developer can choose whatever model he wants to display a "page", no longer be limited to the Document Object Model.

[lpghatguy]

Once upon a time, Flash, Java, Silverlight, ActiveX, etc. ruled the web.

I think the world is _much_ better off today, with a common language and platform. I don't think those big third party runtimes could survive in the browser in today's threat environment.

[exabrial]

Unfortunately "common" means being what Google wants, and they abuse their market position to push whatever through (advertising support in an HTML client... what?)

[CharlesW]

> From there, the developer can choose whatever model he wants to display a "page", no longer be limited to the Document Object Model.

How are apps like AutoCAD Web, Photopea, Figma, Google Docs, Google Earth Web, and Flutter for Web apps (CanvasKit) different than what you're asking for? AFAIK developers aren't forced to use the DOM for applications where it's not the best choice.

[socalgal2]

The DOM (HTML) has the advantage that it's designed to be responsive to different displays. SVG is not