1. Simplicity vs. Feature‑overload
Many commenters argue that C’s minimalism is a virtue, while C++’s rich feature set is a source of pain—especially for teams that are not already fluent in C idioms.
- Keyframe says, “Working in a group of people on a C codebase tends to introduce pain on multiple levels unlike some other languages.”
- uecker counters, “Working with a group of people always causes pain, but I found the pain much less severe for C than for C++.”
- randomtoast notes, “C++ compile times are mostly a self‑inflicted wound via templates and metaprogramming, not some inherent tax you pay for having virtual functions.”
2. Language choice for game development
The discussion repeatedly circles around which language is best for writing games, weighing C, C++, Rust, Go, Zig, Odin, etc.
- vascocosta writes, “I love languages like C, Golang, Odin and Zig… I often work with network code that is highly concurrent, must be as correct as possible and benefits from good performance, so then again, Rust feels natural here.”
- NewsaHackO points out, “The library support for games in Go is quite poor… doing so adds a lot of busy work.”
- andai adds, “I did a bit of game dev in Odin last year and it was a wonderful experience… Odin has batteries included with many useful libraries.”
3. Tooling, compile times, and ecosystem friction
Several comments focus on practical hurdles—compile speed, searchability, garbage‑collection pauses, and the need for custom libraries.
- tmtvl says, “C can be quite good if you know what you're doing and use a decent compiler.”
- gfody notes, “Rust compile is slower than C, on more than average.”
- Melonai complains, “I always have to add 'golang' because otherwise it just fucks up… googling for 'C' is a lot more dire.”
These three themes—simplicity vs. complexity, language choice for games, and tooling/ecosystem friction—capture the core of the discussion.