First off, I agree regarding the admin protection dialogs; however, three points: 1) these dialogs and the whole model should be significantly cleaned up by release; 2) this is the only real option; and 3) they may get bit if they don't require a user name and password. Consider the method used by some other OSes (OS X, and some Linux distros): when you elevate to admin access, in some situations, you've opened yourself up to malicious attack for a given period of time, rather than until the desired function/task is finished. Microsoft's model is more annoying, but it closes a significant security hole. However, because people blindly click through dialogs without reading them, they can put as many prompts in the way as they want, and people will just click through until they go away. It's only when they have to enter their user name and password that they will think twice.
Honestly, though, I find myself paying less and less attention to Paul's take on things. Personally, I feel that he (along with much of the tech media) tends to review Windows almost strictly from a consumer mindset, and furthermore, always through the prism of OS X. He puts his focus on the built-in apps, and only covers the technology "guts" on a very superficial level. I think that is a mistake. The OS X model and ecosystem is wholly different than that of Windows. For example, the most popular mail app on Windows is Outlook--not anything built into Windows. It's not a moot point necessarily, but it is of questionable value to compare how the "Windows email client" compares to the one in OS X.
As I see it, the mistake Paul makes is a mistake of perspective, or rather, approach. Certainly, most business customers aren't approaching new versions of Windows comparing it OS X, but of an older version of Windows. Moreover, they aren't approaching it from the perspective of Windows alone, but a whole ecosystem made up of Windows, a host of applications, and a lot of years of user experience. Do they really care how it compares to OS X? Not in a practical sense; perphaps the enthusiast pays attention, but even then, for most it rarely weighs in on their decision.
Even on the consumer side, I think Paul makes a mistake in paying too much attention to built-in apps, and not enough on built-in platform technology. Microsoft has always rather conservatively chosen what it develops for built-in apps, mostly leaving it up to partners and other 3rd parties. I agree, Vista's DVD application is pointless (so far), but in two ways: it's pointless in that it's hopelessly hobbled, but also because no one probably cares--you'll get a better DVD application pre-installed with the PC, or it will come with the DVD burner, or whatever. That model is certainly something for debate, but debating the merits of the Vista DVD application itself is probably not that worthwhile. I realize it's an evaluation of Windows alone, but it's probably not worth getting too bent out of shape over what are probably irrelevant shortcomings in reality.
What is really disappointing, though, is that Paul rarely digs below the GUI and application level, and even if he does, it seems like lip service. For example, look at the threading model available in Windows vs. that of OS X--there is no comparison. OS X is seriously deficient in this area, and I've not once heard it mentioned in any tech media article. This will become more and more important and apparent as processor manufacturers turn to multicore designs to increase performance. Look at Group Policy... look at Remote Desktop (particularly the performance)... look at the .NET Framework... look at the very fine-grained file permissions... look at the true 64-bit support... look at the new networking stack... the list goes on and on.
|