← Back to context

Comment by jahewson

3 years ago

Actually a from-scratch web browser is being built:

https://www.fastcompany.com/90611677/flow-ekioh-web-browser-...

Also you should take a look at the WHATWG because it’s far more relevant than the W3C nowadays.

9 comments

jahewson

Reply
dmitriid  3 years ago

"The total word count of the W3C specification catalogue is 114 million words at the time of writing. If you added the combined word counts of the C11, C++17, UEFI, USB 3.2, and POSIX specifications, all 8,754 published RFCs, and the combined word counts of everything on Wikipedia’s list of longest novels, you would be 12 million words short of the W3C specifications"

https://drewdevault.com/2020/03/18/Reckless-limitless-scope....

No idea how Flow does it, but building a browser is nearly impossible.

  • fabrice_d  3 years ago

    It's well known that Drew Devault count is meaningless since it includes dupes, drafts, and unrelated specs. Still, the space to cover for a from scratch browser is huge.

    Flow didn't start "from scratch" recently, it's an evolution of a primarily SVG+CSS renderer for set top boxes. They also re-use Spidermonkey as their Javascript engine.

    • dmitriid  3 years ago

      > It's well known that Drew Devault count is meaningless since it includes dupes, drafts, and unrelated specs.

      It's not meaningless. Because in order to implement a browser, you have to figure out which of them are dupes, deprecated, drafts etc.

      And even that won't help you. Because a huge amount of "deprecated" standards are in the browsers. A huge amount of stuff in the browsers is still at the "community draft" stage, and yes, you have to implement that, too.

      Microsoft simply gave up, forked Chromium... And they still can't keep up: https://web-confluence.appspot.com/#!/confluence

      2 replies →

carapace  3 years ago

Flow browser isn't FOSS.

> WHATWG [is] far more relevant than the W3C nowadays.

Which is arguably part of the problem.