red_hare
So their base price is 1/5th of Opus 5.5 per token, but if you want "highspeed" it's 2x that and then I guess it generates 2x the number of tokens as well?
That might suggest that Opus is competitively priced after all.
A question I've been struggling with, however, is what are the artifacts that live at this level? Are they design docs? Are they standardized? If I read your design docs, will I understand the code or do I need to "decompile" (use a coding agent to explain) to get back to this level of abstract for me to edit it?
It's a humbling reminder that not all fields of knowledge application are verifiable in post-training.
The phones are watches are primarily sold on annual leases through carriers. And no one is buying them for the chips, it's all camera and form factor.
The macs, on the other hand, can more easily swap between chips in manufacturing. And the form factor is pretty static. So Apple, in a race to have the best chip in the field at any given time, is just releasing them as soon as they're ready.
I agree the whole "m5 max > m6" is confusing, but I think they figure only the nerds who learn the specifics are going to care anyway.
You're right that it's probably a little too in the weeds, but it's also a nice clear and fun objective that teaches you the basics. Like building a TODO list in JavaScript to learn webdev or a Gameboy emulator in C++ to learn how a CPU works.
I've found a lot of success pointing claude at locally downloaded docs over llms.txt URLs but not sure how to scale the pattern for a bigger project.
1. They're just a python file so they work with python editors
2. There's no hidden state
3. I can import from them
4. I'm not accidentally committing base64 encoded image output anymore
But for a single like button, an effect slider, or magic search bar? It would be be a lovely touch.
I think, over time, it's going to become a SQL / NoSQL sort of divide. There will be the right kind of RAG for the job and lots of forcing the wrong kind because the developer doesn't understand the nuances.
This isn't a critique of your product. It's just that the a beige-orange theme, the pill components, and the left-border highlight give me that visceral reaction as reading a paragraph littered with em dashes and "not X but Y." It makes me take you less seriously.
Cool demo otherwise.
But car batteries, brake pads, tire pressure sensors are all becoming increasingly software-locked in. We're lacking open standards for this stuff.
Given it requires a Steam login of a certain age to register, I suspect this is just to limit the scalpers.
I'm sure I'm not the only one, but I've gotten so aggressive about monitoring for this. I do most interviews zoomed in on the candidate's eyes and I rubric on how they "thought" through the problem, not just the results.
Thankfully the interview tools are catching on as well and now tracking this like browser focus, number of monitors, window size, and sending notifications when any of those change.
Also wrong, gay marriage had 60% support before Obergefell v. Hodges.
And it's not actually necessary for it to exist at the API level. It's a pattern. Making it API-side is just an optimization.
To do it client-side: 1. Define a single tool, tool_search 2. List the names of your deferred tools in context (or tool_search's description) 3. When tool_search is called, match the query against the tool names (or names + descriptions) 4. Append the matched tool def to the context in a new <system>-esque tag
Claude Code (as of the leak) does this client side. You can even see the custom matching function and A/B tests about whether to include the descriptions.
Whether or not that tool definition comes from MCP or a local definition is kind of beside the point.
Its crazy that people are still discussing this. It's ancient history. Deferred tool loading, large contexts, and prompt caching have made 2026 completely different from 2025.
Also, the "CLI saves token" debate really falls apart when step one of using the CLI is running "--help". The problem remains: if knowing how to call the thing isn't in parametric memory, it has to be in context.