I agree the SDK can get you far but it isn't a complete replacement and it probably will never be. You stated in earlier post: Originally Posted by nathan you developers do not need a device to get things going at all! ..and that is not true. The Scratchbox+SDK platform does not use the same architecture the target platform uses. It either runs x86-32 software, or uses QEMU to emulate ARMEL. QEMU contains bugs. For example, see cmake thread, or fact it doesn't run GUI, and sometimes my ARMEL environment is screwed and I have no clue what happened. So architecture specific problems are concern. It is also difficult to test usability without touchscreen and finger/stylus using mouse instead. I wonder how Nokia deals with this internally?!
you developers do not need a device to get things going at all!
Which brings me to Scratchbox not emulating certain hardware features the real device has. For example, I've seen posts about using GPS and Bluetooth inside the SDK. The former is easy to solve (gpsd or gpsfake running on host platform port 2947 reachable from Scratchbox) but the latter is a bit harder to solve. Another example, and that is my main reason, is that it doesn't emulate performance of Nokia N900 rendering tools such as htop, iotop, powertop, latencytop, nearly useless.
Although the number of situations these problems arise is up for debate, karma reflects past effort not present or future effort, and I'm not saying above must be fixed (is difficult), it is IMO important to take note.