1. Asus isn't the only party "at fault", while responsible to the customer the issues are a result of Android not yet being mature and the complexities involved (of OS + hardware + changing component & embedded programming + third party hardware & driver dependancies + third party apps programming and quality). We do however have Asus as the only "visible" party available to us, which makes sense since they sold the tablets to us, and while I am convinced they are now on the ball it does not hurt to remember for a moment that Asus too depends on others, much like we depend on Asus. They carry the responsability to their customers, but sofar in its history Asus does have a record of taking that responsability (much more often than not).
2. It sucks for all of us affected, direly, and it something all parties involved will have to draw lessons from. I do think that Asus is already doing so, but unfortunately the results of this will have to wait for the work being done. Which is only natural.
3. But commercial necessity dictates we will get a patch which will address the most visible issues. That this is being worked on seriously is already visible in the initiatives Asus has ongoing with user testing groups and their communications with those.
4. After that most of us should have a stable unit for normal use again, but a further patch probably timed with another OS update can be expected. Asus does have a reasonable history of learning from mistakes, and it is not a company that wants to diminish itself so while there are natural (commercial) limitations that do apply I do not doubt that they have this as a definite focus.
5. If current circumstances have to be prevented from happening again, both OS Vendor and OEM's & suppliers are going to have to mature the Android market.
And to include a little pun ...
6. All of this has happened before, but it does not have to happen again. OS Vendor and all others can simply look at how the PC computing industry went through this, and not make the same mistakes.