4 ms·
> I have huge respect for Rob Pike but there's a bit of revisionist history going on here. > Go was originally envisioned as a systems programming language. A
by blablabla123 7y ago
> I have huge respect for Rob Pike but there's a bit of revisionist history going on here.
> Go was originally envisioned as a systems programming language.
Already with the release of Go 1 it was quite clear that Go has its best fit as a Server language. I don't think the usage of a language can really be planned. But looking at the previous works of the language authors, it's clear that they worked on solutions for distributed systems.
Also I think like 10 years ago people would have written stuff in C++ that today nobody would even remotely consider writing in it.
- mgummelt 7y ago> Already with the release of Go 1 it was quite clear that Go has its best fit as a Server language. CLIs as well. Before Go, how did you build a native CLI in a garbage collected language?
- pjmlp 7y agoI don't know, by using one that had support for AOT compilers? Something like Java, .NET, OCaml, Haskell, D, Scheme, Common Lisp? Yes, it isn't a typo regarding Java and .NET, there are AOT compilers for them since around 2000.