Hacker News Reader

Thanks, I appreciate the support, but my opps, you caught my initial phrasing before I clarified to disambiguate: I didn't mean to write an operating system; but to write one in Dijkstra's way (ie by showing - proving - that it works before you write it). ugghh I shudder just saying it.

View on HN

Ah, ok, now I get it :) That was more than just a little bit ambiguous, I completely fell for it.

I'm sorry; I didn't mean to dig a pitfall to entrap a helpful fellow traveler. When I noticed that a reading with the last two sentences as separable was misleading, I edited directly. I think the "sadly" part was communicated though, and I've tucked away your remarks for when I'm confronted by a multitasking OS. I think debugging the race conditions would be nightmarish.

The trick is to write your OS in such a way that you minimize the chance of having races. The way I chose was to mimick 'QnX', a message passing real time OS.

This is also what experience gives you: the ability to predict where problems are likely to crop up so you can avoid them.

Easier to not inject a bug in the first place than to try to find it later.

Reply on news.ycombinator.com