Microsoft Asks Open Source Not to Focus On Price
Microsoft's supposed open-source guru Sam Ramji has asked open-source vendors to focus on "value" instead of "cost" with respect to competition with Microsoft products. This is especially funny given the Redmond giant's recent "Apple Tax" message. "While I'm sure Ramji meant well, I'm equally certain that Microsoft would like nothing more than to not be reminded of how expensive its products can be compared with open-source solutions. After all, Microsoft was the company that turned the software industry on its head by introducing lower-cost solutions years ago to undermine the Unix businesses of IBM and Hewlett-Packard, and the database businesses of Oracle and IBM."
You can tell that most Microsoft apologists haven't had any sort of role in supporting or managing IT in business.
Been there. Done that. Have the faded t-shirts to prove it.
Although this isn't just about the fabled "business case".
This is also about the bargain conscious consumer that might
see various bits of commercial software and get a sudden case
of sticker shock or try something that claims to be free but
is really just an open door to malware and spam.
This is about taking Microsoft's own marketing approach and turning it on them.
A Pirate and a Puritan look the same on a balance sheet.
Open source software is often the better option both on cost and quality. As a consultant, I've found that when you stand up open source and proprietary solutions side by side for a customer, the open source solution wins most of the time. Now ISV's prefer the kickbacks, training and marketing support they get from proprietary vendors, so the customer has to ask for the open solution to be compared, but when they do the results are significant.
I don't know about you, but when someone asks for a change to one of my apps and I tell them "It's open source, make the change yourself," what I'm really saying is "**** off."
If you're business this is only possible:
- Assuming you have the budget for a development team.
- And the time to become familiar with the code base before the feature is needed.
- And a repository maintainer who is willing to accept your changes, or an even bigger team and budget to track security and bug fixes from the original developer and incorporate them into your modified code base.
- And a silver tongue, so you can convince your investors that it's totally worthwhile to spend their money improving a product that anybody can use for free with absolutely no way to profit directly from the improvements you made to the software.
Or if you're a home user, in which case you probably don't know C, and if you do you're probably too tired from writing C all day to fix someone's code for them.
The ability to make contributions is far from the main benefit of open source software. The main benefit is the fact that someone can't shut it down for selfish reasons. The code is essentially in the public domain. Apache or MySQL will never enter a "vault" like The Lion King or Sleeping Beauty; the Linux kernel will never have its "support period" expire. The real benefit is social, rather than technological.