As programmers we complain about the ~1% from copilot-type models where the code is terrible. It is annoying but you can live with it.
A 1% error rate for many things, and with no bounds of how terrible the hallucinated error is, perhaps that's unworkable.
For example, Air Canada ended up liable for a discount which its AI chatbot made up.
There are other ideas how to make it more useful, but my point is that non-zero failure rate with unpredictable answers is not applicable to many domains.
In my opinion, this AI development stalemate is more layered. Big companies set such broad targets in a race to catch up with OpenAI that they lose focus on real use cases. So the loudest voices, those good at navigating internal politics, end up in a good spot to push their own ambition over actual customer needs or technical practicality. They set goals that sound just a bit more exciting than their peers, which pulls resources their way. But the focus shifts to chasing KPI's rather than drilling into real problems. Even when they know going smaller is smarter, knowing and doing are two different things.
It’s still a great time for small AI startups. My favorite kind is a team that quickly learn a business’s needs, and iterate toward the right interaction points to help. I think just staying focused on solving a lot of small related problems very fast, you can create something that feels like a real solution.
While the base technology is now there and is rapidly improving, a lot of the "glue" and "plumbing" is still missing. What is the best way to integrate these tools into our normal workflows / daily lives and so on?
It will take time...
Articles like the one above are not very useful as they completely miss the big picture.