It brought me to this conclusion (hardly conclusive): how the hell do you get a product out of beta? Beta isn't a time-period, it's a quality threshold. Kinda seems like the path outta beta includes having some specific/measurable goals, maybe a spec to start. Then, someone had better have an idea about how the service isn't meeting those goals... This leads us to where we are now: new features or band-aid fixes to perceived problems are easier to deal with than performance/compatibility/clarity/usability issues.
There have been several prominent blogs that mention the appalling quality of software. I am a somewhat-silent co-conspirator with my current project. Here are some irrefutable facts about our situation:
It seems like the best use of the group's time would be to address these classes of issues rather than forging ahead with this motto:
'Let's put some makeup on this pig'