On Sun, 24 Jun 2007 11:30:12 -0500, Adam Albright
>On Sun, 24 Jun 2007 08:49:03 -0500, "mikeyhsd"
>Windows Explorer is fatally flawed, has been for over a decade
>at least and it seems Microsoft either doesn't know how to fix it
>or doesn't give a rat's ass how poorly it performs.
It's always flaawed, but the flaws vary :-)
One persistent design safety failure is duhfault settings that hide
file name extensions - and these duhfaults are applied in "safe" mode.
If icons are to be the "easy" replacement for .ext as a risk
prediction, then this is brain dead too; the most dangerous file types
can set their icon to whatever they like.
Vista does make one improvement, though. When renaming a file,
Vista's initial selection (and therefore what is replaced when you
start typing the name) now excludes the file name extension. You can
still change it if you want, but you no longer have to deliberately
avoid changing it by accident, as you do in older Windows.
>Explorer is so damn dumb in Vista it will frequently rescan the entire
>contents of some folder if you copy/move a file to it in some stupid
>attempt to keep the contents in order DURING the copy or move.
In general, there seems to be too much per-item overhead that scales
poorly when you use NTFS's ability to efficiently store many thousands
of files in a single directory. It feels like they did their testing
with trivially-small "demo" file sets, and didn't factor in things
that slow down storage access that magnify the impact.
There's also the need to protect against race conditions, given that
the trend in Windows Explorer is towards more concurrancy. If it were
a database, it would be like going from database locking (no two
entities can update the same database at the same time) to record
locking to field locking.
For example, in Win95, the destination window for file system changes
could not be used until the operation ended; this changed with Win98.
The overhead was intolerable in the Vista betas, and is still onerous
but less horrific in RTM. But optimization gains may be eroded if
race conditions need re-kludging of code to fix.
I also dislike unsolicited file "groping", as this exposes the OS to
exploits from material I have shown no intention to "open". File
"gropers" include indexers, thumbnailers, handlers that kick in when
files are listed within a folder, and when files are selected.
As it is, it is so slow that one gives up on the shell entirely and
does file ops from command line instead - which is like regressing all
the way back to DOS. That was often a necessity in Win98+IE6...
http://cquirke.mvps.org/bexp1.htm
....due to a bug that never got fixed.
It's hard to take an OS seriously, when simply copying files around is
too buggy to use. Some enhancements in Vista I like, tho:
- show destination and action as tooltip when dragging-and-dropping
- more effective ways to avoid nags during bulk ops
- the "breadcrumbs" address bar navigation
BTW, another buggy situation seems to arise when Shadow Copy is
involved, e.g. while you are being nagged to do a backup, you may find
files you are copying, are copied twice. You get an unexpected
"...exists, overwrite?" and a Yes causes everything to be copied twice
(though only one set of files will result at the destination).
>--------------- ----- ---- --- -- - - -
Error Messages Are Your Friends
>--------------- ----- ---- --- -- - - -