Of course there're many hard questions. For example downloading an entire JS+HTML+CSS engine with every website is not a good approach, some caching must be done. There should not be version hell with every website asking for a different version of engine. But those questions could be approached as a more general web library issues.
But convergence on a minimal set of solutions is inevitable. Even though Geminispace could have hundreds of browsers, most people just use one of the most popular ones, like Lagrange.
Your solution wouldn't lead to a vibrant marketplace of competing web engines, everyone would just ship the equivalent of Chromium like they do now and call it a day.
https://web.archive.org/web/20150405004057/http://apple2info...
If site A can tell based on timing information that you probably visited site B recently, that's a pretty big privacy issue
This has largely killed cross-origin caching on the web, as I understand it
This repo in particular is for JavaScript host environments
Another thing is resource consumption where you likely want to limit cpu- and mem-usage.
WASM probably doesn't add much there.
The performance was quite adequate.
https://github.com/Shopify/javy/tree/main/crates/quickjs-was...
QuickJS JavaScript Engine - https://news.ycombinator.com/item?id=30598026 - March 2022 (67 comments)
A small but complete JavaScript engine - https://news.ycombinator.com/item?id=24867103 - Oct 2020 (146 comments)
QuickJS JavaScript Engine - https://news.ycombinator.com/item?id=20411154 - July 2019 (261 comments)
QuickJS JavaScript Engine - https://news.ycombinator.com/item?id=20404503 - July 2019 (3 comments)