B00tDisk wrote:
Firstly, there's so many cries of "Well, I've got windows running on xyz processor. It crashes. It's junk." or "Well, windows was running until I installed 'xyz', then it totally crashed and I had to reformat and reinstall."
My keyboard died and I had to do a hardware reset.. and Boom.. Windows2k didn't boot anymore. A good OS shouldn't be able to be destroyed that easily.
Having done PC support and network administration for a few years, I can't take statements like that at face value. That's like saying "I was driving down the road and suddenly my car was sitting in the junkyard, wrecked. Man, those 'xyz' manufactured cars suck!"
The analogy with the car and my experience above would be something like a got a flat tire had to turn of the engine. When I changed tyre and tried to start the car it just didn't start anymore

That doesn't mean buying Crucial RAM (although it helps), but know what kind of gear you're putting together. If you can spend $120 on an AMD CPU, then save your pennies and spend the money on a decent motherboard (Asus and Abit are particularly well-regarded). Don't buy no-name junk with unsigned drivers. Buying a NIC? Skip over that $5 card and spend the extra money on, say, a Netgear or Linksys. One of the worst problems with XP I had was due to a bad NIC driver - buffer overflows would cause the damned system to reboot! Swapped it out, put a $15 Netgear in place of that SunshineRainbowFarEastRicePaper piece of crap card and presto! No more issues.
True some hardware is flaky, and really cheap stuff should be avoided. But sometimes good brand name hardware isn't much better anyway. And when Linux can run stable on the same hardware that Win2k can't run stable on.. then it can't be a hardware fault.
Actually I don't find win2k particularly unstable.. it's quite stable and I'm pretty satisfied with it. But the times that it do crash I'm afraid that it will not start again. Something that I don't have to worry about with Linux or AmigaOS.
Secondly...the issue of RAM and HD footprint? I think we can all agree here that despite the "bloat", WindowsXP or 2000 can easily fit on a 5gb HD, right? And run well enough with 128mb of physical RAM, correct?
Yes, but with 128MB you better have a fast harddrive. And still 64-128MB for just running the OS is bloat in my book, but Linux is quite bloated also when you want to use a decent gui. Doesn't matter that RAM and HD's are cheap.. an OS shouldn't require that amount of RAM. The OS can't be very well optimized when it uses that kind of memory footprint.
Which brings us to the ridiculous subject of "boot times" or "response times".
Guys, the "issue" of OS size and RAM requirements is nonexistent. RAM and HD space are commodity items. This isn't the days of 5MB fullheight MFM drives anymore. Incidentally, you can install a stripped down XP or 2000 on a 1gb HD...
And that is exactly the kind of attitude among programmers that leads to bloat and unoptimized software. RAM and HD is cheap so who cares if it's optimized. Just let people buy more RAM and better CPU's.
Not "you don't do as much with it", but it in and of itself doesn't do as much. Take 3.1*, out of the box, and tell me how you network it with other systems. Tell me how you set it up to have a static IP or use DHCP. Tell me how USB classes work under it.
Still I can have AmigaOS with MiamiDx, Poseidon (for USB), Turboprint, Apache Web-server all running at startup and still it takes less than 15 seconds to boot. AmigaOS is really efficent and so are all it's programs. Which gives even greater speeds when run on something like a MorphOS/AOS v4 box with a G3@600Mhz
But with Win2k it takes ages to boot. WinXP is alot faster at boot, although it's nowhere near the AmigaOS boot times.
And with AmigaOS just press the power button when you want to turn off the computer. No ridiculous shutdown stuff.