Well Registry Bloats, aging related slowdowns, boat load of apps in Start Menu is all old windows speak (pre XP era).
You are incorrect, but read on...
Today having ton of stuff in Start Menu is no big deal - just press Windows key and type first letter of what you are looking for and you are done.
I never had trouble finding my apps (duh!). The problem is that those apps add countless numbers of registry entries and DLLs.
Slow startup ? Really that is a problem with Win Vista/7? Did you know that services start in parallel, and that many tasks are started in the background, returning control to the user much sooner than previous versions of Windows.
Google Search for "Windows 7" "Slow boot" results in about 34,000 results
You understand that if people install crap applications that hog resources on startup it is not Windows' fault firstly and secondly it is easily fixable. Just disable those things that you don't need to be available on startup. Msconfig is the name. And for a technical person few clicks shouldn't be a big deal.
Yeah, right. Every trojan horse and piece of malware is listed there, too, right? What you're not getting is that there are like a half dozen different means that an application can force itself to load at boot time and they are not all listed and controlled by MSConfig. Take a look at the old program Startup Cop that lists the many places that an app can start.
But you're still missing it: It's often nearly impossible to tell what's hogging resources during startup. It's not like you can bring up Task Manager before Window starts. And even if you do manage to discover what's taking so long, do you know that the "uninstall" will remove all registry entries, all files that it's added to the system directories, and all processes that it invokes upon startup? Do you know that it will return to stock all system settings that it modified? No.
I thought you were going to make technical arguments against windows (memory management sucks, File IO is slow etc.) but you look like you want to stick to either old or irrelevant complaints routinely regurgitated and misinterpreted by clueless folks.
Your lack of knowledge and comprehension is not my problem. Discussions of fragmentation of registry and swap files, registry bloat, and architectural flaws (e.g., apps writing to system directories) are technical. You, on the other hand, seem to want to argue that it's 'good enough' because it's popular.
AidenShaw said:
fmaxwell said:
At the architecture level, Windows NT (the grandaddy of the current generation of Windows) tried to graft a security policy onto an unsecured OS (Windows 3.x/95) while minimizing application breakage.
This is just so wrong it's sad.
No, it is not wrong so stop spreading misinformation.
AidenShaw said:
Windows NT was a clean-slate operating system
No it is not. If it was, every app that worked on Windows 95 would have been incompatible with Windows NT. You would have tried to install Word and the OS would have failed as if you had tried to install a Solaris, Unix, or AmigaOS application.
AidenShaw said:
To imply that NT is based on Windows 3.x is silly. (And to imply that it is based on Windows 95 which shipped 3 years after NT was shipping is absurd.)
Based on does not mean that it had the same code base. Microsoft hired a DEC engineer (Dave Cutler), one of the chief architects of the VAX VMS operating system, to come up with a new version of Windows that, among other things, added a security policy while still allowing the same apps that ran on Windows 3.x to run on Windows NT 3.1. That's why NT had two different APIs: Win16 and Win32. The NT Win32 API was then back-ported to Windows Chicago in the Windows 95 release. It supported Win16 apps through a mechanism called "thunking"
What they should have done is start over and not tried to maintain compatability between the old 16 bit versions of Windows, which had no security, and the new Windows NT. This was their chance to come up with a comprehensive, clear security policy such as had been implemented in Unix years earlier. Any app that tried to write to an OS directory (e.g., C:\WinNT\*) should have immediately failed. Instead, they made the massively overcomplicated mess that has evolved into Windows 7.
See, I actually ran Windows NT 3.1, 3.51, and 4.0 when they came out, following the development and architecture closely as they evolved. So if you think I'm wrong about something, just ask and I can clear things up.
AidenShaw said:
Also didn't go through the list of Apple "fails" when comparing a little "Windows Home Server" appliance to "Time Machine".
Such as the fact that Windows Home Server is a joke? Hook up a USB, Firewire, or ESATA drive to a Mac and it asks if you want to use it for Time Machine. You say yes, and off it goes. No network traffic or bottlenecks. If you want more speed (as I do), tell OS X to use a pair of RAIDed internal SATA drives for Time Machine. I just bought a pair of 2TB Samsung green drives to use for my Time Machine backup. I paid $99.99 each and installed them in my Mac Pro. How much would it cost me to use them in a Windows Home Server to do my backup? Maybe the cost of the whole Windows Home Server PC, plus the cost of the electricity to run it?
I've migrated my user space to three different Windows installations in the past few years. It started off on Vista Ultimate and then to Windows 7 Beta/RC. Once I got my copy of 7 Final I migrated to that.
I've done that multiple times. Usually takes about a week to get things right again. Just do a clean install of Windows and then migrate all of your applications, settings, and files there. Let me know how it works out for you.
Hell, even Microsoft was telling most people that a Windows 7 "upgrade" would mean backing up their files, wiping their hard drives, reinstalling all of their apps, redoing all of their app settings, and restoring their files.