Main Content

Should I use Open Source or Commercial software?

Archive - Originally posted on "The Horse's Mouth" - 2011-03-26 15:24:55 - Graham Ellis

If you're starting a new project, should you choose an Open Source solution, using software that's free at the point of distribution and for your use, or should you spend money buying a commercial piece of software?

First reaction - use open source
"why pay when you can get something for free"		 Second reaction - use commercial
"I need help and support and I can get that if I pay money for software"


It's not as straightforward as either of those answers though. You should look at the total cost of ownership.

With Open Source software, you'll tend to have far more options and alternatives available to you within the products, with hosts of addons available, most of which will be excellent. So although you'll save on purchase price, you may end up spending more in terms of your own / your programmer's time on your first project than you would if you had chosen to use a commercial product. But once you know the Open Source software well, you'll be able to make good use of those alternatives and flexibility, and on the second and subsequent projects the Open Source route should be much quicker.

Do you want training? There *are* exceptions, but training on commercial products tends to be more expensive, and is sometimes MUCH more expensive. If you've bought a commercial piece of software, you'll tend to gravitate to the author / supplier company for your training too; they know this, and sometimes it's the training rather than the software sales price that makes them their money. Third Party trainers (I used to work for one) have software licensing issues for their training machines, and may be "strongly encouraged" to run official courses for which a per-delegate royalty is payable to the author company.

There's sometimes an assumption made that you can't get support on Open Source software. That's wrong, there are companies who will sell you support. If you're a bit of a geek (or even minigeek) you'll find a lot of support in newsgroups, postings, forums, etc.; other users of open source (and authors) are typically very proud of what they've done. Common questions - go through existing resources / searches. Less common ones - the forums and people behind the software may love the challenge.

The question has been asked of me "but what if Joe Bloggs, author of K++, gives up on it and I've used K++ in a business critical application?" It's a good question, but let me ask another question: what if [big corporation], author of J++, gives up on it and I've used K++ in a business critical application?" The answer - when you think about them - are a bit of a surprise. If the author of the Open Source product gives up, you've got the source code of it. So in the worst case you can employ someone to fix issues. If the author of a commercial pece of code gives up on it when there are business critical users out there, it's writing itself something of a blank cheque to charge them for ongoing support if it chooses to do so ...

My diagram stacks up the various costs for a newcomer's project, and for an experienced user's project, using commercial and open source software. Of course, the sizes of the boxes here are purely illustrative so where my diagram shows one approach winning over the other, you may find that it's the other way round for your particular needs.