4 ms·
> I thought we killed this notion already but it still seems to be lurking around. I don't have experience with Go beyond reading some snippets, but the Asciin
by lucb1e 10y ago
> I thought we killed this notion already but it still seems to be lurking around.
I don't have experience with Go beyond reading some snippets, but the Asciinema developers clearly developed with it and they seem to think it so. It's not some notion going around but something an (at least moderately) experienced developer says.
I'm not saying they must be right, they might simply be more experienced in Python and prefer Python because of that, but I don't think it should be dismissed as "some notion that's still going around".
Edit: You just got downvoted it seems; I didn't.
- vvanders 10y agoYeah, not knocking their choice in Python. I think they made the right evaluation there. It's more that Go keeps getting held up as a replacement for C without understanding what makes C/C++/Rust viable in their domains. It's all down the the memory model and if you don't have control over that then it isn't a replacement. Take volatile for instance, there's certain pieces of hardware that you'll never be able to use Go for without wrapping some parts of the hardware in C because there's fundamental memory IO semantics that volatile provides but Go doesn't support.
- jackmott 10y agoVery many developers today do not fully understand what low level means, so very many things get called 'fast' or 'low level' or 'C-Like' that really are not.
- lgunsch 10y agoUntil you can load up Go code on a microcontroller, or build an OS kernel in it, it is not going to replace C in many circles. Go is also garbage collected, which rules it out for being low by some definitions of "low level". Low level is a very ambiguous term, for some it simple means anything to do with CLI. For others, it means kernels, drivers, etc.
- collyw 10y agoC used to be considered a high level language a few decades ago.