>I think that the definition of "compilation" will continue to blur, especially as JIT grows.
>
>Changes in data structures are also an issue- as xml gains ground, interpreters are and always will be required to cope with these transactions. As data is the cornerstone of most applications, it seems counterintuitive to focus on true compilation for apps when most processing and potential bottlenecks will be in interpreting the data.

Sure. In fact, "binding" screens/dialogs to data in virtual every language is interpretive in nature. You cannot hardwire it. The app has to perform field name lookups in order to perform data exchanges as well as convert between different data types. All your SQLEXEC's need to be interpreted, unless you "prebuild" them. That's why at some point, all apps appear to perform the same when it comes to displaying data ... be it VC++, VB, Delphi, etc. (Sorry, but VFP is the slouch in this company ... although FPW used to outperform them all).

The advances in CPU speed, memory size, etc. has a lot to do with the shift in emphasis. However, until they can cram something better than a 386 into hand-helds, compilation will still have a place (IMO).

At the very least, I hope that the "interpreter" will at least be "compiled". :)