I used to be a blackberry developer, granted it was my first job, but nevertheless: I'm glad blackberry died it's slow, painful death. Developing for blackberr

I used to be a blackberry developer, granted it was my first job, but nevertheless: I'm glad blackberry died it's slow, painful death. Developing for blackberry was a disaster, I can even say it was the single worst programming experience I've been through. To name issues off the top of my head: - signing code with BB's SLOW servers every time you wanted to deploy to a physical device (I'm talking waiting times of 50+ seconds). These servers regularly keeled (there were websites to tell you if they did), meaning you couldn't deploy to a device to test on, which was important because: - emulators were so far off the actual devices you needed to deploy to multiple devices regularly to make sure you code worked - devices would restart regularly, and blackberries took a long time to start - each device, with the same OS, had different quirks, and different APIs would give different outputs depending on a combination of device/OS-version, which was important when those outputs were for things like screen size. - the developer tools were just not there: things like getting to logs, etc - heroics were required to do things like override the default blue highlight in a list selector (i forget the name) in order to get our application's design to work right. I used to do dual Android/Blackberry development, and I hated projects on BB. I am however talking BB OS 5/6/7. Our company wouldn't even invest in developing natively for BB10, we'd just port android. Good riddance.