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.

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.

https://12seasons.nyc/explore/

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.

https://neopets.fandom.com/wiki/Jelly_World

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.