Hacker News Reader

Comment by ubercow13 | Hacker News Reader

Yes, but as a user rather than developer, I have never had a problem with it in practice, unlike Windows. And it is honestly much more convenient (as a user) to be able to manipulate open documents on the filesystem if you can keep in mind how the semantics work.

View on HN

The user of a corrupted document won't be very happy when it happens.

Maybe in theory, but it has never actually happened to me. I don't see much *nix user/sysadmin advice around the internet about how to avoid all those inevitably corrupted files, but there is plenty of evidence that Windows' strict locking causes real users real annoyance.

In theory only bad programmers write C code that corrupts memory, and yet it happens even in projects with top coders and multiple levels of code reviews.

Files are just memory in a different storage device.

>In theory only bad programmers write C code that corrupts memory, and yet it happens even in projects with top coders and multiple levels of code reviews.

In theory only bad programmers write code with bugs related to Windows file locking, and yet... well just check the OP I guess

Except Windows is not alone, only UNIX clones have careless file locking.

I've been using Linux for years and have encountered this problem exactly zero times.

Yeah, because you validate the writes across all files on the system.

Many people also swear that only bad programmers write C programs with memory corruption bugs.

Reply on news.ycombinator.com