4 ms·
To me it's largely about the communities that each have attracted. Golang has a lot of overlap with the Node world and the more trend-following parts of Ruby an
by eropple 11y ago
To me it's largely about the communities that each have attracted. Golang has a lot of overlap with the Node world and the more trend-following parts of Ruby and Python, IME, and my experience with all of those suggests to me that that's selecting for a very product-focused community with, frankly, a generally lower need for high-end approaches and tactics. But Golang is popular, and it is thought to be easily accessible, and so the easily accessing need more stuff to read and talk over. So you will see many more introductory and "obvious" posts, and it'll be reflected in the ones that jump out of the Golang pond into more general environments. It's not exclusively that, of course - there are plenty of console emulators, etc., written in Golang - but they're not what Product People are reading because they don't know how to handle errors in their new pet language of choice yet.
n.b.: While I have seen very, very competent programmers writing good software in Golang despite the language's considerable efforts to thwart them, and doing so in a product-focused environment, my intuition, as an outsider (which I disclaim because, as somebody whose job is to build systems that do not fail, the worse-is-better ethos of the Golang community scares the hell out of me), is that there's not as much deeper discussion to be had when you are of a generally product-focused mode; many things are unspoken and many others are very specific to your tiny slice of the world--is there as much to say, publicly, about that stuff? And are the other loud people in that community even listening when you do?
Rust seems instead to attract immigrants from what I consider better programming environments; not necessarily better business environments (almost certainly not, in the cases of people I personally know) but environments that are more welcoming and enabling of building hard stuff. The Rust people I know are migrants from heavy-hitter C++ backgrounds, functional programming backgrounds (the biggest fan I know personally previously lived and breathed OCaml), and a few from the deep end of the Ruby community. Thus to me it follows that the interesting stuff that leaks out into the general public is going to be more esoteric to many outside of it (and maybe, for you personally but certainly for me, more interesting).
It also probably helps that the Rust APIs are really smartly designed and it seems--though I am a Rust novice, and this is a personal take--much harder to shoot yourself in the foot. There may just be less need for "these things work but will secretly ruin your day" in general.
A single language that can demonstrate this continuum pretty well is actually Java, I think--you see tons upon tons of "here's why you don't use == in Java"-level posts, but you also see stuff like Aleksey Shipilev absolutely throwing down useful and actionable stuff about the JMM. Java as a community is fragmentary and huge, and there's more space for, and more need for, discussion at both ends of things.