Live data from Hacker News

Shadow: New browser engine made almost entirely in JavaScript

goose.icu

41–50 of 303 posts

Re: Shadow: New browser engine made almost entirely in JavaScript

#41

There's a product here that's been waiting to happen for awhile. I've been anticipating somebody cross-compiling another browser engine to WASM but this works, too. Deliver your site only to the "inner browser" (that the user has no control over because it's heavily obfuscated and tricked-out with anti-debugging code) and you eliminate all ad blockers. Throw some DNS-over-HTTPS w/ certificate pinning in for good meas…

I was worried from the very start of the WASM tech, that it would lead to the end of the user-controlled client. You don't even really need an embedded browser, a motivated provider could create a completely proprietary protocol for rendering their pages.

Re: Shadow: New browser engine made almost entirely in JavaScript

#42
post #41

There's a product here that's been waiting to happen for awhile. I've been anticipating somebody cross-compiling another browser engine to WASM but this works, too. Deliver your site only to the "inner browser" (that the user has no control over because it's heavily obfuscated and tricked-out with anti-debugging code) and you eliminate all ad blockers. Throw some DNS-over-HTTPS w/ certificate pinning in for good meas…

I was worried from the very start of the WASM tech, that it would lead to the end of the user-controlled client. You don't even really need an embedded browser, a motivated provider could create a completely proprietary protocol for rendering their pages.

A browser is nice because the provider can continue to use their whole tech stack, hosting, dev tools, etc. Just wrap it in a proxy that only wants to talk to the "inner browser".

Re: Shadow: New browser engine made almost entirely in JavaScript

#44
post #15

There’s something really beautiful about creating a browser that can run in a browser. We can finally steamroll a lot of those cross browser incompatibilities by replacing the host browser engine entirely. It’s like the nuclear option to fight against the new IE (Safari)

It would be interesting to have Firefox available in WebAssembly

Re: Shadow: New browser engine made almost entirely in JavaScript

#45

There's a product here that's been waiting to happen for awhile. I've been anticipating somebody cross-compiling another browser engine to WASM but this works, too. Deliver your site only to the "inner browser" (that the user has no control over because it's heavily obfuscated and tricked-out with anti-debugging code) and you eliminate all ad blockers. Throw some DNS-over-HTTPS w/ certificate pinning in for good meas…

People could have been doing this with JS for a long time. This is hardly the first virtual machine in JS and it seems like overkill.

The far more likely way we'll see push back against Ad Blockers is by simply detecting that an Ad did not play and then refusing to display content until it does.

Re: Shadow: New browser engine made almost entirely in JavaScript

#47

Earlier quoted context omitted.

except without the local-system security risks

And no plug-in to download because everybody's browser has a highly-performant Javascript engine.

i don't feel having like extra virtual dom over the virtual dom of react, will make things highly-performant, god we need this doesn't happen. i wish to see the 0,1 fps react crud app, that will come from this.

Re: Shadow: New browser engine made almost entirely in JavaScript

#48
post #27

We are sorely lacking inner browser virtualization. This way web pages can virtualize other web pages internally via canvas and get true micro-front ends! Every component can be fully isolated from every other component and they will communicate via network requests to each other

Wait until scammers start adopting that technique for their fake websites. Each widget will then be responsible for its own bounded con text.

Re: Shadow: New browser engine made almost entirely in JavaScript

#49
post #41

There's a product here that's been waiting to happen for awhile. I've been anticipating somebody cross-compiling another browser engine to WASM but this works, too. Deliver your site only to the "inner browser" (that the user has no control over because it's heavily obfuscated and tricked-out with anti-debugging code) and you eliminate all ad blockers. Throw some DNS-over-HTTPS w/ certificate pinning in for good meas…

I was worried from the very start of the WASM tech, that it would lead to the end of the user-controlled client. You don't even really need an embedded browser, a motivated provider could create a completely proprietary protocol for rendering their pages.

[deleted]
Post reply on HN