News for hackers. Stuff that matters.
Re:Google I/O and the Coming AI Battles by trasz4 on Monday May 15, 2023 @09:21AM (#35947718)
>It didn't work, but it still generated it.

So neither could generate the plugin, it's just that one of them lied about it.

Re:Google I/O and the Coming AI Battles by jeroenvlek on Monday May 15, 2023 @09:45AM (#35948048)
No, I suspect it's more the case that ChatGPT could generate it anno 2021, but can't anymore due changes in Chromium (I switched to Edge ultimately) and the Gmail API and Google Cloud Credentials workflow that I tried to add to it later.

It was interesting to see that ChatGPT annotated its code with pitfalls to avoid, that it actually didn't avoid in the code.

Re:Google I/O and the Coming AI Battles by disgruntledphd2 on Monday May 15, 2023 @10:30AM (#35948757)
Just like a real human;)
Re:Google I/O and the Coming AI Battles by trasz4 on Monday May 15, 2023 @09:47AM (#35948077)
>No, I suspect it's more the case that ChatGPT could generate it anno 2021

Why? I mean, why does it sound more plausible to you that it ever could, when we have countless examples of models lying (or rather hallucinating)?

Re:Google I/O and the Coming AI Battles by jeroenvlek on Monday May 15, 2023 @10:11AM (#35948409)
Because it was trained on old documentation, but I see your point. My original point was also not necessarily that ChatGPT was correct, but that ChatGPT at least gave something to work with, whereas Bard simlly refused.
Re:Google I/O and the Coming AI Battles by badrequest on Monday May 15, 2023 @11:15AM (#35949539)
The company I work for is building a browser extension that involves ChatGPT, and we can unfortunately confirm that it is, in fact, not capable of writing browser extension code.