Reading the full blog post, I think the summary was just poorly written (because it's hard not to read that sentence like all coding is redirected to Opus).
Fable 5 apparently can't be used for coding? (This is from Anthropic's announcement.)
> After a series of productive conversations with the US government, we're redeploying the model with a new set of classifiers to target and block more cybersecurity tasks. In the near term, some routine tasks like coding and debugging will fall back to Opus 4.8.
Flowers for Algernon. And, sadly, expect this from now on. You saw it with OpenAI releasing Sol/Terra/Luna with a chart showing how they weren't quite as good as Mythos. It's all messaging to the USG to try to avoid/minimize arbitrary review from multiple agencies. 'Hey, it's smart, but look how stupid it is at "cyber."'
Holy moly this is upsetting to see on HN. If even here we're cheering on data center bans, AI is on track to become the next Concorde, or nuclear in the US. AI is the most amazing tech innovation that I've seen in my career since I started programming Perl back in 1994... Gosh, I'm gonna be gloomy for the next day.
> Plus, turning off the ads should more clearly classify my blog as “non-commercial” for the various legal tests that impose greater liability on commercial actors.
Anyone know what these might be offhand? I think federal trademark law may sting more if used commercially. But what else could he be referring to?
Min release age sucks, but we’ve been here before. Email attachments used to just run wild too, then everyone added quarantine delays and file blocking and other frictions... and it eventually kinda/sorta worked. This does feel worse, though, with fewer chokepoints and execution as a natural part of the expectation.
Edit: bottom line is installs are gonna get SOOO much more complicated. You can already see the solution surface... Cooling periods, maintainer profiling, sandbox detonation, lockfile diffing, weird publish path checks. All adds up to one giant PITA for fast easy dev.
Ok, but 3 generations ago, shorthand was a core skill that any competent professional could read and extract MORE value from than laboriously typeset prose. Something similar is probably happening now with prompt-ese and human-to-human (vs just AI) writing.
Relatedly, I just registered for PACER to download court documents. It's pretty shocking that to get public legal documents the US Federal Court system requires full name, birthdate, address, phone, email, credit card info... and I THINK (it's past the initial registration page so can't confirm 100%) also mother's maiden name and 2 common security questions. Just a treasure-trove of PII if it ever falls into the wrong hands. (What's esp frustrating is even after going through this, I had to call a number and wait on hold for 1 hour to activate the account.)
Nuts to let a 42k starred project just fade away. Seems like it could really have been something. I remember being supe rimpressed w it when I installed it in its first few months.
Nowadays my writing (and maybe all of ours) has totally devolved into "prompt-ese." Much like days of yore where we all approached Google searches with acrobatic language knowing how to specifically get something done.
Now? I am pushing so much of my writing into prompts into AI where I know the AI will understand me even with lots of typos and run-on sentences... Is that a bad thing? A good thing? I am able to be so much more effective by sheer volume of words, and the precision and grammar is mostly irrelevant. But I am able to insert nuances and sidetracks that ARE passing vital context to AI but may be lost on people. Or at least pre-prompt-writing people.
A related technique used to work so well for search engine spiders. I had some software i wrote called 'search engine cloaker'... this was back in the early 2000s... one of the first if not the first to do the shadowy "cloaking" stuff! We'd spin dummy content from lists of keywords and it was just piles and piles. We made it a bit smarter using Markov chains to make the sentences somewhat sensible. We'd auto-interlink and get 1000s of links. It eventually stopped working... but it took a long while for that to happen. We licensed the software to others. I rationalized it because I felt, hey, we have to write crappy copy for this stupid "SEO" thing, so let's just automate that and we'll give the spiders what they seem to want.
That's great. What's also amusing is how you felt it necessary to provide the diacritical pronunciation guide for "Vaughan"... because I think to most native English speakers we can't imagine any other pronunciation!
Yep. And try "lieutenant" or "herb" on for size. (Edit: I guess "herb" is a bit of a complex one... originally from Latin's "herba" where the H was pronounced, but from UK it came most immediately from French's "herbe" with no H sound. So UK did somehow shortcut back to a more original sound.)
British aristocracy has been pronouncing their own surnames wrong for centuries on purpose. Cholmondeley is "Chumley" Featherstonehaugh is "Fanshaw." If you read it phonetically you mark yourself as an outsider. The misstake is the membership card. (Heck, even in Portland we locals hear about misprouncing Couch St probably every year in local press as some bar for membership to our own locals only vibe.)