News for hackers. Stuff that matters.
Re:Playing with Go1.1beta2, it's much faster by pjmlp on Tuesday April 09, 2013 @03:54AM (#5516925)
> At program startup time? Java is a joke in this area.

It is always a matter if you are using a JVM (from which vendor) or compiling to native code.

Language != Implementation

Re:Playing with Go1.1beta2, it's much faster by enneff on Tuesday April 09, 2013 @04:11AM (#5516964)
> Language != Implementation

Ideally, yes. But in practice a language and its implementation (whichever one you choose) is a tool. If you're comparing tools, you've got to compare a language with its implementation.

Re:Playing with Go1.1beta2, it's much faster by pjmlp on Tuesday April 09, 2013 @04:43AM (#5517027)
So what you compare when a language happens to have multiple implementations?

Which from 6g, gogcc, go express you pick for Go?

Which from OpenJDK, Oracle JVM, IBM J9, gcj, RoboVM, Aonix Perc ... you pick for Java?

Which from Sun Forte, IBM xlc, hpcc, gcc, clang, CINT, Visual C++, ... you pick for C or C++?

Which from CPython, IronPython, PyPy, JPython, ... you pick for Python?

Re:Playing with Go1.1beta2, it's much faster by coldtea on Tuesday April 09, 2013 @11:20AM (#5518684)
That's easy. Except for C++, which is a multi-vendor language.

For all others there is a definitive, used in the overwhelming majority of cases, implementation:

Go: 6g Java: Oracle JVM Python: CPython Ruby: Matz's Haskell: GHC ...

Re:Playing with Go1.1beta2, it's much faster by pjmlp on Tuesday April 09, 2013 @12:04PM (#5519028)
Except that in many cases, e.g. Python, the canonical implementation is not the fastest one.

So of course, the presenter will carefully select the best implementation to prove his arguments, even if there are others available that contradict him/her.

Re:Playing with Go1.1beta2, it's much faster by enneff on Tuesday April 09, 2013 @05:15AM (#5517086)
It depends what you're trying to compare.
Re:Playing with Go1.1beta2, it's much faster by pjmlp on Tuesday April 09, 2013 @06:50AM (#5517269)
It is always up to the present to use the evidence that better fulfills its goals in the eyes of others.
Re:Playing with Go1.1beta2, it's much faster by cmccabe on Tuesday April 09, 2013 @03:11PM (#5520416)
There are fundamental language reasons why Java has a slow startup time. jar files do not contain native bytecode. Instead, they contain standardized, platform-independent bytecode for the Java Virtual machine. What this means in practice is that when you start up, you have to convert all this Java bytecode to native bytecode. This is a CPU and IO-intensive operation. It would be a little like if the first thing your C++ program did was compile itself every time it was run!

There are advantages to the way Java does things. You can distribute a single binary for multiple architectures, for example. However, it does have costs, and one of those is slow startup time.

Re:Playing with Go1.1beta2, it's much faster by pjmlp on Thursday April 11, 2013 @10:33AM (#5532171)
If you distribute jar files yes, there are however Java compilers that generate native code, if you are willing to pay for them.

Even Sun, nowadays Oracle, sells them as part of the Java SDK for embedded platforms.

That the JVM from Oracle, that most people think as the only way to run Java, does not offer that option out of the box, does not mean other vendors don't do it.