3 ms·
> Presumably they'll eventually port Chrome to WASM. Then they can completely control the browsing experience. ...what? As opposed to shipping binary executabl
by spijdar 5y ago
> Presumably they'll eventually port Chrome to WASM. Then they can completely control the browsing experience.
...what? As opposed to shipping binary executables for an OS/arch combo, they'll ship a binary executable for WASM, and then a second binary executable for the OS?
If they want to take Chrome closed source and make it fully obfuscated, they can do that already, with or without WASM. Chrome is already closed-source, only Chromium is open -- and we know Chrome has secret sauce in it not from the repos.
- EvanAnderson 5y agoI didn't express that very eloquently. I expect there will be a WASM-based browser embedded within some (most?) websites, eventually. The public-facing webserver will serve-up the WASM-based "inner browser" and nothing else. Content will only be accessible via the "inner browser". Determined attackers will be able to extract the keys used by the "inner browser", for sure, but the average person won't be able to. It'll be packaged as a product, probably targeted at "traditional media" sites: Use this on your website and nobody can block your ads or bypass your paywall. You can use all your existing development tools, servers, etc, and it'll "Just Work".
- blt 5y agoWow, this is plausible and disgusting.
- jorvi 5y ago> and we know Chrome has secret sauce in it not from the repos Does it? I thought they have pretty much identical performance.
- tbodt 5y agoIt's minimal, not much beyond widevine and a set of hard coded API keys for things such as sync. The code that uses the API keys is all open source, only the keys themselves aren't.
- chrisco255 5y agoSecret spyware sauce.