Shadow: New browser engine made almost entirely in JavaScript

Post by SoftTalker » Fri, Oct 27, 2023, 9:42 PM UTC

DaiPlusPlus wrote: post #36

hughes wrote: post #32

Earlier quoted context omitted.

Sounds a lot like Flash.

except without the local-system security risks

Post by devman0 » Fri, Oct 27, 2023, 9:47 PM UTC

kube-system wrote: post #31

forgotpwd16 wrote: post #26

Earlier quoted context omitted.

Anything I tried returns fatal error. Is this really how it meant to browse a URL?

That sounds consistent with the intro: > known issues > basically every site doesn't work ;)

Post by dirtyhippiefree » Fri, Oct 27, 2023, 9:51 PM UTC

DarkNova6 wrote: post #2

This guy knows his audience well. He answers the question of "but why?" in the first sentence: > So I started making a browser engine (for fun) a few days ago, it felt kind of inevitable so here we are And I got to admit, it is pretty neat.

Post by rzzzt » Fri, Oct 27, 2023, 9:53 PM UTC

insanitybit wrote: post #45

EvanAnderson wrote: post #30

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.

Post by dirtyhippiefree » Fri, Oct 27, 2023, 9:57 PM UTC

xp84 wrote: post #23

IAmLiterallyAB wrote: post #18

Earlier quoted context omitted.

I dunno I'd say the new IE is Chrome. They basically control the ecosystem and everyone targets them when developing. "Best viewed with I̶n̶t̶e̶r̶n̶e̶t̶ ̶E̶x̶p̶l̶o̶r̶e̶r Chrome"

This is interesting. Chrome is the new i.e. as i.e. was in 2002, namely, most people regarded it as “the only browser any normal person would ever use.” Safari is the new i.e. in the sense that i.e. was in the late 2000s/early 2010s, meaning it’s the browser that we would like to ignore due to how weird it is compared to the browser we normally target. And how stubborn the vendor is in neither acting like the majorit…