Our current product has a UI that is on par with windows 2000. We reuse the same ~26 hand-rolled UI elements on a fixed-size layout. Things like alpha blending and pixel shaders are a distant fantasy for us. Target market is highly regulated B2B, so we have more tolerance to work with here. Everything is very serious business. No one really cares about button radii or drop shadows. They just want to push the paperwork as quickly as our screens will come back and then go home. We listen to our user delegates on a weekly basis. On the actual telephone for up to an hour. Any little UX gripes are usually dealt with judiciously as a result.
Nothing is more frustrating than a perfect UI being fucked up by the passage of time. You don't need fancy shit. You just need consistency and speed. Give me back my xp-era explorer and start menu snappiness. Put a high speed camera on a windows 10 task bar and record someone right clicking on it. You might need a larger SD card than originally planned for this activity.
XP explorer is so much faster it blows my damn mind. I ran it inside Windows 10 in VirtualBox, the explorer window opens instantly and navigates instantly, while the new explorer has lag with every operation. The best way to see this is to copy or rename a file. Explorer, a Microsoft product (presumably better integrated with the kernel) will take a second or two to show the result of the action that it itself performed (!!), while Sublime Text open in the background will detect the change and display it instantly. Madness!
I feel like way too many engineers ca. 2005-2010 internalized the misconception that "asynchronous" is synonymous with "I don't need to care how long it takes". It turns out that the distinction isn't trivial.
I wonder if Explorer is deliberately updating the display after a timeout to handle the scenario where many files might rename in short succession.
One simple way to handle this could be to compute the timer to fire at $last_rename_time + $delay, initialize $last_rename_time to 0 (and later set it to the current time in milliseconds), then only actually start the timer if the calculated value is actually in the future (which it won't be for the first run).
Of course... Explorer might (...still) be using periodic polling. xD
You might be able to use Event Tracing for Windows to find out if Explorer is actually following events in real time, with the minor caveat that it might be a bit of a project. I gathered a small handful of ETW-related links over at https://news.ycombinator.com/item?id=28348564 a little while back FWIW.
I believe this is what's happening. I read something recently from Raymond Chen that it works like:
1. Open file with the delete flag
2. Call a function to set the new file information
3. Close the handle.
The signal that a file was renamed happens in step 2, and that signal/event is what many applications subscribe to.
Explorer will wait until the rename is fully completed with the handle closed before showing the change.
Nothing is more frustrating than a perfect UI being fucked up by the passage of time. You don't need fancy shit. You just need consistency and speed. Give me back my xp-era explorer and start menu snappiness. Put a high speed camera on a windows 10 task bar and record someone right clicking on it. You might need a larger SD card than originally planned for this activity.