I would actually sort of debate that too ;-)
Misinformed people are misinformed people, wherever they are a 'customer' or not. In all matters of life, they are the ones who need to be worked on the most. Sometimes it is just not worth the cost in time or anything you may invest in them.

I remember a company who was in difficulties by not being able to sell enough products. It went into litigation mode trying to sue the hell out of everyone or everything that moves, hoping to generate revenues from those patent enforcements. This company no longer exists because that mode ended up not being sustainable as a good business.

• Q1: Name said company
• Q2: Name a company that is adopting the same "I'm losing it" tactics

Yes, and the inability to answer to comments on the Android Market is a major pain. There is nothing more frustating to see comments such as "I couldn't do this or that - UNINSTALLED!!!!" where it is obvious that a few lines of explanations would make one clumsy user happy.

What can you investigate when the problem isn't described and assumptions are made about your application, which you know have absolutely no grounds.

I went through your first lines of misinterpretations of TFA, but then I stopped there. This doctrine is ridiculously outdated. If you constantly listen to the unwashed masses, you get non-sense most of the time.
And yes, that review was wrong and paranoid with far reaching consequences. Another example of an idiot who will be trusted by others. That is way too much power to leave it to a "customer" - who thinks "is always right".

In regard to your apparent blindness, one question comes to mind. Did you actually really tried any of the Android tablets?

I could spend hours replying inline to your arguments, but another slashdotter summed it all by pointing at your login name. Add it that your post is factless and you reference "people" that you have no statistics about. We probably do not revolve around that same 'people' according to what you say.

So far I am just fine, thank you.

So in light of a lawsuit, the USPTO finds out that a granted patent should not have been granted. Or many. Everyone is focusing on the impact this may have on the case, but no question asked about the USPTO? (besides Slashdotters?)

I've got a XOOM and an Asus EEE Transformer. The hardware and performances are basically the same. The Asus one can have a keyboard extension, which is great as it transforms it into a small notebook and back to a tablet, but without the extension, the Asus one is disappointing. On the other hand, the XOOM feels more solid and much less plastic than the Asus, and the dock extension is totally useless. However Motorola doesn't seem in a hurry in fixing the SD card issue and upgrading us to 3.1 (I live in a remote country, north of "America", it takes time to bring anything here apparently)
All in all, it's hard to tell which is the best. If you're looking for an hybrid, go for the EEE. If you're looking for a tablet-tablet, go for the XOOM. I would not consider the Cisco one unless it's geared toward business usage, and your business use Cisco phones.

No they don't. Most applications look smallish, still have the ugly phone workflow with stacks of activities and endless pressing of the "Back" button. Tablets have much more screen estate that applications written for phones don't use and should.
Oh and to the OP

You're overgeneralizing...I own two!

*Waves hand*. It's a gamble, but I honestly hope for the sake of tinkering and openess that the IPad hype will slowly decline in favor of Android-based devices.
I read a lot of "People prefer the IPad", "People say NO to Android" but in my day-to-day experience, people just do not know what Android devices are capable of and how they really compare. When I show my XOOM to people who are telling me they're about to buy an IPad, they are usually surprised how the XOOM seem to work just as well. Most of the feedback I get goes around "I'd buy that but it doesn't have that app that I love on my IPhone". Absolutely true and on spot with TFA.

Use the Compatibility package (it now comes as an add-on in ADT) for backward-compatible Fragment(s) and rewrite your Activities using Fragments only. I did this before I adapted my application to tablets (3.0 / 3.1) and never ever wanted to look back. Yes, the tablet code is not really "3.0x" but it works beautifully and Fragments are so much better!

Note: You can thank me after you've refactored :P

I understand "Fragmentation" is a cute and trendy word to use but TFA is actually right in saying that it's not the SDK that is the problem, but graphic resources and the fact that tablets are a much different beast than a simple phone, and the workflows (aka use cases, aka user stories) cannot be the same on a phone and a tablet. Applications designed for small devices miserably fail to be attractive on tablets because they aren't re-worked for them. However, most of the work in doing this is actually about re-thinking the interface and how it is going to be used. If you code your app correctly, there is no difficulty in re-using your components for one device size or another.

And back to fragmentation, the real headaches come from working around bugs in older version of Android that still need to be supported. That, my friend, is the real pain. And testing because you need to basically test each Android version.

You mean, nobody told Canadians how to drive properly in roundabouts? At least they don't "fear" implementing them anyway, unlike southern neighbours. Montreal for instance could use a few hundreds of them. Traffic sucks BECAUSE of traffic lights everywhere and people stuck in the box.

You must be new to rotaries...That's an added benefit of them. When you miss your exit, or you just don't know where to exit, have another spin.

Oh, you are definitely new to rotaries. As many have explained here, rotaries have a lot of benefits when implemented and used properly, and in most cases are much better for overall traffic at junctions. You "believe" wrong. Check the intertubes, it's full of stats!