Ignoring the source code is akin to an ostrich sticking its head in the sand

eWeek’s Jim Rapoza recently released a slide show called 10 Things You Should Know About Open Source. I admit, I love lists and I love the perspectives laid out here. You’ll need to visit the slide show for more info, but here’s the list …

1. Check the label

2. Not just for coders

3. Forks feed open source

4. You can ignore the source

5. GPL is not a social(ist) disease

6. Open source is no secret society

7. Open Source in Windows-friendly

8. Releasing the code isn’t enough

9. Watch out for orphans

10. Dog the bounty hunters

As the notion of open source and its pros and cons permeate the market, I think numbers 2 and 4 are especially poignant.

Sys-admins and coders are not synonymous. Sys-admins may like to tinker and experiment, but they also need things to work, want somewhere to turn when things don’t work, and are constrained by costs and time. Decisions are based on what solution solves their pain. We’re shifting from a proprietary vs. open source discussion to a quality discussion.

Open source is hardly a “must have” in solving any and all aspects of IT. It’s not the golden ticket for everything – take the desktop for example (ouch). In such instances, you can ignore the source. But in integration (like MuleSource)? Systems management? In these arenas, open source is causing a seismic shift that says sure, you can ignore the source code, but that’s akin to an ostrich sticking its head in the sand. There’s utility in the code. There’s power. There’s efficiencies for the taking.