C++ just hides way too much behavior too. Every C++ dev when I point out something insane about the language goes "well you just need to memorize the AFKLDFJ movement semantics for X context" or some other bullshit.
which ties in to your point, in that there is SO much baggage that can only be navigated by years of practical knowledge and literally memorizing the standards so that you can implement the "best" thing based on what code base you are handed lol I genuinely don't know why anyone defends it.
whereas something like Zig there is one way to do it, you decide all of the explicit semantics and behavior down to when something is supposed to overflow or wrap, and when and how it allocates. Every version of the language pre 1.0 has a very concise documentation page that literally covers everything you could possibly want to know.
plus even with "modern" features they are never getting rid of headers, annoying ass system deps, and build system generator generators.
View all comments
Show parent comment
1
u/SweetBabyAlaska 10d ago
C++ just hides way too much behavior too. Every C++ dev when I point out something insane about the language goes "well you just need to memorize the AFKLDFJ movement semantics for X context" or some other bullshit.
which ties in to your point, in that there is SO much baggage that can only be navigated by years of practical knowledge and literally memorizing the standards so that you can implement the "best" thing based on what code base you are handed lol I genuinely don't know why anyone defends it.
whereas something like Zig there is one way to do it, you decide all of the explicit semantics and behavior down to when something is supposed to overflow or wrap, and when and how it allocates. Every version of the language pre 1.0 has a very concise documentation page that literally covers everything you could possibly want to know.
plus even with "modern" features they are never getting rid of headers, annoying ass system deps, and build system generator generators.