How about a summation of the snowball fight:
No one is happy that some .mac and MobileMe service are not functioning at even the nominal level for us. Some people are most upset because they relied on .mac for mission-critical Web applications. This was clearly a mistake, no matter what they feel Apple promised in the bargain, as evidenced by a rollout that requires an outage as opposed to the sort of two-stage rollout you get with mission-critical hosting services: the entire architecture exists twice, and when the new one is as good to go as humanly possible, they roll it forward, it takes mere minutes, perhaps an hour to stabilize the whole process.
So, on the one side of the argument, try to understand these folks were not expecting this sort of service outage and were not aware these things could happen with this service. On the other side of the argument, you folks have learned that .mac/MobileMe is not acceptable for mission-critical business applications if you're business can't easily withstand a couple days of TOTAL outage. (Yes, I know email works fine, but in future, everyone should assume you could get two days of TOTAL outage.) You need either a full fallback solution, or a mission-critical in-house or out-sourced hosting solution.
The argument "Yes, we can" and that this .mac/MobileMe outage represents mediocrity doesn't really apply here. This is more like the muni water company is replacing mains in your area, and they leave a notice on your door that water will be out on Thursday at least six hours, but could run indefinitely longer, circumstances depending. Apple is applying the reasonable amount of effort to bring the service fully operational, a day before it even applies to it's primary purpose, integration with iPhone firmware 2.0, for THIS LEVEL OF SERVICE. It's not mediocrity, it's merely application of resources commensurate with level of service sold.