Hacker News Reader

Comment by Glavnokoman | Hacker News Reader

Yep. C++ is not good at naming things somehow. But bringing up Golang in a discussion about naming is just ridiculous. Unless you want to show that C++ is not actually the worst.

View on HN

Is go worst than rust at naming? It took me a while to get used to Cow and Arc... (not to mention "fn" which to me will always be the french far right political party)

I like that Rust has optimized certain bits for ease of intermediate use. Sure those could be EitherOwnedOrBorrowed and AtomicReferenceCountedPointer, but that'd be annoying to type once you know them. They're also not hard to remember if you learn the acronyms (for me, at least).

  EitherOwnedOrBorrowed and AtomicReferenceCountedPointer, but that'd be annoying to type once you know them.

code is read more than it is written, so having those longer terms helps with reducing mental load and providing self-documenting code

and with most modern ide or even text editors providing autocompletion, (imho) i think abbreviations not really neccessary (though they can be fun in the case of kotlin ^^)

I disagree. Code should optimize for the things you want to look for being relatively the most prominent. This is why I think go is harder to review: the bits you actually care about are overwhelmed.

well, i think we can at least say, there is a balance for sure, so there is a limit to verbosity where it get overwhelming, ill defintely agree to that

To me, the parent poster didn't imply that golang's naming is better, they just wondered why there's a lack of naming conventions regarding threading in general.

Ah! Thanks! You're right. I did not read it this way...

Latch is actually the standard name for this concurrency construct.

It's the other way around. Latch is the standard accepted name for this concurrent construct. It is also used in Java, databases, concurrency papers, etc.

Reply on news.ycombinator.com