Titanium is not a wrapper around a web view as stated before (though that accurately explains how Phonegap works). Jeff’s answer, linked in the question, is a technically correct explanation of how Titanium works, but here’s the best version I’ve heard so far, from Marshall Culpepper:
It’s true that Titanium Mobile used the WebView (in both Android and iOS) in the pre-1.0 days. However, this is no longer true and hasn’t been since our 1.0 release is March 2010.
What jhaynie is saying in your linked question is that Titanium interprets your JS code and converts it into something that is almost identical to Objective-C.
That means you won’t find anything that looks similar to what you originally wrote in your script. Anything that must be left to an interpreter is still processed and converted, and your symbols will change (e.g. a call to
Titanium performs the interpretation of your script as any other program would do (such as a web browser). It figures out what dependencies your script has on the Titanium API and sets that stuff up. It then maps your symbols directly into (in the case of the iPhone) Objective-C.
A program usually would read in your script (which is a simply a String), interprets it, and runs C code to accomplish what your script asked for. Titanium does this before-hand to figure out what C code should be run, and does the conversion in advance.
For iPhone, the compilable C is compiled with GCC to create a native binary.
Now you have an app that you can run on your mobile device. Your compilable code has been compiled and runs at lightning speed, while the rest is converted and still interpreted in a more efficient way which runs at near lightning speed. 😛
I hope this makes sense now, because it’s all I’ve got! 😀