∞ PlayBook OS 2.0 delayed until 2012

In an apparent effort to make sure I had something to write about today, RIM announced that it has delayed the release of its PlayBook OS 2.0 software until February 2012.

CrackBerry.com reported the news last night. The full text of the announcement from David J. Smith, senior vice president of the BlackBerry PlayBook is available from the CrackBerry Web site.

However, there are a few choice comments that I would like to point out.

As much as we’d love to have it in your hands today, we’ve made the difficult decision to wait to launch BlackBerry PlayBook OS 2.0 until we are confident we have fully met the expectations of our developers, enterprise customers and end-users.

It would have been great if RIM considered these things before releasing the PlayBook in the first place.

First off, we have decided to defer the inclusion of the BBM application to a subsequent BlackBerry PlayBook OS release.

One of the reasons people want a RIM product in the first place, so let’s not include it in the PlayBook.

In the meantime, BlackBerry smartphone users will be able to continue to use BlackBerry Bridge…

The same greats solution that allows Internet access for the PlayBook.

These betas will be rolled out over the course of this year and are an important next step to bringing our unmatched enterprise app deployment, device manageability, security and email integration capabilities to the tablet category.

Unmatched email integration? You don’t have email on the PlayBook.

We believe BlackBerry PlayBook OS 2.0 will deliver a great experience for our customers, building on the powerful performance introduced with BlackBerry PlayBook tablet earlier this year.

Now you’re just messing with me.

The software update will add advanced integrated email, calendar and contact apps

By advanced, you mean “for the first time,” right?

For the enterprise, we’re addressing many barriers to tablet adoption, including device manageability and enterprise application deployment.

Wait a minute, you just said you had “unmatched enterprise app deployment.” Which is it?