5 ms·
We should convert browsers in to just a basic wasm window responsible for rendering html and running wasm. Then JavaScript and all it’s apis can become a shared
by Gigachad 4y ago
We should convert browsers in to just a basic wasm window responsible for rendering html and running wasm. Then JavaScript and all it’s apis can become a shared library as a wasm package or something.
- IshKebab 4y agoI'm not convinced that JavaScript is the difficult part. HTML/CSS rendering seems far more challenging.
- Gigachad 4y agoServo seemed to have pretty much got rendering working. I'm no expert but I feel like the hundreds of JS apis contribute a lot to the complexity. Just looking at the list here looks like it would take decades for a single person to complete https://developer.mozilla.org/en-US/docs/Web/API https://developer.mozilla.org/en-US/docs/Web/API
- NoGravitas 4y agoIt's the interaction of JS with HTML and CSS, combined with the expectation that all browsers will implement everything in ways that are functionally identical. Current "web platform" specs are in the form of algorithms/pseudocode rather than descriptions of desired behavior.
- guerrilla 4y agoSo... aren't we kind of coming full circle if we do that, going back to the JVM+Swing except this time it's boxed in a window and is more dynamic...
- diggernet 4y agoNo, we are coming full circle back to the days when a company might put up a website that was just a single Flash app, and you couldn't link directly to anything in it, you could only interact with whatever navigation they built into it.
- Gigachad 4y agoSingle page apps and wasm apps have full access to the URL and usually integrate well with it. With the age of SEO, everyone wants their pages fully linkable.
- spacemanmatt 4y agoSeems like that sort of retrofit could take a good month, given the rate of churn in JS/frontend land. </sarcasm>