You can indeed switch between sound output devices, but on iMac "headphones" and "internal speakers" are the same device, so switching is only available if you have something else, like USB speakers or an AirPlay device.
If you click the sound button on the menu bar to open the menu, it will have a headphones entry if headphones are plugged in, and an internal speakers entry if headphones are not plugged in.
As you plug in and unplug headphones, with the menu showing, that entry dynamically changes. (Same on the Sound panel in System Preferences).
This appears to be entirely a software decision on Apple's part, rather than some sort of electrical/mechanical design that forces the speakers to be disconnected when the headphones are inserted. In this discussion [1] on Ask Different people report that when they run Windows via Bootcamp, they can choose via software between headphones and internal speakers.
BTW, my iMac is a 2017 model. They might have changed this with later models.
I keep my custom commands and styles in a separate tex file that I `\input` into the document file I am working on. The document file usually looks very clean with this method. It feels very much like HTML and CSS to me.
I run into all sorts of problems with Word's automatic numbering when I try to leave space, insert images, tables, or a make sublist. And it's never clear to me what the issue is.
LaTeX seems much more predictable. I have a file with my custom commands and styles that I `\input` and use always use consistent style. Nothing too crazy. But I also never try to do anything too crazy in Word, either.
The whole point of software is to reduce or manage complexity. Git cli fails miserably at this.
Google's perforce with mercurial client has been the best VCS I've ever used and I now have a deep hatred of everything that isn't that system, especially git.
They have checks, hints, and interactive plots that update based on your answers. It's really satisfying to get this immediate feedback. The content is great, too, which helps.
Such disappointing backward progress. They obviously have developers who know how to write cross platform, since they are also targeting consoles. Would it kill them to compile and release unsupported Mac and Linux binaries?
This is likely very much on Apple for depreciating OpenGL for a proprietary standard, making cross platform development a hell of a lot of work for such a niche market.
Combine that with the lack of Nvidea drivers and Macs are in an especially dismal place for 3D gaming for the forseeable future.
In fact, the original documentation of Homebrew described this approach as "The GoboLinux Way". (They no longer call it that, but this reference is buried somewhere in their git history.)
