Chrome DevTools now uses Gemini to help with JavaScript Errors in the console

Post by [deleted] » Fri, May 17, 2024, 10:40 PM UTC

sublinear wrote: post #21

Why does this exist? The example AI-generated explanation shown doesn't seem any more helpful than the original error. It just states the same information in a long-winded manner. Errors and warnings are already deterministic and unambiguous. Why introduce the opportunity to confuse people or just be plain wrong?

Post by [deleted] » Fri, May 17, 2024, 10:41 PM UTC

jraph wrote: post #26

> To use this feature, make sure that you: > Are located in one of the supported regions and are at least 18 years old. Seriously. For to get an explanation of a freaking JS error message. Now for a debug session you need a Google account, to agree with a legal notice, a privacy notice and be at least 18 years old and boil I don't know how many liters of water for generating a text that could be static in some docume…

Post by [deleted] » Fri, May 17, 2024, 10:41 PM UTC

influx wrote: post #23

[flagged]

Post by [deleted] » Fri, May 17, 2024, 10:42 PM UTC

wiseowise wrote: post #25

Another reason to ditch Chr*me.

Post by MrDarcy » Fri, May 17, 2024, 10:57 PM UTC

olliej wrote: post #35

ajross wrote: post #32

Earlier quoted context omitted.

People have been trying to get compilers and runtimes to generate better errors for decades, and sites like StackOverflow exist to backfill the fact that this is a really hard problem. If an AI can get you a better explanation synchronously, doesn't that in fact represent an improvement in the "messages"?

No because all the AI is doing is making up statistically plausible sounding nonsense? The best case output is a correct summary of the documentation page - why add a huge amount of power use alongside massive privacy invasion just to deal with that? I have read and re-read this article and I don’t understand how this is better for any purpose other than “we put AI in something, increase our stock price!”