3 ms·
I don't think it's the equivalent. First native iPhone apps are compiled. Second Apple specifically made it that garbage collector is not used, although they r
by malkia 17y ago
I don't think it's the equivalent.
First native iPhone apps are compiled. Second Apple specifically made it that garbage collector is not used, although they released it for Mac OS X (Objective C 2.0 runtime).
Here is how low-level - "C", and assembly - for example you can use (depending on the ARM version) various math libraries on the iPhone to get speedup.
Check the oolong engine for more details.
- abolibibelot 17y agoThere's a lot of people here who seem to think .NET bytecode (or Java for that matter) is run by the VM. How 90's of you guys. It's compiled on first run, so technically there's no difference with (iPhone) Objective-C apps. The GC may factor in, though.
- malkia 17y agoMaybe, but where it is compiled? On the device itself, right? If that's the case - what kind of compiler we are talking here? A really good optimizing compiler would probably use a lot of memory, and cpu clocks. I'm not expert, so I might be totally wrong about it. Just thinking out loud.
- nomoresecrets 17y agohttp://developer.android.com/reference/java/lang/Compiler.html http://developer.android.com/reference/java/lang/Compiler.ht... "The Android reference implementation does not (yet) contain such a JIT compiler, though other implementations may choose to provide one." I thought that was one of the complaints about Android/Java - the VM runs the code; there's no JIT. That's why the prototype Dalvik JIT that was announced very recently was big news. It certainly wasn't announced in the 90s, anyway.