Yeah, I think we're talking about the same thing. But taking your example, virtualized list problems recur every few years. They were a problem in Swing, in JSw

Yeah, I think we're talking about the same thing. But taking your example, virtualized list problems recur every few years. They were a problem in Swing, in JSwing, in Flex, Flash, on and on. I mostly use DataTables, which is its own endless hall of mirrors. They're among the glitchiest UI elements because so many things come into play. They try to do everything and be everything for every application and for all browsers, right? But more importantly, there are a lot of different ways of approaching the problem of virtual lists. You could do offscreen rendering in the DOM, or render on the fly, or reuse existing elements, or go nuts and draw the whole thing on a Canvas. So this is like the last thing you would want to rely on an AI to actually write. You could definitely let it embed some existing solution, but then you wouldn't know why it had some code that shifted everything down 3px for Safari.