I'm just tired. On the last post about having Linux at our work, many people that seems to be an IT worker said there have been several issues with Linux that was not easy to manipulate or control like they do with Windows, but I think they just are lazy to find out ways to provide this support. Because Google forces all their workers to use Linux, and they have pretty much control on their OS as any other Windows system.
Linux is a valid system that can be used for work, just as many other companies do.
So my point is, the excuse of "Linux is not ready for workplaces" could be just a lack of knowledge of the IT team and/or a lack of intention to provide to developers the right tools to work.
Many places support MacOS as well, so it would only be a third additional toolset. Plus, there's a ton of overlap between toolchains, which reduces the overhead further. If you're supporting enterprise MacOS, you're probably using Foreman, JAMF, or Puppet with Active Directory.
Not to mention, a lot of places already have Linux servers, so the configuration management toolchains and expertise may already exist in a given organization, unless they're absolutely pathologically mired in the Windows ecosystem. Which, granted, is a lot of places, but you're making it sound far harder than it would be in a real world situation.