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.
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).
Alacart · · focus · HN ↗
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.
nicoburns · · focus · HN ↗
warkdarrior · · focus · HN ↗
Speed is probably not part of a web spec.
> wrong architecturally
Nor is software architecture (though web security specs may have some influence here).
freecodeio · · focus · HN ↗
"being a grandmother is not part of the bike frame spec so my grandmother with wheels is a bike"
nonethewiser · · focus · HN ↗
10000truths · · focus · HN ↗
<a href="https://youtube.com/watch?v=2G9ZGIOiPjY" rel="nofollow">https://youtube.com/watch?v=2G9ZGIOiPjY