←back to thread

Web Browser Engineering (2021)

(browser.engineering)
679 points MrVandemar | 1 comments | | HN request time: 0s | source
Show context
currygen ◴[] No.41848445[source]
It's refreshing that browser engineering seems to become a "trend" now. The ecosystem is quite sparse with basically only Google, Apple and Mozilla defining it. I'd like to see forward into a future with more independent browser engines.
replies(4): >>41848575 #>>41848648 #>>41848756 #>>41850985 #
01HNNWZ0MV43FF ◴[] No.41848575[source]
Something that uses less RAM would be nice. Other than that and the spyware from Capital-G Google Chrome and Capital-M Mozilla Firefox, I don't have a problem with it being sparse. It's millions of hours of de-duplicated work.

I'd like an alternative to HTML though. If I was to make a browser maybe I'd focus on replacing HTML because I can't stand it, and replacing js just because the runtime is heavy.

Like, a browser that only runs wasm and has nearly no JS runtime would make me giggle

replies(2): >>41849961 #>>41854462 #
PaulDavisThe1st ◴[] No.41849961[source]
> Like, a browser that only runs wasm

That's not a browser.

More or less by definition, a browser is an application that can use HTTP (and potentially other protocols) to make requests to other systems and retrieve stuff described using HTML (and possibly other formats).

Sure, a tool that just loads wasm and executes it would be fun (and probably exists, at least for the local case). But it's not a web browser.

replies(1): >>41850229 #
1. 01HNNWZ0MV43FF ◴[] No.41850229[source]
As opposed to current browsers that run wasm and JS I mean

Yes there would be a DOM in addition