>> As a corporation, I might not want to use it in conjunction with my code, but that's the point. I've worked for several large corporations and were in the t

>> As a corporation, I might not want to use it in conjunction with my code, but that's the point. I've worked for several large corporations and were in the throes of a major project. Using an Open Source tool would've cut a lot of our dev times by many hours. Three out of three times, all three team leads and managers said "no" to using open source. We had to build several large components from scratch, which did lead to extended development timelines, a ton of working late at night and several "crunch" weekends. Their rationale? They didn't want to have to maintain a piece of software that was open source. The resounding opinion was it was "dangerous" and not safe - because someone could check in a malicious piece of code and that could end up in our very large, enterprise application when we needed to update it. Nobody wanted to be on the hook if that ever happened. In the end, it seemed like it was more about upper management types playing CYA instead of trying to put out a solid product.