Posted on 04/25/2009 10:47:16 PM PDT by libh8er
This is from the wikipedia article on Java vs C++ performance. Also check references 7 and 8.
Or Oracle makes MySQL more compatible with Oracle DB, and puts a ceiling on MySQL performance so that people migrate to Oracle DB as their performance needs increase.
That’s basically what I meant. MySQL as a free alternative to Oracle DB and comparable in performance wont exist. I wonder if it would be still “legal” to run earlier versions of free MySQL in production environments.
If Java were a profit center, Sun might still be Sun instead of Oracle.
But then Java might not be what it is today.
It certainly isn't what it will be tomorrow, eh?
ping
LOLOL!!! Now I don't care who ye are, thet right there's funny!
Might not hurt to start learning Ruby.
And yet Krakatoa was actually west of Java. That movie didn’t get anything right.
The Java of 2009 is fatter and uglier than what I left behind in 2000. It's certainly the last thing I would put on an embedded system. Conversely, the gcc/g++ compilers continue to get better. The code is getting smaller and faster. Exactly what I want in an embedded system.
Java is not best suited for graphics apps. The AWT can bog down a system and cause poor performance. Java’s forte is *server side computing* - business logic, security, database connectivity, messaging, remote computing, web apps..etc. As for embedded systems, I have no experience with them but I know Google Android is Java based. Google even publishes an API so you can write your own apps for your phone.The Blu Ray specification(BD-J) also calls for a Java implementation.
In 1996, I was using Java for server side CORBA. The JVM garbage collector made amends for the crappy state of CORBA code at the time. The C++ versions leaked memory. Java did too, but had a means to clean up. In 1998, I joined a project in progress. It was a giant applet with Oracle stored procedures for the back-end data. It performed terribly on the Netscape browser. I found a nice profiling tool and discovered most of the problem to be handling of memory by the garbage collector. I ported the applet to run on Microsoft's JVM. It ran MUCH better. The MS JVM had a superior garbage collector. I further improved the code by eliminating thousands of "font" objects and replacing them with a fixed set of about 20 common font objects. That reduced the memory footprint and reduced startup time. Just as the new, fast implementation was ready for delivery to the customer...Microsoft abandoned their JVM. We were stuck with Netscape/Sun again. Barf.
I read through it - and I must admit - I was surprised. I had a few thoughts I felt like sharing after reading -
While it may be true that C++ is harder to optimize - I don’t see that as a valid point in a speed comparison. The proper use of optimizers and debuggers go a long way to dispelling those issues.
For C++ on a Windows/Linux platform, you should really go with Intel’s compiler. In my experience, it produces the fastest code. Comparing to free/legacy compilers just aint right.
I understand in theory the benefits Java could take advantage of in coming versions - but properly written C++ code can as well.
For anyone who has programmed both - especially for a Windows/Mac environment, or as a Web Service - the reality of the situation is that C++ outperforms Java, has less issues, and requires less overhead to maintain.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.