[jdcarr]

What's your use cases where you've found startup time to be a significant issue?

[lobster_johnson]

Command-line programs.

[jahewson]

Short-lived processes are an issue, because while startup time can be ok, code won't perform well until it's hot enough to be JITed.

[pjmlp]

You can set the JIT threshold to 0, assuming the impact would still be worthwhile.

The alternative is a commercial JDK, almost all of them do support AOT compilation.

[kasey_junk]

Long running processes without a lot of events can also deal with "startup issues", in that they won't trigger JIT.

[pjmlp]

You can set the JIT threshold to 0, then it will JIT the full bytecode on startup, but it might perform worse.

[_0w8t]

Fast compilation and minimal startup time in Go allows for very fast development feedback similar to what one gets with interpreted languages.