
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.
control is good if your writeing low level stuff like kernel or drivers as there you need to map directly to the addresses. but when your writeing a app you dont want to worry about memory cleanups or buffer sizes, you just want the app to work. this is the essence of what he was trying to say, i think. just look at the number of remote exploits that are buffer overflows (virtualy all). if the system did automatic size checking on all traffic then that attack method would go away (alltho at a cost of performance).
fine control is good, when you need it. other times it just gets in the way of what you are trying to do...