It is apparently an unsolved problem in computer science to build an OS that doesn't grind to a halt when a network drive cannot be reached.
-
-
Replying to @cmuratori
@cmuratori "A drive that is completely unrelated to the operation you're doing right now is unavailable? ARE YOU SURE?? STOP EVERYTHING!!!"5 replies 0 retweets 3 likes -
Replying to @cmuratori
@cmuratori Oh jesus, yes. I'm so glad my NAS is stable now, that shit was a nightmare before I switched to custom firmware.1 reply 0 retweets 0 likes -
Replying to @mbowman
@Niyeaux The problem is ubiquitous, too. I have Windows, Mac, and Linux machines, and _all_ of them have this problem somewhere.
2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori Yeah, it's really strange. I've run into it on Win7 and CentOS, and the behaviour is uncannily similar.1 reply 0 retweets 0 likes -
Replying to @mbowman
@Niyeaux It's just that everyone writes code assuming dir/file queries return immediately. Guess what? They don't.
2 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori Very silly. It's not like network storage is a recent phenomenon. This shit should be figured out by now.1 reply 0 retweets 0 likes
@Niyeaux It is also true that we only run OSes that are at least 20 years old, though :( At least on PC.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.