Casper, about your minimalism - ReactOS is built on stubbed-out/unimplemented functions. They exist for a good reason - to provide a starting point for someone who has time to and wants to do the work to implement them. If obtaining minimalism was really the ultimate goal here then we have lots of deleting to do. But that would be reckless.
Minimalism is not about removing needed code and the stubs are needed. Without them, applications would crash at start up. Many applications (or part of them) still run even if only some of the APIs are implemented. When working on getting an application working on ReactOS, all references must also be able to be resolved in order to get anywhere. This only applies to ReactOS because it implements APIs which are used by already written applications. Had it been stubs for new APIs used only by code we would write tomorrow then yes, we should wait until tomorrow before adding them.
I admit that the code isn't used currently. And I'm not opposed to #ifdef'ing it out and not compiling it in. But I don't think we should delete it and make everything call the TUI stuff directly. Would this be an acceptable compromise for you?
-Brian
It is still unused code until the day someone *might* use it (which may never happen). How about documenting it in wiki instead? You can even write the revision in which it was last present and any other useful comments about the code.
Casper