I predict "data centers" are going to start being built but they'll say it's a distribution warehouse for motorcycle parts or a factory or something. There'll be a token amount of floor space set aside to manufacture pen cartridges but then there'll just be an incidental 200000 sq ft of server racks.
Lets assume one of two worlds - one where AI is constantly improving and one where the tooling is a dead end. In the first world the AI generated comments are no better than the commentary that would be generated in the next six months - in the second world the AI generated comments will obscure the human written comments.
In what world are AI generated comments actually value adds?
If the AI (or the person) ran into a non-obvious constraint, or some externality, or there’s a plan that just isn’t implemented yet- then the comment wouldn’t be able to be divined by the AI. But yeah just pointing the AI at something and saying “write me docs” will get you something at best equally good as what’s going to be available.
I was thinking you could probably get a fair bit of accessibility by using <div>s for your text rendering- or by maintaining a separate, hidden outline of DOM elements mirroring what’s on screen.
> maintaining a separate, hidden outline of DOM elements mirroring what’s on screen.
Is there any analysis on the efficacy of this approach? This is always my first thought in these discussions. Performance of WASM with native text IO. Being fully "hidden" one could just use semantic elements, skipping most layout div's, maybe in turn reaping untold accessibility benefits?
Being such a simple idea I cannot believe that it wasn't tried and abandoned before.
reply