There's definitely a saturation point depending on the complexity of the problem you're solving. For example, any model can write a small shell script to resize a video with ffmpeg for you right now, so it doesn't matter whether you're using a local Qwen model, GLM, or Fable. They'll all do a roughly comparable job and you'll end up with a working script that does what you need.

Then you have things like CRUD apps, where a model needs to write some SQL, make a service endpoint, serialize some JSON, etc. Here a local model might have a bit more trouble juggling all the pieces, but any hosted model will do just fine. If your day to day job involves working on CRUD apps, then it's basically a solved problem now.

The cases where frontier models matter are when you're solving genuinely complex problems, but that's not what most people are doing day to day. So, paying an order of magnitude for a model that has capabilities to solve problems outside the range of problems you actually work on becomes a waste of money.

There's going to be a market for these models from people who really do work on complex things on regular basis, but the question is how big that market is. Additionally, open models keep getting better, and GLM 6 or DeepSeek v5 could end up being another big jump in capability where they fully close the gap with Fable. At that point, even more of the market becomes covered by these models leaving truly complex cases on the frontier.

Another thing to consider is that most big problems can be broken down into smaller ones. That's the basis for how programming languages are structured. We have primitives which are arranged into functions, that get bundled into classes or namespaces, and so on. So, you don't need an infinitely capable model to solve big problems. You just need to be able to break large problems into smaller ones, and a model that's smart enough to decompose a problem to the point where it becomes tractable.