81–90 of 104 posts
I have been using the 2016 MacBook Pro 15'' for more than a week. Overall, I like most things about it. It's nice and thin, the fingerprint reader is a time-saver. I'm also fine with USB-C and the new dongle normal. I'm disappointed about the lack of bump in performance or RAM, but those things are not dealbreakers. The new touch bar/keyboard combo, however, is. Here are the issues I'm having. * No tactile feedback .…
Earlier quoted context omitted.
Took me months to realize (on macbook) ... no one believes me until I power it off and have them try again. Spooky is the word.
"Any sufficiently advanced technology is indistinguishable from magic." -Arthur C. Clarke I completely agree though, I checked it out in-store and was far more impressed with the new MBP than the reviews had me believe I would be. People must be very spoiled to downplay it IMO. The keyboard and trackpad are really impressive. I'm debating whether to replace my old desktop with a i7-7700K or pickup the MBP15 1TB with…
I still think they could have kept a couple standard USB ports to help ease the transition, but overall it seemed like a fine machine.
I hadn't considered the removal of the esc key from a vi/emacs perspective. Is this something that can be lived with?
Earlier quoted context omitted.
>If you need access to function keys (F1–F12), hold down the Function (fn) key at the bottom-left of your keyboard. Touch Bar changes to show the function buttons for you to select, and then it returns to its previous state when you release the Function key. From https://support.apple.com/en-us/HT204436 .
I have my MBP (with real function keys) set up to not require than I press the Fn key to operate them. Pressing Fn to access the function key is an undesirable workaround.
I hadn't considered the removal of the esc key from a vi/emacs perspective. Is this something that can be lived with?
tl;dr: If you, like me, touch-type and work very fast, then the absence of tactile feedback on the new Esc is unnerving. It's like a work-stopper. Even if something did happen when you hit it, the lack of feedback means your brain automatically thinks you didn't hit anything. I don't know if this is something one gets used to. After a week, it's still awful.
Earlier quoted context omitted.
I have my MBP (with real function keys) set up to not require than I press the Fn key to operate them. Pressing Fn to access the function key is an undesirable workaround.
Can you not do that with the new macbook? I figured you'd be able to do this context-dependent, so that they'd be function keys for relevant programs.
>For some apps, you can make the function keys display permanently in Touch Bar: In System Preferences, choose Keyboard. Click Shortcuts. From the left sidebar, select Function Keys. Click the “+” symbol, then navigate to the app and select it.
From: https://support.apple.com/en-us/HT207240
If you want always function keys, you can do that too:
>If you prefer the top row of keys to always behave as standard function keys without holding the Fn key: Choose System Preferences from the Apple menu. Click Keyboard. Click the Keyboard tab if it's not already highlighted. Select "Use all F1, F2, etc. keys as standard function keys"
The person who reviewed this may have been a programmer, but the review doesn't seem to be in context of programming. I care about how well I can work on it, not now well it works with remotes. > The MacBook Pro is more an evolutionary than a revolutionary upgrade over my MacBook Air. That seems to sum up this review. The macbook pro is a successor to the air, not the old macbook pro.
So a MacBook Pro is a "Pro" device because it has lots of different ports ? That seems illogical.
This little detail is a big problem for me when using any image or music program where I want to quickly find the arrow keys and shift things around.
Edit: Just checked Atom, there's not really any F-key dependence there. But I use escape all day long to cancel out of UI dialogs. Just saying there's a lot more affected here than just vi users (and I do use vi all day long too, for git commits and editing smaller param files).