Slashdot Mirror


Eric Raymond: Why Open Source will Rule

DNapalm writes "A very interesting two part interview with Raymond from ZDNet, talking about the success of open source and Linux on the desktop, among other things. Check out Part I and Part II (I liked part II)." Raymond also asserts that Microsoft could have killed Linux if only they'd started a little earlier.

32 of 404 comments (clear)

  1. One thing I don't understand by LordOfYourPants · · Score: 5, Insightful

    A direct quote from the article:

    "If OpenOffice still exists, and it's GPLed, and they're going to start charging for StarOffice, then they just shot StarOffice through the head."

    Replace the word "StarOffice" with "Redhat Linux".. why does the same logic not apply?

    1. Re:One thing I don't understand by GrenDel+Fuego · · Score: 4, Insightful

      "In case you haven't noticed, RedHat already charges for the boxed version of their linux distro. You can still get the .ISO's from their download sites."

      I believe this is his point.

      "If OpenOffice (Freely downloadable redhat) still exists, and it's GPLed, and they're going to start charging for StarOffice (Purchased Redhat), then they just shot StarOffice (Purchased Redhat) through the head."

      Of course I don't quite believe in either of these statements because corporations generally prefer to license software for the better support.

      And in Redhat's case, you have redhat users who want to suppor the company that makes good software, and supports a lot of open source developers.

  2. What's the next step? by IamTheRealMike · · Score: 3, Interesting
    Mod this as Offtopic if you like, but I've been wondering lately what happens "after" linux. As an OS it's clearly on a roll, and is heading for even greater things, but it's still based on a design that is 20 years old.

    I can't help thinking - would it be possible to do it again? But this time, instead of basing it on the solid, well known but old and unadventerous unix, use new ideas, incorporate the latest technologies and so on. Would the open source community be willing to move away from Linux to this new open OS, or is the momentum behind it too strong to abandon?

    1. Re:What's the next step? by linzeal · · Score: 3, Informative

      You mean like plan9?

    2. Re:What's the next step? by Pussy+Is+Money · · Score: 3, Insightful

      There are no new ideas in computing. Anybody who tries to sell you a "new idea" in computing is a gasbag who is either a) blissfully ignorant or b) willfully ignorant.

      --
      Pushin' 'n dealin', shovin' 'n stealin'
    3. Re:What's the next step? by jd142 · · Score: 4, Interesting

      Actually, the filesystem as database, which has been around for a while, see beos, has the potential to be very big. That doesn't mean you wouldn't have to be able to use some of the same *nix tools and pipes, just that there would be more information available to describe a file.

      It would be nice to have the following types of information associated with a file as part of the file system, for example:

      --crc or md5 info to tell when a file was corrupt
      --detailed information about what executable should be used as the default to open the file
      --more detailed permissions, like in netware, as opposed to *nix very basic rwx
      --rollback features (think something along the lines of netware's salvage feature, a feature yet to be implemented in *nix or windows to the degree it is in netware
      --detailed information about files that access data in the file. For linked objects, for example, to know that when I change *this* graphic, it means that *that* document will be changed
      --user customization. If the file system is a database, why can't I make a table with new attributes that I want to track and use the filesystem's unique id for the file as a foreign key?

      Sure, some of these features are implemented to a greater or lesser extent by programs today, but they are program specific, not built at the file system level and not as expandable.

      Just some thoughts off the top of my head.

  3. One thing I never really understood... by dnaumov · · Score: 4, Insightful

    is why do the OSS and FSF people care so much for the "Windows world". During the last several months, I've seen an enormous amount of articles that deal with how evil Microsoft is when compared to Linux developers and vise-versa. I ask these writers: "Why ?" Why should I care ? I really don't think we're gaining anything by doing the same things MS has been doing all these years. It always goes on like this: "MS attacks, OSS movement responds, MS attacks, OSS movement responds, OSS movement attacks, MS responds". This is getting boring you know, why not make deeds instead of shouting ?

    OK, sure, Windows is installed on the majority of the computers out there, but it doesn't make it world's most important thing. Britney Spears and the Backstreet Boys are popular too, are they important to me ? Nope.

    1. Re:One thing I never really understood... by fanatic · · Score: 5, Insightful
      If microsoft didn't do so many thngs to deny co-exisitence to competing views of OS and applications, it would be a much smaller issue. But they:
      • deny OEMs the right to package other OS's or else invoke per-CPU licensing to artificially increase the cost of doing so
      • Make gratuitous changes to protocols, APIs and file formats that hurt their own users as much as the competition
      • engage in ethically questionable diddling with the legal system (see their role in UCITA for the most gross example)
      • engange in other anti-competitive practices as laid out in US v. Microsoft
      • try to use bizarre licencing to sow FUD upon Open Sourece and Free software
      • lie everytime their lips move when discussing Open Source and Free software

      This war is brought about by MS's actions, not ours. They have adopted a search and destroy approach.
      --
      "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
  4. Re:Not in the world of science it won't by IamTheRealMike · · Score: 5, Insightful
    That's why I choose Microsoft Windows(TM) for my computing work.

    LOL! This is a troll right? I'll bite. Maybe you have a point and Windows is right for you, but maybe you work for Microsoft, as they are the only people I ever see who write Windows(tm). You sound like you just walked out of a TV advert!

    That's why I choose Microsoft Windows(TM) for my computing work. The easy setup and configuration let me get right to work and the cross-platform standardizations let me easily port my work for colleagues. Furthermore, the highly-optimized nature of the Windows(TM) Operating System Kernel makes for blazingly fast simulation runs even on the low-end hardware that my University is willing to pay for.

    What cross platform standarisations? I don't see any. In fact, I'll think you'll find that EVERY major OS out there other than windows is based on unix.

    Sheesh, I'm way too easily trolled. -sigh-

  5. Linux is *not* a disruptive technology by AdamBa · · Score: 5, Insightful
    The constant repetition of this annoys me. I see why people do it, since in the classic disruptive technology battle, the disruptive technology (Linux) overtakes the existing technology (Windows) and Bill Gates cries a lot.

    Unfortunately in every aspect *except* price, Linux looks more like a sustaining technology vis-a-vis Windows. Linux is the more secure, more high-end, more niche-like product. In the disruptive technology model, what happens is that *Windows* becomes reliable "enough" and hacker-pleasing "enough" and takes over from Linux.

    Now Linux is free...that is true. But that is the only way it is like a disruptive technology. In fact that is not really like disruptive technologies either. They are usually cheaper. Free is strange.

    Now Linux is indeed a disruptive technology compared to something else -- Sun. Linux on a PC, compared to Sun on a Sun box, has all the classic hallmarks of disruptive technology, and in fact is doing so.

    I ranted more about this last year on another site. Here's a quote: "To take this to an extreme example, at some future date Windows CE might displace both Windows 2000 and Linux, and the Personal Web Server shipped with Windows might displace both Internet Information Server and Apache. This is highly unlikely, but it illustrates the direction in which disruption happens.".

    And don't forget this profound comment where I ask the question ""Is the bazaar upmarket from the cathedral?" (read that again).

    - adam

    1. Re:Linux is *not* a disruptive technology by zulux · · Score: 4, Insightful

      Agreed..

      Linux is not a disruptive technology.

      the GPL is a disruptice technology.

      Microsoft can't compete with the GPL by buying it. If they try to copy the GPL, then they kill off their legacy business in a week. MS(Hard), MS>Rock .

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

  6. Re:Hindsight is 20/20 by dkleinsc · · Score: 4, Funny

    Excerpts from the 'fall of Redmond' radio conversations:

    "Red Hat, this is Yellow Dog. Come in.'
    "Red Hat here. We've gotten Balmer. I repeat, we have Balmer in custody."
    "Mandrake says Gates isn't here today. Debian, can you clear out the marketing department please?"
    "Roger that, General Raymond. Attacking marketing immediately."
    "Suse reporting that legal has been secured."
    ...
    "Who the hell is that?"
    "Looks like the FSF showed up. For once them and OSI agree on something."
    "Hi there, Stallman. Raymond here. What are you boys doing here?"
    "We came to download the source code for all the MS software to look for GPL violations."
    "Good thinking. I have Slackware in there now, and I'll let em know your coming."
    ...

    and so on and so forth. Maybe I'll write a more detailed version one day.

    "The normal channeling of aggressive instincts into acts of senseless violence."

    --
    I am officially gone from /. Long live http://www.soylentnews.com/
  7. Re:Not in *YOUR* world of science it won't by jgardn · · Score: 4, Insightful

    Humm, I tried to use Word to write equations when I was in college studying Physics. Even though I had no exposure to Linux at the time, I found that most of the professors and grad students used LaTeX instead. It's much easier to use, and it's much easier to learn. I picked up most of it in an afternoon. It's also pretty much standard for Physics people to write papers full of equations in LaTeX and not word.

    And as for the "blazingly fast simulations" - I'm sorry, we never ran simulations on Intel based computers (too slow except for really easy stuff). We'd use mainframes for that, which used Unix. And what kind of University that is considering doing real physics can't afford that? Are you sure it wasn't a community college? And if you're curious, the University doesn't buy the computers for the physicists - the physicists get grant money from the government for that kind of purchase.

    You wouldn't happen to be paid by MS to make such a false statement? I have been seeing a lot of these nutcases making wild claims that are absolutely false and full of crap. (Do you REALLY love Linux? haha! I caught you!)

    Jonathan

    --
    The radical sect of Islam would either see you dead or "reverted" to Islam.
  8. ESR's Flaw by VAXman · · Score: 5, Interesting

    ESR's fundamental argument to Linux taking over the desktop is solely cost. Because the cost of Windows will be a bigger chunk of the PC price as PC prices, OEM's will seek out cheaper options (e.g. Linux).

    I believe this is wrong for at least two reasons:

    1. Microsoft has a much freer pricing structure than most other component makers. Since they employ monopoly pricing they are able to price the product exactly at the point where it maximizes profit. Futher, since their marginal cost is essentially zero (as opposed to chips, disks, and other hardware components), they have a lot of downward headroom in their prices should this ever become an issue.

    2. There is little evidence that cheaper wins out. A classic example is the IBM PC (and clones) which were substantially more expensive than home PC's (such as C64, Atari 400/800, Apple II, etc.) but won over the market big time. There are many factors other than cost which contribute to the success or failure of a computer product. Indeed, very cheap computers (e.g. $350 or so) computers are available today, but the sweetspot seems to be the $800-level machine which will get you something pretty good.

    1. Re:ESR's Flaw by dgroskind · · Score: 4, Insightful

      There are many factors other than cost which contribute to the success or failure of a computer product...

      These factors include:

      • Compatibility and interoperability
      • Stability of vendor
      • Amount of ongoing development
      • Feature set
      • Marketshare and userbase
      • Adherence to standards
      • Ease of use
      • Security
      • Stability
      Microsoft is credible in all these areas and ahead of open source contenders in most. In addition, Microsoft is getting better in all these areas.

      The time when open source products had some advantage because of Microsoft's weakness in security and stability is limited.

      Even people like me who are simply put off by the idea of proprietary systems are having second thoughts after looking at the feature set of IE and the size of its userbase.

  9. WTF? by imac.usr · · Score: 4, Insightful

    I think Linux will take over the desktop, and I think the reason it will doesn't have much to do with whether we clean up and polish our interfaces or not. Linux will take over the desktop because as the price of desktop machines drops, the Microsoft tax represents a larger and larger piece of OEM margin. There's going to come a point at which that's not sustainable, and at which OEMs have to bail out of the Microsoft camp in order to continue making any money at all. At that point, Linux wins even if the UI sucks.

    And frankly, the UI doesn't suck. It's not perfect, it's got a few sharp edges and a few spikes on it, but so does Windows.


    Oh dear god, this is the funniest thing I've read on slashdot in six months. So no matter how bad a computer interface is, all it has to do is cost less than Windows for everybody to adopt it? Well, hell, I'd better dust off my Apple II then!

    --
    I use Macs for work, Linux for education, and Windows for cardplaying.
  10. Re:Not in the world of science it won't by gilroy · · Score: 4, Informative
    Blockquoth the poster:

    non-standard packages like LaTeX and gnuplot

    Well, another one zapped by the Microsoft machine. In their context, LaTeX and gnuplot are the standard. Ever wonder why the Los Alomos preprint server offers the papers in that format?
  11. "Killed" Linux? by PeterClark · · Score: 3, Insightful
    I'm sorry, but Eric seems to be inhaling too much gunpowder these days. He, better than anyone, ought to realize that you can't "kill" FS/OSS. Furthermore, his argument is that if Microsoft had started its FUD campaign back in 1998, no one would have bought into Linux. This is similar to charging Microsoft with failure to have a crystal ball. Back in 1998, Linux was barely a blip on anyone's radar. I've been using Linux exclusively since Feb. 1999, and I speak from experience when I say that MS had nothing to fear then. Furthermore, even if someone in MS had a premonition, it would have been an absolutely stupid blunder to start FUDing Linux. Think about it; were MS to have attacked Linux at that point, interest would have only gone up. There's no such thing as bad advertizing.


    :Peter

    1. Re:"Killed" Linux? by llywrch · · Score: 3, Informative

      > Furthermore, his argument is that if Microsoft had started its FUD campaign back in 1998, no one would
      > have bought into Linux. This is similar to charging Microsoft with failure to have a crystal ball. Back in 1998, Linux was
      > barely a blip on anyone's radar.

      Actually, Linux was on a number of radars. A lot of ISPs (predominantly mom-&-pop shops with little spare cash) were using Linux (& *BSD) for their servers because they couldn't afford Win NT.

      And knowledge of some of this usage must have filtered back to Redmond. Remember, the infamous Halloween Papers (which were published in 1998) were written in August of 1998 after careful study of how Linux & Apache are written.

      What is more cripling for Eric Raymond's argument that MS could have FUDed Linux to death is that these memos clearly state that FUD will NOT work against Open Source Software. I don't understand is why Raymond didn't remember this assertion: after all, he published the original documents.

      Geoff

      --
      I think I see a trend here. Maybe for them it really would be easier to muzzle the entire internet than to produce p
  12. Bad programming by Mobutu · · Score: 3, Insightful

    from the article :"This is necessary because software is growing ever more complex, and an increasing amount of work must be done simply to debug programs."

    This is the real problem with todays new software: every programmer wants to put every functionality in every program he writes. This creates bloated and bug-ridden programs.

    For example: if I want to buy a new bicycle, and I would like to look up information on the internet. I NEED a browser that supports pdf files, flash animations, at least 5 different graphic file formats, cascading style sheets, java scripting and so on, just because nobody cares about standards. Because of that all pages look really bad, because my fonts scale differently, or I have a different screen size.

    Wiebe.

  13. Has anyone figured out how to pay the coders? by reemul · · Score: 5, Insightful

    With all of these endless /. posts about how Linux will rule the world, I have yet to see a single post explaining how programmers will ever get paid. Don't any of you want to write code for a living? Open Source companies can make money, sure, charging for services. But services cannot pay for programmers. Let me repeat that so that everyone is sure to see it: services cannot pay for programmers.

    Since Open Source code is, well, Open, absolutely any service provider or consultant has access to the same software. If company A pays programmers to write code which is contributed to the community and makes their money selling services related to that code, and company B has no programmers but offers the exact same services for the exact same code, the company B will always be able to make more profit than company A. Because company B is in the exact same business as company A, but doesn't have to pay programmers. They can cut their costs below company A, stealing their business, and still enjoy higher margins. Company A either fires the programmers or dies.

    A company can only afford to pay programmers if they have name recognition high enough to charge higher prices for services, or don't give feedback to the community about upcoming releases until its actually out so that they have a big enough head start to give competitive advantage, or they use closed code. That means they either pimp themselves, act like weasels, or go proprietary. Nice way to make a living. The Open Source movement lives on successfully, but the coders end up eating a lot of ramen and working at Circuit City. The only model I've seen so far depends on coders working for free. Volunteerism is great, but you can't base a business on altruism. Besides, in some ways making money off of unpaid workers is worse than Nike using cheap foreign labor - at least the foreign labor gets *something* for their effort. With few exceptions, contributing to Open Source is like pissing yourself in dark slacks - you get a warm feeling, but nobody else notices.

    Can some of the clever folks here at /. come up with a way for Open Source to succeed and pay programmers at the same time?

    --
    You're just jealous 'cuz the voices talk to *me*
    1. Re:Has anyone figured out how to pay the coders? by swb · · Score: 3, Interesting

      Since Open Source code is, well, Open, absolutely any service provider or consultant has access to the same software. If company A pays programmers to write code which is contributed to the community and makes their money selling services related to that code, and company B has no programmers but offers the exact same services for the exact same code, the company B will always be able to make more profit than company A.

      What kind of services can company B sell without any programmers? Probably only basic services related to installation, troubleshooting and basic support. They can't fix the application's bugs, expand the applications capabilities or customize it without programmers. Thus Company B can only provide the same kind of consulting services that a zillion shops provide for Win2k -- installation/maintenance for places too small to do it themselves. It's a low-profit model thats also dependent on Company A continuing to maintain the application. No development, no future for Company B.

      Furthermore, Company A may actually *want* Companies B/C/D/E/F to provide low-end support for their product, since there's little margin for them in low-end support and it provides better market push for their application. Company A can stay focused on high-end, high-margin installations that need customizations or other custom services.

      They may also hedge their bets by releasing a version of their application that only hints at its capabilities and *requires* customization to make it scale/integrate precisely to limit parasites or to encourage purchase of their services. This is a tightrope to walk tho -- not enough goodness in your free app may prevent interest in a customized version.

    2. Re:Has anyone figured out how to pay the coders? by pussyco · · Score: 4, Insightful

      I don't see proprietry software as the great solution to this problem. You write foobar
      and sell in at $50. Microsoft brings out foobar-for-windows. While they are charging $50 also, you are still in business. Once they bundle it with Windows XP ultra, you are out of business. No guarantees that you will recoup your development costs before that happens.

      Suppose you are in a part of the software market that is still competitive. Five different companies, each selling a similar package for $1000. Lots of programmers are getting paid, but for what? If a new company enters the market it will hire programmers to write its package, that it will try to sell for $1000, but these programmers will not be improving the existing code, they will be employed in repeating work already done, so that the new company can own its own version and split the money available six ways instead of five ways.


      What does this do for the users? We saw what it does to the users in the UNIX wars. You get several versions of much the same concept. The programmers break inter-operability between the different versions for commercial advantage by locking in "their" users. I guess that RMS would say "reduce to serfdom" rather than "lock in". Whatever. Users aren't getting value for money when they pay the coders via the proprietry software system.


      I'm trying to get back into computer programming after a very lengthy illness. I'm horrified by how insanely complicated it has all become in the past ten years. C++ is twice as big as ANSI Common Lisp and offers a quarter the functionality. XML has 3000 pages of manuals that tell you how to do sod all. The PDF manual is about 1000 pages, and it is just a document format. What does html offer? The core functionallity is the anchor tag so that you can click on links, and reflowing the text so that you can resize your browsers window, but can you write your own browser? No way, there is Java, and Java Script and Flash and endless complication, but can I put maths on my web page? Until very recently, no.


      Presumably the point of all this insane complexity is to create barriers to entry, in that programmers have to work in big teams for large companies. It is naive to continue to believe that a programmer can write a program, retain the copyright and join the rentier class living off the royalties. You have to work for a big company who own the copyright to your work, and exploit you just like the big record companies exploit their artists.


      There has been no progress in software components since the UNIX pipe was invented. It ought to be possible to write a tiny little program, plug it into your desk top, and hey presto, a fancy program with a full feature user interface. Then users could write their own programs. Somehow we have got trapped into a model of software development that requires big teams of full time coders to get anything done. It looks to me like we have been too successful in paying coders in the past, and have gone down a blind alley

    3. Re:Has anyone figured out how to pay the coders? by binaryfeed · · Score: 5, Insightful
      Okay. First of all, when you're talking about paying software developers to write code, you have to understand that there are a few different "types" of software. I'll stick to the two I'm most familiar with: consumer software and enterprise software.

      Let's take consumer software. Consumer software is things like applications, consumer operating systems, development tools, etc. Companies like Red Hat, CodeWeavers, Mandrake, theKompany, Suse, etc. all employ programmers. As far as I know, these programmers are making money, and in some cases, the companies are as well. CodeWeavers, for example, contributes code to the Wine project and then writes non-free "easy-installation and setup" utilities in order to have some "value add" that is worth paying for. Red Hat actually makes money from selling only services, as every piece of code that they write (AFAIK) is released to the public under an OSS / FS license.

      Now let's take enterprise software. Look at projects like JBoss, Tomcat, Castor, etc. In nearly all enterprise software, there is a need for an "infrastructure layer". My company actually PAYS ME to fix any bugs in JBoss, Tomcat or any of the other things we're using as our "infrastructure" because it's a hell of a lot cheaper than paying for a resale license of WebLogic or WebSphere. Our customers are happy because they get a reliable system. I'm happy because I get paid to work on OSS stuff. My company is happy because they save money (or make more money, depending on how you look at it) using the OSS / FS infrastructure ... everyone is happy. I'm not starving to death, I swear. Lots of enterprise software companies take this approach. Why? Because it makes economic sense to do so. Why? Because if they pay their programmers to fix bugs in an OSS codebase, they get the added advantage of other people (who they do NOT pay) fixing bugs for them, too.

      So, I'd hate to be harsh, but ... you're just WRONG.

    4. Re:Has anyone figured out how to pay the coders? by Saeger · · Score: 3, Insightful
      I'm horrified by how insanely complicated it has all become in the past ten years. ... Presumably the point of all this insane complexity is to create barriers to entry...

      No, I'm sorry, but the increasing software complexity and software development complexity is one barrier-to-entry that almost certainly has no anti-competitive conspiracy theory behind it; it's just the march of progress' :-)

      Eventually the complexity will get so bad that the only way to manage it will be with artificial intelligence, 'adaptive solutions' with genetic programming, etc. Human programmers will one day wake up to find themselves an anachronism... much like basket weavers.

      25 years tops.

      --

      --
      Power to the Peaceful
  14. Hmmm by nomadic · · Score: 5, Funny

    talking about the success of open source and Linux on the desktop

    There's a short conversation.

  15. Re:Not in the world of science it won't by Anonymous Coward · · Score: 3, Funny
    As a PhD in OS Design, I can't help but agree with you strongly. However, two weeks ago a colleague of mine introduced me to something even more solid and powerful, and I have to say I'm hooked.

    I suggest you give it a try too at your first opportunity: it's called "Commodore Basic", and runs on a machine called the "Commodore 64". I have assisted the Astronomy department with setting up a simulator of stellar collapse on that, and they were completely blown away by it.

  16. A guess by Arker · · Score: 3, Insightful

    I noticed the same thing. A guess: Perhaps what he meant was that since they did this, StarOffice is dead in the long run. Which would make sense. Eventually OpenOffice will outstrip StarOffice and there will no longer be any reason to pay for Star. Sun is just cannibalising it for a short term revenue stream, really.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:A guess by hartsock · · Score: 3, Insightful


      Peace of mind is a great thing. Even though it's an illusion from most closed-source companies, people will still pay for this and this alone.


      Some of the government offices I work with continually lamblast Linux for being free. Not opensource. Free. You see... these same offices happen to want someone to sue when stuff breaks. That is peace of mind for many government offices and contractors. Who do you sue when a Free open source program breaks or lets in the commies?

      Ultimately the price tag is there for the liability-implied and the right-to-sue-somebody. Well, as far as some contracts go anyway.

      --
      Live to Code, Code to Live!
  17. Microsoft doesn't want to kill Linux... by po8 · · Score: 4, Interesting

    If Microsoft doesn't want to kill Linux, why is it running ads attacking UNIX, spreading FUD about the GPL, etc.?

    First, MS does want to kill for-profit UNIX servers, and UNIX-derived MacOS X. These companies represent competition in the for-profit market, and have carved out niches difficult for MS to penetrate even given their desktop monopoly.

    In this modern era, however, it is important to maintain a duopoly, to avoid the appearance of monopoly. Traditionally this has been a weaker commercial competitor that is dominated but protected from destruction: think Apple, AMD, or Pepsi. One danger of this approach, as all three of the aforementioned companies have illustrated, is that it is hard to keep this balance: companies tend to consistently lose (Apple) or gain (AMD, Pepsi) market share in ways hard for a competitor to regulate.

    Enter Linux, a revolutionary new duopoly opportunity! Now Microsoft's "competitor" is a non-profit volunteer organization: very hard to kill, and yet very unlikely (at least in the estimation of Microsoft) to gain dominance. Better yet, this is an organization supported by major corporate players such as IBM that give the appearance of being competitors without actually attempting to directly compete.

    Granting this analysis, Microsoft's best course in dealing with Linux is clear: sufficient repression to prevent dominance, but not sufficient to marginalize the "competitor". Indeed, all of Microsoft's actions to this point have been in line with this behavior.

    All that is left now is to see how this new strategy will play out...

  18. Services have ALWAYS paid for the programmers by FaithAndReason · · Score: 3, Insightful
    Think about it: with every product you buy, you're really paying for a service. You don't have to buy a car - you could just purchase the raw materials yourself (or even mine them directly) then design and assemble it into a complete vehicle. I actually know a guy that did this - hand-forged and assembled a complete '42 Dodge (from an "open-source" design, I guess.) What - you don't have that kind of time on your hands, and you'd rather spend $20-30K for the convenience of having somebody else provide that service for you? Fine. But don't say you're not willing to pay a lot for services.
    So, your question is really: "How can the programmers make money if they're willing to give their stuff away for free?" Three possibilities:
    1. Stop giving it away for free, or just provide the source under a different license than the GPL; for example, make the software available for free, but you only get the source if you *buy* the product. Of course, then you'll lose the advantage of "many eyeballs", <troll>but hey, who audits all that code anyway?</troll>
    2. Ask for donations. By all accounts, Mandrake and TransGaming are doing reasonably well with this approach. (See my other post below.)
    3. Do the coding, not to get paid directly, but in order to increase your chances of getting a better-paying job. There was a very interesting study linked a few months ago on /., analyzing the countries and backgrounds of contributors to GNOME. The observation was that a disproportionate percentage of open source contributors are from countries that have developing IT industries, not established ones, so his conclusion was that the coders were contributing in order to develop their skills and establish their reputations.
    The last one is the option that can motivate me personally. I'm out of work at the moment (hire me!), so I'm planning on contributing to the Wine and/or Mono projects to boost my marketability. Is that so bad?
  19. Open-source debugging, or lack therof by Animats · · Score: 4, Insightful
    If the "many eyeballs" approach to debugging actually worked, so would Mozilla.

    Many open-source projects get to the point where they sort of work, but aren't pushed through to the point that they work solidly. Probably because the grunt work to achieve that is boring.

    A very few high-profile projects, like the Linux kernel, attract enough developers to push through this barrier. Most projects don't.

    There's another possibility. If you get the architecture wrong, the open-source process won't fix it. That may be Mozilla's problem.