HN Explorer

12 comments

[ 4.2 ms ] story [ 44.1 ms ] thread
1vuio0pswjnm7
This says Webkit uses flex and bison for HTML parsing.
akling
It says it uses flex and bison for CSS parsing, which was true at the time of writing. It was replaced by a hand-written parser by Dave Hyatt in 2016.
octoberfranklin
How Browsers Work (2020): everybody just repackages Chromium.

...and Mozilla has some people dorking around with VR headsets.

the_only_law
I've known a few people (including myself) who have casually thought about what it would take to write a new browser engine. Obviously it's a titanic undertaking and unrealistic project but one thing I considered recently:

There are a ton of new API's the browser has added since HTML5 giving all sorts of capabilities. Hell, Chrome can access USB devices on your host if you allow it permissions.

But is there a canonical list of all standardized web API's somewhere? Something that a browser engine developer could look at to decide what API's are must haves and what are optional.

swiley
That's what the documents the W3C maintains are supposed to be.
userbinator
I have also had that thought for a long time (nearly a decade), remember seeing this article and progressed beyond thought to start writing some code, but naturally have plenty of other things to work on, so it's been very slow going. I have in mind only something comparable to NetSurf or Dillo, but even that is not trivial.
lucideer
> is there a canonical list of all standardized web API's somewhere

MDN[0] is probably the best list intended for this purpose, but it's easier to use if you already know what you're looking for.

While not explicitly its intent, I think caniuse[1] may be a better list for top-level browsing.

[0] https://developer.mozilla.org/en-US/docs/Web/API

[1] https://caniuse.com/ciu/index

la_fayette
Is there any newer work on that matter published somewhere?
dccoolgai
I must have read this 20 times. Great resource over the years... I've been looking for a newer version.