Linked by Hadrien Grasland on Fri 28th Jan 2011 20:37 UTC
OSNews, Generic OSes It's recently been a year since I started working on my pet OS project, and I often end up looking backwards at what I have done, wondering what made things difficult in the beginning. One of my conclusions is that while there's a lot of documentation on OS development from a technical point of view, more should be written about the project management aspect of it. Namely, how to go from a blurry "I want to code an OS" vision to either a precise vision of what you want to achieve, or the decision to stop following this path before you hit a wall. This article series aims at putting those interested in hobby OS development on the right track, while keeping this aspect of things in mind.
Permalink for comment 460230
To read all comments associated with this story, please click here.
RE[12]: Machine language or C
by Morin on Sun 30th Jan 2011 20:58 UTC in reply to "RE[11]: Machine language or C"
Member since:

I don't disagree with the order of priorities here. But I do believe efficiency should have a larger role up front than your suggesting.

Once the whole thing works, the "cement" has already begun to dry, so to speak.

You shouldn't do *anything* up-front except writing a prototype to get feedback. Then you'll see what you did wrong, including performance issues. If "drying cement" keeps you from fixing problems, your project will have much more serious issues than performance.

Reply Parent Score: 2