Earlier this month, Computerworld reported on the Texas state Senate banning Windows Vista from use in government agencies. Specifically, Senator Juan Hinojosa proposed the ban because "of the many reports of problems with Vista." Microsoft officials reacted angrily, saying "we're surprised that the Texas Senate Finance Committee adopted a rider which, in effect, singles out a specific corporation and product for unequal treatment." Hinojosa has proposed Windows XP and the upcoming Windows 7 as alternatives, but why wasn't moving to an open source solution even considered? That's the gist of an interesting letter sent to Hinojosa, and here are some of the good points it makes.
In Ken Starks' letter to Senator Hinojosa, (Starks is a Linux lobbyist), he writes this, referring to the option of switching state government offices to Linux and open source solutions:
"The state of Texas is paying tens of millions of dollars a year to Microsoft when they have a free, virus-free and stable alternative at their fingertips, literally. Sir, let me pose a question. Why does the state of Texas insist on purchasing a product that proves to be more expensive to maintain than it does to purchase? Anti-virus software, defrag and registry fixers, malware protection...why? Why are we paying for software that demands we purchase other software in order for it to work? That is a question that I would honestly like answered."
According to Texas Department of Information Resources data the state has already spent many millions on Windows Vista deployments and maintenance across more than 40 agencies. Starks' letter points out that governments around the world are switching to open source, and the Obama administration is pursuing open source at the federal government level as well.
One thing that really jumped out at me from Starks' letter is that he singles out malware, viruses, disk defragging, and other common Windows problems as creating cost centers for any Windows deployment. It is true that open source platforms are far less targeted by hackers than the Windows platform, and thus there is far less of a cost center created for the "other software" that Starks mentions.
Of course, these are only some of the issues involved in switching state agencies to open source. There are support and training issues, compatibility issues with existing applications, and more. Still, it's one thing to debate a switch to open source, and it's another thing to not even consider it as an alternative at all. This could well be an instance of a problem I've mentioned before: Open source needs better evangelists.
Â