The really concerning part is how widely accepted these takes are outside of niche circles.
Yea, it's always been that way in the security industry and anything adjacent to it. A similar thing happened about 10 years ago, a group of academics released a whitepaper claiming they developed a framework that could automatically generate exploits from start to finish using some tool they wrote. Similarly, they didn't release it, claiming it was "too dangerous", but anyone who knew anything about exploit dev could read it and see it was *** by omission. Before that it was source code scanners making all sorts of crazy claims, fuzzing tools being released to the public, etc. The talking heads all melt down over these things and create FUD, which is driven by the industry types they interview who benefit from it. The problem, in comparison, is that AI seems a lot more plausible on the surface and does, to an extent, provide more useful information
when used properly and in the correct context than those tools do (which isn't saying much).
It's always what is not said that matters the most. The omission and missing contexts that make things seem scarier than they should be, but would only be visible to people who are technical enough to understand the entire scope. Concepts like reachability, reliability, and exploitability are lost on the majority of the industry to the point some vendors will give exploitability rating scores to bugs that are flat out not exploitable or reachable. This has long been an issue.
In the end, though, it doesn't matter. What matters is what people believe, that's where budget decisions come from and what will steer the industry.
Anyway, I'm practicing my "Welcome to Wendy's, what can I get you?" in the mirror.