Some cardinal rules for O/S contender hopefuls

I find it pretty hilarious to watch operating system creators tackle certain problems. The solutions they sometimes put in place make it clear to me that they are not just new to the graphical end user O/S, but in reality don't 'get' the concept of visual computing.

Here are some cardinal rules for wannabe O/S makers if you ever hope to get a foothold with the unwashed endie masses;

1. What starts graphical stays graphical. Did you think that by flashing a few dialog boxes and asking some questions of the user that it would then be okay to drop down to a csh/bsh whatever shell and have them executing sudo commands? It isn't. If you start something with pretty pictures, finish it that way.
2. Programs don't just 'go away'. They crash, sure, they crash all the time, but if anything be annoying in your followup. Too many times I try to load an app in a linux based system trying to be an end user O/S and the app tries....but then it just goes away. No dialog, no pestering error, no offer to report it. End users know they did something, so trying to trick them into thinking they have amnesia is just not going to work. Offer to send the error somewhere, offer a picture of Paris Hilton. Play a crying baby sound. For gods sake, do something.
3. When something is 'installed', its helpful to actually make it appear as though something new is on the system. I've installed so many Linux and Open Src programs only to find that they don't seem to have any concept that the 'start menu' or any graphical menuing exist. This is key to end users! You must place a physical, visual metaphor for your application somewhere on in the users view after install.
4. Users don't understand 'better'. They understand 'does the same thing I already have and more'. Different is not good, different is different, and end users have a really hard time moving to new things when they'd simply prefer to use what they already know.