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!"

78 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
    1. Re:OOoo, first post! by Esion+Modnar · · Score: 2, Funny
      ...dipping their feet into the Linux desktop

      You would probably get electrocuted doing that. Licensed metaphor mixologist.

      Seriously though, the Linux desktop will be ready when the average user never has to know all the gritty details of the mount command.

      --

      They say the first thing to go is your penis. Well, it's either that or your brain. I forget which...
  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.

    9. Re:We need a new toolkit... by evvk · · Score: 2, Insightful

      We don't need yet another new WIMP toolkit. We need to totally abstract the UI to give the user more freedom, and to separate UI from functionality. See e.g. http://iki.fi/tuomov/vis/ for some ideas.

    10. Re:We need a new toolkit... by Muggins+the+Mad · · Score: 2, Insightful

      > 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.

      Personally I'm glad they do.

      Otherwise we'd be stuck with the visual appeal of Athena and the efficiency of Motif.

      Today's QT is yesterdays Tk.

      Yes the cost of rapid improvement seems to be UI inconsistency. To me that's worth the price.

      - MugginsM

    11. Re:We need a new toolkit... by chewmanfoo · · Score: 2, Informative

      I've been coding in Qt about as long as I've been coding in Java. If you think Qt is a beautiful API, you really gotta get out more.
      Java from Sun is much better.

      Try netbeans!

  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.

    1. Re:quite simply ... by dbIII · · Score: 2, Interesting
      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.
      Win4lin still has a place. All those old win98 licences are now worth something for all those little things that linux and breeds of NT will not run.
      personally, i'm waiting for the linux desktop that comes loaded with enlightenment
      Mandrake.
      and all things audio editing
      Snd has been around for many years, while ecasound is there if you want to do complicated mixing or filtering in batches.
      and every funky/odd thing that was available in the rh7.3 stage of development
      The code is still out there, even if the projects are not in development. If they won't run or compile on your current setup there are relatively simple ways to install the old libraries they depend upon - linux does not suffer from DLL hell, you can have a few versions of the same library on the same system, since they are named by version number.
  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 bersl2 · · Score: 2, Funny

      That cannot be what he meant to say. It contradicts what was said in the summary.

      Of course, maybe if I just RTFA...

    3. 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. Young by agm · · Score: 2, Funny

    Is it just me or is the world of developers getting younger? No offense to Nat but it looks like he'd have trouble getting into an R16 movie.

  7. 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.
  8. No mention of Mono by GnuVince · · Score: 2, Interesting

    He doesn't talk about how Fortune 1000 see the Mono initiative, that would be interesting.

  9. 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!"
    1. Re:Ximian Bails Out by miguel · · Score: 2, Informative

      I remember that particular case, because I had the
      marketing people calling me on the office.

      What happened is that someone had scheduled Nat
      without letting Nat or his assistant know about
      this particular trip, someone forgot to follow
      up and Nat was in Boston when that happened.

      Miguel.

  10. The BIG Migration is coming...soon. by qualico · · Score: 2, Interesting

    "We're developing a Windows migration program to make it easier to move to the Linux desktop with training and documentation and migration tools that automate tasks"

    Migration Tool #1: fdisk - delete Windowz partition.

    Sinicism aside, it would expedite things if Linux had an emulation package that supported a greater number of Windowz appz. Wine and Win4Lin just don't seem to cut it.

    Novell is being very smart by aligning its business model with Linux.
    Although, I hope they don't UnixWare it to SCO this time.

    Time for some of the major apps to start porting over.

    Adobe and Macromedia Petition for Linux
    http://www.petitiononline.com/adMaLin/petit ion-sig n.html
    (Take out the space after the dash, Slashdot has a bug sometimes in "Plain Old Text" posting of html items that wrap)

    I'm *not* much of an Adobe fan though.
    They make bad software IMO, save for the satisfactory Photoshop CS.

    Macromedia is good but could be better.
    They are supposedly going to begin testing on Linux.
    http://news.com.com/2100-7344-5170061.html

    Starry Night Pro would be great on Linux.
    At least there are some good freebies for now like KStars.

    Applications may start to take the Web route also.
    Accounting for example.
    I'd love to pair up with some geeks on here to start up a company to develop a full web based accounting system in LAMP, seriously lacking in the Linux community.

    Also, hardware vendors are going to have to jump on the bandwagon in bigger numbers.
    Otherwise, we are going to have to wait for all those legacy scanners, printers cameras and other accessories to expire before typical users take the plunge.

    So that just leaves games.
    Well DirectX is not something I see on Linux in the near future.
    Regardless, businesses thinking to migrate won't shed a tear because Barbie Pet Rescue can't be installed.

    In summary, the big migration is coming.
    The challenge will be converting those tight ass business folk clinging to win 3.11/95/98/ME because they don't want to move forward or rub two nickels together.
    Same problem that plagues Micro$oft to this day.

  11. 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...
  12. Re:huh? by zymurgyboy · · Score: 2, Funny

    They're trying to use the Linux desktop with their feet??? Maybe that's why it's not working for anyone yet.

    --
    If you never make mistakes, it's probably because you're not doing anything.
  13. 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.
  14. 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...

    1. Re:Can desktop linux ever be sold? by killjoe · · Score: 2, Insightful

      Novell is unique in that they have excellent add ons. Groupwise and edirectory are peerless in linux.

      They can sell you a desktop system with full groupware capability and centralized management. I don't think anybody else (not even IBM) can do that.

      --
      evil is as evil does
    2. Re:Can desktop linux ever be sold? by _Sprocket_ · · Score: 2, Insightful


      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?


      Oddly enough, you seem to be describing the exact same methods and challenges facing proprietary software. Let's compare....


      - Pay-per-seat? No way, the GPL lets you get undercut by "Free" if you do that.


      Some elements of proprietary software certainly uses "per-seat" licensing. Niche software producers will certainly see per-seat licensing as its main income. However, those who sell OS' tend to play fast and loose with the value of a seat. Microsoft sells boxes - but the big deals are Enterprise and OEM licenses. Apple sells upgrades but OSX is really more about pushing their hardware. And, of course, companies like IBM and Sun use their OS as a hook to sell hardware.

      The per-seat license is certainly common enough in proprietary software. But when it comes to a desktop OS, it isn't the money-maker it might appear to be.


      - 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.


      I'm amazed that you discount this so quickly. Every piece of hardware and software I've ever deployed in an enterprise involves support. In some cases, we accept a greater level of support ourselves. However, even as we pick out the most promising technology, anything with a commercial backer has some kind of support attached to the purchase order. Even when it's easy to use.

      Microsoft does a fairly brisk business in support contracts. And, of course, the basis of IBM's Linux interest is that they make their money pushing hardware and, to a major extent, selling service.

      Another point that you discounted early was the "tied to your mothership for patches" model. That is another support model. Enter RedHat. They aren't selling software, they're selling support. You can get all their software without a fee. However, you will either have to find your own sources for RPM updates or build your own.


      - Selling-add-ons? That's a risky play, not likely to cash-in.


      Yes, this is a risky model. But it is also very common with proprietary software. There are plenty of products that offer a base at a very reasonable rate, or even without a fee, and additional functionality that can be purchased through modules, other products, etc.

      Sure - your overall message is spot on. But it can be applied to any business in the IT industry. It is not all that unique to Linux vendors.
  15. 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.

  16. 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.

  17. 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.
  18. 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...

  19. 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.
  20. 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 abigor · · Score: 2, Insightful

      Really? Try running an X app over dial-up, or even DSL. MS's RDP can do it, and do it well. How come X can't? Because X is bandwidth hungry. For a LAN it's okay, I guess. Add to this the other problems the grandparent post mentions, and you'll quickly realise its time has come.

      If there are other ways to do the same job better, shouldn't they be explored? Assuming that X is some perfect protocol is just stupid.

    3. 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?
    4. 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...
    5. 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?
    6. 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.

    7. 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.
    8. Re:X works just fine thank you by Khelder · · Score: 2, Interesting

      I agree that the networking demands of X are often overblown, but I don't understand what you mean by running 150 desktops off a single server. The X server is what runs on the desktop machine; it's what draws the graphics and gets the raw keyboard & mouse events. Do you mean you have 150 desktops running X servers that all use a single server box to run applications (i.e., X clients) on?

      (Yeah, the X terminology can be confusing since in X-speak the server runs on the desktop, not in the back room, but we're stuck with it.)

    9. Re:X works just fine thank you by Edulix · · Score: 2, Interesting

      Hey harikiri, I've got a solution for your X problems: NoMachine/NX. You can see their details in their webpage where they explain them very well.

      A story about it have already been posted in Slashdot and I've tried it myself with their testdrive, where they allow you to connect to a test NX server.

      The core of the app is open source and you can use it freely, but their helper apps are closed source. But this is a problem being solved just now, because KDE is going to ship NX server and client support in the near future. In fact, it seems that they closed their config helper apps because it was a need for them, but they want to develop open source software.

      PD: I apologise my bad english.

  21. What is so strange... by Anonymous Coward · · Score: 3, Funny

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

  22. 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
  23. 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!"
  24. Re:Linux will take-off... by imroy · · Score: 2, Interesting
    ... as soon as it is as "easy" and "intuitive" to use as Windows.

    It's appropriate that you put quote marks around "easy" and "intuitive" because Windows really isn't as easy or intuitive as most people think. It's just that most people haven't used (or even know of) anything else. If anyone has problems, they can usually find someone else that can help them with Windows or can at least sympathize with them (most computer-illiterates will blame themselves rather than MS or Windows). Then you have the business types that reason Microsoft must make better software than everyone else simply because they make the most money.

    The nipple is intuitive, everything else is learned
  25. 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.

  26. Re:Basics tasks & understanding of the UI (on by Anonymous Coward · · Score: 2, Insightful

    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.

    That doesn't make any sense at all! Sending email and surfing a web page are tasks one does through an application. You don't send an email using Windows or Linux, you send it using Outlook, Mozilla, Eudora, etc. Whoever tries to judge the usability of an entire OS by throwing around test results for unnamed applications is a total moron.

  27. 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

  28. Re:No thanks by justins · · Score: 2, Funny

    Hey man, it was a school night!

    --
    Now before I get modded down, I be to remind whoever might read this that what I am saying is FACT. - bogaboga
  29. 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
    1. Re:I guess you've never used Mandrake Linux, then? by Master+of+Transhuman · · Score: 2, Insightful


      K3B is a CD burner program.

      The other has me stumped, too.

      It would be nice - but boring, too - if OSS used some sort of rational, boring, corporate software names instead of hacker handles to name software.

      Although not everyone gets "Nero Burning ROM" either, you know.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
    2. Re:I guess you've never used Mandrake Linux, then? by jsprat · · Score: 2, Informative
      SWMBO is "She Who Must Be Obeyed"


      You must not be married ;)

    3. Re:I guess you've never used Mandrake Linux, then? by spacecowboy420 · · Score: 2, Funny

      Oh! Here in the city it is: BBHMM

      For:
      Bitch Better Have My Money

      It's a joke mods

      --
      ymmv
  30. Can someone remind me by bigberk · · Score: 2, Insightful

    Please remind me, what major benefit does it bring us (the Linux community) if there are big companies involved with Linux? Seems to me we did a pretty good job with hobby programmers and academics for a long time... of course IBM did help, oops but then there's that SCO crap... but what I'm getting at is, why do we need to impress anyone?

    1. Re:Can someone remind me by da+cog · · Score: 2, Insightful

      Two words: network effect. One of the main reasons that most people use Windows is because most people use Windows, since as a result most (Desktop) hardware and software is made for Windows machines, with Linux etc. maybe, maybe supported as an after-thought.

      It would be really nice if I could just get rid of the copy of Windows I have on my hard drive, but the fact is that I cannot because there are many programs and some pieces of hardware I have that will only work in Windows. The only way to escape this is for software and hardware makers to have motivation to make sure that Linux is supported, and the only way this will happen is if they will lose significant sales if they do not support Linux.

      Thus, the reason we want big companies to support Linux is because it encourages others to make sure that their hardware/software supports Linux, which in turn makes Linux attractive to more people, which in turn gets us better hardware/software support, etc. In other words, maybe we could finally get the network effect working in our favor.

      --
      Snarkiness is inversely proportional to wisdom because it emphasizes feeling right rather than being right.
    2. Re:Can someone remind me by _Sprocket_ · · Score: 2, Insightful


      Please remind me, what major benefit does it bring us (the Linux community) if there are big companies involved with Linux?


      Today I came home from work and relaxed with a bit of Neverwinter Nights and Enemy Territory. Sometimes I'll play Unreal Tournament 2004 but I cut my goofing-off short. I connected to my work's employee VPN server, downloaded some documents I've been working on, and began hashing out some work that's been sneaking up on me this week. Did some system configuration at work. Uploaded my modifications. Called it a night.

      This all from my Linux-only home workstation.

      I would not have been able to do all this if there wasn't corporate interest in Linux.
  31. 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...
    1. Re:On package management by Master+of+Transhuman · · Score: 2, Insightful

      > In the end he threw up his hands in disgust and
      > stopped working on his new Linux box.

      I've done that too several times on my Red Hat 7.3 system. Tried installing K3b because the version of KonCD on 7.3 was crap. Couldn't install K3b due to various issues.

      Well, I can easily upgrade to a more recent distro - I HAVE Mandrake 9.2, Fedora Core I, etc. But I want to upgrade my 7.3 slowly to current so I get the experience doing it.

      So while I was booting one of my various live CD's the other day, I used the fully installed K3b on the CD to backup my system - neat as a pin.

      Old Linux is crap. Windows is crap. New Linux is crap - just less crap.

      More important, Linux is FREE crap - so I'm not getting reamed financially as well as spiritually dealing with this crap.

      There is NO software that "just works" - no matter what Mac people claim. We just have to deal with it until there is.

      I spent the day trying to compile an Oracle Forms app - the stupid product would compile it, tell me it was compiled, THEN NOT SAVE IT ANYWHERE THAT I COULD FIND IT! And not only that, NOWHERE in the product can you set a path for the destination of the compiled app! Fucking unbelievable!

      Oracle Forms has a couple 500-page books to explain it - and NOWHERE does it tell you where the compiled app goes. It SHOULD logically go in the same directory where the source form is - well, it didn't.

      Tell me Windows software is easier to use. Go on, tell me.

      Hardware is crap. Software is crap. In the immortal words of the Twentieth Century's greatest philosopher, Woody Allen, who summed up the human condition in five words: "Nothing works and nobody cares."

      Complaining about Linux usability is truly laughable.

      NONE OF IT IS USABLE. Ted Nelson said at a West Coast Computer Faire many years ago that there was NO acceptable software on the market. He meant it dead seriously and he was totally right. And he is still right today.

      But again, at least Linux is cheap or free.

      How a corporation can suggest that it would be more expensive to use Linux crap than Windows crap is just laughable.

      If that corporation is worried about training costs outweighing license savings, I submit they should be worrying about stupid corporate practices outweighing both of them.

      But then, I suppose stupid corporate practices has to be taken as an environmental given, not subject to change or improvement.

      In which case, why bother whether Linux is ever taken up by them? It simply won't be no matter what the OSS community does. Even if we develop Hal 9000 in OSS, the corps still won't get it.

      Let them eat Windows - and choke on it.

      --
      Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  32. 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

  33. Re:National lab? by andalay · · Score: 2, Funny

    Their stupid Exchange connector broke down and he didn't get the pop-up for the meeting from Evolution. Should have used Outlook

    Bill Gates

  34. 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!
  35. Re:Basics tasks & understanding of the UI (on by Master+of+Transhuman · · Score: 2, Insightful


    Nobody "uses a total OS" - you use applications that are built on top of an OS.

    Only when you have to CONFIGURE the OS - for hardware or software installation or user maintenance or some other ADMINISTRATIVE task - or when the OS PERFORMANCE is an issue - do you need to worry about an OS's "usability".

    Since UNIX still runs most of the world's servers, I'd say it's still an open issue as to which OS is more usable FOR ADMINISTRATORS.

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!
  36. 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

  37. Re:Linux will take-off... by Paul+Jakma · · Score: 2, Informative

    Roaming user profiles controled by logons is also something that Windows does well but Linux doesn't do out of the box.

    RedHat Linux (and hence now Fedora) have done this out of the box for *ages*. Run authconfig and you are given a choice of several Network directory systems to use for account information (NIS, LDAP and/or Hesiod), and a choice of several authentication services (LDAP, Kerberos and even SMB). Then run autofs to automatically pick up the appropriate network volumes..

    All of this presumes you actually have some kind of directory service in place, which is not trivial to setup be it on windows or unix. On unix one might use the 'directory administrator' GTK LDAP tool to manage user accounts, or the more level (but still graphical and user-friendly) 'gq' GTK LDAP frontend. There used to be a nice GTK kadmin app included with GNOME 1.2 or so, to administer Kerberos, but it appears defunct and dead. (the command line kadmin still works obviously, and can be run from anywhere, kadmin has its own network protocol).

    I regularly use a large, global, corporate Unix network. No matter where I go on this network (ie access it from), I can always just sit in front of any arbitrary computer and just login. My home directory and my files are always there, so my browser's config and bookmarks are there, my email client's config files are there, the config files for my desktop are there, my custom background is there, etc.. I log in and its all just there, as it always is and just works the same no matter where I am. Wherever I lay my hat, my /home is already there. (the only downside is that being far from home can mean slightly slow NFS access, but its fine for running a GNOME desktop from, it's more noticeable from the shell.).

    I have never seen or even heard of any decently sized Windows network having such transparent and wide-ranging roaming support for its users. Indeed, I suspect the reason windows requires this intricate "roaming user profiles" support and such is because of its idiocy in not confining users to a "home directory".

    Anyway, I suspect you never actually have seen a large corporate network, never mind a large Unix or heterogenous network. If ever you do, you'll probably find Linux (and solaris, and IRIX, and ..., but not Windows) does "do it" out of the box, with just a quick twiddle of the RedHat (or other) GUI configuration tool or, for lots of installs, with a few lines in a kickstart config.

    The difficult part is, by far, in setting up and administering the infrastructure required, not the clients, unless the clients are Windows.

    --
    I use Friend/Foe + mod-point modifiers as a karma/reputation system.
  38. Hmmm..... by SerpentMage · · Score: 2, Interesting

    Interesting that you mention this. I do not know whether to believe you or not. So lets say I am going to give you the benefit of the doubt.

    The reason why I mention this is because I had the same thing happen to me with Netscape. In 1996 when Netscape held their first conference I was blown off by Netscape. We wanted to initally buy about 4000 client licenses. In the end what happened was that we were too small for their tastes (I was working for a major Swiss Bank at that time).

    While attending their conference I saw that Netscape's days were numbered. BTW the meeting blow off happened after the conference. I could not exactly put a finger on it, but the buzz at the Netscape conference seemed wrong.

    Tying this back to Ximian leads to me believe that maybe this is "Netscape" all over again. Hmmm.... Interesting, not sure, something to think about no doubt...

    --

    "You can't make a race horse of a pig"
    "No," said Samuel, "but you can make very fast pig"
  39. Critical mass in germany by Qbertino · · Score: 2, Interesting

    My predictions for Linux reaching critical mass in germany haven't changed. Right now it'd be roughly another 12 months for it to happen. And I still _do_ expect germany to be the first. I'm starting to meet more people somehow involved in Linux than I can count.
    Once Linux is rolling in that direction I also expect things to go very fast. Remember how fast Windows95 gained critical mass when all of us were saying 'Who the heck needs an OS that uses 50 MB of diskspace?' and 'Gee, look at Geos on PTS DOS, this is the future of PC operating systems'.

    --
    We suffer more in our imagination than in reality. - Seneca
  40. Compression adds latency by Moderation+abuser · · Score: 2, Informative

    Most X performance is about latency rather than bandwidth. If you're on a LAN, straight X is a much nicer proposition than the compressed protocols because the latency is lower, imperceptible even.

    So, if you're running it over a high latency link like ADSL or god forbid a modem then go for it with the protcol compressors.

    --
    Government of the people, by corporate executives, for corporate profits.
  41. Latency, not bandwidth. by Moderation+abuser · · Score: 2, Interesting

    The perception of the performance of any GUI depends on the *latency* of the GUI. If you compare X with RDP, X has a significantly better latency response than RDP does so when there is sufficient bandwidth it is a faster option than RDP.

    The bandwidth required to run X is cheap. It was designed for shared 10Mbps local area networks and on today's 100mbps switched networks it absolutely flies. I run several hundred engineers using full screen Gnome (yes, that was a mistake) X sessions on a couple of login servers and the burst rate doesn't flatten the interfaces even when they log in. It peaks at around 4Mbps for a few seconds during login and then dies off to bugger all. It doesn't get anywhere near 10mbps, never mind 100mbps or 1000mpbs.

    The "run it over a modem" set is a very limited subset of the population who use remote GUIs. The vast majority of people who use X and RDP, do so over a local area network. So the statement that X must be replaced because it doesn't run on a 300 baud modem (or whatever) is bullshit. Especially when there are protocol compressors which you can plug into the architecture to improve low bandwidth performance (at the expense of interactive latency BTW).

    --
    Government of the people, by corporate executives, for corporate profits.
  42. Re:compatibility / applications / installation by Dot.Com.CEO · · Score: 2, Interesting
    I have been reading most of your posts in this discussion and let me say this: you haven't got a clue what being a user means. I shall analyse my position:

    1. Hardware WORKS in windows. You download the driver, doubleclick, next, next, finish, reboot, it works. Full stop. Now compare to linux. Download driver. rpm -Uvh *.rpm, perhaps a --force in there, notice the errors because the bin package is not compatible with your distro. Download tgz. Make, make install. depmod, vim modules.conf. Reboot. Pray. It works UNLESS you upgrade your kernel (and have suse). Now THAT is a good user experience. I cannot understand how you can say Linux is superior in this matter, but anyway... And don't you dare say apt-get or emerge are superior. They are not. Once you go outside the approved .deb or whatever depositories, you are treading on dangerous ground. And you WILL need to go there if you want multimedia support.

    2. "Look, there is plenty of downloaded Windows software that fucks up when you install it."... Big huge hairy bollocks. Unless you are doing something really wrong like messing with the registry or installing seriously buggy applications it's not really normal that something like that happens. For the normal user who has 10-20 apps installed and doesn't install/uninstall things, it just works. How about when you do a rpm -i --force (which you HAVE to do sometimes) and it just completely fucks up your system? Oh, I'm sorry, it really is my fault, I shouldn't have "forced" the installation.

    3. "The only problem Linux has that is significant is when new hardware needs to be installed that is not directly supported by the kernel and for which there are no drivers. The solution? Don't buy that hardware". Really? So I should buy what I consider an inferior and overpriced nvidia card rather than an ati for playing games in my Windows partition because nvidia drivers are easier to install? Or I should buy a via mobo rather than a nforce one because via nic drivers are pre-compiled in the kernel? Do you think that hardware companies do not support Linux as well as windows because there are more windows users out there than Linux users and it doesn't make economic sense? No. They don't support Linux as much because the linux userbase is fragmented as hell and there is no "Linux Driver Model". They develop one driver for Windows and they package, I don't know, 5 plus a src.tgz for Linux. Whose fault is that? Is it the Microsoft monopoly or the pigheaded Linux developers that have been resisting the push to standardised binary kernel modules?

    4. People want stuff that is standard, user-friendly and just work. Standard, contrary to /.'s opinion does not mean "approved by an international standards body". It's what everyone uses. Can oo or staroffice or hancomoffice or kwhatever open the excel-macro-ridden xls documents I use at work? No? Can I open, manipulate .psd files in a color-calibrated environment? No? Then, my dear friend Linux is not ready, full stop, however much you might think that Linux is a superior solution to Windows - which it isn't, it's a different, more elegant philosophy. Accept it.

    Linux has its places. It's my desktop, it's your desktop but it is NOT grandma's desktop. If you make people choose whether to use a free OS that would make them work twice as hard or even 10% as hard or to spend 100 euros and use a troublefree and standard OS, guess what they would choose. Why do I use Linux? I like the challenge. Not everyone does. And I STILL use Windows for the things that are impossible to do in Linux.

    So please kindly stop trolling your uninformed views, it gets truly annoying to see such blatant zealotry even in a forum as unbalanced as slashdot is.

    --
    Mother is the best bet and don't let Satan draw you too fast.
  43. Re:Basics tasks & understanding of the UI (on by GooTi · · Score: 2, Insightful

    ...and it runs on fast machines.

    That's the easy part. The difficult part is to scale down.

  44. Re:-(-(-(-(1)))) by Trogre · · Score: 2, Funny

    I couldn't possibly fail to disagree with you less.

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife