Linked by Hadrien Grasland on Sat 5th Feb 2011 10:59 UTC
OSNews, Generic OSes So you have taken the test and you think you are ready to get started with OS development? At this point, many OS-deving hobbyists are tempted to go looking for a simple step-by-step tutorial which would guide them into making a binary boot, do some text I/O, and other "simple" stuff. The implicit plan is more or less as follow: any time they'll think about something which in their opinion would be cool to implement, they'll implement it. Gradually, feature after feature, their OS would supposedly build up, slowly getting superior to anything out there. This is, in my opinion, not the best way to get somewhere (if getting somewhere is your goal). In this article, I'll try to explain why, and what you should be doing at this stage instead in my opinion.
Thread beginning with comment 461294
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[9]: Not always rational
by Alfman on Tue 8th Feb 2011 07:52 UTC in reply to "RE[8]: Not always rational"
Member since:

The problem is, an efficient implementation of a microkernel needs a lot of optimization planning up front, which, if you've read the previous article in the series, is a very unpopular notion.

Therefor, most programmers will start writing the OS the easiest way they know how, which more often than not means modeling it after existing kernels. Unfortunately this often results in many new operating systems sharing the same inefficiencies as the old ones.

I was trying to highlight some areas of improvement, but of course people are highly resistant to any changes.

Reply Parent Score: 1