Slashdot Mirror


Windows Beat Unix, But it Won't Beat Linux

Onymous Hero writes "The amazing thing isn't that Windows beat the pants off Unix; it's that so many of the Unix companies survived until today. An article from eWeek looks at why Linux has been so successful where Unix failed." From the article: "While the Unix companies were busy ripping each other to shreds, Microsoft was smiling all the way to the bank. Because the Unix businesses couldn't settle on software development standards, ISVs (independent software vendors) had to write not a single application to get the whole Unix market, they had to write up to a half-dozen different versions. Which would you rather do? Write a single application that would run on all Windows systems, or six different ones, each with its own unique quality assurance and support problems? "

18 of 424 comments (clear)

  1. Make that three. by Xenex · · Score: 5, Informative
    From the article:
    "Twelve years ago, I oversaw a PC Magazine feature on Unix on Intel. My team and I reviewed at Unixes from Consensys, Dell, Interactive, SCO, Univel, Sun, and NeXT.

    ...

    Today, most of those companies are dead. Only two of them--Sun and SCO--are still in the Unix business.


    Make that three.

    NeXT are still in the Unix business.
    1. Re:Make that three. by hungrygrue · · Score: 5, Funny

      That is still only two, he counted SCO as still being "in the UNIX business".

    2. Re:Make that three. by Anonymous Coward · · Score: 5, Informative

      > Still? Apple's new to the UNIX business. They weren't in it 12 years ago.

      They were.

    3. Re:Make that three. by Daniel_Staal · · Score: 5, Funny

      Hey, SCO is still in the Unix business!

      ...the way a tapeworm is in a dog...

      --
      'Sensible' is a curse word.
  2. fortunately its not so hard to write for Unix now by torpor · · Score: 5, Informative

    .. you just have to choose your API's/frameworks carefully.

    i mean, its not so difficult to set up a project that will cross-compile, use GTK+ or one of the other, smart, GUI libs, heck even SDL+libcairo works wonders, and then get it running on Solaris, Linux, *BSD's, OSX, and Windows .. as long as you're developing on Unix.

    but you certainly can't easily do it the other way around: develop on Windows, and port across. It can of course be done (with GTK+, etc), but its not as easy as it is to do under Unix.

    --
    ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
  3. Why it won't. by suso · · Score: 5, Insightful

    And it won't for one simple reason. Its open source and free. Time and time again people say that Linux won't be able to last another year against Windows, and time and time again Linux is still here and stronger than ever. It is for one simple reason. It will last so long as people still have an interest in it and keep developing for it. Theoretically, Linux could last forever against Microsoft because there will always be people who don't want to buy into them. And there will always be people who want software for free and be able to modify their software. We could sit at 24 million Linux users for the next century and be fine. Still using Linux? (version 8.6.12-ac3) You bet I am.

  4. Is LSB a valid system or isn't it? by TripMaster+Monkey · · Score: 5, Insightful

    From TFA:
    They [many of the Linux distributors] have realized that it takes more than open-source; it takes open-standards to make a successful open operating system.

    That's why the LSB (Linux Standard Base) 3.0 release is so important.
    Hold on a second...according to Ulrich Drepper, the LSB was fundamentally broken.
    (Note: see the Slashdot discussion regarding Ulrich's assertions here.

    If Ulrich is on target, LSB, far from being the saving grace of Linux, could well be its downfall.
    --
    ____

    ~ |rip/\/\aster /\/\onkey

    1. Re:Is LSB a valid system or isn't it? by Junior+J.+Junior+III · · Score: 5, Funny

      LSB may be fundamentally broken, but just wait for LSC, which will almost work. And then, emerging from the smoking ashes of LSC, after much pain and labor, we'll have LSD. And LSD is going to be faaaaaar out.

      --
      You see? You see? Your stupid minds! Stupid! Stupid!
  5. Linux wins because the OS isn't as important... by MosesJones · · Score: 5, Interesting


    Back when Unix ruled the world you programmed in C at the OS level, you had to understand about pipes and processors and threads and lots of other elements of the OS. This meant it was a pain to re-learn across all the other platforms.

    Now there are (for enterprises) only two real choices, Java and .NET. Java in paticular abstracts the operating system questions away so it becomes irrelevant what OS is running it just needs to run Java fast and cheap, so using lots of small boxes tends to be the way to go. Similar things can be said about Python, Ruby et al but large enterprises use them less.

    Linux is winning in large enterprises because its the cheapest, and safest, way to run Oracle RAC and J2EE Application Servers. If you really don't care about the OS (and most of the time you don't) then you might as well pick Linux.

    If programming was still at the OS level then IMO Linux would still struggle as you'd have to understand a lot more about it. J2EE in paticular has made hardware a commodity, and in the commodity world Linux is the best choice.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
    1. Re:Linux wins because the OS isn't as important... by tomstdenis · · Score: 5, Informative

      At the OS level?

      Um *cough* POSIX.1 *cough*....

      My apps built and tested in Linux build in BSD routinely with little to no modification (occasionally I need to fix a makefile to use the build tools differently).

      Just because some people *can't* code a program without going directly to asm to make syscalls doesn't mean things like glibc [which has threads] and the POSIX.1 standards don't exist. In fact I once wrote a webserver for QNX that built out of the box for GNU/Linux because I used nothing but standard function calls.

      Stop being a poser. You don't need Java to get program portability.

      Tom

      --
      Someday, I'll have a real sig.
  6. What's wrong with a win-win? by mcraig · · Score: 5, Insightful

    Why is it that for Linux to succeed Microsoft must fail and vice versa? Surely there's room for both of them in the market and competition is a healthy thing to prevent stagnation. No one looks for ATi to destroy Nvidia or wants Sony to put Nintendo out of the market so why the constant desire to see Microsoft fail? I actually like a lot of what Microsoft is trying to acheive with its next round of software. At the same time I love the progress made by Debian, Ubuntu, E17 etc. one spurs the other. If Microsoft fails surely thats bad for the American economy and in the long term means less jobs for people like ourselves, it's almost like wishing another Katrina on yourselves, doesn't make much sense to me.

    1. Re:What's wrong with a win-win? by jmacleod9975 · · Score: 5, Insightful

      Judging from Microsoft's past track record, it defines success as completely destroying its competitors.
      Defining success as being a relevant OS, and failure as being not relevant, it all depends on your point of view.
      From a Linux advocates point of view (if you can nail that down), they should both be able to succeed.
      From Microsoft's point of view, to succeed, Linux must fail.

  7. Dissing the BSDs, alas... by Noryungi · · Score: 5, Insightful

    From the article:

    The second advantage was it had Linus Torvalds.
    There are other open-source Unix operating systems: the BSDs.
    None of them, though, have had even a fraction of Linux's success.
    Because Torvalds is the single leader of Linux, it has avoided the old Unix trap of in-fighting, which continues to bedevil the BSDs.


    Excuse me? Sure, there is in-fighting among the BSDs, but there is certainly more in-fighting and more competition among the Linux distributions.

    For instance, the ports/packages of OpenBSD is inspired by FreeBSD's, while NetBSD's pkgsrc has been selected by DragonFlyBSD. OpenSSH, from OpenBSD, has been adopted by both FreeBSD and NetBSD (not to mention countless other OS) and pf has also been imported into FreeBSD and NetBSD. And so on and so forth. That does not sound like in-fighting to me.

    So... in-fighting? Sure, there is competition between the BSDs, and a fair amount of sniping and name-calling, but I don't think this is worse (or better) than the in-fighting between the different Linux distributions.

    --
    The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
  8. One word: Bollocks by squiggleslash · · Score: 5, Insightful
    "Unix" failed because of the following:

    1. Most Unix operating systems ran on proprietary hardware only. NT could be installed on cheap hardware you could buy from a store.

    2. The exception was SCO Unix. But SCO treated it exclusively as a high-end product, so it didn't end up on desktops.

    3. No serious push was made to put Unix on the desktop. As a result, Microsoft was able to sell NT as an operating system that the majority of system administrators were familiar with, as opposed to Unix where almost nobody had it on their desktops.

    If these issues had been knocked on the head, Unix might have stood a chance. As for "rival" versions all making different decisions, who gives a crap? So "Unix" wasn't one operating system, but several: if it was five different operating systems, then it had five chances to be successful. Any one of them could have succeeded and changed the market. None of them did, not because they were rivals, but because they all had at least one major flaw as documented above:

    • AIX might have been successful had it been available for x86 and with low-cost desktop versions available that were properly pushed.
    • Solaris might have been successful had it been available for x86 (before Linux) and with low-cost desktop versions available that were properly pushed.
    • HPUX might have been successful had it been available for x86 and with low-cost desktop versions available that were properly pushed.
    • DEC Tru64 might have been successful had it been available for x86 and with low-cost desktop versions available that were properly pushed.
    Whether, of course, it would have been capable of being properly pushed, given Microsoft's stranglehold on the desktop market in the early nineties, is open to question.

    What the summary documents is a nonsense and ignores the real issues. Arguing that AUX didn't succeed because it competed with Solaris would be like arguing MSDOS didn't succeed because it competed with CP/M. The fact all of these operating systems shared a brandname does not mean they didn't independently fail. They may have failed for the same reasons, but they didn't fail because they were all slightly different yet had a brandname and some code in common. That's ridiculous.

    --
    You are not alone. This is not normal. None of this is normal.
  9. Wrong premise by Anonymous Coward · · Score: 5, Insightful
    they had to write up to a half-dozen different versions. Which would you rather do?

    Good grief what bull - anyone would think you've never been able to write large scale single source apps until you ship on one platform (Linux, Windows or the Mac, choose one). Between 1990 and 1994 I worked for Laser Scan (out of business for about a year now) www.laserscan.co.uk. We wrote GIS systems for VMS and 6 Unix platforms. All single source, in C, using X11 and Motif with Oracle I think, using object based code (the GNU C++ compiler wasn't up to much in 1990 when we had to choose). There was I think one header file with the few platform specific things in (like missing macros on Solaris) etc. I can't remember how many lines of code, but I think about the 1 million line mark, excluding comments. 11 years is a long time to try to remember that stuff.

    But single source - that is the majority of your headache gone right there. Which leads to the next FALSE assertion:

    Write a single application that would run on all Windows systems, or six different ones, each with its own unique quality assurance and support problems?

    Write a single App for VMS and six competing Unix vendors from single source - why thats the same as write an app for seven different Linux vendors from single source. You STILL have the seven unique quality assurance and support problems because each distribution will be different.

    It would be nice to assume that because you built it on RedHat it will run on Suse. Maybe it will most of the time. But will it always? And when it does not, will the cause necessarily always be the same when it fails on Linux vendor #2 compared to failing on Linux vendor #4? Maybe, Maybe not, that is the question, for alas quality assurance and support did not exist when he wrote plays in Stratford upon Avon.

    Still, I'm sure the informed journo that wrote that article has a nice pay cheque.

  10. Except: Microsoft's evolution was WORSE... by awfar · · Score: 5, Insightful

    "Which would you rather do? Write a single application that would run on all Windows systems, or six different ones, each with its own unique quality assurance and support problems? "

    Development, installation and running on multiple MS platforms was NEVER easy: how quick everyone forgets...

    In Win 3.x installation was text files, then .INIs, then some .INIs and half a registry, then Win32s, Win32, then Win 9x and the registry, then NT, it's unique registry, then running 16 bit in 32 via thunk and later WoW, ad nauseum! Then, its C, then VB, then, Visual, then VB + VC++, whatever...

    Never mind the network. Monolithic, NDIS, NDISII, II(?), Netbios/NETBEUI, then Bill Gates invented the Internet and IP, then broken IP stacks....

    Then COM, COM+, ADO, then AD, then....

    Then this .dll, then VxDs, then .NET,...

    MS Easy to Develop and maintain for, and runs on all machines my Rear.

  11. 'cos there is no win-win with Microsoft involved by DFJA · · Score: 5, Insightful
    If Microsoft wins and Linux loses, there is no competition left, only a monopoly. That is not good for anyone (except the monopoly).

    However, if Linux wins and Microsoft loses, there are still N-1 companies competing in the OS market, where the -1 is the loss of Microsoft. So still (almost) as much competition as before, and it's still good for everyone.

    I want NVidia and ATi both to succeed as while they are both there, there is real competition. Linux doesn't work that way, it's not a good analogy.

    That's the beauty of the GPL. It's all in the licence, stupid.

    --
    43 - For those who require slightly more than the answer to life, the universe and everything.
  12. What the hell!? by SalsaDoom · · Score: 5, Informative

    This is of course, going to get modded down into oblivion, but damnit, this is going too far now.

    Are are you mods on crack? This is the lamest troll I've ever seen and you tools are lapping it up? Fuck me, but is slashdot ever full of POSERS if you guys can't tell that this is pure crap.

    FreeBSD has Linux have always been very neck to neck. While linux would be a touch faster at this, FreeBSD would be a touch faster at this, etc. Linux has better hardware support, FreeBSD tends to have better stability. It goes on like that and pretty much always had.

    FreeBSD has not benefitted from Apple. Apple has benefitted from BSD. Purely a one way relationship. Since when did Apple write FreeBSD's VM and SMP code, that makes "OSX running effiecently" -- OSX is not efficent. Its bloated to the max. You might dig is GUI and design, thats fine, but you can't tell anyone that its effiecient code because you don't have to look hard for benchmarks to make that claim a joke.

    FreeBSD does not run on Apples mach microkernel, holy shit, how did this slip by? Is this just Apple fanbois modding anything even remotely pro-apple up? This has got to be happening here. What the hell is this long and precarious history of FreeBSD -- its bloody free software, what exactly is supposed to happen to it? And... ooh! So annoying, the troll even posts about how FreeBSD has wicked HARDWARE support now -- argh! Like they even run on the same machines sand you guys still modded it up!

    If god were real he would strike you down for modding this up, even if you are a mindless apple fanboi.

    --SD

    --
    "Computers will never truly be free until the last windows user is strangled with the entrails of the last mac user."