3 ms·
> then the solution is to make it chew through the quota quicker This is terrible from a product perspective. Right now they can subsidize workflows with poor
by solenoid0937 7mo ago
> then the solution is to make it chew through the quota quicker
This is terrible from a product perspective. Right now they can subsidize workflows with poor caching performance.
If OSS hacked clients become a big thing, they can't do this anymore.
- Daviey 7mo agoHow does that make sense? If Claude code can have great performance by optimised caching and Opencode doesn't.. I'll run out of quota using a third party client and have a terrible experience, and the choose to use Claude code instead because wit is superior. So why not simple quota counting?
- solenoid0937 7mo ago> So why not simple quota counting? Consider this: you are Anthropic. There are some Claude Code used cases that will have poor caching performance. Let's say these are 10% of your use cases. You explicitly don't count cache misses right now because it would make the UX poor for these use cases. It's no big deal since the remaining 90% of use cases can subsidize the 10%. Now open source clients become a thing. Instead of 10% of usage having poor caching, it grows to 50%. You can no longer subsidize those users because the economics don't work. You have to start counting cache misses and the UX goes to shit for everyone.