3 Dominant Themesin the Discussion
| Theme | Key Take‑away | Supporting Quotations |
|---|---|---|
| 1. Confusion over Apple’s AI stack and tooling | Commenters are frustrated that Apple’s new Core AI, Core ML, and MLX are not clearly distinguished, and they call for better documentation that explains feature parity and benefits. | • “Yes. From the CoreAI docs: If your app uses model types other than neural networks, such as decision trees or tabular feature engineering, see Core ML.” – earthnail • “Seems they planning to replace it but overall now I’m really confused about this and mlx and coremltools. They should do better work explaining the benefits (and cons) of it and any feature parity between coreai, coreml and mlx.” – pzo • “My reading of it is: … Core AI is for models that run everywhere already and also need to be fast.” – LoganDark |
| 2. Excitement about on‑device / local AI and large foundation models | Many users are bullish on the ability to run substantial models locally on Apple silicon, citing fast inference, low power draw, and the arrival of new foundation‑model updates. | • “i am more excited about the ondevice foundation model update that is coming … (not much info yet)” – franze • “Running Qwen 3.6 35B can really do a lot… 75 tokens/sec with GGUF on an M1 Max” – dofm • “The new siri models will be some variant of the gemini models. This framework seems to be more generalized than that though.” – ankit219 |
| 3. Practical limits, cost & privacy of on‑device AI vs cloud | The conversation circles around real‑world constraints: battery life, compute limits, future pricing of cloud APIs, and Apple’s Private Cloud Compute strategy. Users debate whether local inference can truly replace hosted services. | • “Apps would not be respectful and end up draining users’ batteries to zero in no time.” – tyre • “does edge deployment … drive enough revenue to get this to happen?” – dofm • “Free server‑size model access for apps with <2M downloads, getting the same privacy guarantees” – connectsnk (referencing Apple’s private‑cloud offering) |
Takeaway: The thread reflects confusion over Apple’s fragmented AI frameworks, strong enthusiasm for local high‑performance models on Apple hardware, and a pragmatic debate about the limits, economics, and privacy implications of shifting AI workloads onto devices.