Obama wants to know: Why open source?
President Barack Obama is a smart guy. Where others zig, he zags. It's perhaps not surprising, then, that he's been asking around about the benefits of open source, according to Sun Chairman Scott McNealy, who has been asked by President Obama to author a white paper on the benefits the U.S. government can derive from open source.
McNealy, cited in a BBC News story, wasn't shy in identifying them:
It's intuitively obvious open source is more cost effective and productive than proprietary software....The government ought to mandate open-source products based on open-source reference implementations to improve security, get higher-quality software, lower costs, higher reliability--all the benefits that come with open software.
While I agree with those benefits, I'm not a supporter of mandates. I wouldn't want the government mandating Microsoft software--why would I therefore seek an open-source mandate? Open source has done remarkably well in the U.S. federal government without mandates, and will continue to do so because of the benefits identified by McNealy.
Will President Obama listen? I suspect he's more likely to do so. He'll get plenty of lobbyist cash from technology companies like Microsoft, but with few companies now solely dependent on proprietary software (indeed, I'd argue that there aren't any left), open source is going to be on everyone's agenda.
For other positions on McNealy's open-source suggestions, see The 451 Group's Matt Aslett's blog and OStatic.
Matt Asay brings a decade of in-the-trenches open-source business and legal experience to The Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure. You can follow Matt on Twitter @mjasay. 





And McNeely generalizing open-source software as providing the following benefits: "improve security, get higher-quality software, lower costs, higher reliability--all the benefits that come with open software" is not true. I can create an open source project and it can deliver none any of these things. All software should be evaluated on its merits alone and not just be cause it is open source.
Also, do you think McNeely would be supporting this initiative if he didn't stand to profit from it? That up-front cost of $0 sure looks nice, but once you've selected software, its typically hard to transition from it, and that's where the hidden costs are.
You mean like moving from Office 2003 to 2007?
Yeah, moving everything around and burying useful functions underneath 5 dialog boxes is seamless.
I have spoken to many folks who have upgraded to Office 2007 and they say its way easier. Nothing is hidden under drop menus, its all there in front of you under a few tabs. I think your complaining is more related to why didn't OO.org or K-Office didn't think of that? Sometimes there needs to be change and Office 2007 is the best one to date. Its selling like hot cakes btw. So, whatever issues you have with it relates to your internal Richard Stallman jealousy syndrome.
It's true, all software has some cost associated with installation and maintenance. But open source will always have a lower TCO, since that support is not restricted to a single party. If Outlook 2007 has a bug, there's only one company that can fix it, Microsoft. And they'll fix it at their leisure, and charge you what they want. If there's a bug found in an open source product, you can potentially fix it yourself (if you're a developer), or contract the job to an arbitrary developer and have fair more negotiating power in how much the job will cost. Also, proprietary software vendors (even Microsoft) typically don't support their products indefinitely, whereas with open source, you'll always have the source code, so you can buy support as long as there are developers familiar with the code's language.
Btw, it's also fun to see you argue against open source by accusing McNeely of attempting to achieve some sort of software monopoly/lock-in. Per my arguments above, that idea should seems ridiculous, but it's amazing you don't see that danger with proprietary software, where lock-in is virtually guaranteed.
There may be a button for nearly everything on the laughable tabbed toolbar, but then you are faced with a rather deep dialog box mess.
You obviously haven't used it(I have and was forced to teach poor freshman how to use this turd), so stop commenting.
[CNET editors' note: Prohibited content deleted.]
Other software choices may be less cut and dry, but when it comes to office suites, Open Office is the clear winner in cost, both short term and long term.
Office '07 is widely recognized as much easier and efficient than Office '03. Just because you got so used to Office '03 that you couldn't find the things you were looking for doesn't mean Office '07s UI is a pile of junk.
If you were to show someone who had never used Office before both versions and ask which one they would rather use Office '07 would be the pick 99.9% of the time.
There is a reason the ribbon is replacing the UI on most of Microsoft Software and it isn't because it is a pain in the ass to use, no it is the exact opposite actually. And the CUSTOMERS are the ones asking for it.
That said, I'm with the author regarding mandating certain products of any creed being a bad idea. The file formats should be mandated to be open (so they can be viewed even if M$ goes under and the .doc file format dies in 4 years), but let them use what ever software they decide to use. Even if they decide to torture themselves under their M$ masters. Just because bondage and enslavement isn't for me doesn't mean I have a right to dictate whether or not it's right for you.
I disagree. I think it is more 1%, and secondly there are many distributions that are absolutely free and the support for them matches Microsoft in many ways. CentOS, while great for a server, can also be used as a desktop system. Ubuntu offers a Long Term Support and Canonical provides paid support for a number of years. Linux does not force anyone to upgrade, you can stay at any version you want. But just like Microsoft, which has been saying it will drop support for XP, security updates are needed if you don't want your machine to become compromised. So by saying you aren't forced to upgrade with Windows, I suggest you turn on automatic updates and you will change your opinion.
If you think Windows doesn't have an agenda, then you are naive. Linux may remain a hobby, but it will be because the Linux community as a whole can't agree on what's best, and everyone has the power to change what they have. Microsoft spoon feeds it's customers, which isn't always bad, but it is illegal to change their source code.
Look at Netbooks, that form factor debuted as a Linux device, but soon as Microsoft supported it with Windows XP, it grabbed 70% of the market ...
-------------------------------------------------------------------------
by xcal78 January 22, 2009 11:44 AM PST
Specially in this down economy companies will choose the cheapest way to do stuff and that's staying with Windows.
-------------------------------------------------------------------------
It's like we entered the red light district around here. Just keep going, don't make eye contact ...
I use both, there are pluses and minus to both.
Not sure what you mean by this because at least German public sector tells that they have made huge savings last year because of going Open Source though they did have bad start back in 2006 when Novell implement it.
http://www.busadm.wayne.edu/article.php?id=13
There are many others such as this.
http://www.post.edu/online/technical_requirements.shtml
Most problems occur due to a reliance on Active X and IE for online activities.
WKC
A side note: as open source software becomes progressively main stream, we will see many of the same issues that have plagued MS - legacy support, malicious software, etc.
Obama needs to mandate true open file format protocols.
OOXML doesn't count because it can be changed on a whim, has patent traps and is impossible to implement 100%.
Once that is done, the applications used to write and edit them are irrelevant.
In the next decade or two, how many billions of dollars of taxpayer money is going to be wasted to move all those documents from older, unsupported formats to newer formats? Hopefully those newer formats have no lock in attached, or this merry-go-round of insanity will never end.
Just say no to proprietary formats.
Mandate Open Formats and leave it to the user/organization to choose which OS/Office suite he/she/it wants to use.
Thousands of programmers worked on Windows. You really think they didn't use copyrighted code(include GPL code) that they don't own?
You keep pointing to one paper written by someone of dubious technical knowledge as proof of your ridiculous claims.
How about you point to real world proof?
The last time that I checked, the Cornell Law Review was a very reputable publication. I should add that the legal opinions expressed in this publication have much more credibility than your previously expressed legal opinions in this blog a few weeks ago about the legal basis of open source developers who hack proprietary code. Once again, I tend not to take legal advice from an avowed software hacker like you.
You might want to read Elinor Mills article in the Security Section of Cnet.com on January 13 for a story about an open source software hacker like you who broke through a proprietary software program and effectively pirated it. The piracy was unequivocally illegal.
While I am sure that some of the pirated illegal code or trade secrets also go into proprietary development, it is very hard to discover in closed proprietary software that is kept as a trade secret. On the other hand, in open source software, such illegal code is out there for all to see. That is why the Cornell legal scholar thinks that thesei incidents like reported on CNet.com on January 13 are just the tip of the iceberg for legal problems facing open source development.
If you want to look for other examples of incidents, just read any open source blog or help forum and you will see countless examples of open source developers bragging about how they are in the process of cracking or pirating proprietary code (just like you were bragging a few weeks ago!).
The last lawsuit involving alleged "stolen" intellectual property in open-source software left the plaintiff bankrupt and discredited.
Read the most recent Cornell Law Review article by Huang. You need to get more current with your understanding of open source law. You are several years out of date.
And if you took ms and apple out of the picture, contrary to what you suggest, you would suddenly have a MASSIVE INCREASE in the resources devoted to the advancement of open source software. The reason for this is that those same resources are going to be put into something no matter what.
If what you want is better software / information technology, F/OSS is obviously the best choice, but software can be the means to the end of either profitability or better software. Profitability can mean more money to stay competitive, or better software can be produced that is more productive such that the software can be used to do better business.
As long as there is a need for better faster software to do things and look at problems in new ways, there will be money for programmers. Microsoft has contributed to the software industry as much as, and in the same way the RIAA has contributed to music culture. Great music has always come from the truest music lovers, and I am certain for as long as people could hear, there has always been value in music. Only since there has been money in heavily controlled mass distribution of information has a new type of criminal been imagined in order to ensure control and maintenance of a very profitable business.
The government and other users are not in this business. Just because of the present level of control by Microsoft, and possibly the long for people to get back in touch with culture could be difficult with companies like Microsoft and members of the RIAA and MPAA that have so much to gain from the commoditization of our culture is no reason to continue to support it.
If the best move for the government is for them to gain the most money through the largest bribes and handing out control to large companies that results in "standardization" through exclusive control, then sticking with Microsoft will be the sure way to go. If Obama wants to make a move for the people, encourage transparent culture where people participate in it, rather than just pay for it where a faith in humanity is what will be the most profitable (with regard to value and encouragement of useful labor) then the FIRST thing Obama can do is embrace open standards and free open source software.
Open source development is mature and just as professional. Hell, it's even the same programmers sometimes but it's bad for business. Therefore, if an open source product can do what you need and had a lower overall impact, go for it.
Microsoft, and Apple for that matter, want to lock you in. They want you to use their software only and they use all types of tricks to make you do that. Why think for yourself and build a kick-ass IT environment when you could just use their products and have a fair environment that's sort of OK but expensive. You're a fool if you unknowingly get locked into the Microsoft world. They have some good programmers and great products but they also have some that are pretty lame.
http://news.netcraft.com/archives/web_server_survey.html
Apache (Yes... it's open source) kills Microsoft in this space. Guess what operating system the majority of those web servers are using? Yes... open source Linux variants.
You are also seem to be under a false assumption that if open source software comes into play that all users will have to adapt. Most Windows users are clueless to they fact that they are *already* dependent on tons of open source software for their daily use. You appear to be one of those (who incidentally is viewing a page delivered via open source technology currently).
You may also find this reference helpful for future posting:
http://www.wikihow.com/Use-Apostrophes
Security because the code is an open book, and so no vested interest can bias the code without many people knowing.
Quality because the development effort comes not from a lackey on the clock waiting for beer o'clock - but by those that have an intrinsic interest in the software. Many developers only care about end of the year reviews, and will only do what's needed to meet the bar, they have no interest in going over and beyond.
Integrity since special interests with long term strategic and covert scheme are not given control. This is one reason why Microsoft products suck so much - there's always a hidden agenda within them.
I agree with other posts saying that the actual software is not the most important cost with regards to software.
This openness is also a liability as we now discover by some of the legal cases being won by opponents of open source software as reviewed in a recent Ivy League Law Review article (Cornell Law Review, Huang is the author). I am sure that most developers of open source have integrity like you. However, there are a few like MSSlayer (see above) and his type who openly brag about their ability to pirate other's trade secrets into their open source code. When they act upon their malicious skillset, the end result is you get a legal maze of problems for the other 99% of open source developers who have integrity. The honest open source developers have to live with the legal implications of this hacked trade secret or code in their open source application. You need to depend upon 100% of people having integrity for an open source application that has long term legal viability. Unfortunately, that is too idealist for the real world.
I have no problem with proprietary software. But when government uses software, I prefer that the code be open to peer review.
The Total Cost of Ownership is a topic that can change with each situation, each software package, even with each user. But not being able to review the code is something we cannot afford.
The real problem and expense is an issue of management. Microsoft makes it as easy as possible for people to get locked in by the promise of doing all the work for you. With Linux, there is an expectation for people to take some initiative either by learning it yourself, or hiring someone to remember it all. Fortunately this is easy because for the most part, there is primary or third party documentation that is easy to follow and understand. But like with anything else, if you don't try, you are going to pay for it. Between all the people that read the documentation and made an effort and are seeking expert help for a few pieces, they are going to pay the same price for support per hour as you to be hand held through everything.
So average TCO is very misleading, and even median TCO makes some bad assumptions. How about look at the range of TCO and listen and take advice from those that were able to do successful implementations. Listen to what worked and didn't work. When you look for advice, do you want the average story, or the most common story? Of course not! You want to know cost / effort of what works + cost of worst possible scenario. Using this information, you can decide what resources are important to invest in to reduce business expenses. Microsoft, Apple, Red Hat, and Sun want to offer you total business solutions. The first two specialize in simplicity, but at the expense of flexibility and diversification among others. Within those two elements, OSS typically offers modularity, and for the greatly ambitious, well documented code that is easy to add onto, whereas Microsoft and Apple limit you to API's that can't be audited (for whatever that is worth).
A better government I thought Americans appreciated was the idea of participation by the people. Even if most people choose not to participate, the opportunity for all to become active political members has always had a high value. While well managed use of F/OSS has survived the FUD, even if t was more expensive, isn't there an obligation in the digital age to support transparent government through open standards? It is not impossibly expensive to enable our best and brightest to keep us aware of the way things are working, and allow any American to become one of those people?
There is no way this discussion would even be taking place if Microsoft were not an American company. Why? because there is no way we are going to give that away! Why should we take what should be given to the American people and give it exclusive to one very small American company. Sorry, but Microsoft is very small when you consider opening opportunity for all.
The only counter argument is "Just sell out because I don't care". Well, you know what? I don't buy that! The Internet is an example of what can be built on free open source software and open standards. ATM, token-ring, and mainframe systems are what came from proprietary software, which gave us great opportunities to get off the ground. TCP/IP packet switched networks were evolution and birth of digital freedom and ultimately the Internet.
Government is ready to move forward.
Inmost cases, it does not make sense to replace existing aint-broke-yet systems just for the sake of open-source or even cost reductions. There are natural replacement points where this can happen more effectively, as long as the IT teams have had time to prepare.
I thought President Obama was going to appoint a Federal CTO. That person should be the one making the decision and setting up the supporting teams, planning, training and processes to make it happen. There is plenty of good learning from case studies in South America and Europe that could be applicable.
I've done way way too many system upgrades, changes, etc. to know how it really works in business.
------------------------------------------------------------------------
ROFLMAO!
Oh please, stop ... my sides are hurting!
http://www.picogrid.org/
- by Dingus9 January 22, 2009 1:30 PM PST
- I guess I am forced to ask the question, why is this the presidents decision, we are in a democracy. If the mandate would only cover his executive branch operations, then it makes sense to begin a switch. However it would seem unfair to require all executive employees to use a specific set of software, if and only if another equivalent product was more usable, or more preferred. I can't imagine what the repercussions would do to all of the current executive branches some examples being the IRS, FCC and law enforcement, who all rely on technologies to function. Just look at the scramble the FCC's mandate of digital broadcast stations has caused(pro digital.) Now imagine that across all US government computer systems Nation and World wide! Maybe a more gradual approach would be advisable? What ever the decision, maybe the debate of intellectual property and open source will finally get "Noticed" by elected officials.
- Like this Reply to this comment
-
-
- by ChipAndre January 22, 2009 1:55 PM PST
- It is not necessarily the President's decision on a case-by-case basis, but it IS up to the President to set guidelines that should be followed by the people who do make the case-by-case decisions. It is VERY important that these guidelines be well thought out, or there could be massive problems.
- Like this
-
Showing 1 of 3 pages (110 Comments)For example, the Bush administration decided early on that it wanted to do away with the (perfectly functional) Lotus Notes based email system that Clinton had been using. Instead of examining their options, they went with the Biggest Name in the industry, and switched to Outlook and Exchange. They never bothered to look into whether or not this setup was secure or would actually be able to do what they needed it to do. The result: thousands (or millions, depending on who you ask) of emails that have gone "missing".
Open source alternatives may or may not have provided a better solution, but TAKING THE TIME TO EXAMINE ALL THE OPTIONS certainly would have led to SOMETHING more appropriate. The fact that Bush demanded that the system be changed without doing any research caused that particular debacle. Obama taking the time to examine his options and set guidelines based on research and expert opinion shows that he's far more aware of the importance of IT.