It means writing code for an RTOS is annoying and for many devs ActionScript is as native as they're likely going to get.
This is different from Android (Java), WP7 (C#) which use much more dev friendly, higher level languages. ObjC is about par with C++ (depends on what you like) but Apple has spent a lot of time making the Core APIs not suck.
For the average BB dev to move to (or back to) C++ from Java is probably one of those meh kinda moments.
It means writing code for an RTOS is annoying and for many devs ActionScript is as native as they're likely going to get.
This is different from Android (Java), WP7 (C#) which use much more dev friendly, higher level languages. ObjC is about par with C++ (depends on what you like) but Apple has spent a lot of time making the Core APIs not suck.
For the average BB dev to move to (or back to) C++ from Java is probably one of those meh kinda moments.
OK, I get that. But I was and am still having problems believing someone supposedly as smart as Lazaridis can somehow make a statement that a managed runtime with on-the-fly interpretation to bytecode before compiling to native code is actually native.
Steve Jobs just said "No" when asked about tethering. That's hardly evasive at all. The rest of that stuff you just made up.
I didn't say Jobs was evasive --- he is blunt.
I said that other CEO's are evasive on answering loaded questions --- but that doesn't make them morons. You might as well call every single politicians as morons because they will never give you a straight answer.
The people who complains about how RIM is evasive on how non-blackberry owners (say an iphone owner) can tether the Playbook --- they should drop down on their knees and thank god that RIM is allowing tethering a Blackberry with a Playbook because you as a iphone owner can't tether with a wifi-only ipad.
It means writing code for an RTOS is annoying and for many devs ActionScript is as native as they're likely going to get.
This is different from Android (Java), WP7 (C#) which use much more dev friendly, higher level languages. ObjC is about par with C++ (depends on what you like) but Apple has spent a lot of time making the Core APIs not suck.
For the average BB dev to move to (or back to) C++ from Java is probably one of those meh kinda moments.
But that works for RIM's flavor --- because there will be a sdk suitable for everybody.
If you are a hard core C guy, then you fit right in with the QNX people.
If you are a legacy blackberry app guy, then you can use the playbook java sdk.
If you are a flash/air guy, then you can use the flash/air sdk.
If you are a web guy, then you can use the webworks sdk.
Trying to be a Jack-of-All-Trades for rev one usually means not being very good at any. And that's a very bad thing for rev one hardware software pairs.
The continued lack of technical focus and coherent communication only makes it look worse. RIM isn't only fighting everyone else to get in the market, they are fighting their own leadership who is writing capability "checks" they cannot cash.
Trying to be a Jack-of-All-Trades for rev one usually means not being very good at any. And that's a very bad thing for rev one hardware software pairs.
The continued lack of technical focus and coherent communication only makes it look worse. RIM isn't only fighting everyone else to get in the market, they are fighting their own leadership who is writing capability "checks" they cannot cash.
Conversely, there is no jack of all trade tool as well. There are many more suitable tools that developers that iOS app developers can't use, just because Apple doesn't allow it.
Wait until the Playbook is launch, then you can criticize them for not delivering.
Conversely, there is no jack of all trade tool as well. There are many more suitable tools that developers that iOS app developers can't use, just because Apple doesn't allow it.
Wait until the Playbook is launch, then you can criticize them for not delivering.
Comments
WTF does that meaN?
It means writing code for an RTOS is annoying and for many devs ActionScript is as native as they're likely going to get.
This is different from Android (Java), WP7 (C#) which use much more dev friendly, higher level languages. ObjC is about par with C++ (depends on what you like) but Apple has spent a lot of time making the Core APIs not suck.
For the average BB dev to move to (or back to) C++ from Java is probably one of those meh kinda moments.
It means writing code for an RTOS is annoying and for many devs ActionScript is as native as they're likely going to get.
This is different from Android (Java), WP7 (C#) which use much more dev friendly, higher level languages. ObjC is about par with C++ (depends on what you like) but Apple has spent a lot of time making the Core APIs not suck.
For the average BB dev to move to (or back to) C++ from Java is probably one of those meh kinda moments.
OK, I get that. But I was and am still having problems believing someone supposedly as smart as Lazaridis can somehow make a statement that a managed runtime with on-the-fly interpretation to bytecode before compiling to native code is actually native.
It's juts totally bass-akwards.
Steve Jobs just said "No" when asked about tethering. That's hardly evasive at all. The rest of that stuff you just made up.
I didn't say Jobs was evasive --- he is blunt.
I said that other CEO's are evasive on answering loaded questions --- but that doesn't make them morons. You might as well call every single politicians as morons because they will never give you a straight answer.
The people who complains about how RIM is evasive on how non-blackberry owners (say an iphone owner) can tether the Playbook --- they should drop down on their knees and thank god that RIM is allowing tethering a Blackberry with a Playbook because you as a iphone owner can't tether with a wifi-only ipad.
It means writing code for an RTOS is annoying and for many devs ActionScript is as native as they're likely going to get.
This is different from Android (Java), WP7 (C#) which use much more dev friendly, higher level languages. ObjC is about par with C++ (depends on what you like) but Apple has spent a lot of time making the Core APIs not suck.
For the average BB dev to move to (or back to) C++ from Java is probably one of those meh kinda moments.
But that works for RIM's flavor --- because there will be a sdk suitable for everybody.
If you are a hard core C guy, then you fit right in with the QNX people.
If you are a legacy blackberry app guy, then you can use the playbook java sdk.
If you are a flash/air guy, then you can use the flash/air sdk.
If you are a web guy, then you can use the webworks sdk.
The continued lack of technical focus and coherent communication only makes it look worse. RIM isn't only fighting everyone else to get in the market, they are fighting their own leadership who is writing capability "checks" they cannot cash.
Trying to be a Jack-of-All-Trades for rev one usually means not being very good at any. And that's a very bad thing for rev one hardware software pairs.
The continued lack of technical focus and coherent communication only makes it look worse. RIM isn't only fighting everyone else to get in the market, they are fighting their own leadership who is writing capability "checks" they cannot cash.
Conversely, there is no jack of all trade tool as well. There are many more suitable tools that developers that iOS app developers can't use, just because Apple doesn't allow it.
Wait until the Playbook is launch, then you can criticize them for not delivering.
Conversely, there is no jack of all trade tool as well. There are many more suitable tools that developers that iOS app developers can't use, just because Apple doesn't allow it.
Wait until the Playbook is launch, then you can criticize them for not delivering.
You don't parse English well either.