4 ms·

Again you keep trying to position Go as a C successor, I don't understand why you are so hellbent on that. Look where C is being written today, mainly in libra

Again you keep trying to position Go as a C successor, I don't understand why you are so hellbent on that. Look where C is being written today, mainly in libraries or very/extremely performance oriented applications and low level systems programming where any kind of unecessary overhead (performance, footprint, dependencies) is actively being avoided. Where does Go fit in here? Instead Go has mainly seen an uptake in web oriented development, I personally think it also has great future in desktop style application development, but that remains to be seen.

pjmlp 14y ago
> Again you keep trying to position Go as a C successor, I don't understand why you are so hellbent on that. Actually I rather vote for D or Rust, after a few disappointments with Go's design. What I will ALWAYS defend, regardless of the language, is the use of GC enabled systems programming languages. I am an old dog and have used quite a few operating systems in academia and also internal in-house ones developed in such languages and know from experience they can be usable if only an OS vendor cared to support such languages.