‹ 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. nicoburns · · focus · HN ↗
      As someone who has spent the last 3 years implementing a browser engine from scratch full time (that currently passes ~half the 200k "css" tests that test style/layout/rendering), I find that (without a lot of close hand holding) the AIs are very far from being able to do this. They'll give you something that passes the tests, but it will do it a ridiculous way be far too slow to be useful (and is wrong architecturally such that it's not going to converge on a better solution).
      1. warkdarrior · · focus · HN ↗
        > far too slow to be useful

        Speed is probably not part of a web spec.

        > wrong architecturally

        Nor is software architecture (though web security specs may have some influence here).

        1. nsagent · · focus · HN ↗
          Not sure why you are being downvoted, but this is definitely a limitation of current models and difficult to optimize for. Anything you are not specifically optimizing for is essentially unconstrained: the model could learn it by pure chance, but the likelihood is exceedingly low.

          Techniques, like the newly announced RL-XAR from Meta [1] are being developed that will likely improve reward models and guide RL training to optimize for metrics like software architecture that are hard to verify otherwise.

          [1]: <a href="https:&#x2F;&#x2F;facebookresearch.github.io&#x2F;RAM&#x2F;blogs&#x2F;unslop&#x2F;" rel="nofollow">https:&#x2F;&#x2F;facebookresearch.github.io&#x2F;RAM&#x2F;blogs&#x2F;unslop&#x2F;

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.