Quote:
Originally Posted by kartu
May I ask for how many out of those 124 you had payed?
Need to go native "to take advantage" is not true. Software on older Sony models also followed VM paradigm. Idea is, that you implement memory/CPU intensive basic functions in native code, then do the rest using language with automatic memory management. (garbage collector)
It's a common pattern, actually, followed by many, for instance, by World of Warcraft.
Going native makes sense if system doesn't provide performant version of needed operation out of the box. But if anything, it makes mem leaks / crashes more likely.
|
It isn't just about compiled/interpreted code, it is about expected behaviour and UI. Each system will have different user interface conventions, different expectations of how a program will react to a particular action. Just transporting an application from one system to another with no allowance for these will rarely produce an ideal result. See the initial response to the Bluefire port to Android for example. It did things in an 'iOS way', which weren't intuitive to Android users.