Thread: eMonitor
View Single Post
Old 12-11-2012, 04:54 AM   #67
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by twobob View Post
One thing you don't (directly) mention in this tech lowdown is that code not specifically designed for the devices will/may have extra slowdown owing to other resource/optimisation related issues.

Or to put that another way - code specifically crafted for the device from the ground up will (usually) outperform code that is just dragged kicking and screaming onto the platform.

: )
One of many reasons why I like "programming on the bare metal". I have always been a big fan of pushing limited technology much farther and faster than most people believe is even possible. Often, the hardware is capable of far more than the device drivers even attempt to support (due to developmental budget constraints).
geekmaster is offline   Reply With Quote