Every time I use Composer 2.5 I have to spend a bunch of time cleaning up its mistakes. It is unusable compared to GPT 5.4 or 5.5.

My time is more valuable that I will use a model that doesn’t f** up my code base.

I think we need to be explicit about the domains we're applying Composer 2.5 to in these discussions.

I mentioned here (https://news.ycombinator.com/item?id=48766275) how poorly it handles my specific use cases. My coworkers in DevOps and frontend UI swear by its cost-effectiveness, whereas I strongly prefer the reasoning capabilities of Opus 4.8 and Fable 5.

Composer 2.5 seems to be SOTA for Helm charts and React/Vue, but, for my usecases it absolutely struggles spectacularly when tasked with rigid body dynamics or kinematic logic.