Nabil Abbas <[EMAIL PROTECTED]> wrote:
__________
>When you want real speed, forget about interpreted languages.
>Personally, I would go for C++.
>
>Best of luck:)
>
Two points to concider-
1) he said C++ CGI, your C++
is going to have to be -very-much-
faster than the equivelent Java to
compensate for the CGI overhead
of starting an new process per-request.
2) Java keeps getting faster,
each year, C++ has hit a plateau.
I've heard convincing arguments
to the effect that Java will be quicker
than C++ for many real applications
within a few years.
How? Well the argument is that techniques like Hotspot can optimize
your code at runtime better than a
static compiler can. What's more
the VM can tune itself for the
hardware you actually have, and
take advantage of it, rather than
a static compiler which must make
conservative guesses about the
processor type, L2 cache, graphics card etc.
So even if C++ is quicker
now, it may not be by the time your
program is deployed.
Lastly you should concider scalability-
if you write a single threaded C++
progam for Nt (say), the fastest
system you can find will be a 1000Mhz pentium. However if you
write it in Java, you can run it on a
whole range of heavy iron without
recoding. This is great for web projects
where the numbers of users can
way exceed expectations.
Tim.
---
Due to an admin error, I'm available for 2 weeks consultancy in Feb, interested?-
Email me.
URL http://www.westhawk.co.uk/
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
