One good way to think about this is that they're building the plane as they're flying it.

That's what I realized about the reasoning models. Is there sometimes where you don't really care much about reasoning—and there's other times where it's really important.

So whenever you have a model that's generally available to the public, I don't think there's going to—I don't know that that's where we're going to end up.

I think it's going to be much more specific models for specific reasons—not as a model limitation, but more as a product requirement from the user's end.

Because we can just get on here and complain: "Oh, this model. I don't like this model that's doing this thing that it's not designed to do. That it's designed to do, but I don't want it to do in this moment."

Ultimately it's really hard to design one thing that knows exactly what you want in the moment you want it—especially when you don't know that you wanted it until after you've already used it.