I thought I was building a C replacement. I was wrong
birdculture
17 points
1 comment
September 29, 2026
Related Discussions
Found 5 related stories in 109.9ms across 7,945 title embeddings via pgvector HNSW
- Marketing failure: I thought I was building a C replacement. I was wrong lerno · 15 pts · August 16, 2026 · 88% similar
- C Is Not a Low-Level Language (2018) tosh · 93 pts · September 07, 2026 · 56% similar
- C Strings: A 50-Year Mistake – By Trần Thành Long rbanffy · 12 pts · July 15, 2026 · 52% similar
- Everyone Says Assembly Is Untyped–Everyone Is Wrong adamrezich · 31 pts · August 20, 2026 · 51% similar
- Claude Is Not a Compiler bryanmikaelian · 148 pts · July 21, 2026 · 50% similar
Discussion Highlights (1 comments)
Panzerschrek
> methods first I agree, that sometimes doing things OOP-style with methods isn't the right choice and using plain structs and free functions is a better way of doing things. But there are cases where using methods is inevitable - when internals must be hidden in order to prevent incorrect usage. Also it's needed if one needs runtime polymorphism, in such cases (in C++) inheritance and virtual methods come to rescue. Doing so in C way (with void pointers and structs containing function pointers) is less ergonomic and bug-prone.