-
Mike (X CEO) noticed that a bunch of QNX resources were being used to produce the
PB and its OS. This upset him and pulled some if not most of the resources off the PB and moved them to the QNX phone development. This happened last summer.
This not only shows that Mike didn't have a clue as to what was going on in his company but it shows the state disarray that RIM was and seems to be still in under Thor. (Also note Mike is still there)
The result of this move was the delay of the items they said the PB would have "soon".
Instead of increasing the resourcess of both the phones and the PB he cut the PBs.
Thus both the phones and the PB were hurt badly.
Native email, according to Mike B. on a TV interview, the native email would be available within 60 days after the launch. We now know he didn't know what he was talking about or RIM was unable to deliver.
Cascades were supposed to be on the PB by that fall as well.. per Mike.
I do not want to go through the whole time line.
Just compare the PB to what other successful tablets have and you will see the large holes it had and still has over a year after it was released.
To drop support for it would not only off a ton of PB owners but would do even more damage to RIMs reputation of not being able to deliver a products that works and has the functions the buyers want.
Folks say it takes a long time to produce a "new" OS. It's not all that new! The QNX OS has been around on a wid ranging number of products for a long time now. Years.
2.1 is needed and the promise needs to be kept. Period.
Tim09-04-12 11:23 AM - I apologise for being the old cynic that I am, but RIM's response to that question was always going to be "yes, official 2.1 will come out".
If 2.1 was actually coming, the answer would be "yes".
If 2.1 wasn't coming, the answer would also be "yes" so as not to depress anyone with a PB that was waiting for it. And by the time the lie was revealed, the imminent release of BB10 would be announced... and we could all play this waiting game all over again! Part of me does appreciate the humour of this situation. LOL
I'd be more interested in a tweet (is twitter the entirety of RIM's PR operation these days?) stating an unequivocal release date for 2.1 and not using any of the following: "soon", "around the corner", "Summer", "later", or "after".
09-04-12 11:42 AM - Maybe the co-op student working on the patch finished his/her final work term before graduating and has left the building much like Elvis? Honestly, the fabrications arising around BlackBerry Tablet OS 2.1 and the future BlackBerry 10 might lead some people to think the first casualty of product development is truth. When Clewely says "Yes, it is coming," are we to equate this statement with the more profoundly honest statement "Everyone dies eventually?"
09-04-12 12:00 PM - Even though QNX isn't new, do you think it works right out of the box on tablets and phones? I equate QNX to a car engine....it is what runs the car, but there are also other things needed to make it work. As an example, the cars interior components = the GUI that RIM has built (aka PB OS1.0, 2.0, 2.1, BB10, etc.). This isn't something you can just build overnight and throw it on a device. Look at Apple, iOS is still getting features/functionality that my BB handsets have had for years...and how long has the iPhone been out? Exactly...Mike (X CEO) noticed that a bunch of QNX resources were being used to produce the
PB and its OS. This upset him and pulled some if not most of the resources off the PB and moved them to the QNX phone development. This happened last summer.
This not only shows that Mike didn't have a clue as to what was going on in his company but it shows the state disarray that RIM was and seems to be still in under Thor. (Also note Mike is still there)
The result of this move was the delay of the items they said the PB would have "soon".
Instead of increasing the resourcess of both the phones and the PB he cut the PBs.
Thus both the phones and the PB were hurt badly.
Native email, according to Mike B. on a TV interview, the native email would be available within 60 days after the launch. We now know he didn't know what he was talking about or RIM was unable to deliver.
Cascades were supposed to be on the PB by that fall as well.. per Mike.
I do not want to go through the whole time line.
Just compare the PB to what other successful tablets have and you will see the large holes it had and still has over a year after it was released.
To drop support for it would not only off a ton of PB owners but would do even more damage to RIMs reputation of not being able to deliver a products that works and has the functions the buyers want.
Folks say it takes a long time to produce a "new" OS. It's not all that new! The QNX OS has been around on a wid ranging number of products for a long time now. Years.
2.1 is needed and the promise needs to be kept. Period.
Tim
09-04-12 12:04 PM - Nope. It is clear it didn't work right out of the box, isn't itEven though QNX isn't new, do you think it works right out of the box on tablets and phones? I equate QNX to a car engine....it is what runs the car, but there are also other things needed to make it work. As an example, the cars interior components = the GUI that RIM has built (aka PB OS1.0, 2.0, 2.1, BB10, etc.). This isn't something you can just build overnight and throw it on a device. Look at Apple, iOS is still getting features/functionality that my BB handsets have had for years...and how long has the iPhone been out? Exactly...
And it hasn't been "overnight" either. Its been over 365 overnights so far.
I am not asking for the parting of the Red Sea here. Just simple items that
should be on the PB.
They sold an unfinished product for top dollar. Indicated items that would be soon coming and then did not deliver.
I could care less how long it takes to build the OS. I want what they said it would be and for the price I paid I dang well better get and soon.
I think giving them over a year since its release to add the items I listed is more the reasonable and from the lack of sales I would say I am correct.
The company I work for does custom programming for financial institutions. We seem to be able to get a complete bank system out and in the banks hands on time and with the features needs. Yep, some bugs pop up that need to be fixed but that is done in short order.
I would say it just as hard to produce software that works from the Teller to the
processor on time and with the promised features.
If you think it is hard to make an OS, try to make a system for a bank that meets all the security needs and the needs of the Federal Reserve, Visa etc.
Tim09-04-12 12:19 PM
