3 ms·
It's so true. In order to evaluate open source software you have to have someone competent set it up. However with a software vendor they can provide a demo a
by dasil003 17y ago
It's so true. In order to evaluate open source software you have to have someone competent set it up. However with a software vendor they can provide a demo and you can have different key levels of management evaluate it.
I think the problem is one of expertise and motivation. A software vendor will necessarily be an expert in their own product, and they have a huge incentive to sell it. Internal IT staff are not going to be expert in some random open source package. Their expertise is going to be domain knowledge, and their interest is just to make sure things are working smoothly. In theory they would prefer better quality open source software, but in practice they need someone on the hook to blame when things go wrong just as the brass does.
I think this could be changed though. If a corporation had the mindset that they wanted their IT to be a competitive advantage, recruited and paid accordingly, I think a large corporation could mop the floor using the right mix of proprietary and open source.
- tptacek 17y agoI really think the problem is simpler than that; in most enterprises, I think there's literally a company neurotransmitter that doesn't get activated until someone has to cut a check. Until your project gets JBoss-big --- hell, even after that --- nothing you do is going to get open source taken seriously. I base this in part on a number of friends who have hugely successful open source deployments in their companies (BSD/pf firewalls, for instance), and who are locked in a constant struggle to keep those deployments from getting "upgraded" to "real software".