Re:Why Java still isn't faster than C++
on
Java Is So 90s
·
· Score: 1
Did you try reading any of the rebuttals helpfully provided by the site (the links at the bottom)? They are pretty damning, and show that his benchmark C++ programs are ridiculously inefficient, leak like a sieve, and improperly measured in any case. The rebuttal benchmarks don't look like they were bunched together by an amateur unfamiliar with the language either.
In the end, the Java Runtime is doing a bunch of stuff that simply doesn't get done in C++. No manner of optimisations are going to make something look like nothing.
Under very narrowly defined circumstances, you are not required to distribute the sources. Under all other circumstances, you are required to distribute the sources.
The terms of the GPL only apply to your derivative if you are re-distributing it. In other words, you cannot change the licence without the say-so of the author.
This is quite simple, and in no way means that the original author loses any rights to their own code. You are still constrained by the GPL, in so far as you must also distribute your derivatives under the GPL.
So basically none of the GPL'd software out there is copyrighted any more. Which is good, because it means you can do whatever you want with it. It's in the public domain.;-)
You can do what you want with it, unless what you want to do includes re-licencing it in any way, shape or form. If an author puts his work under the GPL, it is guaranteed to stay under that licence, no matter how many people alter it. This is a very simple licence.
Slashdot Mirror
For your reading pleasure:e d/
http://www.w3sys.com/pages.meta/benchmarks.html http://www.freewebs.com/godaves/javabench_revisit
In the end, the Java Runtime is doing a bunch of stuff that simply doesn't get done in C++. No manner of optimisations are going to make something look like nothing.
The terms of the GPL only apply to your derivative if you are re-distributing it. In other words, you cannot change the licence without the say-so of the author.
This is quite simple, and in no way means that the original author loses any rights to their own code. You are still constrained by the GPL, in so far as you must also distribute your derivatives under the GPL.
So basically none of the GPL'd software out there is copyrighted any more. Which is good, because it means you can do whatever you want with it. It's in the public domain. ;-)
You can do what you want with it, unless what you want to do includes re-licencing it in any way, shape or form. If an author puts his work under the GPL, it is guaranteed to stay under that licence, no matter how many people alter it. This is a very simple licence.