Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Linux Software

What the Linux Community Needs to Grok 570

Charles Connell sent in an article that he wrote following the onslaught of flames he (and even his boss) got following articles that were critical of Linux. I've said many times that Linux's worst enemy is the army of angry, self-appointed advocates: they don't write code, but they have a lot of pent up anger that often gets directed in the wrong places. Anyway, read the article and talk amongst yourselves.
This discussion has been archived. No new comments can be posted.

What the Linux Community Needs to Grok

Comments Filter:
  • After reading this...I think the guy is right on.

    I use Macs...have used Macs ever since I stopped using my C-64. I've been trying to work with Linux on IA-32. Right now...I'm at the point, 11 monthes later, where I feel comfortable using Linux as a Server. It's just too much effort to retrain myself to use Linux as a desktop OS. I've found the documentation for Linux to be less than helpful for the most part...there is no central place where I can get information. I'm used to the Macintosh world or the Novell...where I get help from fellow users...not told to RTFM.

    I've been trying to find out if there is a way I can mount Sever Volumes on my Mac like I can with AppleShare or Novell...for eleven monthes I have been looking and have found nothing that says yea or nay. I don't have any Linux friends to ask, I'm on my own here...and it's not that easy of a path. I want to put an Orb Drive in my dual boot NT/Red Hat 6.1 box...but where the hell do I get a yea or a nay about this? No where that I see.
  • The same thing will happen to you. The Linux killer is just around the corner. You don't know what it is, and you won't recognize it when you first see it. The next generation of techies will understand it and will consider you old fogies for having your heads buried in the Linux sand.

    Great article, and great conclusion! Hopefully the fanatics who can't grok the basics of a shell prompt but seem to think they can speak for our entire community will read it and think twice next time they start to act like a spoiled child.

    Linux is a great operating system, and it's getting better and better every day. It's not the best tool for everyone's needs, but it suits mine and I'm happy. I enjoy being part of a community that fosters sharing and open ideas, and despair when zealots give us a bad name by acting foolishly.

    The author hit it right on: Linux will not be around forever. Something better will come along, or Linux will evolve into a different beast entirely and make itself obsolete. What won't change is the community we all build around it and the ideals to which we hold. The recent influx of corporate influences into our community has proven that we can grow and prosper beyond our hobbyist beginnings without compromising our integrity. With a bit of luck, some patience, and a little less fanaticism we'll keep our community throughout the coming years. Good things are in store for us all!

  • Mr. Connell makes a number of questionable assumptions:

    1. "People set up computers alone."

    Actually, they seldom set up computers at all. They use preloads. If customers actually had to install Win98, let alone WinNT, on a blank hard drive, we would cease to hear these foolish, context-less complaints about Linux being "difficult to install".

    2. Further, he assumes that consumers won't accept any other sort of setup regime. Never mind the fact that they already do (i.e., preloads): Why should we believe that OS setup/configuration cannot be a salable service, just because Connell can't imagine it?

    3. "To address this reality, new computers with pre-installed Linux should work fully and completely the first time they are turned on."

    The above appears to assume that such is not the case, which is a fearsome insult to the painstaking work of ASL, Tuxtops, Cosmos Engineering, Cobalt, PromoX, Rebel.com Inc., etc.

    However, he goes on to (one assumes) clarify what he meant:

    "When the user plugs in a standard option that they already own -- printer, network, external storage device, etc. -- those options should be recognized and configured automatically." By way of comparison, he cites MacOS running on Apple hardware.

    But that begs the question: Isn't the ease of installing peripherals on MacOS made possible by the carefully controlled standards of Apple-compatible hardware?

    If you'll pardon the expression, "Apples, meet oranges."

    4. "Unfortunately, most people don't know a computer expert of any kind, much less a Linux expert. It is important for the Linux community to keep in mind that most users will be completely on their own when setting up or installing Linux systems and software."

    Again, this assumes that the only way the world can run is the way Connell is familiar with.

    5. "Learning new applications is hard.... Several Linux fans wrote to me stating that the 'application problem' is actually a 'user problem'. Users are incorrectly resistant to change, the argument goes, when they should be accepting something that is new and better. This is backward thinking."

    More to the point, the entire dichotomy Connell poses, here, is a red herring: The general (proprietary-OS) computer population already learns new applications on a recurring basis -- every time their vendors' upgrade treadmills crank up another notch, and also often when a change of management (or of employer) means learning the new local "standard": If the management team du jour says you're going to use Groupwise instead of Exchange, you'll learn it. If the local standard is Microstation instead of AutoCAD, you'll learn that, too. And when the next revision of your cherished office bundle shuffles half of the functions around, you'll learn that, too.

    The point is that, if you're already contemplating a forced upgrade to your proprietary-OS package (or between two such packages), maybe the real question isn't whether learning new applications is hard, but rather whether learning new applications on Linux is significantly harder than what you're already considering.

    6. "It is not the job of the masses to adapt to your computer system. The history of business is carpeted with extinct companies that did not understand this."

    This seems to assume that Linux is a business. Of course, there are businesses based on Linux, but Linux itself will not live or die according to market acceptance the way, say, OS/2 did. If every significant Linux-based firm were to close its doors tomorrow, the open-source developer community, the user base, the Internet-based community mechanisms that create and nourish them both, and all the $1.99 CD-ROMs would go on with barely a jitter.

    Connell's spectre of "extinct companies" is a mirage.

    7. "Consider focusing your immediate application efforts on the few key pieces of software that receive 90% of home and office use.... You might create a native Linux look-a-like for MS Word."

    Connell's assumption, here, is that this is or should be a task for the Linux community at large (or at least for Linux developers collectively). Which begs the question: Why? Those who want such software will create it or pay for its creation, if they want it so badly.

    It's surprising that Connell should raise this argument, since obviously he's been around Linux for quite some time. The community's tradition is well known, and eminently pragmatic: If you want a piece of software created, you're free to take out your copy of gcc and hammer it out -- or give someone else a personally compelling incentive to create it.

    8. "The Linux community has been on a honeymoon as it has created the Linux software.... As Linux is embraced by more organizations, and used in more ways that are crucial, the demands upon you will increase."

    The Linux community has ignored clueless demands before, and it no doubt will again. "Pressure" and "demands" from third-party companies are a no-op, per se. Of course, they can "pressure" and "demand" coders they pay adequate salaries to (if they can retain such), but that is a different subject.

    The assumption, in any event, is that such "demands" are a problem. That is a claim without substance.

    "Wealthy organizations, accustomed to getting their way, will demand impossible schedules from you, and then complain if the quality is not perfect."

    Ditto.

    9. "Some readers have suggested to me that the open source method of software development causes project management issues to evaporate; that the projects manage themselves. This is a fantasy."

    It is also yet another red herring. Those who need and want legal accountability and fiduciary responsibility will hire (and otherwise pay) people who wish to agree to such relationships. But that occurs distinctly from the regular community-based open-source model.

    10. "You will be managing a large public programming project with conflicting demands, tight schedules, and the need for high quality."

    Connell fails to state what hypothetical assumptions would lead to this situation, but one gathers that he means something like what AOL/Netscape's project managers for Netscape 5.0. Indeed, Netscape might have a project-management problem -- but, if it decides it doesn't like limited social contracts, it can at any time have exactly as many programmers on staff as it's willing to pay for (thereby buying into an entirely different collection of problems).

    Connell also begs the question of what constitutes "good project management". If community-based open-source projects can't always be counted on to meet milestones and deadlines, it's equally true that they're largely immune to shipping in bug-infested condition just because some butthead executive needs to doctor the end-of-quarter books.

    11. "Humility is a virtue. If Linux succeeds in a significant portion of the computer world, and it looks like it might, your time in the limelight is short." Connell then tells the cautionary tale of his former career at Digital.

    However, again, Linux is not hostage to corporate fortunes. Linux cannot "go out of business", or "take a nosedive".

    Connell's suggestion that Digital's fate can befall Linux is thus illogical.

    12. "The same thing will happen to you. The Linux killer is just around the corner. You don't know what it is, and you won't recognize it when you first see it."

    The assumption here is that this would necessarily be a bad thing, and that we have some reason to cling to Linux in the face of this "killer". Suppose the "killer" is something better than Linux. Why would we not welcome it?

    "The next generation of techies will understand it and will consider you old fogies for having your heads buried in the Linux sand."

    Begs the question: Aren't we on Linux because we're early-adopter types who chose it for various technical advantages? If so, wouldn't we be the ones adopting and understanding this new thing, and looking back over our shoulders at the reactionaries?

    And, lest we forget: Connell seems to assume throughout his essay (but here, particularly) that one uses just one operating system at a time. Yet, it should be obvious that diversity serves a purpose, and that no one OS fulfills all roles well.

    Connell is obviously a talented writer. It would be good to see him cease arguing bogus positions resting on doubtful premises.

    -- Rick Moen
    rick@linuxmafia.com

  • It's not about dumbing down Linux. It's about putting some suitable resource sucking eye candy on top of Linux for dumb users.

    Who cares what software people want to run on Linux. Don't be so small-minded.
  • I've never submitted a kernel patch or wrote *anything* that made it to metalab, so don't feel so bad..I would probably fit into your second and third categories; I pushed for and got the chance to implement Linux at work and I advocate it wherever I can, but I try not to be pushy, arrogant, or rude.

    I do agree with the importance of working together on Linux instead of taking the `ivory tower' approach or becoming the proverbial Catherdal.

    I know "Animal Farm" analogies have been flying left and right lately, and I don't agree with them at the present moment..I hope I can say the same in a year.
  • This article on slashdot, and last weeks rant about Loki/Blizard ports on LinuxGames shows that people DO pay attention when deluged in hate-mail.

    People pay attention to drive-by shootings, too, but that doesn't mean they're effective at anything.

    This guy didn't just get flame mail -- people wrote his boss suggesting he be fired!

    Sure, he needs a clue or two (see comment about wealthy customers and schedule pressure) but *nothing* he said justifies atempting to interfere with his livelihood. For that matter, he seems reasonable enough -- why flame?
  • Name for me one significant end-user application that is clearly superior than the equivalent in Windows.

    The argument is a self-fulfilling one. 90% of apps are written for Windows because it's the dominant OS. Nothing is as good when it is ported or copied to another OS (look at Microsoft's own trouble with Office on the Macintosh and the ire it has provoked from those die-hard users). Since applications for Linux are invariably either ported or copied from existing Windows apps, yes, their quality is going to be lower. But I think there's one that at least comes close.

    The GIMP. This may be highly debatable, but I run the GIMP on my 40 MB RAM, Pentium 120 and it never crashes, has all of the features I've come to expect from Photoshop, many many many more default filters, and a much better interface (no large single window). And that's just the development version (Adobe won't let me use their development version).

    Photoshop is a good program, but it frequently crashes and is a huge memory hog (relatively speaking). I use both regularly and I find myself saying, "Man, I can do this in the GIMP," a lot more than "Man, I can do this in Photoshop."
  • Try a statistical statement of probable fact. Arrogance is not the same thing at all.

    --

  • Hmm... However, I think this is a case where intent was important. My intent was simply to indicate that I am quite the Linux fanatic. Maybe I should've been more careful in my phrasing.

    --

  • What happens when something goes wrong? I'm not about to tell my grandmother over the phone how to use vi to edit her /etc/passwd to fix something.

    But what happens when something goes wrong with Windows? You're prepared to talk her through fixing a corrupt registry with regedit? Didn't think so...

    Other than that, I agree with pretty much everything else you said!

  • And iMnsho, there you misunderstood HIS points.

    "People set up computers alone."
    His text relating to this point is not based on "the difficulties people have when installing an operating system for the first time." Rather, it is based on setting up a newly purchased computer for the first time.

    Currently, there are several scenarios for someone buying a new computer and getting it usable in order of user complications. Please note that for the vast majority of users "usable" means able to complete a basic set of tasks. And those tasks are not playing with the computer itself. They are: word processing, email, games, web access.

    1. The Macs. Take it out of the box, plug in the electric, monitor(if it's not an iMac), printer and phone line and turn it on. You can do all of the tasks on my list. You may need to pull out a credit card to set up your ISP, but other than that you're up and running.
    2. A Windows box. You take it out of the box, hook the hardware together, turn it on and it autodetects most of the hardware and sets it up. Depending on whom you bought it from, all of those tasks are ready to go, same as the Mac.
    3. A preinstalled Linux box. The primary hurdle in this is finding one for sale in mainstream distribution channels. Even then, you still get to try to manually configure virtually all of your hardware (and since you just bought your first PC, you don't know what any of the specs mean), then you need to dig to figure out how to do most of those tasks. /tangent/ My biggest complaint about command-line based software is that you have to remember the command names (even to be able to get a list of the switches). In a GUI, you can explore to find what you're looking for./tangent/
    4. A Windows box converted to a Linux box or a blank box waiting for either Windows or Linux. This is the only setup that requires installing an OS from scratch. You're quite right. An average user would have difficulty with any OS from scratch, but he was talking about the entire system being bought and set up, not just an OS being set up on an existing box.
    Re: the manual in most distributions. The biggest problem is that they assume you already know enough to install the thing. Also, manuals (in general) as an only resource during a technical process are notorious for making users scream "BUT". As in, "but my monitor isn't listed, etc." Manuals can't deal in exceptions and the exceptions are what stops most people dead in their tracks.

    "Learning new applications is hard."
    In this section, you make a subtle assumption about "Linux" that seems to permeate discussions such as these. That a change in one incarnation of Linux changes all incarnations. This is simply false. Just because Caldera includes a simple install, with a limited version of DiskMagic(or whatever it's called) and a copy of Tetris to play during install, doesn't mean that Debian, Slackware, S.U.S.E et al need to include it. Nor does it mean that a decent Word clone will overwrite your copies of emacs and vi. Why should it matter to you if one version of Linux is "being dumbed down"? For most users, the computer is not the end; some kind of work is. Ergo, needing to know what is going on in the computer is a waste of time to them.

    I know that the majority of Slashdot readers do not own a high end camera. Most likely, if they own one at all, it's a simple point and shoot. A photo geek (and many do this by the way) could be decrying all of the amateur people taking bad pictures without so much as minimal knowledge of film speed, apeture(sp) settings, shutter speed, lens length. After all, in order to get a decent picture, you need to know what's going on with your camera, film, printing process, etc. But, if you can take pictures of the annual drunken bash with a point and shoot and you're happy with them, why do you need to know all of that?

    If indeed, someone decides to buy an OS (and not just a PC with the OS on it) BECAUSE it's an alternative, your mindset makes sense. However, some people are buying boxes for the first time and being told they need to buy a Linux box because it is more reliable, more stable, cheaper, etc. not because it's an alternative OS. In those cases, the user is approaching the computer to get something done, not to be a rebel.

    "Open source still requires good project management"
    I'm not going to quibble with you on that point. I don't necessarily agree with either side of this issue.

    "Humility is a virtue."
    One of the factors that is being brought into play by the companies is that of evolution by proxy. Up until now, the user base for Linux has been able to implement their design ideas. That allows it to truly be democratic and to evolve according to its users' wishes. However, all along, there has been a group that wishes they could get a simpler interface or other features they'd like, but being unable to code themselves, they are unable to get their ideas into the evolution. Now enter Red Hat, Corel, et al. Those companies will only develop, evolve or improve something that provides a profit margin. You argue that that is a limited vision. It is no more limited than a developer only vision. A company will only see a profit potential where a section of the current or projected user base will spend the money. If those changes wouldn't have been implemented by a developer only vision, that means that the company has found a group of users that had needs being unrepresented in the current democratic development process.

    Just remember, because all of your interests/features are included in the current vision, doesn't mean mine are.

    Any spelling/grammatical/coherency errors are due to no editing, lack of sleep, and a desire to finish posting while it is still a relevant comment.

    LetterJ

  • Overall, this was a very good article, highlighting many of the already-known weaknesses of Linux and it's corresponding community.

    However, there are a few issues where Mr. Connell is, IMHO, mistaken:

    "People set up computers alone."

    Mr. Connell talks about the difficulties people have when installing an operating system for the first time.

    For the 'average' user, trying to install Windows 98 from scratch is _just as hard_ as trying to install Linux from scratch. Installing an OS from scratch is _not_ something that today's "average" user is an any way capable of doing on their own.

    He also speaks of the manufacturer support line being the only resource available to the customer. Again, this is not entirely true. Nearly every 'boxed' distribution comes with a printed manual, and from personal experience I know RedHat's manual to be _extremely_ thorough in covering not only a step-by-step install process, but in also dealing with any problems that might occur both during and after the installation.

    "Learning new applications is hard."
    In this section Mr. Connell talks about the argument that users are resistant to change, and that software should be tailored to work exactly how the customer is expecting it to.

    While he makes a very good point for 'classical' computing methodology, this is simply not the case for Linux. Linux isn't about dumbing itself down to the 'average' user's level. It's about raising the average user to a level in which they can understand the things that they're doing on their computer.

    By deciding to purchase and use an 'alternative' OS, a user has already made a decision to learn something new. That means they should be expecting from the beginning to be learning and adjusting to a new way of doing things. You don't honestly think Microsoft and Apple sit down and discuss the UI for their programs and how they should make them compatbiel do you? Linux will have it's own, unique user interface, just like Apple and Microsoft each have their own, unique UIs.

    "Open source still requires good project management"

    This section, while well-written, argues from the incorrect assumption that the Linux community is/will be at the beck and call of the corporations selling it. Things are, in fact, exactly opposite from that. The Linux kernel itself dictates what features are possible, and it is the responsibility of the _corporations_ to provide the neccesary resources to get the features they want. For an example, see RedHat's sizeable list of on-staff developers, including one Alan Cox.

    "Humility is a virtue."
    Humility is indeed a virtue. However, the problems Mr. Connell describe in this section stem from a lack of vision rather than a lack of humility. Linux has the potential to become the best computer Operating System, period. Why? Because it is designed and evolved by _its own users_. It goes in the directions its users want it to. Not the directions the limited vision of a corporation out to make a profit dictate. The Linux development model cuts out the 'middle-man' of profits and share-holders, and goes straight to the user instead. It is truly democratic software. Anyone is capable of contributing to the whole if they make the effort.

    Linux isn't just an Operating System, it's frame of mind.
  • Charles is right that Linux, even with KDE or Gnome, isn't suitable for SOHO environments where the user doesn't have a 'Linux Friend' handy. And I don't see this changing without us ditching the UNIX underpinnings.

    I disagree. IRIX seems to be fairly user friendly last time I tried it. MacOSX comes from Apple, whose fortunes live and die by UI and ease-of-use, and they seem to be pretty happy with a unix-based infrastructure.

    The point is, it doesn't really matter what you're running underneath as long as it's flexible, stable, and efficient. Linux is (or can be configured to be) that. What you need for ease of UI and ease of use is for motivated developers to create that interface and libraries. It's happening as I write this.

    Personally, I believe that Linux will eventually make serious desktop inroads for many reasons (price, dollar-magnet of UI inevitably drawing commercial interest, international nature of linux, power on old platforms, driver support) and that the areas which are weakest (ease-of-use in the UI, ease of configuration, desktop apps) are being worked on.

    Don't forget, TiVo is a Linux-based solution [tivo.com] that is extremely easy to use...

    It can be done.

    It SHALL be done.

    Be patient.

    Your Working Boy,
  • Are you sure it was a 509b, or did you mistype and mean a 905? I've never had any problems with 509b (once pnp was disabled), and I've known dozens of Linux boxes with them. (Including two in my home firewall.) I can't imagine that anyone would be badmouthing them on Usenet, because they've been stable and recommended since I started using Linux in 1994.
  • File formats.

    If Linux et al. are content to be modest niche hobbyist OS' on the desktop, rather than taking in a sizeable market share, we will not present enough critical mass to persuade content producers to distribute media in formats we can read. We will cede the web to QuickTime, the Windows Media Player format, and versions of RealMedia for which Linux players are unavailable. Others will exchange files that we can't read, and wonder at our curmudgeonly disinterest in communicating with them.

    This is already the status quo to some extent (it is one of the main reasons why I have a Windows machine.) Arrogance towards the 'great unwashed' will exacerbate it; growing the ranks will make it unteneble to keep content in closed formats.

  • As Linux is embraced by more organizations, and used in more ways that are crucial, the demands upon you will increase. New feature ideas and bug reports will no longer go onto a "wish list"; they will go onto a "hot list." You will face pressure to add 50 new items to the next release, when it really ought to have 10. Wealthy organizations, accustomed to getting their way, will demand impossible schedules from you, and then complain if the quality is not perfect.

    Here's one point I take issue with. While I don't take issue with its clairvoyant validity, I do take issue with the idea that this should be accepted practice.

    The idea that anyone should say yes to an impossible schedule, over-promise, kill themselves to work inhumanly sustainable hours is just ludicrous. But we've been doing it.

    It's time to stop it.

    Just got this in my mailbox, and I think it says just about everything I want to:

    Gold Rush Mindset Undermining Programming Field [www.tao.ca]

    Think about it, if you're 20-30 something now, and working 90 hours a week, do you want to be doing that into your 40's? Should you even be doing that now? Why do you accept it?

    If we're so valuable, and in such short supply, it's time to start maybe from the grunt programmer on up to put a stop to the acceptable practice of demanding the impossible and change it into delivering the sane.

  • But if I could point a finger at a possible threat it would be to another Unix base. And a very good user interface; - MacOS 10

    You're making the same mistake the author of the article did - you're ignoring the critical difference that open source makes. While MacOS 10 has open-sourced the BSD backend, but the bit that differentiates the Mac certainly isn't.

    Without completely open-sourcing MacOS, the platform will *never* have many of the advantages (lack of vendor domination, speedy bugfixing etc.) that Linux and the real BSD's do.

    Don't get me wrong I'm sure that Linux could get very sick and old. But it has to many hardcore advocates to just disapear.

    Advocates don't keep a system alive. Users and developers do.

  • I respectfully disagree.

    I'm not a Mac Zealot by any stretch of the imagination, I rather loathe them, but I have to use them here at work, there's a G3 sitting next to my NT and Red Hat boxes here as I write this. However, I think that Mac OS X could be BIG, very BIG. Here's why:

    1. It comes from somebody consumers already know, Apple, and they have a history of making things easy to use. It's a horribly closed platform, but easy to use because Apple controls both hardware and software ends.

    2. It runs existing Mac apps. Now, granted, I'll put on my Windows hat here, and say that ain't a whole lot compared to Windows, but it's something.

    3. It'll run Linux/BSD apps. Sure, it'll take some recompiling and tweaking, I'm sure, but once it's done, that gives you two of the three big end-user OS's. Why run Linux/BSD when you can run Mac OS X and use Linux-ish apps AND Mac apps? Now throw in WINE and you can run everything! (Okay, I'm getting too farfetched here)

    4. It'll run Microsoft Office, the dominant Office Suite. I've used WordPerfect and StarOffice, and they're great products, don't get me wrong, but end-users are terribly stubborn about switching, no matter how little difference you or I see between graphical word processors.

    5. It has a flashy user interface, I gave a Professor a new laptop yesterday, nifty new Sony VAIO, she was the most excited about Desktop Themes, yup, not DVD, not that it was twice as fast as her old laptop, not 128MB of RAM or 100Mbit networking, but that it had Desktop Themes.

    6. You'll be able to just plug stuff in and it'll work. I can't stress enough how this is important, I reccommend USB devices to people all day long, since I know I'll eventually have to install them. I flatly refuse to install parallel port scanners and zip drives anymore. Sure, I can get them to work the majority of the time, but they suck, and when they don't work, you're screwed. My mom and dad, and yours, want a system they can plug something in, and it works, they don't want to track down text files to edit or re-compile a kernel. If Mac OS X delivers on the promise to keep the console completely hidden for 99% of things, this should happen.

    Now what are the downsides?

    1. It's not free, Linux is free, that's nice for those of us who are poor, but we're used to an OS coming with our new computer anyhow, and most users don't change that over the life of their computers, so this will be irrellevant to all but those who get fed up with windows and want to switch to something else without buying a new machine.

    2. It comes from Apple, who tends to screw users from time to time, they abandon hardware standards arbitrarily and without warning. Anyone remember NuBus? ADB? SCSI? Floppy drives? You'll probably have to have an Apple computer to run it, and they're not cheap, despite what Bytemarks and selected Photoshop benchmarks compare PowerPC chips to Pentium III's at.

    3. Apple keyboards and mice suck. This really isn't related to the OS thing, but I really hate them, and wanted to say so, again. :)

    Will Mac OS X kill Linux? I doubt it. Will it convert Windows users to the Mac platform? Possibly. I don't think it's going to be the Holy Grail of operating systems, but I think it'll have a lot to offer to people who are like me, people who don't care about open-sourciness, they just want something that works well, is easy to use and support, that runs the software that users already know, as well as having the power and flexibility to satisfy advanced users. Don't forget that this will bring all those things that Linux has, Pre-Emptive Multi-Tasking, Protected Memory, etc. to the masses that are the Mac community, all with (hopefully) an easier-to-use paradigm in software and hardware installation.
    ---
  • Now, I don't know what direction Linus, Alan, RMS, RedHat, et al want this to go but I'm not particularly interested in making Linux an appliance OS for non-technical users to just plug in, autoconfig, and start word processing and web browsing. I guess that's the value add-on that RH is betting the farm on, but it's all the semi-automatic stuff in Msft that semi-works that causes me untold headaches, over-complicates and frankly just gets in my way.

    The model for this ease-of-setup is the Macintosh system, which truly is user-friendly.

    So, why don't the laity buy Mac's? Why do a lot of appliance folks who may be better of with Mac's end up with broken Msft systems? That's Msft's oversold-PC-marketing-and-the-customers-who-fell-f or-it's problem. They created the 'buy a PC or else...' gangster bullying mentality. They're not getting any sympathy and free support from me! Maybe they'll learn next time and just get a Mac.

    This is what I beleive: If someone wants to open up a box, plug it in, have printers autoconfig, start wordprocessing and web browsing, get a Mac. If you want something fairly automatic but sometimes quite challenging, buy Msft. If you want access to all the nuts & bolts and enjoy learning how computers really work, run Linux.

    To me, the value of Linux is twofold: (1) as much control as I can learn, and (2) easy licensing. Certainly #2 is as appealing to the non-technical user as the technical, (witness how many non-technical types want to run unlicensed copies of easy to use Word, Excel, etc) but a central contradiction exists - if your willing to do a lot of work yourself, the licensing can be free and easy, but if your not willing to do a lot of head scratching and puzzle solving, then you'll probably have to pay someone to do it for you, either directly on site (designer Linux!), or indirectly in lots of autoconfig type software development, Mac and Msft style, which, as I said, kinda turns me off, but as long as I can turn IT off I guess it'll be ok.

    CSMA/CD race driver
  • I guess RH & Co. can make software anyone's grandmother can use, but it seems like an awefully formidible task to try to be all things to everyone; yes I'm happy with a niche 'programmer's OS' and have no prob w/ keeping a MS box for things MS is good at. But if Linux continues to steadily evolve to a human-friendly cross platform compatible level, so much the better!

    CSMA/CD race driver
  • Linux zealots, especially here on Slashdot, are ruining the Linux "reputation". People think they are cool by writing M$, Windoze, Winblows, etc... I often get my posts get marked as troll or flamebait because of my .sig! I would not be surprised if this very post gets moderated down.

    Linux zealots do not want to hear about alternatives. I have a Masters degree in Computer Science with concentration in Human-Computer Interaction. Whenever there is a news story regarding interfaces or usability, I often post my educated comments. Guess what? Most of the times people laugh at my suggestions. Most Linux zealots say "Who needs usability we have QT and GTK widgets that already work. Don't like the" look? Change the window manager." This approach is fundamentally wrong from an HCI standpoint. Anytime I try to explaing why, I just get marked as flamebait. Oh well.

    Another issue the irates me is the "Free" issue. Linux zealots the world around chant "Linux is free, Micro$oft is expensive, convert, convert!" They do not understand that for a business to convert OS would require a large amount of money. The price of the OS (~$300) is chump change with respects to the amount lost on user productivity.

    Now that I have written this, I await the moderation to mark my post down, and the zealots to start "correcting" my viewpoints.

    Note that I use the term Linux zealot not user. Cheers!
    --Ivan, weenie NT4 user: bite me!

  • Hmm... Here's how you install Win98:

    o Boot off Win98 floppy.
    o Answer "yes" when it asks you if you really want to re-install over the existing system
    o Sit there for 20 minutes while it installs.
    o Click on the "connect to internet" icon when install is done to reconfigure for your ISP
    o Go to Start->Windows Update to get any patches from the web-based interface.

    No fdisking. No formatting. yea, a few reboots, but the system does them itself if you aren't there.

    BTW, just for comparison, I'd like to see the equivalent Red Hat install path INCLUDING PATCHING THE KERNEL TO RUN USB :-)
  • Did you actually READ the other two articles he was referring to? He did exactly what you suggested, installed and used RedHat.

    And as to your points about what the "average" user wants -- what you "believe" is probably not what is (hey, I don't mean this as an insult, it's true for most people). It's a good point -- there are 20 MILLION aol users. More than any Linux users I can count. For some people, it is the SOLE REASON THEY HAVE PURCHASED A COMPUTER. Scary, but true. I wouln't be so dismissive.
  • just a guess, and I'm wearing absetos jockey shorts, so flame away, but...
    GNU/HURD
  • Which is my point. If a corporation wants a
    feature, they hire somebody to add it.

    K.
    -
  • Thanks for the hints, I'll give that a go. My distro is ~6 months old. Course I haven't got the thing networked yet so Dling stuff & transferring via floppy is rather a pain ...

    I'm pretty sure there's enough masochistic stuff in there to keep me happy for a while yet -- the next thing I want to learn more about is low-level TCP, sockets programming etc :) It makes a nice change from AIX, anyway, which doesn't have man pages let alone Perl ...

    --

  • > When X first came up, it would only come up
    > in 640x480, I had to mess around with the
    > X86config file,

    Ha ! Count yourself lucky !

    I've been trying to get a fucntional Linux system for /two years/. Before activating flamethrowers, let me point out that my job title is "Perl programmer". I've tried Debian, RedHat and now Mandrake. Alas, X has screwed it up every time. Currently I'm trying to get it working at something greater than 200x320. Whoops, it's a Voodo3fx card, course I can't expect that to work, can I ? I mean, it's /only/ 18 months old, right ?

    The only reason the machine hasn't gone back to NT is that I'm bloodyminded (masochistic ?) enough to keep sweating over the wretched thing.



    --

  • Interesting, thanks ... perhaps the problem is something to do with the box being a strange generic model with possibly dodgy or cutprice hardware (apart from the Voodoo that is.) Also, I'm on Mandrake 6.0 -- perhaps it'll be fifth distro lucky :)

    --
  • 1. Putty [greenend.org.uk]

    3. LiteStep [litestep.com]

    Not that either of these makes Windows perfect, but definitely a lot more usable.
  • Actually, there's another side to some of these views

    People setup computers alone: true. Nope. People at home setup computers alone, but in the workplace a great number of people do not, and that's a huge market. What then becomes important is automated setups and the ability to keep users from breaking things; Linux excels at these.

    The big leap in Linux desktops is going to come when medium-size companies decide that per-seat licensing for Windows is absurd just to give everyone e-mail and web access.

    Learning new applications is hard: true Yes, but notice that in the last 10 years the MS market has gone from DOS to Windows to Win95, significantly different interfaces. And everyone's gone along. More importantly, MS has established a standard of changing to enforce upgrades, forcing people to change when they don't want to. Eliminating that is a big win for everybody.

    Open source still requires good project management: very very true. Well, yes, but the point that's being missed here is that MS, the monopoly-holder on the desktop, has terrible project management. OS's arrive years late and incredibly buggy; MSOffice has traditionally added features to attract new users while ignoring the features that current users want and need. Marketing runs the show on many many desktop products.

    Now, there's an area of software where marketing input is very important, but there's also places where marketing influence does nothing but hurt quality. There's a lot more to be said on this subject, obviously, but the answer isn't simple on either side.

    Humility is a virtue: true. Oh, true enough, but the 'Net isn't virtuous. Complaining about flames is nice and everything, but it's never really accomplished anything. Filtering input is always going to be a high priority.

  • Correct me if I'm wrong, but somebody installing AOL on their system won't affect my system performance, right?

    Why should I mind if they want to run AOL software, as long as it doesn't affect me? Isn't it their choice? Shouldn't Linux be about choice?

    Hold on while I tell my friend to stop using xemacs. Who knows, when xemacs has sucked up all his resources, it might go after my system.
  • There's a middle ground between keeping Linux obscure and making Linux suitable for the masses. That middle ground is using it for server applications, embedded applications, engineering, and research--what it is being used for right now. Having Linux replace Windows for the non-technical user, on the other hand, is an unproven proposition and, I think, threatens the integrity of Linux.

    That middle ground is also keeping around a diversity of operating systems, together with open protocols. Being locked into Linux is no more fun in the long run than being locked into Windows, no matter how nice Linux may look right now.

  • There are a few good points in the article. The ease of set-up and configuration, the addition of peripherals and automated integration of new software... These are things that make a computer easier to use.

    The point about the purpose of computers being to make tasks easier - instead of forcing people to do things the way the system dictates, is very valid. But down this path lays the animated paper-clip and an application named Bob.

    My question to the author is, Why do you address the open source/Linux/GNU community as a company?

    Why should the people responsible for GNU/Linux be afraid of the fate of DEC and Linux? We do this for free, and few of our paychecks depend on the number of bugs fixed in the next version of the Apache.

    I'd be curious to see what would happen if a powerful corporation who embraced Linux suddenly started dictating 'hot list' items...

    Sure, that would suck for people who are on that task, in that company... But trying to dictate features to 'the community' would be like trying to herd cats.. "You want WHAT?! WHEN?!"

    Linux exists in it's present form because millions (are we there yet?) of developers made these things a priority instead of those things. Companies made some things harder to do (i.e. closed specs) so development proceeded along the path of least resistance.

    I pity the project manager who tries to dictate policy and priorities to a bunch of competent volunteers. Don't look a gift-horse in the mouth.
    You can ask, you may suggest, and your request will be considered.

    You can offer free hardware and services, and that might make the minds of the able a little more willing to see things your way. But you try strong-arming people who do charity work to work harder, and they'll take their toys and go home.

    Here kitty-kitty...
  • the author has a perfectly valid point, it seems no one can be critical of Linux without a thousand kids emailing them and being immature. Even saying Linux users are immature in this post is seen as some kind of posturing that MUST be a flame. I've seen dozens of articles linked to /. that people whined and cried over because the author of the story didn't hail Saint Linus and keep a copy of the Cathdral and the Bazaar under their pillow. The same thing happens when you go into a Linux IRC channel or usenet group, people make fun of you and become smart asses when you ask a simple question. The collumists are not hurting Linux by giving it free airtime, the people hurting Linux and the validity of Open Source are the whiners that flame authors up the wazoo. Never trust a zealot, they're in it for themselves.
  • We need to convince new computer users to run Linux? I'm sorry, but I don't think that's a viable option at this point.

    Consider the case of my grandmother. A couple of years ago, she bought her first computer. Running Windows 95, I configured her computer so that she could dial up to an ISP, check her e-mail, and even use Netscape.

    When the computer boots up, she sees a nice friendly screen with the Windows logo. She can even play some games on it.

    There's no way I could do this with Linux. If I was willing to put in a great deal of time, I probably could have come up with a setup so that she could do everything in X. But I'm her resident Linux expert, and I live 400 miles away. What happens when something goes wrong? I'm not about to tell my grandmother over the phone how to use vi to edit her /etc/passwd to fix something.

    I have no problem telling my friends who live down the hall in my dorm to run Linux; I don't think it's reasonable to expect people like my grandmother to run Linux. I think Linux is great, but we've got a long way to go before we can get people like my grandmother using it, and that's the kind of thing that this article's talking about.

    We don't need to get new users to "learn Linux"... We need to get it so that they don't have to. While there's been a lot of progress over the last couple of years, it's just not there yet.
  • I believe grappler was refering to demands on the Linux community as a whole. Obviously the correct response in that case is "Here's the source. Have a nice day". The Linux community as a whole has no other obligations.

    Yup. I wholeheartedly agree. Rereading my last post, I realize I was in a strange mood when I typed it. I was thinking of companies that would try to treat the "Linux Delover collective" as if they were a company that existed to serve the needs of the market, which it of course it is not. Companies that want something developed have 3 choices:
    1. Pay someone to do it (M$ or anyone else)
    2. Ask the Linux people to include it, and show that there is a need. If they agree, they'll do it.
    3. Do it yourself. If it involves modifying the source to a GPL'd product, or if you just feel like it, rerelease the source to the public.

    "Here's the source, have a nice day" pretty much sums it up perfectly :-)

    Obviously, if an individual programmer enters into a contractual agreement to create new or modify existing software, then that's a completely different situation, and, you're right, neither response would be acceptable.

    Couldn't agree with you more :-)

    People, let's not forget that Linux is something most of its developers do in their time off.

    --
    grappler
  • No, I'm *JOKING*.

    Good God, you'd think no one on Slashdot had ever seen sarcasm before!

    For what it's worth, my mom uses a NetBSD laptop, which I built and continue to support.
  • Technical superiority means little in the marketplace, and a huge dose of loud-mouthed platform bigotry will surely do Linux harm despite its merits.

    However, both OS/2 and Betamax did not have overwhelming market and lay-person support at the time. Did you ever see an OS/2 VAR going public and setting first day gains records? Howabout article after article in major paper publications dedicated to the creator of Betamax? The primary difference between Linux and other technically superior failures is the amount momentum behind them.

    Linux's enemy at this point is not all of the loud-mouth bigots; nearly any company would kill for that amount of hype. Remember that age old attage, "There is no such thing as bad publicity."

    -AP

  • Yes, it is true that Linux users tend to be a (over?) zealous bunch, this line has me greatly concerned:
    Convince Steve Case to let America Online's engineers port AOL 5.0 to Linux.

    Yes, we need newbies (ie. more users, who will all be newbies for a time) for the Linux movement to progress, but the last thing we need is a dumbing down of Linux to this level!!!

    Eric

  • Hmm... something just occurred to me as I was reading your post, trog. You say "My fience [sic] ... uses AOL on her iMac. She's very bright and intelligent, but when it comes to computers, she just wants to use them as a tool - nothing more. She has no desire to learn Linux."

    Now, this is where I realized something: maybe the Linux zealots should quit evangalizing to people who are comfortable with their computers and work more at convincing the truly new computer users instead.

    Sure, most people don't need to know how to use multiple computers, but at some point, your fiance learned how to use a Mac. What if, at that point in her life, someone had shown her how to use a Linux machine instead? She's really learned no more or less about computers. She has simply learned how to use a (different) system.

    IMO, there's no point telling a computer user how much better Linux is than the OS they are using now. We need to be the ones there when a user gets his first computer.

    Then again, people who have never experienced Windows might not appreciate what it means to have a stable OS ;^}

    Eric
  • A lot of people just want to use their computers to talk to other people. AOL is full of other people.

    If that's all they want to do, fine. I can't imagine that a company would sell a pre-installed Linux system without a web browser. It's not going to be IE; most likely it would be netscape (among current non-beta browsers). With the AOL takeover of netscape, AIM is built right in. Register a nickname, go to www.aol.com, and follow the links to the chat rooms.

    IMO, nothing there is too complicated for the average newby, especially if the computer came with any documentation on how to do the things an "average" user would want to do. The best part is that no one would have to resort to such a crappy ISP.

    Eric

  • completely redo the kernel as OO once HURD starts gaining marketshare and usablility.

    No way. I mean, I've liked OO as much (or more) as the next guy ever since I discovered Simula back in the late 70s, but you really don't want or need heavy OO in an OS kernel. Too much unneeded overhead.

    Besides, we've had OO OS's (sort of) before -- MacOS, for example -- and while they've been popular in certain domains, they're hardly "killers".

    Given the level that that the hardware is at these days, the "Linux killer" is likely to be some sort of advanced AI interface that recognizes natural language (spoken or written) and learns about the user well enough to anticipate most requests. Of course, the PC as we know it will be considered old-fashioned; we'll have wearables, pocketables and smart appliances that all talk to each other behind our backs. (And yes, some of that software may well be OO.)
  • The GNU/HURD was started before Linux, yet Linux has rocketed past it. I don't expect HURD to ever be widely used. There are few userspace advantages for the HURD over Linux. Plus Linux has reached huge critical mass. Expect Linux development to speed up, not slow down! :-)

    <I>the "Linux killer" is likely to be some sort of advanced AI interface that recognizes natural language (spoken or written) and learns about the user well enough to anticipate most requests. Of course, the PC as we know it will be considered old-fashioned; we'll have wearables, pocketables and smart appliances </I>

    These are all applications. There is nothing preventing Linux from running new AI or natural language interfaces. Linux is so modular and free, expect it to <I>help</I> information appliances, not to be killed by them! Remember how much Linus has been talking about PDAs over the past year.


  • While there are certainly plenty o' valid points in the article, I doubt most of us will want the changes that are talked about. Yes, a few things could be changed to be more user friendly. However, there are lots of things with steep learning curves I for one would like to keep that way, because it keeps the functionality optimal.

    Luckily, open source is a democracy/merritocracy. Those who code, decide where it goes. So as long as enough people agree with me, I think I'll be happy (Of course, having powerfull tools does not rule out having easy tools).
  • Remember OS/2 and Betamax

    Yes, one of the things that killed OS/2 and Betamax was that they came to late. If you already have a VHS and a collection of tapes, you aren't going to invest in a new VCR, specially not if your current equipment still works fine. And if you are buying a VCR for the first time, and many of your friends have VHS, the interoperatibility (exchanging tapes) is more important than a better quality.

    Technical superiority isn't important for most people. Browser plugins and the ability to send word documents by email to your kids are.

    -- Abigail

  • Setting up Windows 95 on a new system is a PAIN. Linux is better (and has problems, too, but that's a different article.)

    How To Set Up Windows 95

    This is how I set up Windows 95 to achieve a reasonably stable system for playing games - the only thing I do with Win95.

    1. FDisk the hardrive if neccessary. Too bad if you've never heard of FDisk. Reboot when done.

    2. Format your partitions. Don't forget the /s flag to install the system files.

    3. Install Windows 95. (I assume OSR2.) I hope your boot diskette included CD ROM drivers! Reboot when done.

    4. Install the Intel chipset drivers for your post-1996 motherboard. Windows will not tell you to do this, but if you don't, you will have Problems. Reboot when done.

    5. Install the USB supplement for OSR2 (Undocumented feature - this also enables AGP). Finding the USB supplement on Microsoft's web site is left as an exercise for the reader. Reboot when done.

    6. Install drivers for your video card. Reboot when done.

    7. Install Intellimouse software for full mouse wheel support. Reboot.

    8. Install Microsoft DialUp Networking 1.3 to fix many, many bugs in the DUN that comes with Win95. Reboot, of course.

    9. Install a big set of mostly network and security upgrades. Some of these may not be neccessary, but who can tell? There is no documentation! (secupd2, vtcpupd, w95grey, winsock2, winsockup). Reboot. Of course.

  • Sorry, previous article wasn't done - why is the submit button the default?!

    Moderators, please moderate my earlier article down as redundant, and moderate this one up. (If you think it's relevant. I do get to a point at the end... :-)

    Anyway, for the sake of reference, everyone needs to keep in mind that setting up Windows 95 properly on a brand-new, blank harddrive system is a nightmare. It is harder than installing Linux.

    How To Set Up Windows 95

    This is how I achieve a reasonably stable system for web browsing and playing games - the only things I do with Win95.

    0. Assume you have a boot disk for your computer with the FDisk and Format programs. Or, that you can boot off the CD ROM. Otherwise you are SOL, go back to the store, pay the nice man way too much to do the job badly for you. Moving on...
    1. FDisk the hardrive if neccessary. Too bad if you've never heard of FDisk. I bet you wish your OEM Windows 95 came with real documentation now, don'tcha! Reboot when done.
    2. Format your partitions. Don't forget the /s flag to install the system files.
    3. Install Windows 95. (I assume OSR2.) I hope your boot diskette included CD ROM drivers! Reboot when done. Note that you will actually want to do this by copying the install directory onto your hard drive, and running the install from there. If you don't, every time you change something in the future, you will have to put the damn Windows CD in again.
    4. Install the Intel chipset drivers for your post-1996 motherboard. Windows will not tell you to do this, but if you don't, you will have Problems. Reboot when done.
    5. Install the USB supplement for OSR2 (Undocumented feature - this also enables AGP). Finding the USB supplement on Microsoft's web site is left as an exercise for the reader. Reboot when done.
    6. Install drivers for your video card. Reboot when done. Gee, I hope you downloaded the latest drivers for your video and sound cards before you started!
    7. Install Intellimouse software for full mouse wheel support. Reboot.
    8. Install Microsoft DialUp Networking 1.3 to fix many, many bugs in the DUN that comes with Win95. Reboot, of course.
    9. Install a big set of mostly network and security upgrades. Some of these may not be neccessary, but who can tell? There is no documentation! (secupd2, vtcpupd, w95grey, winsock2, winsockup). Reboot. Of course.
    10. Change network setup so you can see other machines on the network. (I make this sound easy - it is for me - but good luck if you have never done it before!) Reboot.
    11. Install a large set of useful utilities (like Winzip). Maybe you won't have to reboot!
    12. Install sound card drivers. Reboot.
    13. Install DirectX. Reboot. After the reboot, DirectX will detect more hardware and reboot again. (!)
    14. Install latest version of Internet Explorer. (but where do you get it from? Probably a magazine cover CD.) Reboot.
    15. Install a bunch of Microsoft add-ons like True Type Font Extensions, TweakUI, other Power Tools. You might have to reboot.
    16. Install latest QuickTime, Intel Indeo Codec, WinAmp, Adobe PDF Viewer, other utilities and system stuff.
    17. Install drivers for Zip drive. Reboot. Then install zip drive utilities and reboot again (sigh).
    18. Install Logitech Joystick software and reboot again.
    19. Set up your ISP connection. At least this is pretty easy under Windows.
    20. Congratulations! NOW BACK UP THE REGISTRY, so that when something gets screwed up later, you have half a chance of fixing it without going through this whole thing again!

    Total - at least one hour, and at least 15 reboots, if you don't make any mistakes. You may think I have exaggerated the problem, but I've actually simplified it by not considering the whole installation of significant applications! Oh yeah, I skipped the network card driver install and the details of network setup. But most home users don't do that.

    The point is, people think Windows 95 is easy because they don't do it themselves. For a total computer neophyte, I believe Linux is already easier out of the box, if your distribution includes drivers for your hardware. Admittedly, this may be a big if.

    But if I had to talk my parents (who not highly computer literate) through installing an OS properly over the phone, there is no way in hell I would use Windows 95. I would use Mandrake 7 (because the install is OK and I know it - I am sure there are other good install programs.)

    I have problems with Linux too. I will save those for a different rant.

    Torrey Hoffman (Azog)

  • OK, I'll bite. Charles is right that Linux, even with KDE or Gnome, isn't suitable for SOHO environments where the user doesn't have a 'Linux Friend' handy. And I don't see this changing without us ditching the UNIX underpinnings. If we do that, then Linux isn't Linux anymore. These users aren't interested in learning UNIX. Maybe a SOHO OS will be derived from Linux for precisely these users. Good for them; they'll end up with a more stable platform than Windows is right now.

    Now, this doesn't mean that non-technical users can't make use of Linux; it just means that their boxes will have to be set up by a Linux Friend and locked down so they can't break anything. Imagine a KDE/Gnome box with Netscape, Star Office (or KOffice for the more radical amongst you) and a big red button on the desktop that says 'shutdown'. I think /most/ office users would be happy with that, especially once Star Office's import/export filters are perfected.

    Finally, for technical users, Linux is probably fine as it is. Usable, reliable and easy enough to set up. If it was any easier, it wouldn't be fun, would it?! :)

    I see no reason why the /volunteer/ development community should be /required/ to target the first group I listed and attempt to make Linux easier to use by them. If a corporate wants to sponsor that work; fine, let them. That's what the GPL is all about and the rest of us /might/ get some benefit from it.

    To say the Linux and Free Software community doesn't listen to it's "customers" is incorrect. It's gotten where it is by doing precisely that. It's just that Linux's "customers" are technical users for whom Windows and MacOS are inadequate; and also those who need to deploy stable, secure systems for non-technical users in a traditional office environment.

    Perhaps Windows (and MacOS) does suit the first group best. Perhaps it will for a long time. But I think the best fit of all would be "none of the above", but some kind of information appliance. Look at what Nokia/Intel are doing with their Linux-based box and Sony appear to be planning for the PlayStation 2 to get an idea what I'm on about here.

    Linux isn't for everybody and doesn't need to be in order to "win". This isn't about dominating the market like Microsoft does, and Sun would like to do. This is about making computer systems that don't suck (Thanks ESR).
  • All we have to do is wait for linux to go really mainstream... Then they'll all move to FreeBSD. Just look at the freeBSD users right now, there so bitter. Those people are the flameyest people out there.

    /me sits back and waits for the BSD community to prove me right :P

    [ c h a d o k e r e ] [dhs.org]
  • <i>The GNU/HURD was started before Linux, yet Linux has rocketed past it. I don't expect HURD to ever be widely used. There are few userspace advantages for the HURD over Linux. Plus Linux has reached huge critical mass. Expect Linux development to speed up, not slow down! :-) </i>

    I think there are more than a few userspace advantages for the Hurd over Linux, namely, most of the kernal (Pun intended). Besides, I have read Linus saying that Linux is getting close to being complete except for new device drivers. Software isn't limited by developers but by design. Linux seems to reach out a lot less further than the Hurd. But then again, that is probably why we are using Linux and the Hurd is still trying to be usable.

    And put your politics aside. Linux has nothing to prove by *always* being better. Even if the Hurd 1.0 gets released in 6 months that virtually replaces Linux as the GNU kernal for its advantages, that doesn't say anything about the compentency of the Linux team. It just means Linux's time has passed and the Hurd's has come. The original author was right, there will be a Linux killer around the bend. I would *much* rather it be GNU Hurd than some propietary software. Take it or leave it. We are all in the same boat.

    <i>These are all applications. There is nothing preventing Linux from running new AI or natural language interfaces. Linux is so modular and free, expect it to <I>help</I> information appliances, not to be killed by them! Remember how much Linus has been talking about PDAs over the past year.</i>

    If Linux is so modular then how come Linux users recompile their kernals so much? Even with modules there are devices that aren't supported until you recompile the kernal. And can modules be compiled separately (honest question)?

    And wouldn't it make sense to design a new GPLed kernal for PDAs? It's an honest question.
  • <i>Re: Gimp...

    There is no question that GIMP can do a lot, but... let's face it. It doesn't have nearly the feature set that Photoshop has. Granted, if you stick to basic bread-and-butter stuff, then you can get by with GIMP. But don't kid yourself that it can do what Photoshop can do in the hands of a professional.</i>

    You have sparked my curiousiy. What does the Gimp lack?
  • Whoops, it's a Voodo3fx card, course I can't expect that to work, can I ?

    hmm, I've gotten both the Voodoo1 and 3 working fine. You might want to go back and try from scratch or mess with your monitor settings, they caused me the most headaches (any recent distro should have the voodoo drivers). If you get the masochism down you might someday get to develop sendmail (or at least configure it fulltime)

    Patience, persistance, creativity, and luck. No wonder we think we're 31337. ;-\

    --
  • I hear your pain ZuG, and you make valid points. The root problem is that Linux was designed as a server OS, and has been programmed as such. In this capacity it competes well with billion$ OSes. The usability features for desktop performance (games, web browsing, simplicity) are not up to par yet. It will take time. Only now are desktop users invading the Linux space. Only after they fully understand the system can they improve it, and make it do the happy desktop things that Grandma likes. Try again in another year, maybe it will be ready for what you want then.(or at least easier to get there).


    --
  • Well, to be honest, I don't think the problem is unique to Linux..

    Every OS has/had it's own rabid zealots..

    I remember back in the Amiga days, the flames I got when I mentioned something positive about PC's or Macs (I was, and still am an Amiga user - I migrated from a C64 to an A1000 in 1987, and I still have an old A3000 connected to my home network, and I still use it regularly - however it's seeing less and less use compared to my PC's, which mostly run Linux - although I keep one around which dual-boots into Windows to keep my wife happy.)

    When Lightwave came out for Windows, I was severely flamed by several idiots who had switched, and were calling my trusty old A3000 "useless", and that I should get a P100, which would run circles around it (I actually HAD a P100, and with the A3000's processor upgrade, speed was pretty much the same..) These were the same people who flamed PC users just a couple of years before. They knew nothing significant about either operating system, except the one they used was "best", and that they had to flame anyone who disagreed, or had a differing opinion.

    And today it continues with Linux. It's just the latest in a long line... I've seen Zealots of the Mac, OS/2, Windows, Amiga, Atari, C64, and even SuperNintendo (and, to a lesser degree, Sega)

    In short, there will always be idiots with low self-esteem, who's only means of feeling good about themselves is to bash people who don't agree with them. There's nothing (really) that we can do about it. You can't reason with them, you can't shoot them, and you can't stop them from being stupid; this is a fact of life on the Internet - if you're posting an opinion, be prepared for the nutcases who think you're challenging them.

    ZZZIIPPPP (this is me donning my flamesuit :o)
  • When I suggest people try Linux I often get asked about AOL.Last month I wrote AOL and asked if they planned on adding Linux support. This is the reply I got.
    Hello, my name is Pam and I am writing to you on behalf of America Online in response to your recent e-mail.
    Please forgive my delayed response to your e-mail.
    I want to personally thank you for taking the time to write with your concerns about using the America Online (AOL) software on the Linux operating system.
    America Online for Linux is currently in research and development.
    AOL Member Services is currently "collecting the data" on requests for AOL for Linux and I assure you that your feelings and input are being used to help AOL make the best possible online experience.
    I am excited about any improvements to the service and will be able to answer questions about AOL for Linux as soon as information and a possible release date are made available.
    I apologize for any inconvenience this may cause you.
    Thank you for writing America Online. I hope you were satisfied with the service you have received. Please feel free to write anytime you have questions or concerns. Have a great day!
    Pam M.
    Customer Care Consultant
    America Online, Inc.
  • Eric_Wright wrote:
    Yes, we need newbies (ie. more users, who will all be newbies for a time) for the Linux movement to progress, but the last thing we need is a dumbing down of Linux to this level!!!


    I disagree with you on this. If AOL should happen to port their software to Linux, there is absolutely nothing which forces you to install it. Each of us makes the Linux system we want. It's a "movement" only in the sense that there are a lot of people who, for their own separate reasons, have chosen to use Linux.

    Some people use Linux for ideological reasons -- the folks who agree with Stallman. Good for them.

    Some people use Linux for the stability and reliability that comes from the Open Source development model. Good for them, too.

    Some people use Linux because they are dissatisfied with the quality of Microsoft's product offerings. Good for them, as well.

    Some people use Linux because it's "free as in beer", or because it lets them make use of hardware that would otherwise be populating a landfill. Good for them, also.

    Some people, who would like to use Linux, are prevented from doing so by the barriers which are described in the article. The many comments which I have read in this thread about how it is terrible if Linux is "dumbed down", or how it is essential for all Linux users to learn about system administration do this particular group of potential users a great disservice. Adding the ease of use functionality that this group wants does nothing to take away from any other group that is using Linux. The fact that there's an AOL client doesn't keep you from connecting to any other ISP by whatever means you choose. The fact that a "newbie install" has a flashy GUI, limited options visible, almost no daemons installed, doesn't make vi the default text editor, or other "blasphemous" features has no impact on any person who is running a different style of Linux system.

    I've been running one or more production Linux servers since I set up a DNS server on a 386SX-20 with an 80mb hard drive and 8 megs of RAM running kernel version 0.99pl15 (I forget whether it was Slackware or SLS). I don't need a huge amount of hand-holding for myself anymore, and I act as a "linux friend" (to use the article author's phrase), but just because I had to "gut it" and learn a huge amount to get to where I am today doesn't mean that I think new folks should have to do the same.

    Had I invested the time I spent learning Linux into learning how to play the guitar, I'd be a fair guitarist by now. Instead, when I want to hear guitar music, I play a John Fahey or Andres Segovia or whomever CD. Yet I don't get hate mail from subscribers to Guitar Player magazine because I chose to put my efforts into learning an operating system instead of learning to play the guitar.

    To coin a phrase: "Can't we all just get along?"
  • I don't want to be a dickhole, but WINE will never be a good bridge for everyday users. Why? Because programs under WINE don't work the same as they do under Windows. Maybe they will someday down the road, but it's a long way off. And even then, WINE will still be playing catch-up to the latest-and-not-so-greatest version of Windows.

    I find it more agreeable that certain Windows-based "killer-apps" need to be re-created or ported to Linux. Word/Access/Excel is certainly one of them. Star Division took us part of the way, but they're still a little off -- I look forward to seeing what Sun will do with the Office Suite. AOL, on the other hand, should definitley be ported to Linux. Case and co. have *got* to be thinking about this -- it's just a matter of time until they go for it. And I say, more power if they do. 25 million people are on AOL, right? That's 25 Million people who previously were locked into one of two operating systems.

    As for your other point: I don't think 2.4 will make much of a difference in the desktop arena. Why? Because hardware isn't really our weak-point right now. It would be nice to have better USB support, granted, but I would hardly place it at the top of the "wish-list". What I would like to see is software like KDE and Gnome working together to build a better desktop. XFree86 4.0 looks nice, and that should help out with gaming, but I think the desktop environment is more pressing right now. We need a consistent (themeable for sure) interface that users can depend on for ALL their applications. People say how diversity is one of the great strengths of Linux, but it's not necessarily true. Consistency is much more important in getting people to accept a new OS for their desktop system.

    -----------

    "You can't shake the Devil's hand and say you're only kidding."

  • User: I need this feature, can you do this for me?

    Commerical software company: Sorry, no, that's not on our release schedule.

    Open source software developer: Take the source and fix it yourself you idiot!

    The end result in both cases? Same. Both say : Screw you, the user.

    The big difference is that there isn't just one person/entitiy capable of making the code changes in the open source case. You can pay/pursuade any of thousands of individual developers (quality and price may vary), infuence/pressure the company you buy releases and support from, make your case to the general community or fix it yourself.

    If the changes are truly general and worthwhile, a big/wealthy company who $pends on support should be able to get fixes/features from distributors like RedHat, and the fixes would be done responsibly. If the features/fixes suck, no one will adopt them and the user can keep their crappy code.

    The small, idependent and/or poor will have to rely on the interest/kindness of others or learn to do it themselves, but at least they've got more options than trying to get the one owner of the closed source to hook them up.

  • I suspect that some of the people who do the flaming are actually not advocates. Some of them are just trolls. Some are likely anti-Linux. There are, of course, some quantity who are just clueless Linux bigots who don't understand that they're huring the OS more than helping.

    Either way, it won't change the facts. Linux has soft-spots (e.g. documentation) as does every OS. Those need to be addressed and those who write well thought-out, clear articles about those problems will get MY paise.
  • There are limited places where you could put Linux on the desktop and make it work. Why is this? Because the 'elite Linux gurus' want Linux to remain as-is. A club that only people with the computer and programming know-how can join.


    Would those be the people working on KDE, GNOME, XFree86, the various office suites and graphical installers? Please go grab a copy of Red Hat 4.2 and try using it (I'll dup my CD for you, if you like). I suspect you will detect an OS that has not remained "as-is".

    Then again, perhaps you're refering to the kernel, where video, USB and IR support are being added for easier integration with consumer electronics; or what about those "elite Linux gurus" and their hard-to-use games like Myth2 and Heroes of Might and Magic III; there' always things like Mozilla and Knoqueror, which clearly are aiming at making the desktop harder to use....
  • No no no! You want these companies to demand unreasonable things. The the support companies like Linux Care and Red Hat will have to hire more programmers to do the things that the projects don't want to take on. In the end, this will serve everyone. Of course, some things simply don't make sense, and those will end up not being accepted back into the core projects. Open Source development really does work, why are people still doubting that after so much evidence?
  • People who can't handle AOL, an iMac, or Winxx with MSWord/WordPerfect have no buisness using computers until they fix their attitudes. It's the same as many other situations. I don't try to fly a helicopter or a plane without learning about it, so I stick to my car. If a car is 'tough to drive', then you have no buisness being on the road (there are LOTS of these people), so stick to shoes.

    If people can't take responsibility for their own actions, and aren't willing to learn ("I'm afraid, it's a computer!") then they should get an attitude adjustment or stop whining. A car is far more complicated (and requires real-time feedback from the user, unlike a computer), yet most people are comfortable with that technology... why? They have either grown up with it, so it doesn't seem strange, and they are willing to take a risk (ever driven on the NJ Turnpike? Far more dangerous than trying to get a dual NT/Linux set-up working).

    This may sound elitest, but hey - it's the truth.
  • >You failed to mention that real-time feedback is something users (humans) are inherently good at, in fact, most life is. As a matter of fact, real-time feedback is how the real world operates, so why shouldn't a computer?

    Yes they are. Word processing, freecell... these are not real-time scenarios, any more than they are with a pencil and paper or a deck of cards.

    >Danger aside, we are talking about a large population of people who are fairly intelligent, receptive and aggreable people. The fact of the matter is that they don't have the time, money or desire to change their computer habits when what they have works more or less well for their needs.

    Yes, but most (fairly intelligent) people don't realize how easy, and how little time it takes to learn things. Of course the definition of fairly intelligent varies from person to person (I'd say anybody w/ IQ >120/130, just a rought estimate). What people also don't often realize is that a couple of hours of learning now will save you many hours of time and frustration later. I'm not opposing any specific program, OS, or brand of computer here, just suggesting that people take a little time and responsibility to figure out what really is right for them. Linux doesn't have to take over the desktop, and I've never really advocated it for everyone. I'm suggesting people learn *a* tool.

    Like I said, if you whine about learning to use an iMac, maybe computers aren't for you, but maybe all you need is a little change of thought and attack. You don't need to learn anything, but don't complain to others if you aren't willing to try to learn things for yourself.

    I spoke in some anger and didn't fully explain myself... Responsibilty, not elimination of users is the idea... live and learn.
  • >While you're at it, why don't you quit eating hamburgers, since you can't handle buying a ranch, raising/slaughtering cattle, then preparing the beef.

    I'll just carve what I want and ride the rest home... 8^)

    The idea is that you need to responsibly learn to properly use a hammer, and the same with a computer. "Oh, a lathe is too dangerous to use!" is only valid if you don't learn about the tool and how to safely use it. The same with a computer. Learn, live, love. You should learn to use any tool properly and respect its abilities and limitations.

    >TWACK! goes the Elitest Clue Stick.
    Shouldn't that be "THWACK!" ? 8^)

  • But isn't the point of running Linux (or any OS, for that matter) having something that can do *your* tasks reliably, and with ease of effort? There are many improvements going into just about every OS now, and we should be thankful that there is some competition to provoke more of this. The point about some company setting a deadline is bogus, and shows a lack of understanding on the author's part, though he does make several valid arguments in other areas. What I think he doesn't understand is people, their attitudes, perceptions, and capabilities.

    Many of us here (on /.) would probably qualify in the upper ranges of intelligence. Most likely, the majority of the people here wwould rank highly on IQ tests and other standardized tests. We often take for granted the amount of work it may take us to learn something, and often assume that other people are at all motivated about learning. The author sees an opposite view of things, and doesn't concern himself with people's apathy toward learning, which is the real problem. People are lazy. That's all there is to it. They act scared of technology because they don't want to take the time to learn about it. I've met people who find AOL too complicaed, and some of these people are fairly smart people, who earn good grades. They just aren't willing to explore and learn. "I didn't want to try to turn that paperclip guy off because I thought I would break something." is a bad attitude to take. Likening computer usage to other everyday tasks: "I was afraid to use Broil on the oven because I've only used Bake before... I know that's what it says in the recipe, but what if it doesn't work" or "I didn't want to adjust my rearview mirror/seat position beacuse my turn signal might not work anymore".

    Computers are like books - you need to look at them, open them up (either literally or figuratively - maybe both), and get involved in them. Learn the ideas, get to know it.

    Dive in, learn. Whether it's a Mac, Windows box, Linux box, pinball machine, or whatever - take a few minutes to learn about what you are using. You will be happier with yourself (conquered another hurdle), ease your everyday life, and end up learning more about more things than you ever thought possible.

    My significant other had very little computer experience before we met, but she was more than willing to learn. Her friend had used computers for over three years before, but was 'afraid' of her computer enough to only use freecell and a word processor. Result? 2 years later, My S.O. is finishing her (non-computer related) degree, and has taken the time to explore things like QBasic, Macros in Word/Excel, and isn't scared when she sits in front of KDE or Gnome. She may not be efficient, but she pokes around and learns what she needs to know and asks questions with the aim of not having to ask that again. Her friend still knows how to type a paper, maybe make some of the text bold, or change a font, and asks the same questions all the time with no intention of trying to learn anything. The difference is apparent - attitude toward learning.

    The choice is up to you. Find the tool that makes your life easier, and learn to use it. If a CLI is too tough for people to learn (and I suggest that it is not), then people will use the graphical login managers. Linux grows and improves via the people who use it, so it will not immediately add all sorts of neat little things that many consider "needless eye candy", unless someone really thinks that it is worth *their* time to do it. Use Windows or a Mac if you like - I will use whatever platform suits my needs for the task at hand. I am not afraid of knowledge.
  • by six11 ( 579 ) <johnsogg@@@cmu...edu> on Tuesday February 15, 2000 @12:29PM (#1271629) Homepage
    I very much want Linux to succeed, but I do think that there are certain ideals that need to be maintained. Avoiding AOL is one of them.

    snip

    While I'm all for the spread of Linux as a desktop OS, I'm afraid it will never happen. Most people just want a computer that they can turn on, click on icons, and chat/word-process/etc.

    Not to incite bad mojo, but don't you see something slightly contradictory with that?

    AOL represents the end-user client, the appliance in the computer, the thing that ma and pa can install by themselves and begin using without having to go through an arduous learning process. (recent 5.0 mishaps notwithstanding)

    The Linux glory days are for the most part gone, unless you roll your own. The future is uncertain, but it may be something that is just as good--but if our ideals don't adopt to the changing times, we'll be left with crust. It's a choice: play the game, even if AOL is on the lineup, or take your bat and go home.

  • by Brian Knotts ( 855 ) <.moc.sseccaedacsac. .ta. .sttonkb.> on Tuesday February 15, 2000 @12:22PM (#1271630)
    I assume you are attempting to refer to the X Window System.

    X (or a reasonable facsimile thereof) is an important part of any UNIX-like operating system in which GUI-based programs are used; without it, you lose network transparancy for GUI-based programs, which, believe it or not, can be quite useful in a multiuser environment.

    New XFMail home page [slappy.org]

  • by Amphigory ( 2375 ) on Tuesday February 15, 2000 @10:27AM (#1271631) Homepage
    This guy is right on the money. The biggest problem that Linux faces is the arrogance of its users. (And before someone calls this a flame and moderates it to oblivion, let me point out that I have probably been using Linux since before you ever heard of it (1993)). I love Linux. It's productive for me. It's fun. It encourages cool new things.

    But I don't think that OS nirvana has yet been reached. Capability based systems sound very cool.

    On the topic of flame... I'm actually starting to wonder whether some of the flaming (and possible the ridiculous number of trolls on /. for the past month or so) is not being subsidized by someone who would rather Linux not succeed.

    I mean... seriously. I know that I don't know any Linux users who act as stupidly as a lot of the trolls act.

    --

  • by deusx ( 8442 ) on Tuesday February 15, 2000 @02:42PM (#1271632) Homepage
    As Linux is embraced by more organizations, and used in more ways that are crucial, the demands upon you will increase. New feature ideas and bug reports will no longer go onto a "wish list"; they will go onto a "hot list." You will face pressure to add 50 new items to the next release, when it really ought to have 10. Wealthy organizations, accustomed to getting their way, will demand impossible schedules from you, and then complain if the quality is not perfect.

    Here's one point I take issue with. While I don't take issue with its clairvoyant validity, I do take issue with the idea that this should be accepted practice.

    The idea that anyone should say yes to an impossible schedule, over-promise, kill themselves to work inhumanly sustainable hours is just ludicrous. But we've been doing it.

    It's time to stop it.

    Just got this in my mailbox, and I think it says just about everything I want to:

    Gold Rush Mindset Undermining Programming Field [www.tao.ca]

    Think about it, if you're 20-30 something now, and working 90 hours a week, do you want to be doing that into your 40's? Should you even be doing that now? Why do you accept it?

    If we're so valuable, and in such short supply, it's time to start maybe from the grunt programmer on up to put a stop to the acceptable practice of demanding the impossible and change it into delivering the sane.
  • by xyzzy ( 10685 ) on Tuesday February 15, 2000 @10:29AM (#1271633) Homepage
    Interesting, I had a different reading of the article. I think he was saying that if a community of users is telling you that Microsoft (or Apple, or Sun, etc), is better because of x, maybe you should think a little bit about that and see if there is any truth to it -- NOT just write them off as a bunch of ignorant neanderthals. They might be telling you something VERY important, or giving you a clue as to the next important feature that Linux should have.

    And before you cut me off at the legs, think about how not too long ago (like a year) writers like this would complain about how hard it was to install Linux, and that Windows installation was easier. Now the reviews are getting more positive in that respect -- we have simpler installers and pre-installed computers.
  • by K. ( 10774 ) on Tuesday February 15, 2000 @10:27AM (#1271634) Homepage Journal
    "Wealthy organizations, accustomed to getting their way, will demand impossible schedules from you, and then complain if the quality is not perfect."

    First of all, who will they complain to? There is
    no LinuxCorp. Linux is not a product, it's the
    result of a community effort. Several entities
    sell it as a product, and contribute to the
    development effort, but they're not under contract
    to anyone to, say, deliver USB in the next month[1].

    Secondly, if a wealthy corporation wants a feature
    right *now*, there's nothing to stop them hiring
    a few programmers and adding it in. The
    development process allows for this. It encourages
    it. Try getting a custom feature added to a
    closed OS and see how far you get.

    This is a fundamental misconception in the
    article, and in others that claim that Linux isn't
    ready for primetime. Linux does what its users
    want it to do. Its users mostly want low-to-mid
    range servers, so Linux is perfect for that. Some
    users want high-end servers, and the design allows
    for extension to fill that need. Not too many
    people worry about luser-proof desktops, and so
    work needs to be done in that area.

    But the fact remains that Linux is adaptable to
    a host of applications, precisely because it
    isn't a traditional product and doesn't have
    a closed development process. The open development
    process is not a weakness, it's a strength.

    K.
    -
    [1]And yes I know it's in the 2.3 kernel, so don't
    bother pointing that out.
  • by jetson123 ( 13128 ) on Tuesday February 15, 2000 @01:12PM (#1271635)
    Connell takes it as a given that Linux ought to try to be just like Windows: a CD-installable desktop operating system for the masses. There are several problems with that thinking.

    First, the notion of a CD-installable general purpose operating system is itself outmoded. The consumer market is moving towards embedded and specialized devices. Linux will play a big role in that market, but making it user friendly will be done by the for profit companies that make the devices. Even in the PC market itself, most non-technical users never install applications, let alone a whole operating system.

    Second, open source efforts like GNU and Linux worked because users/customers were also developers: they could make intelligent suggestions for how to improve software and often even supply and share the enhancements themselves. Non-technical users contribute nothing to this ecology and it is debatable whether the open source community should expend a lot of scarce resources on such user communities.

    Third, the world needs an operating system for technically savvy users. The idea of one operating system for everybody is Microsoft's, and if I wanted to use that kind of system, I would (I have licenses to all the Microsoft software). World domination by any operating system, be it Linux or Windows, is bad because it means trying to make one system fit everybody's needs, and that cannot be anything other than a mediocre compromise.

    Let's aim for open standards, open protocols, and open device interfaces, not world domination by Linux or any other system.

  • by EricWright ( 16803 ) on Tuesday February 15, 2000 @11:02AM (#1271636) Journal
    I very much want Linux to succeed, but I do think that there are certain ideals that need to be maintained. Avoiding AOL is one of them. I have no experience with them, but friends of mine who do have complained that AOL does nothing more than mask the *real* internet (their words).

    Since you shared some of your experiences, I'll reciprocate... I also have been using Linux for about 4 years, mostly as a portal to remote supercomputers (during grad school) and somewhat on my home system. During college and grad school, I was continually exposed to *nix environments, and consider myself a fairly adept user. However, when it comes to system administration, at times I still need a good thwacking with a large clue stick.

    IMO, the real problem is that, currently, Linux (which is inherently multi-user) requires a goodly amount of administration compared to Windows and MacOS (inherently single-user OSes). Consider software installation: in Windows, you download a file, extract it (typically through an install wizard) and click ok several times, and *poof* it's ready to run (after the obligatory reboot, of course :) In linux, there are no such "user-friendly" graphical installers (except for some OS distributions) ... at least no widely used ones. Most of what a redhat user does is rpm -ivh foo.rpm, or some such variant. Additionally, this must be done as root, which opens the machine up to all levels of clusterf**king by the user.

    While I'm all for the spread of Linux as a desktop OS, I'm afraid it will never happen. Most people just want a computer that they can turn on, click on icons, and chat/word-process/etc. An inherently multi-user system, such as linux, *BSD, etc. adds a level of complexity that this type of user will never want to navigate.

    I guess I see the spread of linux in the light that there are millions of people out there who actually want to learn and understand more about how their computer works. To me, that's more important than which company comes out on top.

    Nb: M$ aside, of course... THEY don't want computer users to understand what they are doing: they might stop paying for crappy software then!

    Eric
  • by Anonymous Shepherd ( 17338 ) on Tuesday February 15, 2000 @12:55PM (#1271637) Homepage
    Just by using the term 'dumbed down' you defeat the point of a Newbie's Linux. It shouldn't be dumbed down. Either it has a very smooth and gradual learning curve, which is one thing that Linux, CLI, and Unix in general doesn't deal with, or it has a flawless level of useability.

    As an example, Apple's OS and hardware have demonstrated levels of proficiency in both tasks. As much as people criticize the design decisions, a single user interface is ideal for people who are figuring out information flow, computers, tasks, etc. A single mouse button, so people don't have to fear that if they do an incorrect action, something irrecoverable can happen because there is only one action. A single menu bar, so people *always* know where to look for info and stuff, without having to figure out what app has the focus.

    Now here's the problem, if you want to be a Linux advocate.

    Apple will be releasing MacOS X. It will feature all of the above useability functions. I don't know if it will also feature a gradual learning curve for newbies, but it will definitely have all the power features Linux has touted over Win9x and WinNT. The CLI, the GNU tools, the scripting and networking and robustness, unless Apple screws up majorly. If they do throw in a gradual learning curve, all the Newbies will be flocking to Apple because of their strengths, and Linux's weakness

    Consistent, useable, useful UI. I'm not talking about themes or skins. Consistent drag and drop functionality. Patterned interfaces among all applications. Their menu bar. Their single window mode, for new users. The graphical interface for system management. Consistent behaviors among all applications. Transparent windows, for example, to indicate which windows own which dialogs. Animated minimization and maximization so people know where the windows go, that they don't disappear.

    Advertising, focus, and attention for the new users. They will have the nifty industrial design, the nifty desktop graphics, the nice effects possible through display PDF.

    Control. Because Apple hardware is under Apple control, they can design the software and the OS to just work. If they haven't in the past, it's their bad, but they have the resources to provide excellet support and coverage.

    A lot of these things Linux just cannot control. At least until someone does a Linux box, akin to the iMac. Plug in, power up, and use. Until people start focusing on UI, instead of themes and skins. Until we stop thinking of new users as 'dumb', and things for them to be dumbed down. New users are just that, new, and they have their own ramp up and their own distinct needs. We can ignore them, of course, and that would just leave the door open for Apple, or Be, or someone else.


    -AS
  • by mwillis ( 21215 ) on Tuesday February 15, 2000 @10:13AM (#1271638) Homepage
    Linux Advocacy Mini-HOWTO

    http://linux.com/howto/mini/Advocacy.html [linux.com]

    What busy people should read is the Coles Notes version of Section 6, the Canons of Conduct [linux.com]:

    As a representative of the Linux community, participate in mailing list and newsgroup discussions in a professional manner. Refrain from name-calling and use of vulgar language. Consider yourself a member of a virtual corporation with Mr. Torvalds as your Chief Executive Officer. Your words will either enhance or degrade the image the reader has of the Linux community.

    and

    Always remember that if you insult or are disrespectful to someone, their negative experience may be shared with many others. If you do offend someone, please try to make amends.
  • by SEWilco ( 27983 ) on Tuesday February 15, 2000 @10:10AM (#1271639) Journal
    Maybe it's just that more of the Linux users tend to be network connected than other populations, thus they're more likely to be heard from online. Or better at using the network tools to express themselves.

    There is some self-interest in Linux. A Linux user is either a Unix user who adopted this new flavor, or is a non-Unix person who decided the effort to test and learn Linux was worth the trouble. Those who convinced themselves that Linux was worth the effort to try it had to convince themselves that it was worth doing so. Some of those people will be advocates, and some will be defensive about their present O.S. choice.

    You're less likely to hear from those of us who aren't passionate about something. You get to hear from those who most strongly agree or disagree...and those who agree may simply think that you're as normal as them and see no need to comment.

  • by Junks Jerzey ( 54586 ) on Tuesday February 15, 2000 @10:13AM (#1271640)
    The Linux killer is going to be something that doesn't look like an OS. People want to be able to fire up a machine and work. They don't want to do system administration; they don't want to focus on customization. Right now the biggest "non OS" is what's running on the Palm.

    Advocates see Linux as a techie operating system with a command line prompt and an X interface, but if Linux ever get somewhere then that's not what's going to be visible. Linux will be buried under the hood to the point that no one cares it's there.
  • by SnakeStu ( 60546 ) on Tuesday February 15, 2000 @11:16AM (#1271641) Homepage
    When I was just getting my feet wet with OS/2, I ran into some significant problems getting it installed. This was using 20+ floppies, and around the 18th floppy or so it crashed, every time. No recovery, had to start over, only to hit the same wall. So I turned to Usenet, in hopes of getting some help installing it. Well, it wasn't long before I was called an outright liar (i.e., that I was making up the story of it crashing), and my coworker and I were actually accused of being "spies" from Microsoft. All this from OS/2 "advocates" (zealots), in response to somebody wanting help getting started with their OS of choice. (It turned out that a campus-standard network card was causing OS/2 to hang -- then I was accused of using a "cheap" network card on purpose to attack OS/2!)

    Have a I seen similar attitudes from Linux users? Unfortunately, yes, and it makes me cringe every time. I advocate Linux regularly (ask my boss!), but I try to do it in a positive manner. Obviously, Linux isn't alone in having zealots causing 'bad PR' -- I've had problems with OS/2 zealots, as noted above, and Macintosh zealots -- but it is so unnecessary and so unfortunate, for any operating platform. Did I stick with OS/2? Nope. Was the negative experience from OS/2 zealots the only reason? Nope, but I would be a liar if I said it didn't play a part.

    The next time you feel like flaming somebody for being (in your eyes) "anti-Linux" remember the old saying: You attract more flies with honey than with vinegar!

    Journey to Yandol [uninova.com]

  • by Master of Kode Fu ( 63421 ) on Tuesday February 15, 2000 @11:26AM (#1271642) Homepage
    We program because we want to, not because the users are demanding the features.

    I also program because I want to and I can. No argument there, compadre.

    But I also remember that the user is the reason the program exists. That's the spirit of open source -- to meet the needs of users by putting th users in control of the software. Open source is not about replacing a clique of proprietariness with another clique of I-am-a-better-hacker-than-you.

    Now if the user base consists of yourself, go ahead and program as you see fit -- you will naturally program to meet your needs. However, if the user is someone else, I do my best to find out what their needs are. If their needs can be met by a feature they demand, then I implement it. Sometimes you have to say "no" to a feature either becuase it's impossible, there isn't time or there's a better way, but if your software is for someone else, I think you should listen to them.

    Not everyone can pick up a programming language and fix their software -- even those of us who can can't afford to patch every piece of open source software they wish had some feature or another.

    Saying "Use the source. Now leave me alone" to a non-coder (or even a coder) is like having the chef of a restaurant telling you to cook your own damn steak if you don't like the way s/he does it; s/he may be right, but will s/he be a chef for much longer?

  • by ucblockhead ( 63650 ) on Tuesday February 15, 2000 @10:20AM (#1271643) Homepage Journal
    The trouble is that many of the flames are self-deluding. They complain about any criticisms Linux, even when the criticisms are completely justified. If this happens too often, people will stop listening to all criticisms, assuming that they are all unjustified.

    I remember back in the early days, the biggest flamewars were "Apple ][ vs. Commodore 64". In many ways, the participants there were the same sorts as the worst flamers here. Usually it is someone young and niave, who has only really seen one system. They get themselves invested in that one system and feel the need to prove it in order to prove that their investment wasn't unfounded. And so they flame anything that even looks like a criticism of their favored OS.

    But despite their loudness, the majority understand that every system has its strengths and its weaknesses. Unfortunately, if the idiots are too loud, and burn people too often, those on the outside will shut everyone out, idiot and otherwise.

    Every system has its weaknesses. So does Linux. Sending blizzards of mail to correct something that was incorrect is good. Sending blizzards of misinformed mail pretending that black is white because otherwise your OS isn't perfect makes everyone look bad, makes people ignore criticism and is just generally counterproductive.

    Even Linus Torvalds says that someday something better than Linux will come along. Don't be one of the fools that is so blinded by partisanship that they get left behind when this happens.
  • by zorgon ( 66258 ) on Tuesday February 15, 2000 @11:48AM (#1271644) Homepage Journal
    Yess! Thank you, Chromatic. I was not the slightest bit impressed by the article that spawned the flames. I don't approve of angry flamage as a rule, but that article was particularly redundant and lame. None of the self-appointed pundits who say 'Windows is easier' acknowledge the fact that the public have been suffering from Windows for a long time, therefore there is lots of pseudo-experience out there. Windows is only 'easier' because of long experience (enforced by monopoly). Your comment succintly summarized this phenomenon. Think about all the PC columnists who whine about Linux (*nix) being 'hard' -- they've all been hacking at AUTOEXEC.BAT and CONFIG.SYS for over ten years! If they'd been studying /etc as hard, they'd be *nix gurus!
    Just my USD2.00E-2.

    "C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do it blows your whole leg off."
  • *donning asbestos full body suit*

    Anybody look at the last 10 posts or so on this thread?
    This is exactly what the author was talking about!
    A set of flaming comments on the author being "a M$ pawn" and "Grok? Crock!" and so forth. (Especially if you browse /. at a lower level!)
    In spite of the man having some good points about the state of Linux in relation to "newbie" users, i.e. the public in general, he is automatically attacked and flamed as if he was Bill Gates posting on /.!

    As a user of Linux for about two years now I can honestly say that it's not ready for prime time quite yet. Close? Yes! Absolutely!
    Can we just give it to a Windows user and have them use it without having to seriously re-train or coddle them? No. No way!

    I have 10 years of OS/Network experience under my belt and there are still quite a few things about Linux that I don't understand.
    If I don't undsertand it then there's quite a good chance that a new or converted user won't either.

    I'm just as strong a promoter for replacing Windows with Linux as anyone else but as members of the Linux community we have to face facts - we're not going to replace Windows any time soon.


    The Tick - "Spoon!"
  • by Tim Behrendsen ( 89573 ) on Tuesday February 15, 2000 @10:46AM (#1271646)

    Two other things Linux advocates need to learn:

    1. 99% of users don't care about the operating system. The only thing that matters is the applications.

    2. Stability for the desktop is way down the list of priorities for the average user. Is it nice? Yes, but it's not a big issue. [Proof: If it was, the Mac would be dead, and Windows never would have dominated.

    Linux will never go anywhere on the desktop until it gets some decent applications that are at least comparably to Windows. Right now they are way, way behind. I've said it before, and I'll say it again: Name for me one significant end-user application that is clearly superior than the equivalent in Windows. There simply isn't one.


    --

  • by razvedchik ( 107358 ) on Tuesday February 15, 2000 @11:25AM (#1271647)
    "New feature ideas and bug reports will no longer go onto a "wish list"; they will go onto a "hot list." You will face pressure to add 50 new items to the next release, when it really ought to have 10. Wealthy organizations, accustomed to getting their way, will demand impossible schedules from you, and then complain if the quality is not perfect."

    Everybody gets hung up on the thought of a big corporation requiring programmers to add whatever features to a program.

    But, with the GPL, if a company needs a feature and the primary developer isn't able to add it (either through lack of time or ability), the company can add their own features. Or, they can pay somebody to add their features. Or, they can use the existing program as a framework for their own version that has the features they need. Point is, they have the flexability if they need it, and the primary developer isn't obliged to listen to anybody (although it's a good idea, sometimes it's not practical).

  • by havachu ( 108698 ) on Tuesday February 15, 2000 @10:04AM (#1271648)
    I am sick of the negativity towards to more outspoken (and angry) sections of the Linux community. Why is it alright for big media and big business to disparage Linux (and by proxy Linux users)? Then when a Linuxer gets angry and vocal in reply to said insult, he/she becomes the bad guy?
    I know all about the Advocacy HOWTO, and I personally am not a flamey mail-bomber. But I believe it IS an effective form of advocacy. This article on slashdot, and last weeks rant about Loki/Blizard ports on LinuxGames shows that people DO pay attention when deluged in hate-mail.
  • by retep ( 108840 ) on Tuesday February 15, 2000 @12:14PM (#1271649)

    Windows has Win9x and WinNT. The first being for your average joe who just wants Office and the Net to work and the second being for servers. Why shouldn't Linux do that? We already have Caldera Linux for the newbies. If you want "power-user" system you can use Debian among others. There is no reason that all the distros should look and act the same. What's good for a newbie is hell for a power user after all.

    It only makes sense to have different Linux's for different people. You can't please everyone. We don't all run an identical kernel. Nor should we run identical distros that are all dumbed down for new users.

  • by NightHwk ( 111982 ) on Tuesday February 15, 2000 @11:51AM (#1271650)
    What's needed isnt a dumbing down of linux in its existing form...what's needed is a covering up of its (relative) dificulty.. Let me explain:

    MacOS X, designed to be stupidly easy to use by the guys at apple, yet underneath, its a unix based operating system (hey, linux is unix based too!). What linux needs to get into the avg user market share is a opensource/freesoftware equivelant to the MacOS interface. You don't need a command line that understands human style sentances (dumbing down) you need a GUI that is simple, not overly complicated, and allows the user to do what they need/want easily, like type a letter, or surf the web (covering up).

    Are there any projects out there working on a GNU-Bob? =]

    Better (as in simpler) hardware support is needed too. Woz once said the ideal computer would have peripherals that upload their drivers to the computer when they are plugged in, making them truely plug and play. Most distributions have made proggress in hardware support. HOW-To's from a few years ago tell you to write down all information about your computer before installing linux, including IRQ assignments, chipset type etc...
    These days you don't even need to know what an IRQ is to install RedHat or Caldera.

    Linux is moving in the right direction, it is just important to realize that, to avoid stepping backwards.

    -NH
  • by account_deleted ( 4530225 ) on Tuesday February 15, 2000 @10:15AM (#1271651)
    Comment removed based on user account deletion
  • by Ginger Warrior ( 133649 ) on Tuesday February 15, 2000 @10:47AM (#1271652)
    I wonder what the Linux Killer will be? Any suggestions?

    There is no Linux killer, or at least something newer and better may come along and replace the Linux kernel but there will still be a huge body of free software available and it will only grow and improve.

    One reason, there will always be academics and volunteers forming a core of developers, wether they believe in a moral crusade to make free software available, or whether to scratch an itch.

    Another, it makes no sense for a Large company that makes the bulk of it's money through services embracing a business model that produces less reliable software, thus diminishing the value of those services, this is perhaps less certain than point number one, but I believe it will hold true.

    On a side note, what the author needs to grok is that if he posts technically ill informed details about something people believe passionately about, he is bound to meet some resistance, "Red Hat ships Linux with a Windows-like graphical user interface (GUI)" What??? in what way is X "Windows like"?? "the Linux GIU(sic) does not cover many tasks" whatever.

    Another thing, why does Linux need a Windows emulator? surely a more complete version of WINE would be a better solution. And in what way is X incomplete (apart from the "coming soon" 3D support)?

    Whatever, Later

    -----------------------------------
  • by lymax ( 141351 ) on Tuesday February 15, 2000 @11:07AM (#1271653) Homepage
    I wonder what the Linux Killer will be? Any suggestions?

    A "killer" might be a little strong, I find it hard to beleive that Linux could just up and die. Don't get me wrong I'm sure that Linux could get very sick and old. But it has to many hardcore advocates to just disapear. The Linux base is at it's start not it's end. - But if I could point a finger at a possible threat it would be to another Unix base. And a very good user interface; - MacOS 10.

    I know this is a streatch, but think about it. Mac definitly has the whole "out of the box" situation down. And their new OS, with a BSD backend, is a stable, smart idea. It will be backward compatible with all Mac software and compileing software for it that was written for other UnixLike systems will be a brease. Oh and don't forget MS will keep suporting Mac so the big office suite that everyone and ther uncle already knows will be on the system. -- and yes even AOL will be there.
    Scarry!

  • by ZeroWolf ( 152509 ) on Tuesday February 15, 2000 @10:30AM (#1271654) Homepage
    Unfortunately, if Linux really wants to succeed as a desktop OS, I think it'll have to dumb down to this level. Most people are not that smart, particularly about computers. Most people have no urge to develop their skills in this area - they'd rather do whatever they do and have the computer as a friendly, transparent, no-brainer assistant to that. Thus the success of Windows and Macintosh - one a testament to the power of marketing and monopoly, the other of why it's called human interface design and not computer interface design. I'm less sure that Linux really should become a commercial desktop OS. Usenet went commercial, and look what happened to it. Maybe the development/server/hacker niche is where Linux should remain - an OS that can do anything, one that users graduate to when they begin to acquire a deeper knowledge of computers. Here's a little bit of flamebait: perhaps the correct destiny of the Linux OS as an advanced development/server/hacker system has been hijacked by those who would see Microsoft taken down at any cost? =DP= ...Amiga faithful to the end.
  • by jht ( 5006 ) on Tuesday February 15, 2000 @12:02PM (#1271655) Homepage Journal
    Linux itself isn't a commercial product. If everything collapses tomorrow, the kernel will still be there, the GNU software will still be there, and an awful lot of stuff that has been either GPL'd or Open Sourced over the last couple of years will still be there.

    But think about what the commercialization of Linux has brought us. We have games being ported by more than one company because there are people buying Linux for the desktop. There's major commercial software being ported. Virtually every major brand-name add-in card (video, sound, whatever!) is getting a Linux driver, and in many cases the driver is Open Source, too!

    All these riches are not being bestowed upon us because the companies like the way we dress, the way we talk, or because of the Politics Of Linux. They're in it for the money, and they see Linux as a revenue generator, whether now or down the road a ways. All these development resources that have been turned over to us come with a price, friends. The bargain we strike in excahnge for the goodies is the implicit agreement that We, The People, will build Linux into a commercially viable operating system that Joe Schmoe can buy in a store, take home, and install. That's where the development resources are going.

    It doesn't matter if you were running Slackware in 1995 and remember hand-installing applications fondly. It doesn't matter if you prefer the "pure" days when you used Linux because it was Free, and Cool. It doesn't even matter how you pronounce it (I've been using it since way back when, and I still pronounce it "Lie-nux",). It's still being pushed in this new direction regardless of what we think or want. How else are you going to get to World Domination?

    Keep this in mind whan you speculate as to a Linux without all the commercial backing. The developers will still build things the way you say - but there'll be a heck of a lot fewer of 'em.

    I prefer trying to make it the OS for the average luser.

    - -Josh Turiel
  • by Booker ( 6173 ) on Tuesday February 15, 2000 @10:26AM (#1271656) Homepage
    As Linux is embraced by more organizations, and used in more ways that are crucial, the demands upon you will increase. New feature ideas and bug reports will no longer go onto a "wish list"; they will go onto a "hot list." You will face pressure to add 50 new items to the next release, when it really ought to have 10. Wealthy organizations, accustomed to getting their way, will demand impossible schedules from you, and then complain if the quality is not perfect.

    I'm not sure I agree with this - perhaps demands will be put on Red Hat and the like, but when it comes down to programmers, I don't think so. If it happens, it will likely be ignored. The text that comes with the GPL'd app says explicitly that there is no warranty, and if the free software developer doesn't want to implement 50 features in her spare time, then she simply won't. Is this the kiss of death for Linux in the business environment? Perhaps, but it shouldn't be. Someone who wants features right now can throw money at someone, and get it. Otherwise, it's free, and development terms are dictated by the developer.

    Some readers have suggested to me that the open source method of software development causes project management issues to evaporate; that the projects manage themselves. This is a fantasy. The open source method, while it does solves some problems, raises new ones. You will be managing a large public programming project with conflicting demands, tight schedules, and the need for high quality. You have to figure out how to do this well. Hopefully, you can invent and master new techniques for software project management within the open source method. But if you don't, the complexity of this task will sink your whole endeavor.

    Again, I think the Free Software community has demonstrated that their project management (or whatever you want to call it - their development process...) works very well. Perhaps it's not what people are used to, but it provides robust, feature-filled software. What may be lacking is that most software contains features for programmers, rather than for users. But I don't think I agree that a fundamental change is needed. Perhaps it boils down to the goal of Linux - is it acceptance in the business world, or is it a robust, free, operating system?

    Other than that, I think you make some excellent points, and I hope the Linux community can grok them. :)
    ----

  • by chromatic ( 9471 ) on Tuesday February 15, 2000 @10:31AM (#1271657) Homepage

    I have to disagree with a couple of points regarding end users and applications. The author states that people have invested hours and hours into learning the ins and outs of their Office Suites. Yeah, some people have. Most of the people I know sure haven't! They've spent hours and hours doing the same things over and over again because someone showed them how to do a simple task. If they moved to a different program, they'd scramble for a few weeks and call someone over to show them how to do two or simple tasks and then they'd be okay.

    I'm pretty sure this is a representative group, here. They don't want to learn the ins and outs of everything. They certainly don't want to sit down with a manual and learn what options they have and might use in the future. When they try to do something new (perish the thought) they might poke around for ten seconds and then either give up or try to find someone else who might know how.

    So the time spent in learning a new application is a lot smaller than the author estimates -- if the people I know are representative.

    Of course, then he talks about the Palm being a revolutionary device because it did what people wanted to do, as opposed to making people adapt to a new system. Right. I'm willing to bet at least, oh, 95% of current Palm users had to learn that Graffiti language. Granted, Palm users may be more technically adept than the rest of the population, but they learned something new and it became a fantastic success.

    I suspect the truth is closer to my experience than the picture the author presents. :)

    --

  • by jeffcuscutis ( 28426 ) on Tuesday February 15, 2000 @10:19AM (#1271658) Homepage
    This is exactly the kind of thing he's talking about in the article. Most users are NOT like us. They do not want to learn new ways of doing things. They will not learn new ways unless forced to do so. Getting them to Linux REQUIRES these kinds of apps (AOL, Word) and not just look alikes, but work alikes.
    --jeff
  • by JoeWalsh ( 32530 ) on Tuesday February 15, 2000 @11:48AM (#1271659)
    > you simply can't call Linux advocates elitist or snobbish and be expected to get away with it, eh?

    Ah, but then there are those of us who are elitist and snobbish about Linux, and who admit it and even revel in the fact.

    I used to enjoy using an Atari 8-bit computer. It was great. You could get the source code to its OS from Atari. You could also get the source code to its DOS and its BASIC language. They would send you programming tip sheets for free if you asked them to. And, as a 12-year-old, I called Atari Corp. with a programming question, and a couple of weeks later an actual progammer called me back. Me! A little 12-year-old, talking to a big-time programmer about my completely inconsequential problem!

    But, the masses chose IBM Compatibles, which were horrendously expensive and which didn't offer graphics or audio as good as that 1979-vintage Atari until more than two decades later. Even so, the masses chose this broken platform, and before long, almost the whole world thinks the IBM Compatible's operating system of choice (Windows) == Computer. Pretty soon, just about all the hardware and software available in stores is only available for "IBM PCs and Compatibles." So I ended up buying one, and suffered through programming that closed OS for longer than I care to think about.

    But, hey, at least I found Compuserve at about the same time as I adopted that crappy platform as my own. It was a nice online community, populated mostly by people who knew a thing or two about computers. I mean, you at least had to have a modem and know how to configure your terminal program to get on there! I had a lot of fun on Compuserve (and paid the huge Visa bills to prove it), and even met the woman who became my wife on there.

    But The Masses wanted AOL, so Compuserve made itself more and more like AOL, and eventually AOL bought out Compuserve and made them virtually one and the same.

    I could go on and on with this sort of thing, but I'm sure you've gone through the same sorts of processes.

    The bottom line is that I'm sick and tired of having what I love ruined by the will of the masses.

    If they want to use Linux, that's great. In fact, I'd prefer if everyone did. But if Linux has to be adulterated beyond recognition before they'll accept it, then fsck 'em. I'm not going to lose yet another of the great things in my life just because most people are lazy and ignorant.

    While I'm ranting, I may as well rave about the original author's crack that we'd better all watch out or the Big Bad Companies will get upset that they're not getting what they want from us.

    OH REALLY?!

    I'm completely fed up with people telling me that I'd better do X or the companies will be mad, or I'd better NOT do Y or the companies will be upset.

    These are the same entities who are ruining our lives. They're the ones who register software patents, who buy our politicians, who send 16-year-olds to jail for having the audacity to view legal copies of movies on their OS of choice. These are the monsters in our nightmares, immortal, all-encompassing, and growing more powerful by the day. And we're supposed to care more about what /they/ want than what /we/ want when it comes to /our/ OS?!

    They can all go to hell in a handbasket, and so can their cronies who think we should do their bidding.

    Linux is /our/ OS. Let's never forget that.
  • by Darth Yoshi ( 91228 ) on Tuesday February 15, 2000 @10:33AM (#1271660)
    > 2. Tell those "wealthy organizations accostomed to getting their way" to take their "schedules"
    > and shove them. We have no time for that.

    No. The correct response is, "Here's the source, have a nice day". That's why it's called open-source, isn't it?
  • by FreshView ( 139455 ) on Tuesday February 15, 2000 @10:12AM (#1271661) Homepage

    Let me just say that I installed red hat 6.1 over the weekend on a Jaz drive on a computer that is primarily a windows box. It went HORRIBLY.. I had the worst time with it, I eventually bought a new NIC after reading newsgroup posts about the 3c509b nics form 3com. I bought a NetGear nic, which eventually worked, but has made boot and shut down freeze a few times (I fixed this). It is not easy to set up Red Hat linux (I've never tried caldera or corel), that much is clear to me. It is FAR FAR easier to set up Windows 2000 from scratch (I've done that 25 or 30 times, in a testlab). It is the easiest install I've ever seen. Once it's up, I never have any problems finding drivers for my up-to-date hardware. Again, drivers WERE available in Linux for almost everything, but they were very difficult to find (Diamond MX300 sound card). When X first came up, it would only come up in 640x480, I had to mess around with the X86config file, where i set my refresh rate of my monitor incorrectly (it is a used monitor, and I don't actually know it's specs), so in one or two resolutions it was impossible to figure out what the hell was on the screen.

    Now, After about 3/4 hours of work. It works great, and I'm ready to start messing around with perl and CGI. I personally don't mind the 3 or 4 hours lost, it was for a "good cause". I wouldn't even know how to begin getting CGI stuff set up in '98 (my other os, for gaming). But I have a fairly good idea about it in Linux.

    I've been using Linux since the major distribution was slackware 2.0 (at least on the east coast). So I know somethng about it. I actually had fun setting it up on the Jaz drive. Though I can't actually get the Jaz Disk to boot, I can always pull it out and put another OS on another disk.

    Now. I would never expect my mother to be able to do what I did, or even many of my friends. There is a gap between Linux and windows that is closing rapidly, but it is there, and it's not technology, it's usability.

    Anyway, I thought I'd share a semi-newbie's experience. (I hadn't touched linux in 2 years).
  • won't be the ones reading. They'll be the ones skimming and then flaming.

    What kills me about the Linux movement is this: It is composed apparently entirely of people that have never been USERS in their lives. They've never dealt with something that they just don't have the time or ambition to learn. They've never dealt with something that is unnecessarily difficult.

    These people make statements like "Lets not dumb it down THAT far..." about porting AOL to Linux. Linux advocates seem to have forgotten that putting the software that people want on their PC isn't 'dumbing' anything down, it's called customer service. I like Linux. I wish it could gain the market share and market approval necessary to start getting the software development that we need for it to prosper.

    Right now, Linux has no place on the desktop in my company. There are limited places where you could put Linux on the desktop and make it work. Why is this? Because the 'elite Linux gurus' want Linux to remain as-is. A club that only people with the computer and programming know-how can join. An exclusive club from which they can look down upon the [L]users that DARE to ask for user friendly software and configuration tools.

    Next month and the following, as all of the geeks that have to fill out a tax form more complicated than the EZ, I want you to take a look at who you're paying to do your taxes. If you're doing them solo, take a look at the time wasted and the frustration involved in this seemingly simple task. Why is this? Because the IRS feels about the tax codes like you do about the code behind Linux. Job security through obscurity?

    Well, it's a good thing I don't collect karma, because I am confident this is going down in "flames"...hell, you simply can't call Linux advocates elitist or snobbish and be expected to get away with it, eh?


    -Jer
  • by grappler ( 14976 ) on Tuesday February 15, 2000 @10:16AM (#1271663) Homepage
    I thought this article would be about how we need to clean up our advocacy act, lest we turn off those we try to convert.

    Instead, he's insisting he's right about the things he wrote about linux. I agree with his assessment of what end users expect and need, but this part caught my eye:

    As Linux is embraced by more organizations, and used in more ways that are crucial, the demands upon you will increase. New feature ideas and bug reports will no longer go onto a "wish list"; they will go onto a "hot list." You will face pressure to add 50 new items to the next release, when it really ought to have 10. Wealthy organizations, accustomed to getting their way, will demand impossible schedules from you, and then complain if the quality is not perfect.

    I have two responses to this.

    1. God, I sure hope not. I hope it never comes to that. Let's make sure it doesn't.

    2. Tell those "wealthy organizations accostomed to getting their way" to take their "schedules" and shove them. We have no time for that. If they want crappy software with lots of features, point them to the borg in the northwest. They'll come crawling back.

    --
    grappler

Work without a vision is slavery, Vision without work is a pipe dream, But vision with work is the hope of the world.

Working...