This is the Claude-ism that I despise the most, when it states something that was never asked because it leaked from the prompt/context. Claude's writing has regressed so much, it's only usable for "raw coding" now.
They didn't actually steal in the sense that the information is still there on the internet.... About these shredded rare books, now we're talking.
If I may propose instead of "steal" I think we could agree to write they "Aaron-Swartz'ed" the information from the internet, what do you think, is this too harsh on Sam Altman or Carmen Ortiz ?
> Hmm, but there's a subtlety: does babel-jest + preset-typescript transform the file to CJS by default? No — babel-jest doesn't transform ESM imports to CJS unless @babel/preset-env is configured with modules: commonjs. Without preset-env, import statements stay as ESM in the output, and Jest's CJS runtime would fail with "Cannot use import statement outside a module" unless the project is ESM and running with --experimental-vm-modules.
> Hmm wait, actually babel-preset-jest... does it include preset-env? Let me recall: babel-preset-jest = { plugins: [require('babel-plugin-jest-hoist')] } plus istanbul for coverage. No preset-env. So ESM imports stay as-is.
> But wait — if the user's project is ESM (which it probably is, given the .ts extension imports — Node's type stripping requires ESM-style? no, type stripping also works for CJS-style .ts files with require... actually, --experimental-strip-types supports both CJS and ESM .ts files. But explicit .ts extensions in imports only work in ESM mode (CJS require doesn't allow extensions... actually, does Node 22+ allow require of .ts with flag?
Lots of “but wait” and and full sentences, nothing caveman-like or extremely short sentences without verbs like the GPT thinking trace above.
(this is with unsloth's Qwen3.8-27B-UD-Q5_K_XL.gguf with T° = 0.8)
Repeating myself here but anyone who has not yet watched the whole 2024 series of Prof. Sapolsky "Human Behavioural Biology" lectures series... really should.
I wouldn't call this a bias. More likely an A/B tested find that (1) algorithmic YouTube video-surfacing with keyword "graph" plus AI related name-dropping was effective, and (2) the already well established journalistic trick of leading with fear to trigger loss-aversion, as "prompting is soon dead" implies some threat of skills-value loss for the reader.
driving engagement to scrape the bottom of our ad-driven engagement dis-attention economy, tragedy of the commons pure.
reply