3 ms·
You said the BB10 can do so much more but then provided a list of fairly insignificant features and the mention of potential. If you were a sales person, you w
by wvenable 14y ago
You said the BB10 can do so much more but then provided a list of fairly insignificant features and the mention of potential. If you were a sales person, you would have lost the sale.
QNX being real-time has little to do with real world performance. While the Z10 does have good performance but it also has a pretty high clocked processor and double the RAM of competitor devices.
- kunai 14y agoIt may not be much of a boost in performance, but RTOS systems do enhance stability. First off, there are no memory leaks, so the performance of the phone won't degrade over time requiring a reboot as is often the case with my Nexus 4. The system will still stay just as fast as it was from day one without needing a reboot. Second, QNX is a microkernel in contrast to Android's monolithic style kernel or WP8 and iOS' hybrid kernel, so one process gone awry won't bring down the entire system. Again, a big stability boost, which is key in a business environment. Third, process scheduling is unmatched by any conventional OS compared to a real-time operating system, so multitasking is improved and is more rich compared to the crippled implementations that iOS and Android use. I'm sure the average Joe would appreciate speed, functionality, and stability, don't you think?
- wvenable 14y agoFirst of all, how does a real time kernel have anything to do with memory leaks in applications or services? It's not as if modern Linux or Windows kernels leak kernel memory. Secondly, unless you go all the way back to DOS or Mac classic you won't find an OS where a process can bring down the entire system. I can't remember the last time I had a full system crash on any OS on any device (that wasn't caused by faulty hardware). I haven't heard anything that suggests that a real-time kernel has any effect on the multitasking performance of a GUI operating system. It's not as if iOS or Android have crippled implementations, as you said. They just make a different trade off and they should, in fact, more suited to this kind of work.