what would a "good" browser tech stack look like?

replace JavaScript with Scheme, for sure. Separation of presentation and content is kind of pointless since the Web is an application delivery platform now. What would replace styling? What kind of markup?
Follow

@Moon i think it would be interesting to keep the http distribution mechanism. for applications just do away with all the html/css/js legacy. just provide a sandboxed VM with "devices". like already with WASM but without the legacy stuff. then just compile things with this VM as target.

ideally rendering classic pages should be a program for this VM.

one might say that it's too opaque, but the minified JS and crazy generated HTML&CSS of today is also not readable anymore.

guess this idea is a bit like envisioned by inferno or java, only using webshit ;)

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.