points by nerdypepper 2 days ago | 0 comments
my read is that with the right guidance, implementing the vast amount of the CSS spec for example, could be done easily with some AI assistance, the spec is incredibly well defined. just comparing the layouting and styling in blitz[0] (which does use agents), servo is lacking quite a bit, and the implementation of various features don't follow the spec exactly.
that being said, i entirely respect their decision of course, perhaps they will revisit at a later point in time!
[–] nicoburns 2 days ago
[–] Zecc 12 hours ago
Edge cases in the context of rendering border styles. Some unintentional word play there. :)
[–] fschuett 2 days ago
Yes, this was how I did it in Azul[1], which is „reverse engineered from the W3C spec“. But it still took a lot of „agentic debugging“ to get the same visual layout as Chrome[2]. It wasn‘t „easily“ done however and it‘s not yet stable.
[–] 8NNTt8z3QvLT8tp 2 days ago
CSS isn't super well defined actually, at least not compared with HTML or JavaScript.
My experience is that it varies greatly by feature.
Something like border styles, the agent was able to do pretty effectively. Although it still took a few hours iterating on it to get the performance characteristics and edge cases right.
More complex features like hoisting position absolute nodes and other layout features still take days to weeks of iterating to get something usable that isn't so fragile it'll blow up the next time you touch something.