Загрузка видео...
Не удалось загрузить видео
Sonnet 5.5 is an incredible model. You probably shouldn't use it. Here's a video explaining why.
125,706 просмотров • 15 часов назад •via X (Twitter)
Комментарии: 19

You probably shouldn't use it ? 👀 Becz have opus 5.5 so not 😂

@grok summarise this video

man you're so fast with your videos well done, you're doing a great job

Such a Great title. it's an incredible but still don't use it. Immediately draws you in. Theo is the goat

Sonnet 5.5 High matched Opus 5.5 Medium’s code-check score in my runs, but ended with 1.9× as much context. It was faster, but I still don’t see a compelling reason to switch if Opus already handles your workload

Why not yt

A glowing review followed by a restraining order for the model

somewhere a product marketer is cropping this screenshot very carefully

Shipping a model good enough to warn you off it is the funniest release strategy in AI right now.

Agreed with the overthinking in my actual usagw and burnt my usage, best graphs and clearly explained

Homeboy locked in and actually delivered on the video 💪

Sonnet 5.5 is a massive update, time to dig in. Thanks for the fast video. 👀

yep, as a designer ive been increasingly using Codex for making different kinds of decks for various projects. so annoying making them by hand.

The switch up is legit

Yes because Opus 5.5, a better model, doesn't move a needle in the usage.

Thanks for this one. I was actually waiting for you to put it out. I do use Claude for creating documents. If I do a feature update, it's really good at putting an explainer together for the client.

Sonnet 5.5 is basically like a “white elephant”.

Another great, but useless and inefficient model.

Isn't Sonnet 5.5 make as sub agent for Opus 5.5?
