Api

Anthropic’s lineup got two new names recently — Claude Fable 5 and Claude Mythos 5 — sitting above an already-strong Opus tier (Opus 4.6, 4.7, and 4.8). The marketing pages don’t really tell you what to use when, and the API differences are significant enough that a naive model-string swap will break production code. This post is the guide I wish existed: what these models are, how they relate to each other, exactly what changes at the API level, what changes behaviorally, and how to decide which one your workload actually needs. ...

The RPC Evolution: From gRPC to ConnectRPC While gRPC has been the go-to choice for high-performance RPC communication, ConnectRPC is emerging as a compelling alternative that addresses many of gRPC’s pain points while maintaining compatibility with existing ecosystems. What is ConnectRPC? ConnectRPC (formerly known as Connect) is a protocol that provides a simpler, more flexible approach to RPC. It’s designed to be: HTTP/1.1 and HTTP/2 compatible - Works with existing infrastructure Browser-friendly - No need for special proxies gRPC compatible - Can interoperate with gRPC services Developer-friendly - Simpler tooling and better debugging Why Teams Choose ConnectRPC Over gRPC 1. Browser Compatibility Without Proxies gRPC requires special proxies (like grpc-web) to work with browsers because it relies on HTTP/2-specific features. ConnectRPC works directly in browsers using standard fetch APIs. ...