> If you can't even choose the OS you want to work with
I mean not really. Linux is usually an excellent choice for development and if the rest of the company can use it there's probably no reason you can't other than maybe aesthetic ones. IMO they shouldn't take priority over creating a standard dev environment (you still need all OSes for testing, etc but that's a different point).
Yeah, I care about the code that comes into the repository: charset, tab/spaces, style, etc. Who cares about the OS or IDE the developer used to commit or type? Unless you see a productivity/code issues problem...
There is a productivity problem with supporting multiple OSes: either one OS is unsupported (and people who use it waste their time configuring it), or all the tooling, internal documentation and tutorials has to support both - in which case it is often almost double the work.
I have personally seen team members waste days of their time because they tried to adopt an internal script to MacOS, instead of just using Linux VM as recommended.
i'd say a standardized OS and environment for onboarding is a better experience for onboarding so everyone is on the same page. doesn't mean you can't change it to something you prefer though.
I mean not really. Linux is usually an excellent choice for development and if the rest of the company can use it there's probably no reason you can't other than maybe aesthetic ones. IMO they shouldn't take priority over creating a standard dev environment (you still need all OSes for testing, etc but that's a different point).