Dev tooling is about what OS most of your devs use - if most of your devs are on linux, then, the tooling will work well there. I saw this happen to a dev that preferred osx when they came to the one dearly missed linux house I worked at. My point is that tooling working or not is not really a relevant criticism of an entire OS or platform.
I will say that what happened to your linux people at Acquia has happened to me when I was forced to switch to OSX for some kind of vague security reasoning at a job once. My productivity plummeted, I can't believe the defaults in OSX people just... live with for the most part. Sure, a tiled window manager isn't for everyone, but truly, people just accept a new window opening and flying off to some apparently arbitrary portion of the screen, at a completely random seeming width and height? People truly just have a massive dock taking up a significant portion of the bottom of their screen? Eck.
I know you can customize all that but that took me a long time to wrangle OSX into an acceptable dev environment, and that's before I get into all the issues I had with various packages. Lord forbid you want to use emacs. This as well is arbitrary, maybe I should "just be a vscode guy" cause that's what everyone uses, but they already spent the money on hiring me so it's like, consider the economics of "forcing" devs to switch just because you think they'll be more productive on the shiny aluminum slab you prefer to use.
And... if people messing with their docks is actually causing a productivity issue, bring it up in performance review lol. Spend less time fiddling with your 2x4k monitor dock and more time just coding, on the laptop screen if necessary, oh woe. I'm guessing the true productivity issue is less that the hardware isn't working and more that the fiddling is fun! If I wasn't fiddling with my docks, I was fiddling with emacs, or, my personally built keyboard config, or, whatever else!