There are certainly company men in the, ahem, company, but one of the problems is that MS makes so many tools that are good enough that using open source tools is really hard to do.
Internally, we're told to use MS technology whenever possible. Using open source tools is also a nightmare from a legal perspective, and there are some non-trivial process because of that. It's not hard, but it requires due diligence on our part to ensure we don't expose the company to liability.
For the above reasons, it's frowned upon in company culture. I'm facing an internal side-project and am tempted to take a swing at it with nginx, apache and RoR for learning purposes, but the last thing I want is my manager to demo it and get a non-IIS error message along the way.
You could of course make the errors that RoR shits out look like IIS. In the interest of familiarity, of course, not because you're trying to conceal anything :)
Internally, we're told to use MS technology whenever possible. Using open source tools is also a nightmare from a legal perspective, and there are some non-trivial process because of that. It's not hard, but it requires due diligence on our part to ensure we don't expose the company to liability.
For the above reasons, it's frowned upon in company culture. I'm facing an internal side-project and am tempted to take a swing at it with nginx, apache and RoR for learning purposes, but the last thing I want is my manager to demo it and get a non-IIS error message along the way.