News for hackers. Stuff that matters.
Re:QuickJS Running in WebAssembly by vbezhenar on Sunday November 20, 2022 @03:24AM (#33679304)
Imagine something like "base system" with WebAssembly, bare bones HTML engine with canvas support and no CSS. So now you can just download your favourite JS engine, your favourite HTML, CSS engines. But browser does not necessarily need to sheep those. It would allow to lower the bar for entry into browser market. I think that even a single person could implement that kind of base browser.

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.

Re:QuickJS Running in WebAssembly by pjmlp on Sunday November 20, 2022 @05:11AM (#33679776)
Re:QuickJS Running in WebAssembly by krapp on Sunday November 20, 2022 @05:22AM (#33679822)
Check out Geminispace https://gemini.circumlunar.space - one of the design requirements of the protocol is that it be simple enough that a single person can implement a browser for it in a weekend.
Re:QuickJS Running in WebAssembly by makapuf on Sunday November 20, 2022 @06:57AM (#33680255)
I'm not sure, just for the fact that the best browser is something that could vary quickly, there might be niches, different native versions...
Re:QuickJS Running in WebAssembly by rictic on Sunday November 20, 2022 @11:59AM (#33682721)
Cross origin caching of resources is a privacy risk

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

Re:QuickJS Running in WebAssembly by jitl on Sunday November 20, 2022 @01:09PM (#33683480)
Ah yes, Java applets.