>There's too much to memorize, and the standards are too varied. When I go to a project site for maintenance and it's a C++ project, I instantly lose energy — because it's just too difficult.

If you'd already been using it for 10+ years you wouldn't feel that way, because you'd already have memorized a lot of it.

▲

Davidbrcz 6 hours ago | parent [-]

Except the language keeps growing, with

- new features overlapping old features previous standards without replacing them or deprecating them. - new features not usable by the layman - ...

See function::copyable_function vs std::function, modules, coroutines, Reflection syntax is cryptic at best, ...

▲

VoidWarranty 6 hours ago | parent [-]

You don't have to use them. There's a handful of nice to haves in modern releases but its totally fine and sane to just ignore whatever the committee is distracted by at the moment.

Hell, if you wait long enough, they'll just deprecate it before you can care to bother.

	▲	Davidbrcz 4 hours ago \| parent [-]
		And that's the usual fallacy (just ignore the bad stuff). But if you work with C++ in professional context, you will encounter it somewhere (library, teamate's PR, legacy code, LLM output, book / blog / conference ...). \| You actually need to know the bad stuff to be able to judge it and discard it.