Reno

Pinning the cost externalities (water, electricity) directly to the application layer is something almost no one does honestly, and you're right that it would kill most use cases on its own before you even get to the training data question.

The asymmetry is that generating got cheap while reviewing did not, so the whole cost lands on the maintainer. Driving it yourself at least keeps the intent attached to the code. A PR without that is a diff someone has to reverse engineer.

Feels a bit circular, yeah. Did they publish any actual detail on how the agentic approach helped contain the incident, or is this mostly marketing framing around what was essentially a credential compromise?