It will be like that at some point soon, just not now. Are you trying to make the point that because this technology is not yet perfect the fact that it can already do so much is unimpressive?
It doesn't have be to true for all models to be useful. Thinking about small models running on phones or edge devices deployed in the field that would be a perfect use case for a "printed model".
tailwind is very much not a problem for accessibility? if your content is semantic and you add the appropriate aria tags, whether or not you have 300 classes or 1 will make no difference for screen readers
Is that documentation useful? I haven't seen a well-documented codebase by AI so far.
To be fair - humans also fail at that. Just look at the GTK documentation as an example. When you point that out, ebassi may ignore you because criticism is unwanted; and the documentation will never improve, meaning they don't want new developers.
I've been coding for 40 years (23 years at an S&P500) and these coding agents write better documentation than I've ever seen from my peers. You just need to work with it and not expect it to do 100% of the work in one shot.
honestly this blog post was pretty off base. Current AIs have a limited ability to keep up with complexity and using known frameworks helps with managing that complexity. If you need to write everything from scratch every time you have to go through the process of scaffolding and harnessing the whole system from scratch. I don't think it's worth rewriting react from scratch every time you make a browser application, even in the best case it's just a huge waste of tokens.
reply