Top all-time · #9222
Alex Yakunin
Personal blog · alexyakunin.medium.comprogrammingsystems
Alex Yakunin's personal blog at alexyakunin.medium.com covers programming and systems. Since 2020, 8 different Hacker News readers have linked it 11 times, most often “Astonishing Performance of .NET 5: More Data”. It is still writing: the last post was on 2026-06-11, and you can follow it by feed.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
HN commenters cite these Medium posts as sources in C# vs Go debates, covering goroutines versus async/await benchmarks, memory use, slice behaviour and SIMD intrinsics.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- /go-vs-c-part-1-goroutines-vs-async-await-ac909c651c113 people · 3 mentions · first linked 2022-04-30
- Astonishing Performance of .NET 5: More Data2 people · 2 mentions · first linked 2020-11-20
- Astonishing Performance of .NET 52 people · 2 mentions · first linked 2020-11-11
What Hacker News says?
While I can't answer the question directly there is an article about C#-s async/await vs Go's goroutines, which compare the two approaches, and while some of the stuff is probably stack-specific, a lot of it is probably intrinsic to the approach: - Green threads scale somewhat better, but both scale ridiculously well, meaning probably you won't run into scaling issues. - async/await generators use way less memory th…
Comment linking /go-vs-c-part-1-goroutines-vs-async-await-ac909c651c11
on “Achieving 5M persistent connections with Project Loom virtual threads”Submitted .NET 6 vs .NET 5 speedup as a story · 331 points
HN discussionI'm not an expert but from the benchmarks I've seen C# consumes considerably less memory than Goroutines. Eg: https://alexyakunin.medium.com/go-vs-c-part-1-goroutines-vs-...
Comment linking /go-vs-c-part-1-goroutines-vs-async-await-ac909c651c11
on “Why Tracebit is written in C#”Submitted Astonishing Performance of .NET 5 as a story · 233 points
HN discussionAnd speaking of unsafe code and x86-specific (i.e. non-portable) AVX2 intrinsics: 1. First, unsafe doesn't mean you shouldn't use it on .NET. It just means you need to do more checks manually. 2. A lot of things you can do in Go are unsafe in .NET terms - e.g. even slice is a leaky & unsafe abstraction: https://alexyakunin.medium.com/slice-an-extremely-leaky-abst... 3. Yes, the fact Go doesn't support SIMD intrinsic…
Comment linking /slice-an-extremely-leaky-abstraction-in-go-b0eb42bf22c4
on “Astonishing Performance of .NET 5”Submitted Astonishing Performance of .NET 5: More Data as a story · 2 points
HN discussionI want to like F#, but the syntax is just bonkers to me. There are keywords which are used in only one context, such as `then`, and sometimes an operator means something in one context, but something else in another. e.g: equality/assignment let a: int = 1 // Assignment a = 3 // Testing equality, will give you an error a <- 4 // Assignment, valid There's an article here with more things: https://alexyakunin.medium.c…
Comment linking /crying-out-loud-what-i-like-dislike-in-f-c88e746dfcde
on “The combined power of F# and C#”Submitted Astonishing Performance of .NET 5: More Data as a story · 1 points
HN discussionHm. I know this from my personal work, replacing Go code with an async/await code. There's a bunch of benchmarks that compare C# async/await and Goroutines (e.g. https://alexyakunin.medium.com/go-vs-c-part-1-goroutines-vs-... ). Go still wins there, but they all miss the very important case of nested async/awaits. These microbenchmarks also focus on looking at Go channels versus other synchronization methods, which…
Comment linking /go-vs-c-part-1-goroutines-vs-async-await-ac909c651c11
on “Guide to Java Virtual Threads”Submitted Astonishing Performance of .NET 5 as a story · 1 points
HN discussionSubmitted The Ungreen Web: Why Our Web Apps Are Terribly Inefficient? as a story · 1 points
HN discussion
