red_hare
Joined 15 years ago
Joined 15 years ago
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