Top all-time · #6171
Sylvain Wallez
Personal blog · bluxte.net/musingsprogramming
Sylvain Wallez's personal blog at bluxte.net covers programming. Since 2008, 13 different Hacker News readers have linked it 14 times, most often “Go: The Good, the Bad and the Ugly”. The last post was in 2023, but the archive is still widely read.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN commenters cite Sylvain Wallez's posts on Go's mutable data shared over channels and on Rust's unwrap(), mostly as support for their own points.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Go: The Good, the Bad and the Ugly7 people · 7 mentions · first linked 2018-04-10
- TestResult: a Rust error type that panics early (2023)2 people · 2 mentions · first linked 2024-11-02
What Hacker News says?
I'm not familiar with golang, but I did read about a concern with variable mutability and race conditions when communicating across channels: https://bluxte.net/musings/2018/04/10/go-good-bad-ugly/#muta... """ As we saw above there is no way in Go to have immutable data structures. This means that once we send a pointer on a channel, it's game over: we share mutable data between concurrent processes. Of course a cha…
Comment linking /musings/2018/04/10/go-good-bad-ugly/
on “Next steps toward Go 2”Submitted Go: The Good, the Bad and the Ugly as a story · 159 points
HN discussionHey thanks for commenting and sharing! My experience with golang was pretty short; this was back in the days of `go get` and I just couldn't get used to the dependency management system. I think others have had the same problem: https://bluxte.net/musings/2018/04/10/go-good-bad-ugly IMHO a language is a combination of different factors: the community, the spec, the libraries, the support, the toolchain, etc. and the…
Comment linking /musings/2018/04/10/go-good-bad-ugly
on “Concurrency in Python: CSP and Coroutines”Submitted Go: The Good, the Bad and the Ugly as a story · 26 points
HN discussion> That section briefly described that, broadly speaking, using unwrap() is okay if it’s in test/example code or when panicking indicates a bug. I've come to the conclusion that even in tests unwraps look ugly. Especially in doc tests which serve as examples the code is better off using regular "?" that one would see in other parts of code. (that is: don't treat test code as a "worse" kind of code) In Signstar we're…
Comment linking /musings/2023/01/08/improving_failure_messages_rust_tests/
on “Using unwrap() in Rust is Okay (2022)”Submitted Erlang's typing system: less is more? as a story · 7 points
HN discussionSubmitted Go: The Good, the Bad and the Ugly as a story · 5 points
HN discussionSubmitted Go: the good, the bad and the ugly as a story · 4 points
HN discussionSubmitted Go: The Good, the Bad and the Ugly as a story · 3 points
HN discussionSubmitted Getting meaningful stack traces from Rust tests returning a Result as a story · 2 points
HN discussionSubmitted Go: the good, the Bad and the Ugly as a story · 2 points
HN discussionSubmitted TestResult: a Rust error type that panics early (2023) as a story · 1 points
HN discussionSubmitted Go: The Good, the Bad and the Ugly as a story · 1 points
HN discussionSubmitted Go: The Good, the Bad and the Ugly as a story · 1 points
HN discussion
