The degree of Online and specific, niche kinds of Nerdy you have to be to get this joke is (a) hilarious and (b) terrifying, because I immediately laughed out loud.
> That said, if there’s one thing which Go got right, it’s that tooling matters.
oh my god THANK YOU. i wouldn't be surprised if 90% of the reason rust took off was because of its decent tooling. other languages just seem to forget or deprioritise it and it's a huge huge mistake
As someone who started their programming career as a rubyist, I agree. But also, every time I write a type signature, I think: in Ruby this would need at least a 5 line test.
At the same time, Cargo still hugely underresourced compared to rustc — and I don’t think the lang team feels any responsibility for, say, rustup. Just to say, still a lot to improve on the holistic product thinking.
Read this earlier.
They're just not doing enough on the committee and the "banning viral keywords" was an insane jab at Sean.
Honestly, at this point, I'm hopeful for Carbon as the true successor (I just hope they ditch the Go style "we export symbols if they're capitalized". I dislike it so much 😭)
I want to hold up a powerful artifact to anyone who thinks its a good idea and shout "I REJECT THEE, PASCAL CASE!" and see if it forces a demon out of them.
On a semi-related note, something I always found amusing working in C# codebases was how—even with the existence of specific visibility keywords—it was still common to see private class fields prefixed with a `_`, like `_firstName`.
Some people just copy what they've seen in the wild. I'm convinced it's why some people treat `return` as a function in some languages because they saw it once and now they just do it everywhere.
I just wrote some Go for the first time the other day, and the capitalization thing was a real shock. Same vibes as "wait, indent is *semantic*?" when I learned Python.
“Of course, there’s also the question of whether specific C++ standard committee members are just being very, very stubborn, and grasping at straws to prevent an evolution which they personally aesthetically disagree with.”
Comments
oh my god THANK YOU. i wouldn't be surprised if 90% of the reason rust took off was because of its decent tooling. other languages just seem to forget or deprioritise it and it's a huge huge mistake
They're just not doing enough on the committee and the "banning viral keywords" was an insane jab at Sean.
Honestly, at this point, I'm hopeful for Carbon as the true successor (I just hope they ditch the Go style "we export symbols if they're capitalized". I dislike it so much 😭)
I just don't get it. How is that better than and/or preferred over a keyword? 🫠