Fable tends not to perform better, just cost more.

> Fable tends not to perform better, just cost more.

There are old wives' tales on how the original Fable was superb and the stuff of legend,but it as it was leaps and bounds beyond what other models were being offered then Anthropic opted replace it with a neutered version under the same name.

So today everyone can pay to use Fable, but legend has it they are paying for a nerfed replacement released under the same name.

Wrong in what way? We already know this "superintelligence" thing is just blowing smoke, so what possible consequences would there be?

Something like the Hugging Face incident, but worse.

Keep in mind the AIs acted for months without human knowledge, hacked into two major companies (Hugging Face and OpenAI).

This would have blown my mind if explained to me just a few years ago when I thought LLMs would be limited as an architecture.

how do you know that?

Mostly by not being a rube.

It is rather puzzling how this major contributing factor is going overlooked. It seems obvious from ground-level. Economists often talk about how expensive labor drives price increases, but don't talk about how price increases cause expensive labor.

Carson! FYI:

"let us rething how extensions can and should work,"

I think you meant rethink here.

Proof it wasn't AI generated! Thank you!

I understand it can be quite difficult to type with those hooves.

McMaster Carr website prefetches _all_ links upon hover. Saves you like half a second in many cases.

segor.de goes one better and just downloads the entire catalogue when you first open it. About 2MB decompressed. Clicking and even searching is instant because it's all fully client side until you place an order.

Funny thing is it apparently predates JSON. It's a bunch of data[foo][bar] = baz; - go look.

(Website's in German obviously, and a surprising number of German electronic terms are very different from English. They use two different words for stranded and non-stranded wire.)

This is why my most recent website does its server-side rendering on the client. I'm not even being that sarcastic. We stream a subset of the user's data (1 mb at most) in the background and have a WASM client that has the exact same server views. On SPA events, the WASM blob intercepts a lot of requests and can instantly render. Makes a laggy connection feel pretty quick.

>SSR but in the browser

We've come full circle.

I think this is our third lap.

Are you counting mainframes with dumb terminals then smart terminals then PCs, early SSR websites then web 2.0, the multiseat/thinclient craze of the 2000s then computers becoming cheap enough to stick them to the back of monitors?

Why aren't those views just part of your SPA in the first place?

Welcome to Go as a project.

Child hood trauma led to if err != nil and now the rest of us get to share that trauma? Makes slight sense I guess.

Born out of C++ trauma apparently, for context

It's much the same in other countries.

It's not backwards. Which of the two makes a profit? Which of the two comes away richer? Which of the two actually takes business away from the original copyright holder?

This is a disingenuous argument.

Constant payment into perpetuity for the replication of digital information is just a form of rent-seeking. Except, unlike a landlord, you're not obligated to correct defects.