After reading the comments on my earlier post, Delayed allocation and the zero-length file problem, it’s become very clear to me that there are a lot of myths and misplaced concerns about fsync() and how best to use it.

"It's full of bugs. Nothing ever works. I can't get it to do what I want. It's too hard." [It] probably sounds like I'm talking about Windows, but I'm not. Those are a few of the many complaints I've heard about Linux any time it's brought up.

The authentication of FS Daily is so crappy currently and it is such a pain to use it every day. It seems it is becoming crappier by day. I never get my remember my login correctly. Forget it, just to post a news or to vote on a story you need to sign in many times, refresh and above all pray it will let you do it.

Of what use is an operating system if all it does is to make you look forward to the next release - simply because umpteen bugs have been introduced by all the new features in the current version?

Finding bugs in your code can be quite nasty—especially if you don’t know where to look. However, finding bugs automatically does not require astronaut training. I think it’s time to leave that “pleasure” to free (as in freedom) automatic static code review tools like the ones reviewed in this series of articles.

"Over the last few years, I’ve come to accept the fact that regardless of my attempts to quit this job, I am fundamentally a programmer. I wrote a book about security, I am the Editor In Chief of Free Software Magazine, but in the end I am still just a programmer. A lucky one, I must admit. Until last month, I had been blessed by the fact that either the software I wrote was owned by somebody else after a short contract (and therefore it didn’t matter to me once I had completed it: somebody else eventually took it over), or that what I programmed had been created just for myself (I was the only user of the software… bliss!). This changed when I became a free software programmer. I have recently released what I consider an important project: Drigg.

Mozilla has patched a pair of nasty flaws in its Firefox browser, two weeks after security researchers first started posting code that showed how the flaws could be exploited in attacks.