3 ms·

> The amount of Go projects in Cloud Native Foundation shows otherwise. That says nothing at all, actually. Beyond the transparent appeal to authority, why wo

> The amount of Go projects in Cloud Native Foundation shows otherwise. That says nothing at all, actually. Beyond the transparent appeal to authority, why would anyone take decisions seriously when they are made without any technical merit in mind and just follow a mix of cargo curlting and pushing in-house tools, such as the case of the kubernetes migration to Go? > Most people pick languages based on platforms, not a language in isolation and go hunting for projects. The whole point of this discussion is that people don't, and make decisions without any technical merit in mind. > As for the point migrated to a compiled language from Python, if it wasn't for the shinny thing, the migration would have been to a compiled language with proven record in prodution like C and C++, as it is common on the ecosystem. This personal assertion ignores the fact that there are plenty of alternatives that considerably improve over C++, let alone C (?!), not to mention that it reiterates again the mindless cargo cult mentality behind Go. > And regarding Java, everyone that actually knows the ecosystem is aware of AOT compilers since 20 years now, even if they have been available as commercial only for the most part. I don't understand what point you tried to make with regards to Java, specially as the Kubernetes migration from Java to Go was pushed by people who worked on Go, and thus it had an unavoidable self-serving "eat your own dogfood" aspect to it.

lelanthran 4y ago
> This personal assertion ignores the fact that there are plenty of alternatives that considerably improve over C++, let alone C (?!) While it is easy to improve on C++ it's proven difficult to improve on C[1]. C++ is an exceptionally large language, with lots of features that interact in subtle ways which trip-up even experienced programmers from time to time. It includes all the footguns from C, and adds an order of magnitude more. C is a dead-simple language with only a few really dangerous footguns (which are also present in C++), mostly related to memory errors (corruption, leaks, races, etc). I view C++ as "C with more footguns". I view Go as "C without the memory error issues". It's not really comparable to C++ because it is a better C, not a better C++. [1] I think that only Go has managed to improve on C.
pjmlp 4y ago
Docker took the decision to pick Go when it was at version 1.2, hardly that much proven into the battlefield. In 2014 unless we are talking about Ada, there were hardly any better alternatives to C++. If Go is so much better, why does Python eco-system keeps using C++ instead of Go for ML libraries?
- jen20 4y ago
  One reason is that the Go runtime makes building FFI interfaces rather complex.
- anthk 4y ago
  >C++ instead of Go for ML libraries? Because (Open)Blas, Atlas and such have decades of C/C++ implementations.

lelanthran 4y ago

> This personal assertion ignores the fact that there are plenty of alternatives that considerably improve over C++, let alone C (?!) While it is easy to improve on C++ it's proven difficult to improve on C[1]. C++ is an exceptionally large language, with lots of features that interact in subtle ways which trip-up even experienced programmers from time to time. It includes all the footguns from C, and adds an order of magnitude more. C is a dead-simple language with only a few really dangerous footguns (which are also present in C++), mostly related to memory errors (corruption, leaks, races, etc). I view C++ as "C with more footguns". I view Go as "C without the memory error issues". It's not really comparable to C++ because it is a better C, not a better C++. [1] I think that only Go has managed to improve on C.

pjmlp 4y ago

Docker took the decision to pick Go when it was at version 1.2, hardly that much proven into the battlefield. In 2014 unless we are talking about Ada, there were hardly any better alternatives to C++. If Go is so much better, why does Python eco-system keeps using C++ instead of Go for ML libraries?

jen20 4y ago
One reason is that the Go runtime makes building FFI interfaces rather complex.
anthk 4y ago
>C++ instead of Go for ML libraries? Because (Open)Blas, Atlas and such have decades of C/C++ implementations.