Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To be more precise, it is right above the backspace/delete key on every other device that has one. So they decided to stay consistent and put it in the exact same spot here too.

When you make an extended version of a keyboard, it makes sense to me to stay consistent and not rearrange keys on the part of the keyboard that's shared between the extended and regular-sized versions.



> To be more precise, it is right above the backspace/delete key on every other device that has one. So they decided to stay consistent and put it in the exact same spot here too.

Is it really more precise to say above the backspace/delete vs. the absolute top right corner? Until this product rolled out, those statements would have been practically equivalent.

I'm thinking of this like I do the power button. On my Macbooks, that's one and the same with touchid, and is in the top right corner (and yeah, above the delete key, but for me the significance is the absolute position). The power button on my non-Apple keyboards is also in the top right, above the numpad - albeit not a touch sensor as well. Not where the eject key is, but in the absolute top right on the old Logitech Wave I'm typing on right now.

Quite honestly, I didn't expect I'd be in the minority on this one. I suppose this is why design teams exist. I wonder if there's a better spoken version of me at Apple arguing like an asshole for the exact same thing!


> Is it really more precise to say above the backspace/delete vs. the absolute top right corner?

Yes, because that specifies the position of the key in all keyboards, no matter what extra keys they might have.

If your keyboard doesn't have an F-button row, then your numerical row is at the very top of the keyboard. If your keyboard has an F-button row, then your numerical row is the second row from the top. But in reality, it is in the exact same place it has always been, right above the the QWERTY row.

We don't shift the numerical row to the top when we add an F-button row. Neither do we shift arrow keys or Enter key to the far right when we add a numpad. So I don't see why touch ID button should behave any differently.

In general, extended versions of keyboards add more stuff compared to the smaller versions, but they never mess with the layout of buttons present in the original.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: