Linked by Peter Gerdes on Mon 10th Jan 2005 17:35 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



I guess I must misunderstand something. As I understand it, there appear to be two alternative models being discussed here.
1) Static Compilation *once* and for all in the development environment.
2) JIT Compilation *each time* the application is run, so that it can be optimized for a specific environment.
Surely the ideal is to compile an application *once* on a particular hardware configuration? So why not employ a third model:
3) Compile the whole application *once* when the application is installed. Recompile only when significant changes are made to the execution environment.
Or am I being too simplistic?
Kramii.