zlacker

[return to "My iPhone 16 Pro Max produces garbage output when running MLX LLMs"]
1. zcbenz+Ys1[view] [source] 2026-02-02 11:46:08
>>rafael+(OP)
It is a bug in MLX that has been fixed a few days ago: https://github.com/ml-explore/mlx/pull/3083
◧◩
2. embedd+Gt1[view] [source] 2026-02-02 11:51:24
>>zcbenz+Ys1
Blog post dated 28 Jan 2026, the bug fix posted 29 Jan 2026, so I guess this story had a happy ending :)

Still, sad state of affairs that it seems like Apple is still fixing bugs based on what blog posts gets the most attention on the internet, but I guess once they started that approach, it's hard to stop and go back to figuring out priorities on their own.

◧◩◪
3. dahcry+RM1[view] [source] 2026-02-02 14:01:02
>>embedd+Gt1
I think you overestimate the power of a blogpost and the speed of bugfixing at Apple for something like this.

I almost guarantee there is no way they can read this blogpost, escalate it internally, get the appropriate approval to the work item, actually work on the fix, get it through QA and get it live in production in 3 days. That would only happen on really critical issues, and this is definitely not critical enough for that.

◧◩◪◨
4. tensil+QT5[view] [source] 2026-02-03 15:11:20
>>dahcry+RM1
It would have to be a very serious security bug. Even then, unless they've totally upended their software development workflows in the past couple of years, the Apple I knew extremely well from the inside couldn't turn around a software fix this quickly, from PR to OS release, even if its existence depended on it. There's simply too much bureaucracy and process around submitting anything, no matter how vital.
[go to top]