Earlier quoted context omitted.
But this is basically the absence of a query syntax, a way to query via natural language, and not just get back a list of results, but have it almost synthesize an answer. To everyone who isn't a software developer, this is a new paradigm with computers. Hell even for me as a software dev it's pretty different. Like I'm not asking Google to find me info that I can then read and grok, I'm asking something like ChatGPT…
For years I've just typed questions, in English, into browser search bars. It works great. Maybe that is why it doesn't seem like a new paradigm to me.
Using Google with Bard, the regular results from Google search for me are:
1) Is it possible to show warnings instead of errors on ALL of eslint rules? 2) Configure Rules - ESLint - Pluggable JavaScript Linter 3) ESLint Warnings Are an Anti-Pattern
None of them answers the question directly. Bard on the other hand returns with:
To configure ESLint errors to warnings, you can either: - Set the severity of the rule to "warn" in your ESLint configuration file. - Use the eslint-disable-next-line comment to disable the rule for a single line of code. For example, to set the severity of the "no-unused-vars" rule to "warn", you...
I'm not familiar with eslint and have no idea if the answer is correct, but it's definitely a more concise and to the point, and an upgrade over the regular search.