Linux Growth In The Workplace Slowing
BrainSurgeon writes "According to a Business Week article Linux growth numbers have slowed for the first time since SG Cowen & Co. began tracking it on their survey. The biggest reason for the slow down according is due to the hidden cost of consultants." From the article: "That doesn't mean overall Linux use is slowing. The survey only shows that a smaller number of companies not using Linux plan to try the software than in previous surveys. Most analysts expect Linux use to grow at the companies that have already rolled it out -- and do so at a healthy rate. And analysts say Linux is picking up steam outside North America, which the Cowen survey doesn't cover."
BACK TO MICROSOFT. Take Independence Air, a low-cost Washington (D.C.) carrier that had been running the reservation system on its Web site with Linux. The company, which uses Microsoft's Windows operating systems in most other pieces of its business, needed to hire consultants who could write code for Linux, since its Windows developers couldn't.
What can 'Windows developers' do? Use a mouse?
And if this statement is to do with the code running on a web server (Apache, I presume), then even more so I feel they hired the wrong 'developers' to begin with.
Just more FUD - move along.
These statements are skewed to show that Independence Air's Linux deployment cost too much in consultant fees, and therefore Linux is "expensive" to deploy in comparison to Windows. But they really say no such thing. Independence Air's problem was not its Linux deployment, but the fact that it chose to deploy a small part of their infrastructure without in house knowledge. They already had hired a Windows skill base, and therefore the comparison in utility between their Windows skillset for the entire Windows deployment against a small Linux deployment was bound to come out poorly for Linux. One sees savings with Linux in scale, not individually. Deploy hundreds of hosts and you'll save huge. Deploy a few hosts to drive a small piece of corporate infrastructure and not only will the savings be marginal, but you may have to hire external help to support the deployment.
So. Don't deploy Linux for small tasks if you're already heavily invested in an alternate technology. Duh. But to claim poor savings across the board as a result of this anecdote is simply stupid. With in house Linux (or UNIX) personnel and a large deployment - of course you'll save big. Which is why the UNIX houses have dumped commercial UNIX desktops for Linux. And why so many have dumped all their small UNIX servers for Linux (and BSD) on Intel. Because it's cheap. Very cheap (and cost effective). --M