Hacker News Reader

Comment by heresie-dabord | Hacker News Reader

> C++ is a monster.

Perhaps you meant monstrous?

The dev community (and software profession) is crying out for legible, parsable notation and greater safety. All the modern languages are drawing us towards some of these crucial goals. Python above all for its legible/usable notation, Rust for its compile-time and run-time characteristics; Go somewhere in the middle.

As a recovering C++ coder who discovered that there are better languages, I think that within the Tower of Babel that is the coding-language community, C++ has leased an entire floor for its ravings to the congregation.

View on HN

Been programming in C++ for 25+ years and I could say the complexity exploded after C++11 with the introduction of rvalue references. The template syntax could have been simplified, but you get used to it.

People should use more typedef to make C/C++ look sane, but there is some pushback that it hinders readability, but I feel that it is the opposite.

Rvalue references et al are a valuable addition to the language if you're trying to avoid gratuitous copying. The performant alternative is a messy variety of functions that have the same effect as move semantics, except with ad hoc (or no!) compile-time checking. Using them correctly does requires a lot more background knowledge and conscious decision-making from the user than the rest of the language.

Templates are not that bad as a user, but as a template author, they're a completely different programming language that makes it much harder to express even simple ideas. (Concepts may have changed that, but I haven't had a chance to use them.)

”Templates are not that bad as a user”

My take would be they are bad for both users and authors.

In 2024 the expected compiler output for a syntax error in a statically typed language is a specific-as-possible report where in the written source the syntax fails - not 40 lines of illegible template error messages.

There are some cases where templates are the best design option. But they should be used only as the last resort when it’s obvious that’s the best way.

In 2024, I expect people implementing templates making use of concepts, and if not possible, at very least static_assert alongside enable_if.

Naturally reality often times doesn't match expectations.

The solution for move semantics before was specializing the swap function for container types. This was a much more pragmatic approach

I absolutely agree. Move semantics exploded the language.

Gotcha covered: someone wrote a 264-page book about C++ move semantics.

https://www.amazon.com/Move-Semantics-Complete-Guide-First/d...

The problem with typedefs is that you have to find the definition. A compiler-aware IDE can help with this, but I keep cycling through intellisense, clangd, etc. and they only work if you configure things just right -- not good for reading through some unfamiliar code.

Consistent naming conventions help a lot, but then that just introduces assumptions that could be wrong.

As with most points of code style, it comes down to taste.

Reply on news.ycombinator.com