
Every hard-core OS aficionado has done it: Laid out a grand scheme for creating the perfect OS. Taking all the best features and attributes from the OSes we love, and making sure to assiduously avoid the pitfalls of the OSes we don't. Maybe our goals were modest, and we just wanted a slightly tweaked version of an existing OS. But sometimes we're feeling ambitious, and we have large, creative ideas for revolutionizing computing. Long-time OSNews reader and contributor J. Scott Edwards just couldn't help himself, and he has set about to not only plan, but to try to build his dream OS.
I consider kernel programming to be a subset of hardware programming. At that level of programming, the object oriented paradigm of composing software is fragile, inefficient and complex.
I strongly suggest you shift your thinking from the concept of everything being an object, to that of a component-oriented paradigm. I also advice you to use a language that is small, light, structured and fast. Assembly, C and Forth come to mind. I think you are approaching the problem from an extremely high level perspective.
From my observation, there haven't been too many successful kernels designed from that kind of a perspective, at least in practice. And that's another problem with object-oriented programming languages and paradigms. They only sound good in theory.