Time for Some Big Changes in Windows
- 0
- Add a Comment
Since almost everyone is looking forward to the next version of Microsoft’s operating system, it should be a time for a look at what works, and what does not, and has not, for the past iterations of it.
One of the things that, for some, make Windows the easy thing to learn it is also makes it a source of frustration for others. Many operations have 2 or more ways of being carried out. Some of these are carry-overs from previous versions of the operating system, while others are additions to make more sense to the uninitiated user. Changes here could make a huge difference in any upcoming revisions, and should be looked at carefully.
Where there are two or three ways of doing something, the effort should be put into determining the best method, making the most sense, and then the other methods should be eliminated. This will make a big difference in future coding. Here is the rub, however, the brain-dead testers that were the guinea pigs for Vista should be blacklisted, and never used again. Microsoft should use those who have helped with the hardware testing (mice, primarily) as they have turned out winner after winner, unlike the usual software crew, whose taste and basic intelligence are questionable.
One of my personal peeves is a problem that has frustrated many of my customers, even if it is only for a short time. When removing software through the add-remove applet, the typical user will be concerned (as I said, perhaps only for a short time) when the dialogue comes up expressing the ‘configuration’ of the program - let’s be clear about this - NOTHING IS BEING CONFIGURED, it is BEING REMOVED. This is just another place where grossly stupid people put this in place - I can only imagine how this translates in other languages, and what trepidation comes to first time users - wondering why they cannot get the program to uninstall, and that somehow they missed a message that flew by.
Another thing that would make Windows (7) a better operating system is the coding of help files that really help. Instead of those terse, uninformative messages with obscure numbers, there could be a help file, to be pulled into memory only when needed, that would give a reasonable explanation of what has happened, and a hint or two on its solution. (Those who state that this would involve great cost, need to be prepared to convey to Microsoft that we’ve been paying for this for years, with overpriced software, and underpowered help.) A look to Unix man pages gives a clue as to what should be available.
Perhaps Microsoft should sponsor a contest to find the most absurd things with Windows, and remove them, which would be a grand prize for all who use their products.
-
Tags: microsoft, 7, operating systems, unix man pages, illogical methods, improved ui, user interface changes
