Windows Beat Unix, But it Won't Beat Linux 424
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? "
Make that three. (Score:5, Informative)
Make that three.
NeXT [apple.com] are still in the Unix business [apple.com].
Re:Make that three. (Score:5, Funny)
Re:Make that three. (Score:2)
Re:Make that three. (Score:5, Funny)
Hey, SCO is still in the Unix business!
...the way a tapeworm is in a dog...
Re:Make that three. (Score:3, Insightful)
Re:Make that three. (Score:2)
Re:Make that three. (Score:5, Informative)
They were. [wikipedia.org]
Re:Make that three. (Score:2)
Actually, they were. A/UX dates back at least that far. Further, I think. I remember first hearing about it in '89 or so.
Re:Make that three. (Score:2, Interesting)
Sure they were. (Score:3, Interesting)
Besides, Apple of today is very much NeXT. Just [apple.com] look [apple.com] who's [apple.com] running [apple.com] it [apple.com].
Re:Make that three. (Score:4, Funny)
Re:Make that three. (Score:2, Interesting)
SGI [sgi.com] are still in the UNIX business [sgi.com].
Re:MacOS X is not Unix. (Score:5, Insightful)
According to you tf Apple site:
"Beneath the surface of Mac OS X lies an industrial-strength UNIX foundation..."
http://www.apple.com/macosx/features/unix/ [apple.com]
Luckily I commented on you so that I am not tempted to mod you overrated.
Wether you call BSD dead or not, I don't care, I just use what works the best for me, sometimes it is windows sometimes it is Mac other times it is bsd. I tried linux but I am more experienced with BSD's.
What the hell!? (Score:5, Informative)
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
Re:What the hell!? (Score:3, Insightful)
A couple of corrections... (Score:5, Informative)
Actually, FreeBSD does not use the Mach microkernel. FreeBSD, NetBSD, and OpenBSD all use their own traditional kernels. The only free BSD flavor to sport a microkernel is Darwin [apple.com] (and its variant OpenDarwin [opendarwin.org]). Actually, according to Apple, Darwin does not even support SMP on x86 platforms currently (though I'm sure this will change with Apple's transition to Intel)
Actually, this is only partly true. They tend to mix and match bits of the BSD userland from FreeBSD and NetBSD.
Apple's biggest contribution has been in the form of good press. Actually, Apple's OS only sort of resembles FreeBSD. The init plumming is all different. Directory structures are very different. NetInfo is very different indeed than FreeBSD's more traditional model for user management, etc.
And what's with the link in your last line to trollaxor.com? (Look at the period at the end of the last sentence.) As glowing an endorsement this would seem of FreeBSD and Apple (of which I'm fond of both), it would seem maybe that a lot of mods were cleverly trolled?
-Peter
fortunately its not so hard to write for Unix now (Score:5, Informative)
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
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.
Re:fortunately its not so hard to write for Unix n (Score:3, Insightful)
Why group the different UNIX vendors together then complain that they are different? Why not put microsoft in the same group with them and complain that what you write for UNIX does not run on Microsoft?
Re:fortunately its not so hard to write for Unix n (Score:2)
I work with a system that is 95% system independent, it runs on anything from Windows to mainframes. After each release, the main code goes to platform porting to actually port it to the specific flavour of UNIX, i.e Solaris, AIX (4 and 5, difference between these releases), HP-UX, Tru64, Linux (both 32 and 65 bit). So, for a lot of applications, it is a huge mess porting to various platforms, each platform with their own porting group.
The problems with multiple UNIX flavors
Why it won't. (Score:5, Insightful)
Re:Why it won't. (Score:2)
Re:Why it won't. (Score:2, Interesting)
Re:Why it won't. (Score:2)
Re:Why it won't. (Score:3, Informative)
Re:Why it won't. (Score:4, Funny)
Don't think so. It's been in the kernel since 2.6.12. Now, whether userland apps take advantage of it or not is a different story.
But that's not really the point, is it? (Score:2, Insightful)
And that is the point. It's not if it's going to be around for a long time (it will be, for all the reasons the parent posted), but if it will grow to compete with windows on the desktop market. What is really stopping me right now from switching to a linux desktop is software support... I don't want to set up a server here
Knock over that strawman (Score:3, Insightful)
Who says that?
People often say that Linux won't displace Windows, that it won't overtake Windows on the desktop, and so on.
Re:Why it won't. (Score:3, Funny)
Linux may still be around in the next century.... but I don't think a 130 year-old Alan Cox will...
Never! (Score:4, Funny)
Well let me think... I'll write a single application that would run on all Windows systems, after they pry my cold dead fingers off my smoking gun.
Is LSB a valid system or isn't it? (Score:5, Insightful)
From TFA: Hold on a second...according to Ulrich Drepper [livejournal.com], the LSB was fundamentally broken [livejournal.com].
(Note: see the Slashdot discussion regarding Ulrich's assertions here [slashdot.org].
If Ulrich is on target, LSB, far from being the saving grace of Linux, could well be its downfall.
Re:Is LSB a valid system or isn't it? (Score:5, Funny)
Linux wins because the OS isn't as important... (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
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.
Re:Linux wins because the OS isn't as important... (Score:5, Informative)
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
Re:Linux wins because the OS isn't as important... (Score:2)
And of course back in the late 80s this stuff was all sorted, I could use glib and POSIX.1.
My point is that the market has changed from being one where seperate proprietary vendors had a point to the level where the standard has been raised so it becomes less important.
Re:Linux wins because the OS isn't as important... (Score:2)
Tom
And his point was for the earlier era (Score:3, Informative)
There was no glibc to be arsed to use. POSIX was a joke.
TFA dealt with that earlier era. You, sir, are off-topic and irrelevant.
The UNICES were subtly different (Score:3, Informative)
Re:The UNICES were subtly different (Score:2)
But really comparing Windows to UNIX is a bit loaded in the first place as UNIX came out "slightly before" windows. So the entire article is weird.
Tom
Re:Linux wins because the OS isn't as important... (Score:5, Insightful)
Think of all the surrounding stuff:
1. Manuals
2. Installation
3. Interfaces to other parts of the OS
So what if your code compiles on Solaris and Linux. If you want to support both, you will need to write a Solaris package and an RPM package. And one system uses
It's not straightforward.
Re:Linux wins because the OS isn't as important... (Score:3)
Come on, not in the same league (Score:5, Insightful)
Let me tell you, there were a LOT of ifdefs going on to deal with vagaries in the size of an int, byte ordering, even memory management.
You seem to claim that POSIX gives you just as good cross-platform abilities as a system like Java or Python. But that is simply false; at best Posix is only an order of magnitude worse in terms of testing across systems that is required to be done compared to a cross-platform language like Java.
One reason for this (at least in the case of Java) is a really rigorous set of tests that help ensure to what degree Java will do the same thing across platforms. Posix is not as well defined as Java to start with, and as a result simply cannot be tested as throughly to insure a similar level of behavoral similarilty across systems.
The common Joke with Java is that you "Write Once, Test Everywhere". But in my extensive practical experience I have seen no code changes required to easily develop day-to-day Java across Windows, Solaris, and Linux. There is NO WAY if I were writing POSIX C code I would be as comfortable just writing on Windows or Linux and then deploying straight to Solaris.
Java has moved out the bits that you really do need to "test everywhere" out much further on the fringes of coding than C has.
Re:Linux wins because the OS isn't as important... (Score:2)
Ummmm, okay, sure. I suppose if you don't care about the OS you might pick Linux because you haven't done your homework and it's the latest buzzword. Ask a true professional or go buy a clue and you will see that Solaris [especially Solaris 10] will beat the doors off of L
Cost of those old Unix versions (Score:2)
I got rid of my old unix magazines from back in those days or I could get some pricing for you all.
all the best,
drew
--
http://www.ourmedia.org/user/17145 [ourmedia.org]
Re:Cost of those old Unix versions (Score:2)
Bingo! That's the main reason why Unix lost out. (Score:4, Interesting)
Back in the 80's (about 10 years before the compatibility issue resulted in POSIX), there was a complete, well defined standard for UNIX. This was ATT's version, which was BINARY compatible across all x86 versions (not just source code compatible).
UNIX should have won out over Windows then. It had networking back in 1986. It had graphics. It had far superior technology to the main competition, which was DOS.
But, AT&T did everything in their power to kill UNIX. Not deliberately, but out of greed and incompetance. And one of the key factors was that the people who sold cheap UNIX on the PC (Microport, ISC, etc.) all had to pay an exhorbitant royalty to ATT - while Microsoft didn't have any royalties to pay.
The royalty was about $100 IIRC. That's absolutely rediculous in the PC biz. This meant you simply couldn't beat Microsoft when it came to OEM deals. Nor could you beat them when selling to the average consumer, where price almost always won out. So this was the main reason why UNIX could never beat DOS, or later Windows. Not even binary compatibility could surmount that cost difference. Fragmentation of the standards was an issue later on, and was only a secondary issue.
As an amusing side note, for a while NONE of those small UNIX companies selling x86 UNIX were paying the royalties to AT&T, not even SCO. When AT&T found out about it, it caused a serious collapse in the x86 UNIX biz. Microport went out of business, Bell Tech got "aquired" by Intel (who was responsible for the licenses - via the ATT "Micro Port" program). That is, Intel paid AT&T in exchange for aquiring Bell Technologies.
Even SCO wasn't immune. They licensed their Xenix code from Microsoft. It was Microsoft who ended up paying AT&T, and in turn got 20% of SCO stock there for a while.
Now, with Linux, there are no royalties to pay. Everyone is on a level playing field with Microsoft.
Intro ad? (Score:4, Funny)
When clicking on the story to ready it, there was a sun ad saying "With their evil systems, it's no wonder their name rhymes with hell"
haha Classy.
Re:Intro ad? (Score:2)
Standards (Score:5, Insightful)
Oh, and Linux can?
Re:Standards (Score:2)
Great article... (Score:2, Interesting)
If you are running a small company you don't have the time or other resources to support a hundred versions-- you go where the users are.
I can see Linuxers reading this article and spitting their coffee into their monitors (wooooot).
Great falme-bait for a Friday!
Re: Windows will win... (Score:2, Funny)
Make no mistake, THEY WILL DO WHATEVER IS NESSESSARY TO KILL US!
What's wrong with a win-win? (Score:5, Insightful)
Re:What's wrong with a win-win? (Score:5, Insightful)
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.
Re:What's wrong with a win-win? (Score:2)
But the inverse *is* true, from MS's point-of-view. For MS to succeed, Linux *must* fail. For MS to succeed, Sony and Nintento *must* fail. MS doesn't want a 'healthy technology ecosystem' -- it
'cos there is no win-win with Microsoft involved (Score:5, Insightful)
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.
Consider Microsoft blames sun! (Score:2)
No surprise!!
What? That doesn't add up. (Score:5, Insightful)
Now how does that make sense? Microsoft didn't meet anyone elses standards either. If anything even though the Unix guys didn't exactly pull it off, they still did a better job meeting standards than Microsoft. The truth is they were all doing their own thing, just MS managed to sell enough to get the userbase it needed to make developing for their platform a no-brainer.
In short, it wasn't Windows standards compliance or lack thereof that made them win, Windows won in spite of it.
Dissing the BSDs, alas... (Score:5, Insightful)
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.
Re:Dissing the BSDs, alas... (Score:2)
While the Linux kernel 'is fundamentally the same', you should also take into account the (sometime HUGE) differences between the Linux distributions, in terms of packaging, kernel versions and even kernel patches.
Trust me, I know. I used to work for a company that supported a lot of Linux distributions [arkeia.com] an
Re:Dissing the BSDs, alas... (Score:4, Insightful)
OpenBSD has a Benevolent Dictator, Theo de Raadt.
DragonFly BSD has a Benevolent Dictator, Matt Dillon.
There is next to no fighting between the BSDs, which you could easily learn from making use of the mailing lists and news archives that Google has in it's search index. There are conflicts between specific developers, but when it comes to code - they are often willing to help one another retrofit their code to suit another BSD.
Linux systems are fragmented to such a scale it is hard to identify a system worth making use of, while there are only 4 BSDs, 1 of which openly states it's not quite ready yet.
You're delusional if you think that just because there is a Microsoft everyone will unite to "fight the good fight". Because it didn't happen when that was IBM and it's not come close to happening in the past 10 years of Microsoft's market dominance.
Linux distributions are squabbling over the pie just as badly as their Unix counterparts did in the past, there are hundreds of distributions of Linux out there, hundreds.
Attitude (Score:3, Insightful)
The business world loves to be hip and Linux certainly provided that.
Comment removed (Score:5, Insightful)
Re:One word: Bollocks (Score:2)
I still don't get this whole talking about Solaris in the past tense thing. Solaris is alive and active and thriving, even if Sun is struggling. Solaris has more advanced capabilities today than all other commercial unixes and Linux and BSD as well. Sun's failures have primarily to do with designing and marketing hardware, not writing a good operating sys
Re: (Score:2)
Spot on! (Score:5, Insightful)
UNIX ignored cheap systems, everyone knew the money was in the big boxes, and as for the desktop, that was an insignificant market to be sniffed at. No serious vendor paid attention to desktops, only (sniff) Microsoft and their toy operating system.
Unix as a server OS (Score:2, Insightful)
Tyrants and the future... (Score:4, Funny)
Wait just a darned minute (Score:5, Funny)
Maybe I'm wrong (Score:5, Interesting)
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?
Seems a little bit oversimplified. I'm not directly affected because I don't use Microsoft software, but I've heard where I work that it takes months to verify if every service pack for Windows will work with existing software. And when I was a Windows developer, we were doing some pretty low level stuff with the authentication subystem, and things were very different between Win 98, 2000, and NT 4 (was that really still around then?). Granted, for a simple GUI app, Windows is very portable across its products, but if you get a little lower into the OS, things get nasty quick.
History says.... (Score:5, Insightful)
As to why you'd do this (and to some extent, this is still valid), it's because Unices provide a stable, well-mature platform for apps and are capable of more processing power than your typical Windows system -- all desirable traits for an application that people are going to depend on. People use Windows because the time-to-market for development is typically shorter than that of Unix development, mostly due to the fact that 95% of the world can write an app on their Windows desktop and copy it to a Windows server platform without modification. Doesn't mean it's good code or a well-thought out development strategy, but it's an enabling technique that keeps Windows development prevalent in IT.
Wrong premise (Score:5, Insightful)
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.
Enterprise BSD Clusters (Score:2)
Are there any companies successfully deploying BSD clusters that be used cost effectively in the enterprise realm? Or is this just something that Universities and the like are playing around with with little commercial applications.
JsD
Why should Windows beat Linux? (Score:3, Interesting)
The other thing is biting the hand that feeds it: Geeks. Yes, I know, we geeks are unmarketable, economically unviable, socially inept, prone to expect other people to know how to do Really Complex Stuff like unzip an archive, but before you burn us all at the stake just to get us out of the way so you can sell Linux for $14.99 off the shelf at WalMart, you might want to preserve a couple of us. Nobody else is going to make more Linux for you to sell. Programs do not write themselves.
No kidding: Programs really do NOT write themselves!!!!! So if you throw out the compilers based on the notion that including them with the distro will just confuse Joe Sixpack? That's disabling the programming process. If you get rid of the command line? Programs are written there. Throw out programs like vi, Emacs, gcc, gdb, yacc, sed, awk, and man just because they have funny names that won't look tasty on the flashy label? Wait, those are programming tools, we need those! If you make Linux into a Windows clone, thinking you'll attract all the Windows users and be just as rich as Bill Gates (because that's exactly what people are thinking!)? But Linux programmers would really hate that, and you'll scare them all away to BSD or BeOS. Hang lots of whistles and bells on it, decorate it with frosting, throw out every particle of substance and dumb it down? Yes, you will win points with the very lowest common denominator market segment - the ones who spend the money, after all - but you'll ostricize all the other users, who will get tired of being locked in another playpen and wander off looking for better stimulation. Believe it or not, Linux did NOT get to where it is by being Just Like Everybody Else.
Yes, yes, yes, I know this post is getting flamed to a crisp the moment I hit the "submit" button. That's OK, you don't have to listen to me. Look around in three years, five, ten, and see what happened.
Linux victory inevitable. (Score:4, Interesting)
Programs -don't- write themselves, and that is the ultimate point.
Right now, the entry level system for Windows, Visual Studio Express, is completely crippled, for $50. Even the $500 offering lacks source control. The only suite that really wins is Team System, and that's $2500, a year. That's almost enough to make a car payment with. I've been working with Beta 2 and for C++ its actually worse than KDevelop and for the rest, well, I don't see the justification of a $2500 premium.
If you are a small indy developer, the economics of writing for Windows is almost absurd. On the other hand, you can do a lot with Linux for the money. I have to believe that this trend will fuel the wider spread of adoption of Linux. That's not to say that it will be easy, but, the more developers switch, the more MS has to raise prices in its tools division to show growth, causing more developers to switch. Microsoft is in a feedback loop and even now licensing costs are starting to get even large IT concerns to take notice.
It used to be that Linux advocates were a minority, and they still are, but now they are less of a minority than before.
Except: Microsoft's evolution was WORSE... (Score:5, Insightful)
Development, installation and running on multiple MS platforms was NEVER easy: how quick everyone forgets...
In Win 3.x installation was text files, then
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
MS Easy to Develop and maintain for, and runs on all machines my Rear.
Linux will likely lose too (Score:2)
Nonsense! (Score:3, Insightful)
I've written several reasonably big Unix server programs over the years (mostly workflow engines and document management systems written in C and C++ with CORBA, multiple DB backends, etc.) and I think the posters statement is nonsense. Typically, one has to write an app for one version and make only minor tweaks to make it run on other versions. Often, those tweaks will point out mistakes made in the original and so are quite helpful in QA.
The headache is the patch management systems for all of the different vendor's OS versions. When the customer of your product says "We have problem X" and the solution is to tell them to install Unix vendor Y's OS patch 123456, that becomes a support headache. But it really is not very different from telling the customer they need to install a Windows service pack when a product that runs on an MS OS has problems.
Complaining that Unix OSs aren't perfectly standardized clones is like complaining that RDBMSs don't all implement the SQL standards perfectly. But most server application architects/programmers don't have too many problems converting their apps to use DB2 instead of Oracle. These kinds of minor differences haven't led to a monopolist RDBMS supplier.
How about price and Microsoft's bundling.... (Score:4, Insightful)
The economics were: DOS==FREE (forced bundling) -- XENIX $400
When you have 1 or 2 machines, this is not too much of a problem. However, when you plan on deploying 20 or 100 or 1000 machines, this $400 adds up very fast. Management balks....
In the early '90's, we had to pay EXTRA to Dell to get 486 PCs without DOS and Windows. So the cost was EVEN HIGHER. Management would look at the cost of XENIX (or other UNIXs which were comparable) and ask why you could not do it with DOS. As a result a lot of extra, unpaid OT happened to write executives and multi-taskers for DOS when XENIX/UNIX would have been an ideal fit!
Another factor is price elasticity of demand -- lower price, more demand, higher price, less demand. DOS=FREE (or even $29) versus XENIX $400 -- now which would management let you purchase or design into your product? Concurrent (?) UNIX was $99 and it was an option, but not widely supported. It has taken FREE versions of UNIX/UNIX-like O/Ss (Free BSD, LINUX) to change the market dynamics -- it is hard to compete with FREE and with FORCED BUNDLING.
Blinded article.... (Score:3, Insightful)
The "workstation" companies began to fail when they could not maintain this technology lead. Why pay Sun's margins for the same basic hardware you can get from the local whitebox shop? Unix and windows don't enter in to it.
IT is shifting from expensive big iron to throw away whitebox clusters.
Linux will succeed because it allows consumers to further commoditize the cost the computing for companies that have the staff to build and maintain their own OSS distributions (Google?). For companies that cannot do this and have to purchase Linux support contracts, its generally equal to or more expensive than Windows.
which would I rather do? (Score:3, Interesting)
As a programmer, I'd rather write six versions. This is because writing six versions takes longer without really being that much harder. It's not as if you'd have to write six completely different programs, just six similar ones. That would take longer than just writing one program, and then you'd have more to do and thus higher job security. Plus, it sounds a lot better claiming overtime when you're writing six programs versus just one. Of course, if I'm a manager or supervisor or something, I only want one program written. Depends on who you are and what you are looking for, I suppose.
The Art of UNIX programming (Score:4, Interesting)
For related 'extra' information... Chapter 2 [faqs.org] in the Art of Unix Programming (Eric S. Raymond) contains a very interesting discourse about the history of the UNIX operating system, and offers insight into operating system wars in general.
One of his points is that many early UNIXes suffered because of licensing issues. I definitely feel that Linux's edge over older UNIXes is its open source license.
Good code, Bad code (Score:3, Insightful)
This is true for most commercial software, too. But, as long as the machine keeps dumping millions of dollars in it and continue to force it down consumer's throat, it may survive for many, many years. There are many examples of this. *cough* MSFT *cough* *cough*
Can't we all just get ALONG?! (Score:4, Insightful)
Is this a fucking joke? (Score:5, Insightful)
I've worked on software that had to be supported on HPUX, AIX, Solaris, and yes even SCO's crappy UNIX. There were notable differences and QA requirements, but the differences between the Windows branches are much more significant.
Windows won for one reason. It was pretty, so you could trick people into learning how to use it. Well that, and people had windows computers at home, and they brought that skillset with them to job interviews.
It can't beat Linux because Linux doesn't have stockholders to answer to. And it's losing share to Linux in direct proportion to the degree to which Linux is getting prettier.
No multiple versions? Hahahahaha.... (Score:3, Interesting)
Ok, once again for the benefit folks in the cheap seats, let's review:
Windows 3.1
Windows 95
Windows 95B
Windows 95B
Windows 98
Windows Me
Windows NT Workstation
Windows NT Server
Windows NT Terminal Server
Windows 2000 Pro
Windows 2000 Server
Windows 2000 Advanced Server
Windows 2000 Server Datacenter Edition
Windows XP Home
Windows XP Pro
Windows XP Pro SP2
Windows XP Pro 64-bit
Windows XP Media Center Edition
Windows 2003 Server
Windows 2003 Server Small Business Server
blah... blah... blah...
OK, now, let's combine that with the various versions of IE
4
4.01
5
5.5
6
As one Windows C++ developer friend of mine described the process of working with these many versions: "Lions and Tigers and Bears, OH MY!"
Making most any reasonably complex app work on multiple versions of Windows is difficult at best and impossible at worst. That Windows is a panacea is jut plain wrong.
I don't get it. Write for one Linux and (Score:3, Insightful)
There is no need to support all the different Linuxes, just do one and call it good. Hardware is cheap, applications can run over X, allowing application servers dedicated to specific apps, Linuxes are open so compatability tweaks can be done at any level. (Similar to the standard system load performed by most companies these days)
I've spoken to a few major software development teams and they don't get this at all. They see a support nightmare with all the different versions. Open scares the hell out of them because they don't have any real control over what users do.
Why bother with all of that? Let the users do what they will and support those that play ball. The community will evolve whatever is necessary to handle the exceptions and it won't cost a dime. If your app sees wide use, you can bet there will be communities that form around it. Those folks will largely support themselves. In fact, starting such a community would solve the problem and focus the efforts in one known place. Sheesh.
Unix beat? $4 billion 2nd quarter is beat? (Score:3, Informative)
From Information Week dated Sept 5, 2005 "businesses spent more than $4 billion in the second quarter on Unix servers. Sales of high-end machines (priced at $500,000 and more) grew around 20% in the second quarter, while sales of midrange servers ($25,000 to $500,000) grew more than 15%".
If only I could lose like that.
Its also interesting that of the companies controlling "more than 90% of the Unix market", HP, IBM and Sun, only Sun seems to be mentioned at all in this forum. Slashdotters apparently need to open their eyes to the fact that there is a vast market for systems beyond desktops and hobby servers.
Re:Windows vs all (Score:2)
Comment Repository? (Score:4, Informative)
http://linux.slashdot.org/article.pl?sid=05/09/19
Come on, you can do better AC.
all the best,
drew
--
http://www.ourmedia.org/node/57503 [ourmedia.org]
Paper Plane 001 video at ourmedia
If you are gonna keep posting this... (Score:2, Informative)
You are correct. Linux is NOT READY for the home. (Score:3, Insightful)
For example, just recently I wanted to install BlueFish 1.0 on a Solaris 8 system. (No, it's not Linux, but the principle is the same.) Unfortunately, BlueFish
Re:You are correct. Linux is NOT READY for the hom (Score:3, Insightful)
So, the fact that Solaris does not have an adequate package manager means Linux sucks?
1) Solaris's shortcomings are not Linux's fault
2) Most Linux distros have *much* better package managers than Solaris. You would not have had these difficulties in almost any Linux distro.
3) Use Blastwave instead of Sunfreeware; Blastwave has a much better package manager than the native Solaris one.
4) Solaris 8 is obsolescent; it's not surprising you had trouble getting and using decent freeware for it.
Chris Mattern
Re:this article's ignorance is astounding (Score:5, Informative)
Firefox, and netscape before it - self installing executable.
Flash - self installing executable.
MyEclipseIDE (a commercial J2EE feature / plugin for Eclipse) - self installing executable.
Even Oracle is a simple clicky wizard away on Linux these days.
The challenges to installing 3rd party software on Linux or any Unix are no different to the ones in Windows. - In fact, with the complete lack of package management in Windows, most Unix like systems are actually easier to create installs for.
It's not the fault of the operating system if the application vendor can't be bothered spending the extra time to make the installation process easy.
Re:this article's ignorance is astounding (Score:2)
java - pain in the ass to get applications to use it, lots of afterwards manual setup
firefox & netscape - the plugin hell that it is, manually copy libraries around your computer
flash - still big pain in getting it setup after you do the GUI point and click to simply unwrap the files
MyEclipseIDE - haven't used this so I don
Re:this article's ignorance is astounding (Score:2)
Sure. Now multiply by how many different installs you'll have to create - and test - for each linux/unix distro you care to support, and that might not be true anymore.
Re:this article's ignorance is astounding (Score:3, Insightful)
You speak the truth, which is why this post will be modded as a troll or flamebait. Linux will remain a niche player until I can download and install a program without having to compile it from source or wade through a list of compiled binaries by platform a
Re:Huh? rpm, deb, rh, suse, etc, etc. (Score:3, Insightful)
While I am a c++ fan, i don't see the advantage of a C++ gui API. Furthermore, while it may seem huge to you, we only have two main GUI API on linux. They are even mostly crossplatform now. Plus you know that by choosing either one of them it will run on your linux box, as both GTK and QT are installed.
As for the media framework, i guess you haven't been following it very well, but to my knowl
Re:Huh? rpm, deb, rh, suse, etc, etc. (Score:3, Informative)
It's the mostly that's the problem. And besides, when one has to wait on a particular distro to provide their flavor of a given program (which generally you do), it's no longer mostly. As long as Linux programs have to be tailored to specific distros, Linux has a problem.
So then you are saying Apple will win (Score:3, Insightful)
Personally I think that's Microsofts big problem - If your theory is right, Apple wins. If the theory of choice is correct, Linux wins. Note there seem to be no scnearios under which Microsoft "wins", only ones where they cohabit a space... and that's all most detractors have ever really wanted. A world where Microsoft does not win but i
Re: (Score:3, Interesting)