Slashdot Mirror
What Differentiates Linux from Windows?
tail.man sent in a Linux Insider piece about the difference between Linux and Windows. Quoting the synopsis "So, what's really the difference between a Unix variant like Linux and any Windows OS? It's that Microsoft reacts to marketing pressure to make design decisions favoring running a few processes faster but then finds itself forced first to layer in backward compatibility and then to engage in a patch-and-kludge upgrade process until the code becomes so bloated, slow and unreliable that wholesale replacement is again called for."
...also wrote The Unix Guide to Defenestration, which is an executive-level discussion of making a data center profitable.
He's been a Linux advocate for quite a while...
The Army reading list
Murphy writes that "For example, cost is usually important in business only if the products being compared are otherwise very similar." I work in education and cost is everything. I can really say that my Linux OS machines (running the K12LTSP) are equal to my Windows 2K/XP machines but cost is huge. I can literally put a lab in my classroom using Linux, I'd have to settle for a couple of PC's at best under the commercial software regime.
So, what's really the difference between a Unix variant like Linux and any Windows OS? It's that Microsoft reacts to marketing pressure to make design decisions favoring running a few processes faster but then finds itself forced first to layer in backward compatibility and then to engage in a patch-and-kludge upgrade process until the code becomes so bloated, slow and unreliable that wholesale replacement is again called for.
As opposed to Unix, where the design is so open and extensible that anything is possible, yet there is no coherent interface and none of the non-server applications work or look as good as they do on Macintosh or Windows.
Cretin - a powerful and flexible CD reencoder
Unix revolves around the idea of simplicity. Microsoft revolves around complex systems, and misguided attempts to hide them with friendly configuration interfaces.
Net result is that you might get something done quickly, but you still won't understand how the thing works. This is not optimal, especially for critical systems.
Nobody understands Windows. I for one don't even want to understand it.
Save your wrists today - switch to Dvorak
MicroSoft makes an OS to make money, Linux is designed to be an effective OS
The system had the verbosity of HTML combined with all the readability of compiled assembly viewed as bitmap images
Windows also has ease of use and ease of hardware integration...
You can't tell me that Linux is easier to use and install hardware drivers for than Windows.
While I know that we are all Windows haters it does do quite a few things rather well. It isn't used by so many people because it is *completely* inferior. It serves its purpose.
Despite conventional wisdom and some articles to the contrary, sometimes complete ground-up software rewrites are necessary. Windows 2003 is - for my money - one of the best server systems around. Its stability is equal to the linux servers I run, and finally it installs completely locked down.
Windows 2003 wouldn't be possible if 90% of its codebase was from the WinNT 3.1 kernel.
Even Macs - OSX is so completely different than OS9 that they can't even be compared fairly. OS9 was dead in the water before it came out - the rewrite of the OS (albeit on the BSD kernel) was necessary to allow Mac to continue to compete at all.
Excuse my speling.
Making The Bar Project
So by the metric they care about, Microsoft is an effective OS.
dtg
The truth is an offense, but not a sin.------R. N. Marley
.. the gap is closing between the two in terms of usability and stability - in BOTH DIRECTIONS. this is hardly ever mentioned, but Windows has improved BIG TIME since 95/98/ME -> If you have used 2003 you will note the speed is much improved over older versions as is the stability. Now before you brand me a Redmond freak, I've been a linux user for 5 years (since I was 12) and will be forever, but I can hardly help noticing that everyone thinks Linux is gaining on Windows, when in fact Windows is also gaining on Linux
just my 2 pence
Tim
tim
>Linux is made with efficiency and innovation in mind, by lots of people around the world that believe in the idea of freedom.
Ummm IBM, SGI and lots of other profit-oriented companies have contributed code to Linux. Do they actually believe in "freedom"? Why not opensource all of their products?
The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
I know somewhat offtopic... but the article link crashed Moz here for me.. anyone else get that? Ver 1.5
I'll AOL that.
Actually, this is a good opportunity to pinpoint all those Internet Exploder users within the slashdot community and excommunicate them once and for all.
Save your wrists today - switch to Dvorak
yea! The only drivers I ever have to install are the nvidia video drivers linux. For the most part has all my drivers and the only reason for the nvidia drivers is so I can have gl support, otherwise I could just use it out of the box without the installation of drivers.
Although no self-respecting /.er wants to admit, there is a steeper learning curve to using Linux than Windows. How much more steep is debatable. There also is a tendency for closed-minded people who want to do as little thinking as possible to choose Windows, even though it paves the way for migraines later.
My two cents, be gentle with the flames. Ah heck, I'll post anonymously, so flame on!!!!
Boils down to something like this.
Windows: easy to configure, easy to break
Linux: difficult to configure, difficult to break
Don't get me wrong, I use both, its an apples to oranges comparison. The question is what do you want to do with it? A MS firewall is unconsiderable, but so is the thought of putting Linux on my sisters desktop.
K-12 institutions receive lots of donated hardware. How do you make, for example, a donated scanner work with GNU/Linux if SANE lists it as unsupported? Do you reserve a Windows box just for that scanner and a few other donated peripherals that the community hasn't yet figured out how to get to work with a Free operating system?
On one hand, we have an O/S that works with X86, once worked with one other architecture, and has gone nowhere else.
On the other hand, we have an O/S that works with X86, and now works on everything from calculators and old gaming consoles to some of the largest supercomputing clusters in the world.
Anybody who says that Linux isn't inherently more robust and flexible at the critical core areas is living their life under a rock.
I have no problem with your religion until you decide it's reason to deprive others of the truth.
It's like driving a car you're not accostumed to every day. It's just different.
... I'm a huge Linux fan, but I also use windows. (Often tagged, albeit incorrectly, as a 'Microsoft Hater'). Anyhow, my point... what happens when someone open sources windows? Or, more specifically, comes up with an Open Source Windows clone?
But to be slightly OT...
It sort of reminds me of something
I've always wanted to write a book talking about how the two camps actually need each other. Microsoft would have more to fear from an open source windows variant than any threat Linux could ever bring.
FLR
My dad (a reasonable, intelligent, only semi-computer-literate man) asked me this exact question the other day. The best I could give him was that Linux is a hobby OS and Windows is an OS driven by business interests. That gives pluses and minuses to each of them. Dad and I talked about the good and the bad; obvious things like, security issues, lock-in, consistency across apps, integration, stability. We agreed that Linux could really benefit from some of the aspects of Windows, such as centralization and consistency across the UI in every app. We also agreed that Windows could benefit from many things Linux has, such as increased peer review, freedom (beer and speech), and community. In the end, he wasn't interested in switching to Linux or anything, but he hoped that its influence was going to get Microsoft off their rear ends and improve their product. I think whichever OS can meet the other in the middle--with a balance of security, usability, and power--will win the long-term battle.
The points in the article (and others) also reflect the fact that Unix variants came about during an era of big expensive hardware and timesharing versus small cheap (relatively) hardware and a single operator. These categories can also be looked at as Unix favoring "enterprise" tasks and Windows favoring "personal" tasks. The interesting part is that both camps are trying to became more attractive to the other's "side"; i.e. Windows han been targeting the infrastructural role while Unix variants are warming up to the desktop.
Granted, this analysis is a little superficial but I think it's true in a broad sense.
While he was in New York on location for Bronco Billy (1980), Clint Eastwood agreed to a television interview. His host, somewhat hostile, began by defining a Clint Eastwood picture as a violent, ruthless, lawless, and bloody piece of mayhem, and then asked Eastwood himself to define a Clint Eastwood picture.
"To me," said Eastwood calmly, "what a Clint Eastwood picture is, is one that I'm in."
"Prepare for the worst - hope for the best."
Windows on the other hand is sterile and ferile. No one is personally involved in one particular aspect (at least for very long, comparitively speaking.) So you get mountains of code that, once written, are rarely re-thought. They work, they go through testing, and until some new function is needed for it or some vulnerability found, never given a second thought.
Think Bit Rot.
"Learning is not compulsory... neither is survival."
--Dr.W.Edwards Deming
No, and why should a user who just wants to use a computer, not configure a computer, need to know about that? This is the kind of stuff that really makes Linux and Windows different. Linux is for those who care about THE computer windows os for those who care about USING a computer...
It's still in development, but you can boot it and run some programs on it already.
Request your free CD of my piano music.
SCO owns the code to Linux
any questions? /puts on flamesuit/
here is the (very general) main differences IMO:
Windows is an OS driven by the desire for profit and more widespread use.
* ease of use
* compatibility with hardware/programs
* small learning curve
Linux is driven by a desire to create a more 'better' operating system with a desire for more configurability.
* longer learning curve
* more versatile
* not intended for the average user (and will not be anytime in the near future)
* more concentration on bug fixes and security, and less on user-friendliness
there are commercial companies obviously that sell linux, but mainstream usage is not #1 priority for the main developers, therefore it is a hard sell for the linux distribution vendors
Marge, get me your address book, 4 beers, and my conversation hat.
Maybe I read the article wrong, but it didn't state Linux was better, it just stated things that differed. It had multiple Unix type OS's Solaris, Linux, BSD and Mach kernels in the article.
The point that did come up multiple times, Microsoft has to rewrite large portions of windows code to take on new features, which make it incompatible with older software. While Unix based OS's can run older versions of software.
Linux (or BSD/etc) is more modular and can build on newer, better OS implementations. Paging file techniques, VM engines, OS Schedulers, etc.
It's more of a design philosophy article.
Windows still has an edge in simplicity as far as installing apps. Folks who swear by apt (for RPM) do have to realize you still need to deal with adding repositories to sources.list and dealing with GPG signatures.
OTOH, that simplicity in installing apps makes Windows extremely vulnerable as well. Doesn't take much effort to run/install anything off the Internet. Spyware can cling onto your system without much consent at all.
That brings up the major difference I've seen so far. Worms, Viruses, Trojans, Keyloggers, and other forms of malware don't seem to find their way into my Linux machine. The rest of my family who run Windows, though, get infected too many times for my liking.
Is that because most Linux users know to watch out for those types of things while Windows users can be painted with the "AOLer" stereotype? That's probably a factor. But so is the general architecture of not putting yourself in danger for the sake of convenience -- by running mail programs and browsers with enough privs to bork a system.
Cheaper, more secure, and absolutely transparent. Many thanks to everyone who makes OSS possible -- from the programmers and QA testers to the advocacy groups and spokespeople. (and the large corporations backing Open Source)
Well, here's my opinion, anyway.
The Unix philosophy: build tools which do one or a few things very well (and are trivial to develop, debug, and maintain) and build upon them.
I have yet to detect anything resembling a philosophy in the 'other' place. It seems to be build a single big-ass swiss army knife application (which doesn't seem to do anything very well).
Ads are broken.
Close. Microsoft makes something which runs like and O/S, but includes massive amounts of code for things you may never use, but fill up the disk and memory anyway. It's like the joke that inside every fat person is a skinny person trying to get out, but with Windows there's a bloated pile of software smothering an operating system.
A feeling of having made the same mistake before: Deja Foobar
This article articulates very well the opinion I've come to hold, since being network and sys admin for about 300 Solaris and 2 or 300 NT machines for about 4 years.
My point of contention is that Microsoft built its legacy on home users, and "amatuer" (for lack of a better adjective) operating systems. Sun, HP and the other enterprise OS companies built it for business. I pitty anyone who relies on M$ servers for their bread and butter. I was talking to a DB manager for a M$ shop, that manages 7 terabytes of data. I complained how we had to bounce Oracle about once a month, and it was always the middleware failing. He laughed, and said, "We have to reboot the M$ DB _daily_ and reboot the whole machine". We only had to restart the middleware processes (e.g. ps -ef | grep middlware....kill ...and the processes would automatically kick back off) and were back up and running in seconds, without affecting other DB processes on the box running.
This speaks volumes.
Those who don't know any better will keep their opinions for their own camp (either M$ or *nix) and those who've been on both sides are probably too busy to weigh in here anyway. (I'm out of it now, so I have more time :-)
John
Innovative? I'd have to say Linux's strength is that it isn't innovative in its design. It instead replicates tried and accepted OS paradigms. It's monolithic (although that's changing. Although it definitely isn't a microkernel like OSX or Hurd), it eschews object orientated programming, etc. OTOH NT and all of its derivatives do try to absorb some of those features; exponentially increasing its complexity (and resulting in all of those pitfalls). In some ways its a 16 part screwdriver.
Innovation in technology isn't necessarily a great thing. For every Macintosh you have your NeXT. Heck, even the Mac was just derivative of PARC's work. Linux plays it conservative and just does what it does.
What is music when you despise all sound?
One has adherents that are noisy, abusive, close-minded, stubborn, silly and the other- oh, wait a minute...
--- Ban humanity.
The rest of it, the "Lunix never crashes because of open-source!" I don't especially buy into.
What I'm listening to now on Pandora...
" MicroSoft makes an OS to make money, Linux is designed to be an effective OS"
Why do you assume making money and making an effective OS are mutually exclusive?
Vote for Pedro
For non-trivial things, though, I have scads of problems just like the grandparent. He's right: the key difference between Windows and Linux is ease of hardware and software installation. Time and again I have problems with dependencies and searching down different versions of this or that library, or circular reference dependency problems such as MySQL needs Perl which needs MySQL-DBI which can't be installed without MySQL. Or trying to get a real video card working, and having XFree ask you 100 questions about your monitor frequencies, only to finally barf to text mode when it's show time.
Many things are wonderful and easy in Linux, but installing hardware and software is 50 times as difficult in Linux as it is in Windows.
So, what's really the difference between a Unix variant like Linux and any Windows OS? It's that Microsoft reacts to marketing pressure to make design decisions favoring running a few processes faster but then finds itself forced first to layer in backward compatibility and then to engage in a patch-and-kludge upgrade process until the code becomes so bloated, slow and unreliable that wholesale replacement is again called for.
1. You'd think a journalist could write a more coherent and jargon-free paragraph, but maybe that's just me?
2. Asking what Windows vs. *nix does different is too broad. You can ask this question literally forver - if you keep abstracting down further and futher. Once again, vague journalism.
3. Ok, you can flame me (as if I would deny you that) but I don't think Linux zealots are in any position to say that windows is any less bloated than Linux. Mandrake 10.0 community from just yesterday's is 2.1 gigabytes (re: torrent), most of which is unnecessary for 95% use. Suppose I manage to start the install from CD1 without having CD2 or CD3, well I *hope* there's not a package required by default that is on CD2 or CD3.
4. Microsoft runs a few processes faster and others slower? I think he needs to define what he means by processes. Because I dont think he's using the same terminology as the rest of us when we say 'process'. Once again, too vague.
until the code becomes so bloated, slow and unreliable
5. Is the code bloated, or are the features bloated? Or are the features bloated and the code that composes those features bloated? Once again, too much abstraction.
I think I'll stop here.
Let's not begin the quarrel of which OS has the ~better~ GUI. The point is that although a GUI can be well-designed, it will by its very nature be a greater burden on the OS than a command typed at the prompt. It's a performance burden, it's a design burden, it's a maintenance burden for the development team. (Axiom: The more complex software becomes, the less even its creators and maintainers understand it.) Eventually it produces a Support burden because users know dulcet coital nothing about their computers.
Then bring in the Internet. Make it very popular. Hell, make it commercial. People are learning that you can get things done quickly with Linux. UNIX was networking when Bill Gates was battling pimples.
Linux builds on the better tradition. So it's not just the cost, but the design philosophy of Linux that is beating Windows.
Rich And Stupid is not so bad as Working For Rich And Stupid.
My comment is mostly for the beanie-heads who are newer to Slashdot than us dyed-in-the-keyboard vets of many computers, so forgive me by driving home the obvious.
An operating system is an operating system is an operating system is an operating system. It's only purpose is to provide you, the user, a human-readable interface and control system for the computer's hardware and software.
How Linux, other UNIXen, and Windows handle this, however, is the big question to me when someone asks me the question that the article posed.
Applications designed for Windows are just that--developers typically use programming tools that create apps which are hardware-and-operating-system-specific. Barring an emulator such as Virtual PC (funny, that's owned now by Microsoft, too), Windows applications simply will not operate unless it has a conventional Intel-style PC hardware architecture running a specific flavor of Windows. And nope, your 16-bit Windows apps will likely break in Windows XP, so you have to hunt and peck for the app that works in the OS you have.
The UNIX family has things differently. UNIX-family applications are frequently hardware-agnostic and non-operating system-specific. You could be running Solaris, or FreeBSD, or Mandrake, or SuSE, or Darwin, or Mac OS X--generally, the code just works. (Plenty of exceptions, like OpenOffice ports to Mac OS X, but a version does work now in OS X's X11 environment, to take an example.)
Where you would walk into a computer store to buy Windows software, a *NIX user could download the source code for an application and compile it, or build it to work for their particular operating system and platform. Of course, we could buy the source code from a store as well, or the binaries for our platform, if a software maker distributed most of the UNIX software in that format. Currently, the inability of a home Linux user to visit CompUSA for the latest UNIX application is among the greatest challenges to *NIX as a popular home desktop OS (Mac OS X's inroads notwithstanding).
Nevertheless, I can download most BSD and many UNIX and Linux source code from my Mac OS X (BSD variant) workstations, compile it, and use it, without problem or complant. Windows users generally aren't compiling squat--they have to buy or find the already-assembled binaries that run within Windows--and pray that those versions of the binaries were compiled with their Windows version (and patch version, and service pack version) in mind.
The best example of a well-written application that doesn't particularly care about platform (at least in terms of its data files--binaries must still be obtained) is BioWare's Neverwinter Nights game series. It works on Windows, Mac OS X, and Linux. While the two expansion packs for the original game haven't yet been released in an official Mac version yet, because BioWare designed the game's data to be platform-agnostic, many impatient Mac users have figured out. without a lot of hassle, how to install the game expansions using the Linux versions of the games.
Windows is a proprietary operating system, and any applications written for it feed into that mold. The UNIX world is literally open in its design and flexibility. Don't confuse "open" for "Open Source," however--that's another (related) story.
Vos teneo officium eram periculosus ut vos recipero is.
On the other hand, my ex girlfriend sent me a screensaver she made with photos and video clips on Mac OSX (another unix varient), and lemme tell ya, she is no 1337 "power user". As outrageous as it sounds, I sometimes I think we give Windows a little too much credit in the usability department.
"You know why you do not see me styling wit my homies? Because I have no homies!!" -Mojo Jojo
"Ease of hardware integration" is not Windows. That's the vendors. If anything the hardware vendors have a harder time creating new versions of drivers for each release of Windows than each major release of Linux.
As for ease of use, that's arguable. I've used Windows since 3.0 and find the continually changing and inconsistant user interface frustrating. I find Linux much much easier to use on a regular basis.
Developers: We can use your help.
If you don't like Gnome or KDE, run fvwm or WindowMaker or
some other lean WM. Just because some distros come with large
desktop environments by default doesn't mean you need to
use them.
*sigh* back to work...
You can't tell me that Linux is easier to use and install hardware drivers for than Windows.
As many people will attest, Linux works quite well out of the box. I think you are refering to the fact that hardware manufacturers often write WinXX drivers but not Linux drivers; this is entirely a market share decision, based on limited developer time. Windows, natively, does not support hardware better than Linux. I would argue Linux does, because I have gotten far more random BSOD's from Windows. One of my biggest complaints with Win2k was how sloooooow it got as I added additional hardware. Linux was not as easily encumbered.
While I know that we are all Windows haters it does do quite a few things rather well. It isn't used by so many people because it is *completely* inferior. It serves its purpose.
I don't think it does anything "rather well"; it does the bare minimum. People have accepted Windows' flaws because they have to, but the flaws are tremendous.
The reason WinXX is so popular is primarily because of marketing; it wasn't "better" than OS/2, it was better marketed. Over time, people who did not use computers ran Microsoft software because that was what came loaded on OEM boxes. OEM's loaded Microsoft software because that is what people wanted for compatibility with their friends. It had nothing to do with Windows being a better product.
Someone asked if I had patched against MSBlast; I said yes, I installed Linux.
Yes, in Linux it's either it works out of the box, you download and COMPILE something and it works well thereafter, or it just doesn't work at all.
...but that's just because it is in the manufacturer's interest to support windows in some way or another. Even if the support for your version of windows is pretty crappy.
:( I was a little peeved, but managed to figure out how to get it working by downloading some rather new drivers and compiling, but that's kind of a rare case... then there is the printer I bought last year BECAUSE OF THE PENGUIN ON THE BOX! (can you tell I'm still peeved about that one?) ...a Lexmark Z55, again it came with drivers that only work in a handful of Linux versions and on the website they don't even provide the option to get drivers that are generic.. after fighting with it for a long time I bought an HP printer and it worked out of the box, no driver install needed (just emerge cups on my gentoo box and away I went.)
In windows there are many more levels, but fewer pieces of hardware in the Just doesn't work at all category.
I remember buying a server once that was designed for Linux use and trying to upgrade from Mandrake 7.2 to 8.0 I think it was, and finding that the driver for the disk controller only existed in binary form on the install disks and that only worked with the kernels in Redhat 6.2
*Practically* speaking, that's a crap argument. I haven't seen any linux distros installing libc5 support by default recently. Which means old libc5 apps won't run (unless they happened to be statically linked). I even seem to recall some pain in the glibc 2.0->2.1 transition. Or how about trying to install some older rpms on a shiny new distribution? It's about a 50-50 shot that it works.
Microsoft has to rewrite large portions of windows code to take on new features, which make it incompatible with older software.
The larger problem is that backwards compatability seems to be directly proportional to bloat. Microsoft's problem is that since they aren't a "distribution" per se, they can't even attempt to fix all your executables to use new libraries as they're developed. And then when they (finally) remove or fix obsolete/broken libraries anyway, shit breaks. Then they get blamed for 'intentionally' breaking other vendors' programs. It isn't actually their fault (..sometimes).
Really, I always thought MS bent over backwards to err on the side of "bloat" whenever possible. Which is why you have the DOS virtual machine and the win16 API etc.
Also if you expect us to believe that after 4 months the machine can't run IE and this is a windows problem, ummm...your on crack, none of us would put up with windows if it completely failed after just a few months. Some of these office machines here at work, are used every day, and are 2 years old, running XP, with end users, lol, and they really are still doing just fine.
Of course I regularly run updates, and my virus scanner updates hourly and runs nightly, but you should do that with any PC.
Anonymous Cowards - Oh God, How I hate you
" ... Given that one is clearly not the same as the other, the real question is, "Why is making money and making an effective OS the same?" ..."
The article speaks quite a bit about how Microsoft if forced to build in back-compatibility in an inefficient manner. Every OS has to deal with back-compatibility to a certain extent, but consider how much more important it is to a company like Microsoft.
They have a business model that could easily be described as based on market share with both business users and home users "feeding" each other's compatibility needs. The business user many be more reluctant to upgrade than the home user because reliability, transition problems and cost have different consequences for both types, yet both have large numbers of current and legacy OS users.
Consider Linux. Upgrade issues remain, but cost is negligible with home users and can be attractive (or not; depends on too many things) to business users as well. However the OS itself (with the more modern code) is available and access to the software itself is not a significant cost issue. Thus, no absolute need for "kludges" to keep older OS's ( or more typically older paid programs from other vendors) running, while a significant number of truly ancient CPUs can also run an effective, compatible "family" *NIX Operating System and necessary software.
Microsoft got where it is on marketshare; it's maintaining it's current income on marketshare, and it pegs it's future on marketshare. It drives every effort from code to sales to lobbying. That marketshare requires users to implicitly agree to paid upgrades of MS and third party software.
Although a given Linux distro does have marketshare interests, a user that switches to a competitive Linux distro is not the end of the world; potential new users far exceed current users, the user hasn't really changed his way of working, and hasn't invested in new hardware. He's still there for future growth.
I think the cost of upgrading of the two OS's plays a significant role in the way they are coded, designed, and implemented. Linux advocates may be just a little blind to it, because it's not a consideration that drives the development process; Microsoft's corporate coders can never lose sight of it, and it does drive the code, design, and implementation.
To the login prompt is 42 seconds. After the login prompt is about one minute 12 seconds, but not really windows fault, it has to update my files with server using active directory remote profiles, load up a real time virus scanner, load all of my network drives, load my calendar, and acrotray which is for the full version of adobe acrobat 6. I also offer that this build is only 2 months old, because I recently got this computer as an upgrade to a Pentium 3 1133. I built it myself, and could give you an exact part listing, but as for the OS install, I didn't do anything special, formatted the whole drive as one partition, ran through the install, ran all the updates, and added the system to the domain. ??? Works fantastic. and I have all XP machines here and ussually if we have a problem it when XP has to deal with running a program designed for like windows 95. and still uses hard coded LPTs for printing purposes. But other than that, I run a clean network, I do spam and virus detection at the email server, preventing worms from getting opened in email. And all in all, few problems.
This isn't a troll, I am just seriously tired of this constant anti windows shit, I think it's mostly based on the older OSs NT, and 98, but since 2000 I feel they have been doing a superb job, and when I bought XP pro moving from 2000 I really liked the upgrade.
I used to use a SGI for autocad, but then we moved to dual Proc Dells, and I really liked it. I do still use Linux, for my e-mail, and web server at home, but only because I didn't want to buy 2000 server, and I thought Linux works well as a server. Personally I used it as a desktop for years, but constant kernel updates, and having to compile every damn thing before I could use it, turned me off. THe linux community should learn to offer binary executables and source because I simply just don't like the hassle of the extra step.
Here comes the mod down. and there is nothing I can do about it. People hate me for my opinion, but I can't be like most of the people here, claim to hate windows and promote linux, but secretly use XP all the time.
Anonymous Cowards - Oh God, How I hate you
But the real point: why the eff should you have to have "scheduled reboots" at all?! YOU SHOULDN'T.
like a scanner
or a printer
or a pen tablet
etc etc
windows: go to mfr website, download install file, run install file, (maybe) reboot. Proceed with using hardware.
Linux: go to mfr website...unsupported (dam), go to linux geek site(s)...hmmm no luck, go to google...hmm no luck, go to another linux site - helpful geek says "just download this source, read your device specs, change these numbers accordingly, compile to your kernel with this line: (insert big ass command line here) and you should be ok; tries it...works partially (not all features utilized or available). crap. *heavy sigh* *gives up*
user boots to windows...
Is the juice worth the sqeeze?
having to compile every damn thing before I could use it, turned me off. THe linux community should learn to offer binary executables and source because I simply just don't like the hassle of the extra step.
What are you blethering about? Provision of binary executables is the purpose of GNU/Linux distributions.
I have not run Windows at home for about five years, and I don't miss it in the slightest. I have a server for NFS, web, mail and other bits and bobs. I have an IBM Thinkpad which is my main work horse. I have an ancient Toshiba Libretto hooked up to my amplifier for playing music.
All of these run Debian. I can't remember the last thing I had to compile by hand; Debian has so many packages prebuilt that I rarely have to build something myself. Either it's already there, or something else is there that does the same job.
If I do need to compile somthing, Debian ensures I don't end up in dependency hell because almost all Free libraries are packaged. I grant you - RedHat used to be a pain. Trying to compile an up-to-date Gnome 1.0 for RedHat 5.1 was the last straw that switched me over to a distro built by it's users. But I'm pretty sure RedHat is much better these days anyway.
My day job desktop is Windows NT 4.0 SP6 and I get through the day but it can hardly be called convenient. It's so lowest-common-dominator that I end up installing all sorts of utilities that are missed out in the shipped OS. I fear Windows XP because I don't want to work in a cartoon.
And finally, I bathe in the warmth of the freedom of GNU/Linux. I don't have to invoke it much, but I know that if I do have to, I can get the source and fix it. Thanks Linus, RMS, et al.
Yours Sincerely, Michael.
My network card drivers were source only, my drivers I recieved for my sound card were source I had to compile and then it didn't support digital audio, Ummm...actually only a few things didn't come as source.
And if you haven't run windows in 5 years, you really wouldn't miss it, because you can't even comprehend how far its come.
That's like saying, I had a 386PC it wasn't very fast so I am sticking to my Dual Processor G5, it's much faster. Your comparing oranges, to old apples, you bought 4 years ago. Maybe you should try a nice K7 Athlon system running XP, even from 2000 to XP, the OS came a long way.
Anonymous Cowards - Oh God, How I hate you