61–70 of 186 posts
They fixed the keyboard, increased the max memory to 32GB and stuck to their guns on the touch bar - and that all seems reasonable to me. (I’m far more annoyed by Microsoft removing ESC as the dbox cancel key for errors in Excel than the disappearance of the ESC key)
The escape key never disappeared. It’s just a soft key rather than a physical one. I use it hundreds of times a day with vim and have never had problems.
Earlier quoted context omitted.
Well one person's band-aid is another's significant fix, and only the data will tell. EDIT: Below is wrong, but keeping it for posterity: Note that the desktop Magic Keyboards that employ the butterfly mechanism do not seem to have the same key sticking issues as those on MacBooks, so it's likely they felt the fundamental design of the mechanism was fine but that it did need an additional silicone barrier for the low…
The Magic Keyboards still use scissor switches.
Earlier quoted context omitted.
Hopefully Touch ID fixes the issue with having to enter a long password?
I've been completely underwhelmed by the touch ID on my MBP. Faster just to type every time, or unlock with my watch
They fixed the keyboard, increased the max memory to 32GB and stuck to their guns on the touch bar - and that all seems reasonable to me. (I’m far more annoyed by Microsoft removing ESC as the dbox cancel key for errors in Excel than the disappearance of the ESC key)
> After all, Apple told The Verge that “this new third-generation keyboard wasn’t designed to solve those [dust] issues.”
Earlier quoted context omitted.
I've been completely underwhelmed by the touch ID on my MBP. Faster just to type every time, or unlock with my watch
The watch is usually how I unlock my computer, but I'm surprised to hear you're underwhelmed by touch ID, as in my experience the touch ID is very accurate and quite fast (and I use it multiple times a day for authorization of things, especially unlocking 1Password).
I'm sorry, but are people actually more concerned with the sound of the keyboard than the arrow keys? It took me a week to get used to the sound. Six months in and I still can't reliably hit the arrow keys. It's as if they're designed to be as difficult as possible.
I just hate that in 2018 I have to do such a stupid thing to a new computer from what's supposed to be a premium computer hardware company.
Apple users have enjoyed the perfect keyboard layout for 15+ years, only for some idiot manager to come along and change the layout for brainless aesthetic reasons. It's infuriating because the change is so unnecessary.
I won't buy or accept another Apple laptop until they go back to the old layout.
This is a pretty sad day that sonething like this can be patented.. Anything wrapped in a cover can “prevent and/or alleviate contaminant ingress” Does any patent office in the world really think nobody has thought of this before?
Literally all they needed to do was retina screen, upgrade the internals, and add a few USB-C ports. Was anyone ever legitimately inconvenienced by the thickness of the 2010 MBP? I know I was directly inconvenienced by the loss of MagSafe, ethernet, SD card and USB-A, the loss of the FN key row, and loss of serviceability.
So much so that my 2010 MBP will very likely be my last Apple purchase ever.
Earlier quoted context omitted.
Ooh, yes, I hate the new arrow keys. The inverted-T arrangement was great for positioning your fingers without looking down, since you could use the empty space to orient yourself.
I haven't used the new keyboard. Can't you still detect the arrow keys by feeling for the split between up/down?
Even on the Apple's new desktop keyboards, the split between the up/down keys is much smaller and much more difficult to detect than their older keyboards. It's much worse on the laptop keyboards.
And because the left and right arrow keys are now full height, it is literally impossible to determine if your middle finger is over the up/down keys or over the shift/up keys. And if your hand is in the wrong spot, nothing works.
As someone who writes code, it is hugely frustrating and it slows me down to the point that I now avoid writing code on Apple's laptops whenever possible.