> How? Read the rest of the sentence. > Yes, and the Touch Bar replaces FN keys, not the keyboard, not the mouse, nor the screen. Read the rest of the senten

> How? Read the rest of the sentence. > Yes, and the Touch Bar replaces FN keys, not the keyboard, not the mouse, nor the screen. Read the rest of the sentence. > 12 Use a modifier. That brings you up to 48 without counting Alt. And if you get to that point you have bigger interface problems, which the touchbar will not solve (I'd argue that at 12 you already have that problem). > Have to remember what each number does in each app You did not read my reply. > Different numbers remain "fixed" for different functions in different operating systems (e.g. F1 for Help, Alt+F4 for Quit.) That's a con? > Not customizable What. It's a key. To bind. Making keybinds. Its purpose is to change based on context or your own choice. > Context-sensitive and adaptive No different than you can do with the screen and the F keys. > Cannot display at-a-glance status without taking up main screen space There's an easy answer to this. Please for the love of god and all that is holy power up half a neuron and it'll come to you. > Billions of phone/tablet users don't consider touchscreens a con. You did not read my reply. > Con does not harm typing experience which is still provided by physical keys. Except for the keybinds you now have to look at a separate screen to use, of course. > Con easily offset by haptic feedback very likely in future gen. Feedback on touch (to see where exactly is the finger positioned on the key and relative to the previous keyboard position) is more important than feedback on activation. Of course, on touchscreens you get neither and touching is activation. I'm not saying touchbars couldn't ever be implemented and be an acceptable replacement for function keys, if something like https://archive.is/B4Rdf https://archive.is/B4Rdf could be perfected, then that'd be something worthy of being a replacement. The current touchbar, is not.