-
You are more than entitled to your own opinion, and I won't be the one to try to change it for you.
As frustrating as it is waiting for this update to pick up, I just think there are better things to stress out about today/tonight. When 2.0 and even 2.0.1 came out I couldn't recall many people that had problems with updating their devices. What I'm basically saying is that when it really mattered (i.e. in front of the consumer), RIM has been pretty good about the software updates for the PlayBooks. Not that devs don't matter, because they do, but I think they have a higher tolerance for tomfoolery like this and may not necessarily attribute this issue to fundamental problems with RIM as a company. For that, you have 6,000 RIM jobs on the line
05-31-12 05:08 PM - I thought I made it obvious enough. I was just saying that servers go down, systems have glitches, they guys in the data center are on a coffee break, etc. I bet that within a few hours we will have our shiny new update and will all forget about this by tomorrow. This problem will probably be filed in the footnote of a wiki page somewhere, nothing really more than that.I'm almost positive they were being sarcastic
05-31-12 05:15 PM - I contend that this is all a little taste of Blackberry's upcoming Marketing.
A Crackberry User fills out the form to get the Playbook 2.1 Beta that they've been waiting for so they can review it objectively. They "check for updates" (C4U) really quickly hoping they got lucky. No luck.
User hits C4U button a second time within a minute because RIM said "as fast as a minute" but no luck that time either. They must be serious about the delay.
User keeps hitting the C4U button every other minute getting frustrated and wondering why those b*stards haven't released it to them yet. Surely their servers are under capacity or they screwed up some how. Rage ensues.
User now lays off the C4U button and checks Twitter, Crackberry and the Developer forums to see what's up? Maybe Waterloo blew up; all the while convincing themselves if might happen. Doubt sets in that they will see the beta.
User checks again repeatedly thinking that they were somehow denied and wouldn't get the privilege of testing out the Playbook 2.1 beta. Surely someone figured out they are not a real developer. Remorse on possibly not getting away with it develops.
User checks again and every hesitation in the glorious green ring of life means the possibility of being milliseconds closer to downloading the Holy Grail. Sadly, they are denied and fear starts to set in. A craving develops.
User continues to check and considers that their Playbook is broken and must not be capable of the magic bits that will make their device sing. Perhaps they need another one? Wonder is the state of the moment.
An hour passes since they made their first request and, if they haven't already, they return to the form and fill it out again. Obviously, they must have done something wrong.
Then the vicious cycle continues...
Once the user does download the Playbook 2.1 Beta, they will think it's the best thing since sliced bread. The browser is faster, the scattered new features are marvelous. They read reviews on Crackberry and try to post something not already found.
Blackberry Marketing just cemented the "Crackberry" back into you and all the while, they just held back a little from flipping the switch
05-31-12 05:45 PM
