I futzed around with the touch bar in Logic when I got one and wrote it off almost immediately. Logic Remote (which works with GarageBand, AFAIK) already exists and works with an iPad. Clear labels, clear text, manipulating multiple elements easily at once--it's a better solution than what they tried to wedge in with the touch bar.
The bigger problem with the touch bar is that, as a developer, I end up hitting the touch bar controls all the time. VSCode "helpfully" has previous tab/next tab buttons on it--and so when I try to hit 2 or 3 on the keyboard, sometimes I brush against them and suddenly I'm disoriented and typing in a completely different tab.
This machine is a work laptop. (Typically my music stuff is done on a 2012 rMBP, which is why I already had Logic and Logic Remote set up.) When I started, I asked for a half-the-price Thinkpad on which to run FC30 and was denied because "everyone else uses a Mac." I love the job but between the garbage touchbar and the hand-wreckingly shallow keyboard travel the computer they gave me it's easily the worst part of my day.
Now, I don't disagree with your sentiment, touch bar is definitely a nuisance without any superior use case over the buttons that were there before... But why do you think this keyboard wrecks hands? It is definitely the fastest keyboard I've typed on, and shallow keyboards are definitely inherently easier on the hands by any metric I can think of
1mm travel keys just leave me thumping my fingertips off the laptop chassis all the time. It hurts.
This suggests a fun and interesting way forward for Apple UI design - layered augments from additional devices. Let OS X be the core of the system, but enable big apps like Logic or Photoshop to have connected supplementary UI's in iPad or VR/AR that provide a high-quality interface to some specific functionality. Reduce alt-tabbing on the main screen.
The real answer for me is going to be swapping for an X1 Yoga or an X1 Extreme, I think.
Maybe there are some shortcuts / combos I’m not aware of???
I'm a keyboard-based person, though I don't use tiling window managers or the like. I've got a system (he said half-ironically). Some shortcuts are more comfortable to do with my left hand on the modifier. Some, the right. All of them are hosed on a Mac and fixing them would take longer than what I did today, which is ask my boss to let me give the Mac to the new guy and go order myself an X1. So this story has a happy ending!
... but both pale in comparison to the mighty AHK for Windows, imho https://www.autohotkey.com/
AHK is so incredibly useful it should be bundled with Windows at this stage
I don't get it, the rest of your comment is mostly positive?
Even if it were annoying for the non-development functions I use it for when developing (volume control is not exactly "development", only auxiliary at best) I'd just remap them to actual keyboard shortcuts.
But it's not.
What's "annoying" is apps that could make it useful but put nonsense actions in there because horror vacui, not making use of its potential; but it's only so in an intellectual way, pragmatically I just ignore the Touch Bar in such cases and use the app as if I had if there was none.
Unless I’m missing something I can’t think of anything the touchbar could do better for me. (just my 2c anecdote)
And Xcode doesn't use a function key to pause, since that would also interfere with any apps that use function keys. The default keyboard shortcut for pausing in Xcode is ⌃⌘Y, and I think you have to bring Xcode to the foreground for that to work anyway.
Ill bet you 99% of mac sales are NOT to developers.
Despite them arguably wanting to court developers to write swift programs, their hardware sales team doesnt seem to care about developer prosumers.
(Heck, technically, Mac developers don't even have to use Apple products to develop Mac applications. I've done native macOS app-dev and the only thing I have that runs macOS is a Hackintosh.)
Consider also this analogy: you don't develop console games on the console itself. You develop and build them on a computer using a cross-compiler, and then push them to a dev-kit unit to test them. Same thing applies here: just because you're writing macOS software, doesn't mean you need to be using macOS. You could stand up an office EXSi server running macOS VMs to serve as a CI server and test environment, and then actually write your macOS software in VSCode on Linux, pushing it over to the server to test it. People have done this. It's no harder than, say, developing for Android.
I have a college aged brother, and Microsoft currently owns GitHub, and is providing the linux subsystem, which is a huge signal that "developers are welcome." His whole generation is developing on $300 Dell laptops and it's easy. Mac used to provide that, but you paid for it.
* I need to develop for this shitty platform, which I hate, because my customers are on it
* I want to develop for this awesome platform, because I just love it and my customers are also on it
If Apple loses touch & favor with developers, their platform will slowly but surely die out over a decade or two. Apple is expensive, the only reason for Apple to even exist is because they deliver quality products. If they ever go down the road of consistently failing this core value, they will die more quickly than reindeer thrown down a cliff.
I am also a musician. The Touch Bar is fantastic to adjust tuneables in GarageBand, without the gorilla arm or wobbly screen effect you get on touchscreens.
If it were annoying to me I'd just remap the two or three functions I use as a developer to some keyboard shortcut. After all I'm a developer, I think I can handle that fairly swiftly by myself if no tool were available (and I'm fairly convinced there is).