That kind of attitude leads to user blaming. I have fond memories of the workgroup network scan freezing my computer for extended durations in the xp days

Or just download a large file, choose save as on a drive other than the C drive because it is too big, and watch IE proceed to fill up the temp dir on the C drive, completely ignoring the fact you asked to save on another drive.

Or if you had enough space, still waste minutes copying the deleting the file...

IE? We're in 2023 dude, don't think that is even usable anymore.

A memory of XP was invoked, hence the comment about other XP anecdata.

haha! can totally relate

that 'save to temp-dir first and copy later' behavior is so frustrating because it's inconsistently applied and not easily avoided, yet somewhat incomprehensible to the average user.

> in the xp days

Those days ended in 2007. I don't know if that issue persisted after XP because I've never experienced it.

I've been using Windows since 1998 and I can confirm all the issues described. The last time I enjoyed hanging Explorer was yesterday, and it was exactly because Explorer was trying to open a network link that I didn't ask to open.

To be fair I have that constantly on Linux. Default applications like ark trying to query every connected drive on every use and just hanging there until they get a response even when all you want to do is open a zip file on a local ssd.