Is it the most innovative concept ever? No, but it looks like it's been executed very well. I think developers will like this macbook.
Is it the most innovative concept ever? No, but it looks like it's been executed very well. I think developers will like this macbook.
Do you need a button like this on your keyboard? No, you could set up a new Vim bind. But this is more dynamic; what if the test re-run buttons were only visible after having modified a file, and replaced with a deploy or commit button if tests succeed?
If you're vigorously opposed to it, don't buy a Mac. But some people can definitely see use in it. It's like your function row, but with visibly context-aware functions.
I don't want a "second display"; I want dynamic, context-aware buttons. Focusing on the fact that it's "another display" misses all the benefits of it not being static hardware buttons.
The buttons on your keyboard are already context aware. All this does is make them difficult/impossible to touch type (I touch type my F-keys), forces me to look away from my display to perform operations, and removes the good tactile feedback you get from a keypress.
I agree, though, that the lack of feedback was a mistake.
>But this is more dynamic; what if the test re-run buttons were only visible after having modified a file, and replaced with a deploy or commit button if tests succeed?
More dynamic in that you have to look away from your work to trigger a re-run? Or more dynamic in that its completely worthless if you use an external display and external keyboard? Or more dynamic in that it's another avenue for show-stopping macOS bugs?
Meanwhile, the other 90% of users will probably love it when their IDE, profiler, every browser's developer tools, etc. can display context-appropriate labels so they don't need to remember what F8 does in the current mode of the current application.
The touch bar is a regression.