On Jan 28, 2008 1:53 PM, Ian Darwin <[EMAIL PROTECTED]> wrote: > > Programming C modules is always* going to be faster than any of the > > other languages listed because C is compiled, and the other languages > > listed are interpreted -- i.e. a parser needs to be loaded for each > > instantiation of the script, which can be very heavy on processor and > > memory load. > > Java can be faster than C/C++ because what you call "interpreted" is > really "delayed compilation" - Java code is compiled down to native at > runtime. Of course this only works well for long-running apps; as you > suggest, a module that has to start it up each time is going to lose > (but that's true of anything that has significant initialization > overhead!). Running it in FastAGI would solve this problem. What Sun did > on the web tier is build a framework that keeps Java "servlets" in > memory (hence, the compiled code is retained) as long as possible. Java > has done very well in the enterprise market as a result of this.
Interesting... learn something new everyday I suppose! So I guess Java is a bit of a hybrid system in this regard then. I don't do any java programming since my java course in school as I found the amount of information you needed to know just to get started (how to use the built in libraries etc...) just made the whole language quite daunting. But then again, I didn't take computer science, so the programming I do is more in the scripting domain. I did write an E911 portal utilizing a DB and SOAP connections via PHP, but let us never speak of that again :) -- Leif Madsen. http://www.leifmadsen.com http://www.oreilly.com/catalog/asterisk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
