- 13'' MB Pro (2560 x 1600, 2016)
- 3.1 GHz i5
- 16 GB RAM DDR3
- 500 GB SDD
- Intel Iris Graphics 550 1536 MB
I use it primarily for software development within the SAP mobility stack (hint: UI5, Fiori, node, SCP(ms), GW, ADT, iOS). Some Virtualization (VMWare). GUI Tooling ~ WebStorm, XCode, Eclipse, Visio. Terminal.app a lot.
Control-Strip/Tab-Bar/$Whatever-its-called
Generally I'm open to all kinds of improvements to the Human-Machine-Interface. Who wouldn't want to break out of the dreaded 2D-way of pushing the mouse to operate a computer?
So the Control-Strip/Tab-Bar/$Whatever-its-called (let's call it TouchThing for now) is worth a try.
In situations where the TouchThing complements interaction, it's really nice.
E.g. quick access to a man page when typing a command in Terminal:
Or using autocomplete when typing in text-centric input areas:
But during programming, I've yet to see a useful UX feature.
Dropping the F*-Keys in favour of the TouchThing has reduced the value of the MacBook as a tool. There's just too few haptic feedback on the TouchThing when reaching out for a LED F*-Key. Working with WebStorm a lot with utilises the F*-Keys a lot - so having the TouchThing is really cumbersome during coding.
(BTW: why, Apple, is there no adapter for the iPhone X lightning headphone cable -> regular headphone jack?!?!?!?!)
For USB-C, there are still too few devices out there. No more quickly using a USB-Stick. Always have to carry around (another) adapter, in addition to the ones for DVI, VGA and DP.
Please let USB-C-sticks hit the market in masses soon. Please.
A step back.
Plain and simple.
Compared to an older MacBook Air model that has the standard keyboard Apple outfitted MacBooks with for years, the keyboard on the new MB Pro is simply worse. Plus the occasional jamming/sticking/clamping of the Space Bar. Meh.
I don't care so much about the bigger TrackPad - use it only for navigating Spaces and uncluttering the Desktop (Five-Finger-Spread). No need for Force Feedback during development work.
Even nicer: for Authorisation, e.g. when installing/upgrading Apps.
Comfort gain right there.
So the Control-Strip/Tab-Bar/$Whatever-its-called (let's call it TouchThing for now) is worth a try.
In situations where the TouchThing complements interaction, it's really nice.
E.g. quick access to a man page when typing a command in Terminal:
Or using autocomplete when typing in text-centric input areas:
But during programming, I've yet to see a useful UX feature.
Dropping the F*-Keys in favour of the TouchThing has reduced the value of the MacBook as a tool. There's just too few haptic feedback on the TouchThing when reaching out for a LED F*-Key. Working with WebStorm a lot with utilises the F*-Keys a lot - so having the TouchThing is really cumbersome during coding.
USB-C periphery
There are no more ports on the new MB Pro other than a headphone line-in jack and USB-C ports.(BTW: why, Apple, is there no adapter for the iPhone X lightning headphone cable -> regular headphone jack?!?!?!?!)
For USB-C, there are still too few devices out there. No more quickly using a USB-Stick. Always have to carry around (another) adapter, in addition to the ones for DVI, VGA and DP.
Please let USB-C-sticks hit the market in masses soon. Please.
Keyboard
A step back.
Plain and simple.
Compared to an older MacBook Air model that has the standard keyboard Apple outfitted MacBooks with for years, the keyboard on the new MB Pro is simply worse. Plus the occasional jamming/sticking/clamping of the Space Bar. Meh.
I don't care so much about the bigger TrackPad - use it only for navigating Spaces and uncluttering the Desktop (Five-Finger-Spread). No need for Force Feedback during development work.
Fingerprint Sensor
...for unlocking the Computer. Nice.Even nicer: for Authorisation, e.g. when installing/upgrading Apps.
Comfort gain right there.
MagSafe power connector
Get outta here.Various observations/remarks
- no use for Siri what-so-ever
- no more telnet on High Sierra - seriously?!?
- battery lifetime has (subjectively) decreased plenty - might be something with my local configuration; though generally I try to use as few custom settings and tools as possible in order to remain as "standards-compliant" as possible (hey, it's the SAP world after all I'm working in)
- overall performance is very good; but in MacVerse, we're spoiled anyway
- closing the lid leaves some not-so-nice spots on the display; can be wiped clean, but still
- iOS integration still awesome (e.g. make calls from contacts.app to regular phone numbers via Facetime Audio on the iPhone)