[ajackfox]

Unfortunately I think these types of restrictions are fairly common in large organizations, even non-financial.

Speaking as someone in a Fortune 500, sometimes the bureaucratic hoops one must jump through to develop in a VM or with docker on ones own machine isn't even worth it.

[eat_veggies]

At a company I interned at, even getting Linux on a laptop was a multi-week process. I ended up running a Linux VM on virtualbox on Windows, used cmder to ssh into it, and used a shared folder to edit code natively while running it on Linux.

[user5994461]

To be fair, it makes no sense for the company to allow any desktop on Linux. The desktop wouldn't have the centralized authentication, the system updates, office or the drivers for the printer that are well integrated only on their windows machines.

[mbrumlow]

Did you mean Linux on a desktop?

Umm, you can do all of those things with Linux... I can't remember the last time I had any issues with printing on Linux at all.

[lifeisstillgood]

So take a major financial insititue you probably have an account with - 300,000 employees each of whom has at least one PC age ranged upto a decade. Including servers and routers they probably have as many machines as AWS, but in several thousand "data centres" some of which get unplugged by the cleaners vacuum.

The management headaches for this kind of distributed computing is off the scale, and banning Linux and locking down senior devs workstations is just table stakes. Everyone is heading to a thin client running citrix to a data centre for pretty much this reason

[mbrumlow]

None of it has to be complicated, it is because people want to make it complicated, and make computers some magical box.

Lets firs talk about removing root privileges on personal workstations or laptops. This is pointless. Anything that might be bad for root to do on a single user system is going to be just as bad running as a user. The second you allow any custom code to run as a user on any system you should treat it as potentially compromised -- adding root in to the mix really does not change things -- on a single user system. Worried about root user getting access to some customer data on the system? To bad, if the data was on the system it is more than likely the user level account (windows or linux for that matter) had access to the data therefor any intruder will also have access, just at the user level. The same goes for just about any other issue you can run in to. Am I suggesting running things as root? No, because there really is no need for most things -- at the same time if your developer needs to have root level access so they can test or work with technologies that require it when deployed to production then it really should be a non issue for sysadmins. The problem is sysadmins are mostly scared to be outed for doing nothing for most organizations these days. These sort of power sweeps are often used to justify big budgets and teams of people who tell you to "reboot" when it does not work right. There is also a bit if power hungry attitude associated with it too.

You state that Linux makes it harder, I can't see how and you did not show me anything convincing. Bold statements without any details into facts can just be tossed into the trash can as far as I am concerned.

Now lets talk about citrix. How does that help? All that does is move any real or perceived problem to a different system. If any of these VMs get accessed by bad actors they will still be able to own any of the information on them that the user had access too.

In any case I did not really come here to argue any of this, your comment is just sort of out of place with relation to what I said.

If you can't trust your employees don't hire them, or just pay them and tell them to sit in a dark room so they can't hurt anything.

[lifeisstillgood]

hmmmmm. I may have drunk too much corporate kool-aid over the recent years. You have many valid points.