On Wed, Nov 03, 2004 at 04:09:12PM +0000, Matt Parker wrote:
On 3/11/2004, "Brett Parker" iDunno@sommitrealweird.co.uk wrote:
Like I said, you really need to read up on the subject before spouting off inflammatory, but false, statements. This is how it works:-
- You compile your source code into byte-code.
- The JVM loads your byte-code at start up
- The "Just-In-Time" Compiler compiles your byte-code to native code
on the fly and optimises it on each iteration 4) On tight loops you therefore can end up with more optimised native code than something like GCC can produce
The only thing is that this process happens everytime you re-start the JVM, but then if you're running it on a server (where I believe Java should only really live - it's not useful for desktop apps really) you don't care about that because you never restart it.
Sorry, never restart a Java servlet engine? Never restart a Java app? I find this a fascinating concept, and one that I've never actually seen work.
You'r obviously not using it correctly. If you look on a site like JobServe you'll see that Java for server-side processing is one of the (if not the most) common languages. All those people can't be wrong.
You've seen the number of sites that use PHP, right? Are you saying that all those people are also not wrong? If you're just going on numbers, there's a hell of a lot of Java developers, and PHP developers about, what's used depends on who's available, not neccessarily on wether it is right for the job. Please don't use the argument that "it's got lots of users, therefore it's good", it isn't an argument that sticks.
Thanks,