upvote
Maybe so, although I don't recall it being that bad.

But Go wasn't designed for CLI apps. It was designed for writing highly multi-threaded servers at Google, according to the designers, hence the focus on features like goroutines. And in that context startup time just doesn't matter. Startup time of servers at Google was (in that era) dominated by cluster scheduling, connecting to backends, loading reference data and so on. Nothing that a change in programming language would have fixed.

Google didn't use classloader based frameworks so that also wasn't relevant.

reply
Golang is frequently used for CLIs, even if it wasn't designed for that exactly
reply
If you want to write CLI tool, you use Rust.
reply
Or you use Golang? A lot of the time there isn't a big difference.
reply
Who said that? Go is pretty amazing to whip up great CLIs quickly.
reply
deleted
reply
Not when using commercial JDKs, but naturally most HNers never worked on companies that paid for those.

For example initial JIT caching experiments on OpenJDK came from J/Rockit.

reply