2 ms·
There was some confusion about it, but in general people backpedalled once they realized the language is not a systems langauge and so they redefined what "sys
by rdtsc 11y ago
There was some confusion about it, but in general people backpedalled once they realized the language is not a systems langauge and so they redefined what "systems" means.
http://techcrunch.com/2009/11/10/google-go-language/ http://techcrunch.com/2009/11/10/google-go-language/
---
Go attempts to combine the development speed of working in a dynamic language like Python with the performance and safety of a compiled language like C or C++ [...] the compiled code runs close to the speed of C.
We’re hoping Go turns out to be a great language for systems programming
---
They pit it against C and C++ and if Rob Pike doesn't know what "systems" means then well, nobody does ;-)
It doesn't matter really, Go is a popular, productive, useful language. There is nothing wrong if it "pivoted" or updated its description a few times in the past. It doesn't make bad or deficient, but there is also no point in denying it or trying to rewrite history.
- spriggan3 11y ago> It doesn't matter really, Go is a popular, productive, useful language. Yes it does, definitions matter or you end up with marketing buzzword like "serverless". Was calling Go "a system language" a marketing ploy? that's the question.