Really, my frustration stems from the fact that people aren't exploring the codebase, and asking questions of those of us who have been here a while.
We have an amazing architecture here, that is unparalleled in so many areas, and while there are some weak areas in the area of Orbiter, the architecture is such that all these pieces can be replaced.
At this point, myself, along with anyone else interested, are trying to build a series of "toys" in a set of UI toolkits, trying to find something to standardize on for the next generation of Orbiter. I have gone over this in the Clutter thread, so I won't recap it all here. But right now, it's all about trying to spur a curiosity in the codebase. This system can do ANYTHING, it's _DESIGNED_ this way, it's not a side effect, or a consequence, but it is the result of applying enterprise design patterns to the problems of home automation. While there are obvious warts in the code (yes, they are everywhere, for various reasons), these can be and are being fixed, we just need more hands.
Chris, I know you're looking at this from the standpoint of a salesman, that's not what we need at this point. We need a few more people who are willing to understand the architecture, and not dismiss it as "crap" because they do not understand it yet.