> Unless you're working with a shit company, chances are pretty good that all of your software and workflows will work on Linux too, and possibly even work better.
I wouldn't call the company where I work shit, but in Germany many big companies are deeply entrenched in the whole Microsoft ecosystem, and some sectors are even more entranched. So, I am very certain that a lot of insanely business-critical software at the company where I work at (which is about a market where easily billions of EUR/USD are moved) will not work in a GNU/Linux ecosystem.
Over many, many years, many parts of the (often custom-built) software was developed to work together with the existing big ecosystem of existing (also often custom-built) software. Some parts of the programs that I work on are deeply intertwined with various products from Microsoft - if they weren't, the users would not be able to work so productively with these programs (i.e. the workflows would take a lot more time for the (highly qualified) users, which would cost the company a big load of money).
I've had another annoying problem with some gigs recently where the employer insisted on MacOS for developer workstations.
While I (generally) like the hardware, I don't like the UX in MacOS but more than that I have a strong distaste for having my runtime deployment environment be entirely different from my working environment. I prefer to eat my own dogfood and have Linux all the way through, and I really like my own tooling and configuration I've set up over the years.
I had a job recently where the whole deployment stack was NixOS (to Aarch64) but the issued devices were Mac laptops, and you couldn't even build the software on MacOS (not even Nix Darwin) so had to do everything inside Parallells etc and it was a giant PITA.
I've never understood why .. if you're going to pay people six figure salaries for their time why would you slow them down with process and tooling that makes them less efficient...
