3 ms·

There some bad judgment around, due, in my opinion, to a couple of main reasons: - heavy Go marketing, which (intendedly or not) makes devs think that Go is "g

There some bad judgment around, due, in my opinion, to a couple of main reasons: - heavy Go marketing, which (intendedly or not) makes devs think that Go is "great at everything": you can't tweak memory management? that's a feature¹. - simplified/misguided categorization into old language models: Golang is the new C, Rust is the new C++. I think with a long enough time, the roles of the two languages will become significantly clearer. ¹: to clarify, that's a feature in some contexts, but not in others (therefore, not appropriate for "everything").

dan_quixote 7y ago
> I think with a long enough time, the roles of the two languages will become significantly clearer. I also expect this to be the case. But when I try to think of historical context, I come up blank. Was there this much polarization between languages in the past? I remember similar rumblings between Java and C# like 15-20 years ago, but that had more to do with the corporate backing and licensing IIRC. This feels more like political/tribal arguing.