Wednesday, December 28, 2011

Fragmentation is a dumb argument.


Tiramisu.

I looked at Epicurious, and there were 31 recipes for Tiramisu.  They're not all like traditional Tiramisu, and some recipes are merely incorporating flavors of Tiramisu into something else.

Each person who produces their own recipe of Tiramisu (or a derivative of), wants you to use their recipe.  Each bakery thinks their Tiramisu is best, and wants you to settle for their Tiramisu.

Then there's the person who hates Tiramisu, and thinks it's stupid that there are so many different versions of Tiramisu.  To that person, having 31 recipes of Tiramisu means that you will be disappointed if you like one, but for whatever reason, can't replicate it, or the bakery you bought it from, went out of business.

It's a poor logical argument.  If you don't like a particular version of Tiramisu, you avoid it; there is no law that says you have to buy that Tiramisu at Bakery X, or use that recipe Y.

Yet there's a lot of media folks who are being suckered into thinking that fragmentation is bad.

Back to mobile platforms.

Sure, for those developers who want to sell  / make money on apps, having fragmentation can be somewhat of an inconvenience.  But you're a consumer, and you enjoy having your choice of devices, features and user interface.  Nook Color running Android 2.1 was popular enough to get Barnes and Noble to produce a successor, the Nook Tablet running Android 2.3.  Neither looked anything close to a stock Android; same thing goes for the Kindle Fire.

So what's wrong with having different flavors?  The truth is, there is nothing behind the argument that fragmentation is bad.


No comments: