Depends on size and what kind of company it is. I once worked for 300+ people research company which was mainly using Linux, there default setup was: - no "no

Depends on size and what kind of company it is. I once worked for 300+ people research company which was mainly using Linux, there default setup was: - no "normal" employee has admin rights - any long running/compute task must run on one of the many server systems available - desktop systems used some form of network boot to install/reinstall/update them on startup, unused systems shut down after a while for both power saving and enforcing the network boot triggering - there was some tooling which allowed admins to easily configure the right combination of Linux distribution and software bundles - if some applications wasn't available you needed to make a ticked and normally got it in a day, that seems high friction but then it doesn't happen that often so it's not really a problem and it tends to get added to a bundle so that other people have it too What somewhat wasn't covered would be local project specific installations using e.g. `pip`/`npm` etc. And naturally there had been a bunch of exceptions. Now this was years ago and this approach was for siency use-case not normal software development, but while a lot of developers probably wouldn't like it should be applicable to a lot of dev use cases, too. As long as you include enough tools/choices in your software bundles. Okay, maybe it will not work for certain system level C/C++ programming, but for most app/web/server use cases it should be possible. I guess one of the worst offenders here would be docker as you would _only_ allow rootless containers. (But then I'm using mostly podman and I thing I only have been using rootless containers the last 1.5 years or so.)