I have a question on Go's performance that I'd like someone here, who has experience writing programs in it, to help shed some light upon.
1) Go does not have a runtime. This means that there is no JIT to do any optimizations based on runtime profiling.
2) Go is also designed to compile fast. Since it compiles fast, the compiler's time budget to do compile-time optimizations is small and it probably can't do the best job possible.
Are these two points accurate? If so, how does Go perform as well as it is claimed to do? Where is the catch?
1) Go has a runtime that's included in the binary that you get when you run `go build`. It takes care of garbage collection, goroutines etc. It does not do any JIT compilation afaik.
2) Go compiles fast because it gives up a lot of modern features (namely generics).
1) Go does not have a runtime. This means that there is no JIT to do any optimizations based on runtime profiling.
2) Go is also designed to compile fast. Since it compiles fast, the compiler's time budget to do compile-time optimizations is small and it probably can't do the best job possible.
Are these two points accurate? If so, how does Go perform as well as it is claimed to do? Where is the catch?