News for hackers. Stuff that matters.
Re:Ask HN: What do you like/dislike about Golang? by cratermoon on Saturday November 26, 2022 @07:21PM (#33758575)
I love case-based visibility. I don't have to look at any declaration beyond the name to know if I can use the identifier outside of the package it's declared in. In most other languages case is just convention and visibility is determined by another keyword.

Yes, I know programmers who came from a Java or C# background who continue to use naming conventions from those languages, to their detriment. I don't blame Go for their problems, though.

Re:Ask HN: What do you like/dislike about Golang? by dijit on Saturday November 26, 2022 @07:34PM (#33758677)
To each their own, it doesn’t sit well with me and I got used to `grep -rE ‘^pub’ <module>` to lazily get an idea of what is available to me.

Glad it works for you though, it’s not likely to change with my little whinge. :)

Re:Ask HN: What do you like/dislike about Golang? by joshuak on Saturday November 26, 2022 @08:25PM (#33759058)
I really hated this feature at first, but it's one of my absolute favorite things about Go now. In general Go communicates more information than other programming languages without nearly as much visual clutter. When reading code one rarely needs to check elsewhere to fully understand what is intended.
Re:Ask HN: What do you like/dislike about Golang? by sidlls on Sunday November 27, 2022 @09:29PM (#33769199)
I don't even like the concept of visibility--at least as implemented in C++, go, Rust, and a host of others. The whole notion of "getters and setters" just seems like so much pointless boilerplate. Explicitly requiring mutability, as Rust does, is much better for data encapsulation and protection.