Slashdot Mirror


Friedman on Linux Desktop Expectations

An anonymous reader writes "SearchEnterpriseLinux.com is featuring an interview with Novell/Ximian's Nat Friedman on the increasing interest about the Linux desktop. Quote from the interview - "A day doesn't go by when I don't talk to a Fortune 1000 customer from the financial services market, automotives or others that are not looking at dipping their feet into the Linux desktop." And by the way, both Nat Friedman and Miguel de Icaza's April 12th blog entry have a picture of Miguel and Nat dancing with David Vaskevitch, CTO of Microsoft. Now that's something you don't get to see everyday!"

42 of 347 comments (clear)

  1. OOoo, first post! by Trogre · · Score: 5, Funny

    "A day doesn't go by when I don't talk to a Fortune 1000 customer from the financial services market, automotives or others that are not looking at dipping their feet into the Linux desktop"

    No no, not more triple negatives!

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  2. David who? by Anonymous Coward · · Score: 3, Funny
    a picture of Miguel and Nat dancing with David Vaskevitch, CTO of Microsoft.
    What? Was Steve Ballmer unavailable? Just wait until he hears about this. He's gonna flip. (literally)
  3. We need a new toolkit... by kcbrown · · Score: 5, Interesting
    I sent this in response to this, but I think it's quite relevant here, too, because it addresses the problem of desktop consistency:

    Btw, if you have been following my posts on my blog and on the desktop-devel-list, you will know that my feeling is that all of the existing toolkits today (Gtk, Qt, XUL and VCL) will become obsolete and we need to start looking at the next generation toolkit system.

    If you're going to do a next generation toolkit system, then do it right: start by creating a network protocol for it.

    You heard me right. The right way to do a toolkit is to make it networkable in a client/server fashion. There are a few reasons for doing so:

    1. Speed over the network. Instead of having to transmit low-level graphics primitives, you now only have to transmit higher-level widget information. This should represent an order of magnitude reduction in the amount of network traffic required. It also means the bandwidth between the code that draws the widget and the code that renders it will likely be as high as possible (a local socket or some such).

    2. Consistency. With a client/server widget architecture, all applications running anywhere will have the same look and feel when they're displaying through your widget server. Additionally, changing the theme in use will change the look and feel of all the applications using the widget server (which, ideally, should be all of them).

    3. Abstraction. Because the widgets are implemented on top of a protocol, widget libraries simply have to all talk the same protocol. This means that it doesn't matter what the widget library itself looks like, what language it's implemented in, what object paradigm it uses, or anything else: the look and feel will still be the same. This is markedly different from the current situation with GTK, QT, and all other Unix widget sets, each of which implements its own look and feel. A client/server architecture can, and should, abstract out the look and feel of the widget set.

    Do it that way and I think it's likely that you'll finally eliminate the one big problem on the Unix desktop: the disparity in look and feel between applications written for different widget toolkits.

    --
    Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    1. Re:We need a new toolkit... by Jameth · · Score: 3, Interesting

      I quite agree. However, there is an unfortunate problem with making a new toolkit: Cross-Platform.

      Qt is great because it is cross-platform. GTK has that too. The amount of things that will run native cross-platform are fewer than those that will run on a single platform.

      Also, you are arguing for a widget server, which will work best when it is the dominant/only widget set. Windows can do this. Linux is still too diverse.

      Still, I think you're right. Completely right. I just was noting a few things.

    2. Re:We need a new toolkit... by phok · · Score: 4, Informative
      If you're going to do a next generation toolkit system, then do it right: start by creating a network protocol for it.

      *cough*Y-Windows*cough*

      They seem to be working on a widget set to go with their protocol. I agree that this is the way to go. Someone will hack $WIDGET_LIBRARY to use the protocol, and we can unify the look and feel. This is a lot more elegant than hacks like GTK-QT because they must all interface to the one widget set to rule them all.

      Abstraction. Because the widgets are implemented on top of a protocol, widget libraries simply have to all talk the same protocol. This means that it doesn't matter what the widget library itself looks like, what language it's implemented in, what object paradigm it uses, or anything else: the look and feel will still be the same. This is markedly different from the current situation with GTK, QT, and all other Unix widget sets, each of which implements its own look and feel. A client/server architecture can, and should, abstract out the look and feel of the widget set.

      You're right, it is a significantly different approach, but as I said above, this is not completely incompatible with current widgets.

    3. Re:We need a new toolkit... by Tyler+Eaves · · Score: 3, Insightful

      I agree, but here's what I want:

      EASE OF PROGRAMMING.

      All the existing toolkits have APIs that are daunting to say the least.

      --
      TODO: Something witty here...
    4. Re:We need a new toolkit... by be-fan · · Score: 3, Informative

      Windows cannot do this. It is way to diverse as well. Hell, Microsoft itself uses 3 different toolkits for its major app lines!

      --
      A deep unwavering belief is a sure sign you're missing something...
    5. Re:We need a new toolkit... by demachina · · Score: 4, Insightful

      "Do it that way and I think it's likely that you'll finally eliminate the one big problem on the Unix desktop: the disparity in look and feel between applications written for different widget toolkits."

      Actually, I think you will just pile another GUI toolkit on to an already large pile, and create a new set of applications with a whole new look and feel. In particular you seem to be understating the major effort you are proposing either intentionally or unintentionally.

      First off it takes a lot of work to develop a complete GUI toolkit from scratch. Once you do it then you have to migrate a large body of applications to it which is probably a larger effort than developing the toolkit in the first place. Are you planning to rewrite all the applications in GNOME and/or KDE, OpenOffice, Mozilla etc. How long do you figure that will take. It would take a long time and it would be time spent not developing the capabilities of the applications. In many respects it would be hitting a master reset on the Linux desktop and starting over, which isn't likely to lead to world domination for at least a few years.

      Chances are you wont even get a majority of the developers on some of these major projects to buy in to your new toolkit, though some probably will so you will probably end up with a bunch of new splinters.

      I'm just not sure what it is about GUI toolkits and window managers that exert this constant allure on geeks, compelling them to constantly develop new ones, the vast majority of which never develop critical mass.

      But hey, maybe through superior uber geekness you will develop a new superior uber geek toolkit and you will be able to migrate a complete set of applications to it, and all others will be abandoned in the face of its superiority. Its just seems like something of a long shot. One thing positive I can say about this plan is it might be the only way to end the death match between GNOME and KDE.

      Exactly how much time were you estimating to achieve this grand unified GUI?

      --
      @de_machina
    6. Re:We need a new toolkit... by LMCBoy · · Score: 3, Insightful

      Really, have you tried Qt? It's a pretty fun toolkit in which to code. A beautiful API, IMO.

      --
      Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
    7. Re:We need a new toolkit... by kcbrown · · Score: 3, Insightful
      I quite agree. However, there is an unfortunate problem with making a new toolkit: Cross-Platform.

      But the beauty of separating out the look and feel of the toolkit from the implementation of the toolkit via a network protocol is that porting the widget set to a new platform is now much more straightforward: you simply have to write a widget server on the target platform, which will take widget requests and display them through the native widget set.

      Where you'll have to write some code is when the native widget set is missing a widget type defined by the protocol. In that event you have a couple of options: reject the protocol request, or implement the look and feel of the widget in software (using as much of the native widget set as possible, of course). You can always do the latter -- how else do you think new widget types are created on a platform such as Windows?

      Also, you are arguing for a widget server, which will work best when it is the dominant/only widget set. Windows can do this. Linux is still too diverse.

      No, this isn't the problem. The problem is that right now the existing widget sets under Linux all implement their own look and feel. They've duplicated a lot of effort as a result.

      With a widget protocol, you implement GTK or QT the same way as before, except that whenever possible you make widget protocol calls instead of doing direct drawing, mouse handling, etc. For cases when the widget protocol doesn't supply the kind of widget you want, you'll have to implement the look/feel in terms of more primitive graphics calls (and thus the widget protocol will have to support the ability to do direct graphics, including 3D graphics) -- but even that should be done on top of existing widgets whenever possible.

      There might be other ways to approach the problem of extensibility, e.g. by making it possible to dynamically define to the widget server the properties of a widget: the inputs it expects, the areas that have to be drawn on, etc. But I haven't thought any of that through.

      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
    8. Re:We need a new toolkit... by pdamoc · · Score: 4, Interesting

      we don't need another hero (toolkit)!
      It is not the toolkit that is needed but a shift in programmers mentality. We should stop wasting time and use the wisdom of people whom are way better than us at this. We should use PATTERNS. Like MVC for example. When applications will have all the code separated in Models, Views and Controllers toolkits will become irrelevant because as long as you can access the model you can create your own Views and Controllers. The use of higher level languages should be encouraged. The higher the language the easier is to understand the program and so more people can get involved. The cross-platform issue will fade due to the fact that there are already a lot of great cross-platform toolkits in which the View-Controller part can be implemented (scripted.
      The separation of the Model will have yet another benefit, no more reinvention of the wheel, at least in some parts. It could be highly optimized due to the fact that such an approach will encourage only one instance of the model per functionality. No more complex compiling schemes: script the interface (View-Controller) in python and compile only the model or provide it as a binary: .so, .dll, whatever.

  4. quite simply ... by Neuropol · · Score: 4, Interesting

    people will expect things to 'just work'. email, spreadsheet, document editing, and other office functions are all well covered on the desktop.

    it's the little things that will get people turned off fast: like browser plugin integration, javascript issues, etc. even though MozillaFirebird(rip), and the like, are great for allowing instant plugin installation, there is yet a large hole for media plugin usage considering all of the formats that microsoft and mac have floating around. this is a current limitation, imo. not necessarily a negative on the linux part, but an obstacle created by microsoft and other companies that continues get in the way of total success. that's potentially a major issue and a lot to overcome. i think it's possible to break the stigma regarding linux on teh desktop. it's come miles in the last few years. on the path it follows now, it will over come the general fear that it just doesn't do what windows can. because it can. time has brough a lot of things closer to completion. hardware compatibilty is no longer an issue if you are running current distributions and licensing is an age old argument but if you're in to function for a small fee then why not?

    personally, i'm waiting for the linux desktop that comes loaded with enlightenment (absolutely manadatory!), and all things audio editing, and every funky/odd thing that was available in the rh7.3 stage of development. then i will be satisfied.

  5. triple negative by mattdm · · Score: 4, Funny
    "A day doesn't go by when I don't talk to a Fortune 1000 customer from the financial services market, automotives or others that are not looking at dipping their feet into the Linux desktop."

    So, to rephrase with the first part in the positive: "Every day, I talk to a Fortune 1000 customer who has no interest at all in Linux."

    Is that really what he meant to say? It may be true, but y'know, I talk to people who have no interest in various things all the time....

    1. Re:triple negative by Swamii · · Score: 5, Funny

      "Erkie gee whizzle guys that's a triple-negative!", shouted the nerdy-looking young fellow. Just then, a pig-skinned covered ball sailed through the air, breaking the glasses of the poor, grammatically-correct soul.

      --
      Tech, life, family, faith: Give me a visit
    2. Re:triple negative by donnz · · Score: 4, Funny

      The golden rule -

      In English a double negative makes a positive. This is not the case in all languages.

      However, there is no language in which a double positive makes a negative.

      YEAH, RIGHT....

      --
      -- Free software on every PC on every desk
  6. Basics tasks & understanding of the UI (on any by zymurgyboy · · Score: 4, Interesting
    Friedman: The No. 1 misconception is that usability is a major barrier to adoption and that's not true. It used to be. There was a study done recently with a group of 20 users who had never used a computer before. Ten were put at a Windows PC, 10 at a Linux PC and they were given a list of simple tasks like sending an e-mail, surfing to a Web page and the usability results were pretty much the same.

    Yes! This is so true. A lot of users I've had to support over the years have trouble doing the very basic tasks Mr. Friedman describes. Why would it make any difference which desktop OS they get minimal training on to do these tasks with?

    If serious inroads are ever made in the US the argument for staying with Windows for compatibilty with clients or customers would fade pretty quick, weather this happens with Linux- or OS X- or whatever-on-the-desktop.

    Even more likely to take off if more people start using Apple's at home. They're less afraid of this when things they make with their computer are as useful at work as they are in their livingrooms.

    --
    If you never make mistakes, it's probably because you're not doing anything.
  7. Ximian Bails Out by geomon · · Score: 5, Interesting

    "A day doesn't go by when I don't talk to a Fortune 1000 customer..."

    Not *exactly* true.

    We had Nat scheduled to show up and he blew us off. I was left standing in a conference room for nearly 1/2 hour telling participants that I was sorry that Ximian bailed on us.

    I had to apologize for their no-show. Not a great feeling.

    Guess a national laboratory isn't the market segment Ximian was interested in.

    --
    "Rocky Rococo, at your cervix!"
  8. I want to dip my feet into linux too.. by nmoog · · Score: 4, Funny
    ..or others that are not looking at dipping their feet into the Linux desktop
    I understand their feelings. If I can't get python running on my slackware machine by this afternoon, I am going to dip my foot so hard into the linux desktop it's going to wish Linus never invented it...
  9. What will it take? by brutus_007 · · Score: 3, Interesting

    "A day doesn't go by when I don't talk to a Fortune 1000 customer from the financial services market, automotives or others that are not looking at dipping their feet into the Linux desktop." With all the tools, utilities and applications currently available, why isn't Linux on the desktop happening already, or why aren't they jumping in rather than just "dipping their feet"? Is there something missing? Do we need THE killer app to be created which would run solely on Linux (which would basically require it to be closed source to stay on top, and difficult/involved enough to duplicate it on Windows to wait around for a port/clone)? Is it perhaps that larger companies are contractually obligated to fulfill order quotas for equipment or application licenses (MS Licensing v6 anyone?) that breaching the contract would be too financially devastating to make a conversion worthwhile or financially sound?

    --
    I have 1 million monkeys on a million year contract to make me a better sig.
  10. Can desktop linux ever be sold? by LostCluster · · Score: 3, Interesting

    One of the key problems that "desktop Linux" seems to be facing is that it's hard to make money as a distro maker. Unless you build your distro to be tied to your mothership for patches, what other models are there?

    - Pay-per-seat? No way, the GPL lets you get undercut by "Free" if you do that.
    - Pay-for-support? Double edged sword. Means your user interface has to suck, otherwise they'll keep using it without the needing to pay for the contract.
    - Selling-add-ons? That's a risky play, not likely to cash-in.

    And without the money... just where is the business-friendly distro going to come from? GPL projects have a bad habit of going programmer-friendly instead of user-friendly when left unpaid...

  11. Re:Triple negative? by Anonymous Coward · · Score: 4, Funny

    You best not don't complan about sthe spalling, grammer and what not here at ./ It always never helps and you usualy don't not get modded in the non negative way which isn't never bad so to speak.

  12. Fortune 500 TRIES anything, uses a few by MrChuck · · Score: 3, Insightful
    I work at a Fortune 500 corporation.

    They have some Linux around. Little utility type functions.

    At a company > 10,000 people, there is a difference between "interested" & "using" and in "we are using it for critical systems and rely on it and recommend it and tell our partners to use it."

    But then, lots of large fortune 100 wall st companies have had "the future" of desktop unix years ago. They just forget the part where I could fix problems around the world without moving my chair. When admins cost more, but you needed half as many.

  13. Re:No thanks by flacco · · Score: 3, Funny
    We had Nat scheduled to show up and he blew us off.


    based on his picture, i'd guess your meeting was scheduled past his beddy-bye sleepy-time.

    --
    pr0n - keeping monitor glass spotless since 1981.
  14. Linux needs name brands. by huchida · · Score: 3, Interesting
    Linux can and should be known as the web developer's platform, in the same way Apple is known for video, publishing, and graphic design.

    Adobe's probably a lost cause, but Macromedia would do well to port its projects over. Dreamweaver, Flash, Freehand, Fireworks...

  15. Re:You know what this means, right? by EmbeddedJanitor · · Score: 3, Insightful

    If anyone can make this happen it is Novell. They understand the corporate market better than anyone and can deliver corporate desktop solutions that work and have a name that people trust.

    --
    Engineering is the art of compromise.
  16. X works just fine thank you by codepunk · · Score: 4, Interesting

    I dont seem to be having much in the way of bandwidth problems running 150 desktops off of a single server. It takes about 150 k sustained bandwidth to suppor that. Now come back when you know what you are talking about.

    --


    Got Code?
    1. Re:X works just fine thank you by buttahead · · Score: 3, Interesting

      I'd like to see some examples of the use on those 150 desktops. In my experience 10kbps is not enough to have a smooth desktop experience. I'd alos like to see the latency you have. Say, at 200ms mozilla takes about 1 minute or more to load, and vnc is just barly usable.

    2. Re:X works just fine thank you by codepunk · · Score: 3, Informative

      No for dialup and dsl users you pay yes I said pay for a copy of nomachine (go look it up) it makes x efficient even across a modem.

      --


      Got Code?
    3. Re:X works just fine thank you by harikiri · · Score: 4, Informative

      I agree with the post above. My mum has recently started work as a regional manager of a company based in the US, working from a home office. How does she access her corporate email? Via MS remote desktop.

      Due to stupid ISP issues, to get her up and running quickly, we had to get her a pre-paid dialup account. I was seriously worried about whether or not she'd be able to do any work, based on my own experiences running X tunneled over SSH from my work system to my home boxes (and VNC across local networks).

      However, I was pleasantly suprised - despite being only on a 33.6k connection, she is able to do all of her correspondence, through outlook, over RDP to a server in the US. Looking back at the latency issues in running X across local networks and over the internet, the Xwindows protocol needs some serious work to be even close to accomplishing the same smoothness.

      And all this is coming from a hardened Unix geek like myself. :-P

      --
      Man watching 6 MSCE's around a sun box, looks alot like the opening scene's of 2001:space odyssey...
    4. Re:X works just fine thank you by codepunk · · Score: 3, Informative

      Actually I would never deploy straight mozilla we always use firebird for thin client deployments. I cannot say I have been on a even marginal network with 200ms latency. Hell I get better than that off of a cable modem across the internet to nearly any site.

      A couple of hints

      No screensavers all of them have been removed

      No fancy background they have a straight color background to keep refresh rates down.

      We currently use kde but are switching to bluecurve because of it's polish.

      20 of those clients are wireless and that works
      fine as well.

      --


      Got Code?
    5. Re:X works just fine thank you by idiot900 · · Score: 3, Insightful

      In my experience 10kbps is not enough to have a smooth desktop experience.

      Of course not. The 150K/s is probably an mean over time of all clients' usage, not a sustained transfer - if it were, Ethernet would been designed to be circuit switched like the PSTN and not packet switched ;) I'd expect any individual client to have spikes of high bandwidth usage separated by long periods of low bandwidth usage, consistent with pointing and clicking. When you combine a bunch of clients, the spikes combine too and even out to the quoted 150K/s.

    6. Re:X works just fine thank you by kcbrown · · Score: 3, Interesting
      I dont seem to be having much in the way of bandwidth problems running 150 desktops off of a single server. It takes about 150 k sustained bandwidth to suppor that. Now come back when you know what you are talking about.

      Yeah, but the reason you can get away with that is that you almost certainly have a much higher burst rate than just 150k, and even if 150k were your burst rate limit, that's far better than 5k per second, which is what you'll be getting over a modem connection.

      X is fine until your client has to send a bunch of pixmaps. Then it gets bandwidth-hungry. Typically this happens during application initialization, so I don't doubt that you're not having trouble with 150k sustained bandwidth. But I'll bet your burst rates peg the interface.

      The widget protocol is not intended as a replacement of X -- in fact in the Linux world it would certainly be implemented on top of X. But the bandwidth savings are still there nonetheless.

      I've done X over a slow-speed (modem) connection before and while it's not unusable it is slow. Transmitting widget protocol commands would make using a slow-speed modem connection work about as well as X works over a medium-speed (150k/sec or so) connection, because applications would transmit pixmaps only when supplying application-specific graphics. So programs like Photoshop would be slow to load images but would be reasonably fast once the image itself were loaded. The bulk of the graphics traffic that passes between X clients and an X server is composed of UI widget graphics, and that hurts application startup time over a slow link a LOT.

      So...come back when you know what you're talking about. :-)

      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
  17. What is so strange... by Anonymous Coward · · Score: 3, Funny

    ...about Miguel and Nat dancing with a MS CTO? Aren't they MS employees?

  18. Why the interest? by bladernr · · Score: 3, Insightful
    Nat Friedman on the increasing interest about the Linux desktop.

    In a vacum, this is not impressive. Is the interest in Desktop Linux due to quality of the platform, available technologies, developer friendly environment, ease of integration, or is it simply based on cost.

    If its simply cost then, well, where is the pride in that? As a true propeller-head, I find winning on price, well, cheap.

    --
    Sarcasm and hyperbole are the final refuges for weak minds
  19. Re:National lab? by geomon · · Score: 4, Insightful

    Nat is always very interested in National labs.

    Then I guess he's going to have a hard sell to make. After pulling a no-show with nearly 100 participants planned (most of whom are in a position to make purchasing decisions), we are certainly going to be taking any claims regarding customer service with a sizable grain of salt.

    Had we given Microsoft's representative a similar opportunity, they would have crawled over broken glass with a killer fever to make the meeting.

    Determination to meet the client on their terms and on their time is what makes a sale. Having a superior technology with crappy customer service will not make it.

    --
    "Rocky Rococo, at your cervix!"
  20. Re:Basics tasks & understanding of the UI (on by Jason+Earl · · Score: 4, Insightful

    If anything this just goes to show how much the average consumer cares about usability. Most consumers don't really care how usable their software is. Usability and $0.50 will get you a Snickers bar. Don't get me wrong. I think that Apple really does have the edge when it comes to making usable systems. Especially if you don't have to share documents and files with Windows users. However, when push comes to shove, consumers want "usable enough" at the lowest price, and that's not Apple.

  21. Interest or hope? by LenE · · Score: 3, Insightful

    With ever increasing Windows problems, it may be more of a hope for Linux Desktops to finally be useable enough for enterprise users, rather than genuine interest. How many non-geeks even know what the various linux desktop systems are, besides not Windows. Linux geeks know that Linux is the kernel, and nothing more, so what desktop is the Linux Desktop?

    Today's Linux desktops fall over themselves trying to act similar to Windows, while having the unfortunate problem of not being even as consistent as Windows. This problem is rooted in the whole X11+Gnome+GTK+KDE+Qt+Ximian+Lestif+kitchen sink quagmire that is required to supply the pieces of this quite disjointed user experience.

    In my not so humble opinion, the interest for the Linux desktop is the hope of Microsoft liberation, without scrapping existing hardware. This is quite silly, as the cost of the disruption in retraining all of the users, will far outweigh the cost of either switching to a useable, coherent UNIX desktop like Mac OS X, or staying on the MS Treadmill. Unfortunately, there is no quick fix here, as the bazaar is not willing to collaborate on a unified, coherent Linux Desktop.

    -- Len

  22. I guess you've never used Mandrake Linux, then? by leonbrooks · · Score: 4, Interesting

    Neither my wife nor my SIL know how to mount stuff, wife would be aghast at the thought of having to type unrepresentative mumbo-jumbo into an unresponsive black window (or, heaven help us, a text screen - which she calls "dos"). It Just Works(tm). The coloured bar graph in K3B is a lifesaver when SWMBO is building CDs to go, the raw numbers would only be confusing. As an artist or musician, she excels, but sit her in front of a command prompt and terror reigns supreme.

    --
    Got time? Spend some of it coding or testing
  23. On package management by harikiri · · Score: 4, Interesting

    I had a workmate come up today and start explaining what his issues were with Linux. This guy is a network engineer, who recognises the usefulness of having a free unix system to use on his spare pc's.

    His beef was that he had installed Mandrake 9.2 on his system, and went to setup NTP. NTP was not installed. So he started looking for an RPM (he knew what they were!) for NTP for Mandrake. He said that he found one (probably from rpmsearch), but that when he downloaded it - it had additional dependencies that he couldn't find.

    Now if it was me, I would've first tried rpmdrake (the distribution's own package management tool), and failing that, built it from source. But this guy was looking at Linux like a tool to be used. He wanted to do something simple (setup NTP), and the software wasn't installed. He found the software package for NTP online. This however required additional packages that were not immediately available. In the end he threw up his hands in disgust and stopped working on his new Linux box.

    I ended up showing him a freebsd box I had here, and the ports mechanism for software installation. I then also discussed apt and the problem of too many ways of managing software installations, and none (that he could find) that accomplished the job for him.

    So I'm going to bring in a copy of Mandrake 10 community edition for him to try out. In the meantime, I'm waiting for him to wander over one day and say "gosh Linux is great, I installed it and setup NTP in a few button clicks..."

    --
    Man watching 6 MSCE's around a sun box, looks alot like the opening scene's of 2001:space odyssey...
  24. conspiracy theorist, start your engines! by markan18 · · Score: 3, Insightful

    Hmmm, 2 open source guys dancing with the microsoft cto, am i the only one afraid? IIRC, they are the ones working on the mono project, i won't be surprised if microsoft crushes them if they finally catch up.

    Please, prove me pessemistic

  25. Re:Basics tasks & understanding of the UI (on by Master+of+Transhuman · · Score: 3, Interesting

    > Windows users pull their hair out. Many of them
    > ay "damn it, this is just too hard" and go buy a
    > Mac. Many Windows users say "good riddance".

    Windows users try Linux and pull their hair out. Many of them say, "Damn it, this is just too hard" and go back to Windows. Many Linux users say "good riddance."

    Many first-time Windows (in Asia, Latin America, etc.) try Windows and pull their hair our. Many of them say, "Damn it, this is just too expensive" and switch to Linux. Bill Gates does NOT say "good riddance."

    There are people who should not be allowed to touch a computer (or a firearm, or much of anything else as well). You cannot judge an operating system's usability by these people.

    The other issue is training and habit. People trained in and used to running one OS will ALWAYS have trouble using one that is not what they are used to. I am used to Windows 98 and to a lesser degree Windows 2000 Explorer - I find Windows XP Explorer to be confusing with its moving screens and whatnot. In fact, I'm used to using PowerDesk on Windows 98 and 2000 - not Explorer at all, so I find Explorer confusing to use on any version of Windows.

    But I CAN learn to use any OS given a certain amount of time playing with it. So can any reasonably intelligent user. And that does not necessarily translate into training expense, either - especially since most corporate "training" is a fucking joke. You don't want to spend money training people to use Linux? Don't bother training them. Just give them the product and tell them to learn to use it. Maybe give them just enough training to point out the differences. Then sit back and stop worrying about a couple months of 15% less productivity - you'll get it back later when you don't need to pay the Microsoft licenses and retrain everyone every X years for a new version of Windows that screws with the eye candy just to be an "upgrade".

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  26. Nat == Former Microsoft employee by Anonymous Coward · · Score: 3, Interesting

    Funny but true!
    Miguel and Nat both met at Microsoft for the first time. Nat was an intern working on IIS and Miguel was interviewing for a job.

    See here on Miguels own site: http://primates.ximian.com/~miguel/ and check the Ximian history page