A Windows weakness
Thinking like a Mac-user again, I came up with this.
If, in Windows XP, the Desktop is, as it is in Mac OS X, a legitimate and discrete folder, then why, when one has "Command Prompt Here" and "Terminal Here" type patches to their context menu, is one unable to use them by simply right-clicking on some unoccupied space in the Explorer Desktop? Why, indeed, does one have to follow the monotonous path of "My Computer/C/Documents and Settings/[username]"*, click on the Desktop folder in that window, and then right-click to engage one of these shell-here add-ons?
This, I hold, is a weakness, a flaw, more proof that going it alone with a proprietary foundation for one's operating system, as if holding out for a happy ending that, friends, will never arrive, mark my words, makes Microsoft look even worse than they already do in the eyes of "bright people" (to borrow a turn of phrase from my Steve Jobs limerick).
If Mr Gates loves the Mac OS so much, as we heard almost once a year from the time of the beginning of M$'s DoJ troubles until well after Windows XP was rolled out, then perhaps he can concede that the wisdom of clicking to engage a shell prompt in a place where the contents of a folder are actually visible is a far more user-friendly way of going about the thing than insisting that the hypothetical user click where they can't see the contents.
Ah, me. Maybe the Net gods will be kind someday and drop a Mac Book Pro in my lap, if only to shut me the hell up.
BZT
*The Windows path delineation slash, or "whack", is a backwhack, so far as I am concerned. I don't use it unless I absolutely have to.
If, in Windows XP, the Desktop is, as it is in Mac OS X, a legitimate and discrete folder, then why, when one has "Command Prompt Here" and "Terminal Here" type patches to their context menu, is one unable to use them by simply right-clicking on some unoccupied space in the Explorer Desktop? Why, indeed, does one have to follow the monotonous path of "My Computer/C/Documents and Settings/[username]"*, click on the Desktop folder in that window, and then right-click to engage one of these shell-here add-ons?
This, I hold, is a weakness, a flaw, more proof that going it alone with a proprietary foundation for one's operating system, as if holding out for a happy ending that, friends, will never arrive, mark my words, makes Microsoft look even worse than they already do in the eyes of "bright people" (to borrow a turn of phrase from my Steve Jobs limerick).
If Mr Gates loves the Mac OS so much, as we heard almost once a year from the time of the beginning of M$'s DoJ troubles until well after Windows XP was rolled out, then perhaps he can concede that the wisdom of clicking to engage a shell prompt in a place where the contents of a folder are actually visible is a far more user-friendly way of going about the thing than insisting that the hypothetical user click where they can't see the contents.
Ah, me. Maybe the Net gods will be kind someday and drop a Mac Book Pro in my lap, if only to shut me the hell up.
BZT
*The Windows path delineation slash, or "whack", is a backwhack, so far as I am concerned. I don't use it unless I absolutely have to.
Total Comments 0
