Yeah, using a kilowatt GPU for string replacement is going to be the killer feature. I probably shouldn't even be joking, people are using it like this already

▲

charcircuit 11 hours ago | parent | next [-]

When the condition for when you want to replace is hard to properly specify, AI shines for such find and replaces.

▲

Aachen 10 hours ago | parent | next [-]

This one is literally matching "innerHTML = X" and setting "setHTML(X)" instead. Not some complex data format transformation

But I can see what you mean, even if then it would still be better for it to print the code that does what you want (uses a few Wh) than doing the actual transformation itself (prone to mistakes, injection attacks, and uses however many tokens your input data is)

	▲	charcircuit 9 hours ago \| parent [-]
		That can break the site if you do the find and replace blindly. The goal here is to do the refactor without breaking the site.

▲

lelanthran 7 hours ago | parent | prev [-]

> When the condition for when you want to replace is hard to properly specify, AI shines for such find and replaces.

And, in your opinion, this is one of those cases?

	▲	charcircuit 3 hours ago \| parent [-]
		It is because the new API purposefully blocks things the old API did not.

▲

littlestymaar 10 hours ago | parent | prev [-]

This ship has sailed unfortunately, no later than yesterday I've seen coworkers redact a screenshot using chatGTP.