Hacker News Reader

> For example, it's hard to build command line tools that start quickly if you target the JVM.

Only for those that don't know what they are doing.

There are plenty of JDKs that AOT compile to native code.

Including the freely-available GCJ, a part of GCC that's not often included by default anymore.

Isn't GCJ obsolete and dead?

It is obsolete as most of its devs moved on to other stuff.

But the gcc folks keep it alive, because many of the gcj unit tests stress parts of the toolchain that other languages don't use.

So I imagine that for quick command line scripts that can live with an aged Java 1.4 API it might still work.

Okay, so how do I do this? Because if I write a simple Scala program that prints "Hello World" it can take like three seconds to start.

I think that's pretty much untrue.

That program is 0.x seconds on Scala-JVM and 0.0x seconds on Scala-Native.

Well, Scala-Native should of course be much faster.

The last time I looked at this was a awhile back; maybe it was 0.3 seconds and I misremembered it.

That sounds more like a Scala issue than anything else. A Java Hello World app runs in about 50 msec.