@mitch074:
"As early as 2005 I had a 3D desktop.."
That's awesome! How many config files did you have to manually edit to get 3d desktop to function the way you wanted?
Short answer: none. Suse had it set up with a GUI option, Mandriva's drak3D application (with an icon in its GUI) did it for me, installing all dependencies: a logoff then back on (no reboot) enabled it. Moving on.
"...administrator prompts that popped only when administrative tasks really had to be performed (and it popped only once for a given task, without disrupting what I was doing at the time)"
Windows UAC in Vista was a PITA, I'll grant you that. However, in a business environment, as well as home, there is a lovely thing called "Group Policy" and it's editor. A wonderful GUI for manipulating pretty much every aspect of the user and computing experience. In a Windows environment it's a must have, and I've yet to see it's equal on any *nix computing platform. Back to those config files!
Nice thing with config files: I can back them up, copy them to a machine through ssh, and be done with it. But we weren't discussing business environments (where Conficker is costing quite a lot these days), we were discussing a single machine's management policies: not everybody has a LAN with Windows Server at home.
Not sure why this is a big deal, tabbed browsers have been available on the Windows platform for ages
In 2005, IE's market share was above 80% (80-20 rule), on every major IE update there was a chance the default browser would be overwritten (both protocols and MIME types registrations), many applications hot-linked iexplore.exe - so even those knowledgeable enough couldn't do without IE 6.
No one would have complained about a monopoly thingie: there was already the capability for Windows to use its network stack (ported from BSD) as firewall (cf. Windows 2000 connection sharing), but there was no GUI, it was hardly documented, and there was also no config file. Go and dabble with the Registry to configure it! Yay.
Yes, the *nix CLI is very robust, but the Windows CLI is also very robust especially in Windows Server versions. Anyone who has done ANY Windows Server administration would know this, apparently you don't. Rebooting for updates also happens on the Linux platform (I know, I've run Ubuntu, Debian, and Mandrake) so what's the big deal exactly? Complete re-install everytime a piece of h/w is changed? What kind of fantasyland do you live in again? 10 min boots? LOL
You use Windows Server for your home computer? Wow! Moreover, I can drive the whole system from the console. Windows' CLI can't, yet (they sure are trying, I'll grant you that).
You haven't used a Linux OS for a while, I see - currently, reboots are required for kernel and glibc updates, and _that's_it_ (most others would need a logoff, not a reboot). New hardware is supported without a reboot - Linux can even handle a CPU and RAM hotswap! Can Windows do that? No. Last time I installed a webcam in Vista, I had to reboot it thrice: once to load the driver, another to actually plug the cam in, and a last time to manually force the driver's install because the WHQL cert had thrown a fit. The same webcam, on Linux, worked ten seconds after it was plugged in. Same thing for wifi keys, scans, sound devices... And yes, 10 minutes boot in Vista: a friend's machine, with 512 Mb of RAM, nothing installed but a free antivirus, took (we both timed it) 14 minutes to boot. It was fresh from the factory, and I had removed most of the trashware. After I disabled most network services, disabled background indexing and defragging, most "system helpers" and a few autostarting knick-knacks, I managed to make it boot in 2min32s (end of activity cursor). On that very same machine, Ubuntu boots in 35 seconds, login included.
Even if Windows crapped it's registry big time there are a MULTITUDE of recovery options (booting to the Windows DVD, Recovery Console, Ultimate boot CD, and MORE) that get your system back up and working without a "backup, format, and reinstall". Get a clue please.
Don't you think I tried all these? And how about a user registry's corruption, which still happens? The WinDVD won't catch that (it resets SYSTEM hives), the Recovery console ditto (and scrapping a user's registry, yay settings!), UBCD will require editing the registry by hand (it's no automatic solution), and dabbling with the Registry's HEX values ain't my idea for graceful recovery. Backing up a user's config files, UID and GID and restoring those, however, is mighty easy: if one config file gets dirty, I don't have to scrap the lot.
Nice troll, get back under your bridge now.
There, you start with insults because I used irony to turn your own sentence on you. Who's the troll?
"I really can't understand why people are so reluctant to embrace new technology."
I will repeat a great statement I heard made about linux "Linux is only great if your time is worthless."
I guess you get paid a lot to rescue all those Windows boxes - time is money, that's for sure. Me, my responsibility is towards my coworkers to allow them to work. Eventhough restoring a backup image wasn't too long, simply logging on through ssh, sending a couple commands on their machines and fix their troubles while they work on something else on their own machine is valuable. And for me, I enjoy not having to keep an eye on my machine to ensure it hasn't been compromised, that the drives aren't getting fragmented, that the AV is up to date, that the spyware o' the month isn't making my installed but unused browser, or installed but unused media player, or installed but unused IM software into Swiss cheese.
I also enjoy a network where all legitimate IP packets, even those coming from NetBIOS and CIFS, are well-formed - something that no Windows version yet has managed to produce. That makes preventing attacks quite a lot easier: just drop badly formed packets.