I'm assuming you mean open source software in general, but I'll use two readily available open source applications as an example: Paint.Net (http://www.getpaint.net/i
Both of these programs are excellent examples of well-written and documented applications from the open source community. Paint.net even has native 64-bit support (something Adobe is still trying to catch up on). Open Office is a good substitute for Corel's and Microsoft's office suites.
The problem from an organizational standpoint is standardization, interoperability and end-user support by the IT organization. You really want all of your users to (within reason) have the same basic desktop application suite (word processing, email, spreadsheet, presentation, internet browser, etc.). Otherwise, desktop support becomes a nightmare as you try to support multiple diverse applications.
From a user standpoint, you have familiarity and training issues. Like it or not, there are many more people in the employee pool (present and future because of turnover) who have at least a basic working knowledge of Microsoft Word and Excel. Sit one of them down in front of a machine with Open Office and see how long it takes them to become as familiar with that product as they were with Microsoft Word, for example. Some will become frustrated, throw up their hands and ask (read: demand) that they receive training. Can you buy a "Learning Open Office" CD at CDW? No, you can't, though there might be a "Open Office for Dummies" book (I didn't check, but you know what I mean). Others will dive in and do the best they can and eventually will learn to become just as efficient with Open Office as they were with Microsoft Office.
Interoperability and compatibility: Open Office and Paint.Net have worked very hard to make sure the end result of using their products can be exported to the common mainstream applications. The reverse, unfortunately is not always true. For a simple "Dear Sir" business letter, it probably won't matter and you'd never know the difference. But if you're writing a 50-page manual, or a prospectus using charts, graphs, embedded symbols, varying formats, bookmarks, footnotes, bibliography, table of contents, indices, appendicies and so forth, that's where you may run into interoperability and compatibility issues. It's kind of a repeat of the old HTML bugaboo where you have to test your web code with different browsers to make sure they all look the same, whether it's Firefox, Internet Explorer, Opera, Netscape or whatever.
Open Source software is almost by definition always a work in progress (but then, so are most mainstream apps too). One of the main advantages of Open Source is cost. Compare a 100-seat license for Open Office with a 100-seat license for Microsoft Office 2003 Professional and you'll see what I mean.
Training and Support are two other issues. Take a look through the phone book, or on Google and see how many companies offer training classes for Microsoft Office, then see if you can find ANY who offer classes in Open Office. Same goes for IT Consulting firms, though with most consulting firms, you can usually find at least one geek who swears by open source and has three Linux machines at home and loves to poke fun at Microsoft fan-boys.
Vulnerabilities and Patching. If a vulnerability or exploit is discovered for a Microsoft product, and Microsoft publishes a patch for it, those patches are rolled out automatically through Microsoft or Windows Update (or through SUS or MOM in a large organization). For the open source community, you have to monitor the website, newsletters and the blogs to find out there is a vulnerability and where to go get the associated patch for it. This is time-critical and manpower intensive. The good news is that because open source software has such a small market share (at least at present), the guys in the black hats turn most of their attention to Microsoft, a much bigger target and a much larger target audience.
Main Topics
Browse All Topics





by: A1opusPosted on 2007-04-01 at 23:56:09ID: 18834686
Well there r lot of disadvantages, the following URLs will guide you more:
/Perceived _disadvant ages_ope.h tml articles/c omment/061 903_Dmitri .php net/articl es5/open-s ource- soft ware.htm badman/OS/ img5.html
http://eu.conecta.it/paper
http://www.gismonitor.com/
http://www.tamingthebeast.
http://astro.temple.edu/~d
If you want more information kindly ask.