‹ BackHN Continuity

Thread

Bez: Generating a browser engine from specs and tests

126 points · 49 comments · nerdypepper

  1. Alacart · · focus · HN ↗
    This makes a ton of sense to me with the huge corpus of web standards that exist. In theory we should be able to generate a browser from those specs, it just took a massive amount of effort before. Maybe if things like this get some traction, some of the human time spent implementing the spec could be spent on creating more/better specs, allowing for even better generation too.

    Edit: replies are making good points about AI capabilities and where the effort really goes. Let’s just say that I meant this in an aspirational sense, rather than where the rubber actually meets the road today.

    1. kazinator · · focus · HN ↗
      Where in the web standards do you find specifications like how bookmark toolbars and menus should be organized, or that Shift-Ctrl-T should bring back a tab that was closed?
      1. looperhacks · · focus · HN ↗
        We're talking about a browser _engine_. The shell/chrome is irrelevant in this context
        1. fabrice_d · · focus · HN ↗
          But some parts are far from being trivial engineering and are not part of any specs. Just consider the security infrastructure (multiprocess, sandboxing etc.) and how that impacts the overall design of the engine itself.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.