Is Go based on llvm? It doesn't seem like it, but would be curious to know why not?
Isn't this the point of llvm, to separate the "language component" from the "cpu component"?
Isn't this the point of llvm, to separate the "language component" from the "cpu component"?
Whereas with LLVM, while they could benefit from all the work that has gone into it, they would get a dependency on C++ for life.
This way, the progress is slower and multiple releases will be required to achieve some optimizations, on the other hand it is the only way to prove to naysayers that for the systems programming use case of writing compilers, Go is also a viable option.
[1] https://golang.org/doc/faq#What_compiler_technology_is_used_...
One of the other reasons relates to how stacks are handled for goroutines.