Re:New MacBook Pro Is Not a Laptop for Developers Anymore
by laichzeit0 on Friday October 28, 2016 @12:18PM
(#12817612)
I put it to you that you've never used a debugger if you've never used Fn keys.
[ Parent
| on HN ]
Re:New MacBook Pro Is Not a Laptop for Developers Anymore
by snowwrestler on Friday October 28, 2016 @01:54PM
(#12818755)
To use the function keys on an old MacBook Pro, you have to chord with the "fn" key to override the brightness, volume, etc controls.
To use the functions keys in the touch bar in the new MacBook Pro, you have to chord with the "fn" key as well.
So where is the difference...
Re:New MacBook Pro Is Not a Laptop for Developers Anymore
by mikejmoffitt on Friday October 28, 2016 @02:00PM
(#12818850)
It has always been possible to set those keys to default to F-key functions instead of media functions. The difference here is that the position may not be constant, and you can't feel with your fingers what you're over before you commit to activating the function, so you must look. In some contexts you can "get used to it", but this is a steeper uphill battle.
Re:New MacBook Pro Is Not a Laptop for Developers Anymore
by snowwrestler on Friday October 28, 2016 @02:17PM
(#12819064)
I would not be surprised if one of the customizations of the touch bar is to set the function keys as the default.
Re:New MacBook Pro Is Not a Laptop for Developers Anymore
by nogbit on Friday October 28, 2016 @12:26PM
(#12817708)
Visual Studio is the only place I've really used the function keys (F5, F10, F11), and I rarely use VS anymore. Outside of that I use F2 when in any kind of GUI that permits renaming of a file or folder.
All of which can be rebound.
Re:New MacBook Pro Is Not a Laptop for Developers Anymore
by dump121 on Friday October 28, 2016 @02:04PM
(#12818899)
What about IntelliJ or Chrome or any IDE for that matter.