I really love the Opus/Fable models but I'm honestly sick to death of the buggy product. The CLI always has some weird issue. Right now it doesn't even output messages before tool calls, it just swallows them and they disappear.
I don't like OpenAI as a company, but they appear to have QA, and that is probably enough to get me to switch.
Not really. They dramatically overhaul the products. Bloated staff are cut, old tech-debt-saddled systems are thrown out and rewritten. In some cases they basically just keep the brand and the database and rebuild the product around that, in a smaller and leaner manner.
"In their right mind?" I wouldn't start a project in anything other than TypeScript now. My platform is a monorepo across web and native mobile (Expo), and is TypeScript throughout. All my types flow everywhere automatically. Even the shape of a database table is shared with the native app with tRPC. Nothing can break the type contract anywhere. How would you do that with another language?
I was a bit confused what this adds other than just standard CDN-Cache-Control page caching that we do now. Some quirks I've found;
- You still get billed per request, whether the request hits cache or not (but don't get billed for CPU time)
- You now get billed for static asset requests! This makes no sense to me. "One thing to watch: when caching is enabled, requests that are normally free — static asset requests and worker-to-worker invocations through service bindings or ctx.exports — are billed at the standard request rate, because each one now consults the cache in front of your Worker." Yeah that sounds like a bug that just happens to generate them more money.
- The cache key automatically has the worker deployment version, so even gradual deployments populate their own cache which is nice
- It seems like you can set a totally custom cache key? But that was previously Enterprise only, can't see if that's still the case here.