There are really two markets for desktop Linux. One is individual users. I'm ignoring them here to address IT departments. If you're a Linux user outside of an organization, you probably face many of the same issues as corporate users, but you can (and must) deal with them yourself, and therefore decide for yourself whether Linux or Windows or MacOS suits your needs best.
The other market for desktop Linux is business organizations. Their OS needs are well-known: reliability, security, compatibility with existing data and devices, and the availability of applications they need to accomplish their business objectives.
To compete on the desktop, Linux must score at least as well on most of those criteria as the other choices, and it does. It's at least as reliable and secure as Windows XP. Microsoft might have the edge in compatibility with existing data and peripherals, but Linux has the edge in compatibility with existing clients -- you may have to buy a whole new PC to upgrade from Windows 98 or 2000 Professional to XP.
Application availability can be a killer. While there's now a greater range of open source applications for users, the number still doesn't stack up to what's available for Windows. But more important than what's available in shrinkwrap is what's been written for special purposes. While simple Visual Basic for Applications macros may run in OpenOffice, the highly customized ones that many businesses rely on probably won't. The same is true of applications programmed in high-level languages. Virtually any such program will require more than a simple recompile of the source code to work under a new operating system.
There's one other key component that I thought was hindering general deployment of Linux in large organizations -- lack of a good desktop management client for server-based network management frameworks. Applications such as LANDesk Software's LANDesk Management Suite, Veritas Desktop Management Suite, Novell ZENworks for Desktops, Computer Associates Unicenter, Tivoli, and Novadigm Radia Management Suite are vital to keeping costs under control when managing large numbers of clients. These programs must be able to perform hardware and software inventory, software distribution, remote control, and desktop policy management.
As soon as I did a little research, however, I learned I was wrong. According to a recent buyer's guide in Network World, leading products like Unicenter, LANDesk, and Radia already support Linux clients. It seems reasonable to assume others will follow suit.
Yes, there are other issues for organizations that switch operating systems, including training for users and system administrators. You certainly have to figure those costs into the decision whether to change desktop operating systems. But that doesn't negate the assertion that Linux is ready for desktop deployment now.
Of course, just because Linux is ready for the desktop doesn't mean users are ready for Linux. Users get very comfortable with their computers, and quite naturally fear change. But new systems come into production all the time as the needs of a business change, and when new client operating system better fit business needs, employees have to change with the times. The best way to assuage users' fears is with a phased-in approach, migrating one department at a time (starting with the most technically savvy) and learning from each move. Also, don't take away every Windows PC at once; leave one or two available in each department, if no longer officially supported, for those that might have a legitimate need for them.
Any network manager facing a desktop upgrade decision ought to factor Linux into his or her calculations. I haven't seen any hard figures (can anyone point me to any?) but it wouldn't surprise me if it took just as much effort to upgrade Windows 98 clients to Windows XP as it would to migrate them to Linux. The initial expense is less, and the total cost of ownership on an ongoing basis is lower. What's not to like?
Note: Comments are owned by the poster. We are not responsible for their content.
This is very brave and incisive commentary.
The Linux world has been crying out for a writer with the courage to step up and pen a "Linux is too ready for the desktop" column. It may have been a week ago that the last one appeared, and that's simply too long. If the point isn't reiterated ad nauseum by every cheerleader columnist looking to phone yet another one in from the pulpit next to the choir loft on at least a weekly basis, it might expose the crisis of imagination that's had this exact same column appearing from everyone and his dog for the last two years.
First it's hard as hell to get Linux to do all the standard things right out of the box.
Is it easy to setup and use to the point that a new user can sit down and immediately do all they want...not quite.
Okay-- I'm a self-professed geek. But three years ago, my wife (a fashion designer) decided to join me when Windows crashed on her one too many times in a day. She was appalled that a restart (along with the attendant loss of data) was something she had to factor in to her work schedule (she was in school at the time and doing a lot of writing-- both research and articles for several publications. StarOffice 5.2, even as slow and dodgy as it was, was better than having to schedule time for reboots. If StarOffice crashed, it didn't bring down the whole OS and even recovered what was being worked on with minimal, if any, data loss.
That was all it took for her-- a decidedly non-technical person. Of course, that led to other uses, but the overall trend was better and better performance, functionality, and-- perhaps most significantly-- no arbitrary extra software costs for all that.
When I was hiring a tech support guy, I required resumes in either HTML or straight text format<nobr> <wbr></nobr>:-)
Sure, they can. If you use RTF format then you can pass files back and forth with almost no issues at all.
Was Windoze 3.1 ready for the desktop?No, but Windows 3.1 was.
(1) Installers<nobr> <wbr></nobr>... "I was disapointed to see that there wasn't a setup program. I had to go to the unix terminal and run some scripts. Why can't Linux make it easier?"
(2) Documentation
(3) Menu Organization - To most of the people I talk to who start Linux they find it confusing when there are like 3 different places for Office Programs on the menu.
One vital question should always be asked (as I was when starting in computers) and that is "What do you want to do with it?" This gave a very "real" direction as to what I would start in. The programmers environment is not the same as a person who just wants to check his/her email and cruse the web. Did Linus want to "just" program or did he have specific thing in mind? When dealing with support, what are we really supporting!?
I would like to propose that it is a much larger thing then a particular OS or application. Whether it is writing source from a engineers standpoint, building the electronics to support functionality or helping folks with printing pictures on their wonderful new HP photo printer, the spectrum is vast. No one answer fits all the catagories, does it? We all make discisions, let us grant freedom to each other to decide how, why and when would like to support the industry. Whether it is in issueing paid licencing and and "locking" people "in" or in open source solutions. There are obvious pros and cons on both sides!! For me supporting the enduser (In corporte or individual) funcutionality is the key.
Tom
i'm a consultant. i write reports after every engagement. the required format is Word. i write my reports in text, import them into open office via a template i have created. then i move them to a windows machine, open them in Word and fix the formatting errors.
i do all that because i hate using Word and prefer my linux desktop. to expect millions of office workers to go through that process all day long is utterly stupid. i'm sorry to say that the real fact demonstrated by this article is that the author has no conception of daily life in a corporate office. while that may be good for him, personally, his argument is shorn of any credibility by that fact.
there is a reason why, when you save a document in "Word" format in openoffice, a dialog box pops up with the message, "This document may contain attributes and information that cannot be saved under Microsoft Word 97/2000/XP. Do you want to save your changes using the OpenOffice 1.0 Text Document format?" The author should acquaint himself with that reason.
if you need a second test, create a "read-only" password-protected document in Excel. now, try to open that document in openoffice. you can't. openoffice cannot detect the fact that the password-protection applies only to making changes and not to viewing the document. these sorts of documents are widely used in our organization, for maintaining documents like product status updates or group schedules, that should be world readable but not world writable.
openoffice is good for simple, general document production. it is not production quality for any office that produces complex documents that must be used by Word users. these facts are well-known to those who regularly use it. i hope and expect that openoffice will continue to be improved and will someday provide the kind of interoperability needed on a non-windows desktop. until that happens, the author's pronouncements have no relevance to people doing real work in the real world.
mp
"happily using a desktop on linux since 1997"
because it's a competitive situation and we (linux users) are trying to take user space away from the Other Company. that Other Company is not going to do anything to make that process easier. nor should we expect them to do so. it is up to us to produce software that will persuade users to leave that Other Company's products behind.
mp
Oh, and the truth of the matter is, if the teenage son is fragging his buddies on a Linux box, sooner or later the parents are going to learn Linux, if, for no other reason, than to try and limit juinor's online escapades. (Yeah, like that'll work.) LOL
Fir$t po$t!
Posted by: Anonymous Coward on April 12, 2003 12:37 AM#