Hacker News Reader

Comment by binarynate | Hacker News Reader

When I heard about the 2018 MBP today, my initial thought was that I would consider investing the cost and time of migrating from my 2017 MBP just to have a reliable keyboard. That Apple prioritized quieting the keyboard over fixing its reliability issues seems crazy to me.

View on HN

Speculation: I don’t think Apple will be able to fix the keyboard in this generation of MacBooks (generation meaning body type). It’s all about clearances, key travel, tolerances. The system doesn’t have room for a drop in replacement that could leave room for debris. That’s why they gave it a 4 year extension — because that’s probably when we’ll see a newer body generation with redesigned keyboard.

I'll wait at least a few months before believing any of this.

Apple being Apple, they might not be telling us whether this new keyboard actually does mitigate the issue. If they said something about this keyboard being more reliable, but then the improvement is not big enough for the bad press to stop, they'll look worse.

Not that I have any interest in defending Apple; I'm still using my 2015 MBP and avoiding the new ones, and I use Linux and Windows desktops. It's just that Apple can be really smart with PR sometimes, and I don't believe anything. Not even what they say they didn't fix.

My guess is that the expense of the repair program does make it a priority, but that they didn't have enough time between admitting he problem and releasing this round of machines to come up with a new design that both fixes the problem and is low-profile enough to fit in the space allocated. It's only been a few weeks, and they may have already begun manufacture on these (let alone design) at that time. I would guess that the next spec bump will include a fixed keyboard.

We don’t know whether they prioritized things. They’re more than rich enough to pay two teams working in parallel, and this may have been faster to fix, given the constraints they set themselves (weight, cost, materials, size, etc)

Don't forget the lead time in hardware development, not to mention problem identification.

The quieting may have been on the roadmap before the dust issue, or its magnitude and PR fallout, became evident.

(Not that I'm willing to cut Apple -- or anyone -- slack for lame keyboards.)

Reply on news.ycombinator.com