Originally Posted by dacloo
I disagree that it feels like a toy. It's a very responsive system in general, more responsive than MacOS which has quite some delays even with 2GB of memory. Also file management is far more effective.
I agreed with you on the former, (as long as you don't tax the poor thing - OS X is much better at handling a couple dozen open apps at once) but whaaaa? File mgmt is *effective*? How so? There's no rhyme nor reason to the where things go on the disk. It's like dealing with Mac OS9 in that regards, but without the obvious clues as to why things are where they are. User accounts are obviously an after-thought, and it feels even worse at trying to hide 'the real disk' from you than even OS9 did.
Or are you speaking of moving files around?
They both give a different experience, I think it's easy to bash OS #1 and praise OS #2.
Every OS has issues, and problems, no doubt. What I'm talking about is the complete lack of craftsmanship and attention to detail that I run into in XP on a daily basis. It *feels* like something slapped together by committee, without a unified design plan. For instance...
I read a review of Vista that said that Windows (XP an Vista both) is like a hyper 3 yr old, endlessly wanting to make sure you know how helpful they are, and apparently terrified you might forget that they're there, while MacOS X is like a gentleman's gentleman, standing silently on the side until an opportunity for assistance is noted, given, and then shrugged off as simply business as normal. I couldn't agree more. I am constantly barraged by notices on my XP laptop that serve zero useful purpose. My favorite one on Friday was plugging in a USB 2.0 USB key, and having it tell me 1) New hardware had been detected. 2) New hardware was now ready for use. 3) The USB device would work faster if plugged into a USB 2.0 port.
1) Thank you for stating the obvious - it should always be detected. I would not expect you to tell me that a key on my keyboard had been pressed every time I did it, nor would I expect this. Unless the standard situation is that hardware is *not* detected, ie, it fails, then this shouldn't be a notification. Notify me when the unexpected occurs, not when things are as normal. The fact that anyone thought this was a necessary notification puts a chill up my spine. It reads like something you have in there while you're debugging, and don't expect it to work.
2) How very odd. You said it was detected, then you make a second notice to tell me it's ready... why not just... let me use it? Bring up an Explorer window showing the data device, or otherwise give me *any* visual feedback that it has been mounted? To be fair, it does bring up a dialog asking how I want to interact with the data device, giving me a list of possibilities like "View pictures as slideshow", and in there is "View device in Explorer". This just strikes me as that hyper 3 yr old again though - the tools to show slideshows, etc, are already in Explorer, (and *very* prominent in that silly task bar on the left, I might add,) so why add an unnecessary barrier to interacting with the device I just plugged in? Note also that *any* feedback here, even the original notification, makes the notice in #1 utterly superfluous.
3) Here's the icing on the cake. Okay, this is kind of useful, in a way, even though most users won't have a clue what it means. I think to myself "Ok, so there's a USB1.x bus, and a USB 2.0 bus on this machine. Common enough. But I only saw two USB ports... hmm..." Into the Hardware panel I go, and find out... the machine *has no USB 2.0 ports*. So please, explain why it gave me the useless notice? Can't the OS tell what hardware it has underneath?
It's precisely this sort of thing that drives me nuts. It's just a complete lack of attention to detail in places that matter, leading to an explosion of semi-useful or downright false information being thrown at the user. I don't care if it's a computer, a car, or any other kind of tool, lack of design detail makes my brain boil over.
And that's just the user experience. As a developer, it's much, much worse.