Like it or not - sysadmins do not get to write the rules, no matter how right they may be. When they break them, they should suffer the consequences.
Could it be that the massive code base and declining sense of community from corporate involvement has driven young open source programmers elsewhere?
Nah, they have all just decided to get paid, rather than work for free... (end.sarcasm)
In all seriousness, a lot of the new generation of programmers are starting out in large corporations, as a means to repay student debt, get themselves established - and are able to do that code work in the open-source world, as corporate acceptance and utilization of OSS for application development grows. This, unfortunately, comes with a flipside - those same developers are not available to do the work the hobbyists were doing a few years back, leading to the perception that the OSS movement is losing developers. The movement actually isn't losing developers - more and more of them are just being absorbed by NDA's
Either that, or they have all decided to start writing flash games for Adult Swim.
Having an browser installed does not make a PC any less or more secure, it has been proven recently that most versions of IE have major vulnerabilities (just ask Google).
Really? Having any random browser installed does not make a PC any less or more secure? Please, please tell me you are not in any way affiliated with any environment subject to federal regulations.
Let us say your environment is exclusively a MS shop. You have all the development resources, security resources, and vendor support to ensure that environment is safe, secure, and compatible with your applications. Then, bam, a problem shows up. Joe User cannot use X web application. Security starts seeing strange traffic coming across the network, traffic that is malicious in nature. Lo and behold, that is because Joe User installed a browser not supported within the organization, which, in this case, happens to be copy of Firefox 3.5 (http://www.mozilla.org/security/known-vulnerabilities/firefox36.html). Suddenly, your organization has just been hacked, corporate data is being siphoned off the network, federal regulators are crawling down your boss's throat, the organization gets hit with a huge fine and other costs related to the data breach, and why?
Because you believed that installing any old browser on any system in any environment doesn't make the PC any more or less secure.
Moral of the story? Don't be a fucking idiot, and understand the need for prioritization and standardization within a corporate network, especially one of those corporate networks that is subject to regulatory oversight regarding information technology.