Davidbrcz

The same usual issue with making a tech you do not own a critical element of your workflow

I have not heard about HLA for a looong time !

This is the 2020s re-enactement of the early 2000 WYSIWYG editors.

The best way to learn a new language is to follow a proper structured resource which would cover syntax, semantic, tooling & ecosystem and best practices.

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.

Python, Java, Lua, Ruby are ~30 years old, Ada being as old as C++.

Sure, none is perfect and they have cruft and warts, but they are not such a mess as C++ is.

No it's not.

The language keeps growing, with

- new features overlapping old features from previous standards without replacing them or deprecating them (function::copyable_function vs std::function, std::less<> key for transparent lookup in maps)

- new features not usable by the layman (coroutines ...)

- Cryptic syntax (reflection...)

- Stuff you are told not to use because of performance reason and that cant be fixed because of ABI (regex)

- Compile errors that are 1km long (no, concepts are not helping here, the 'nicer' message is still buried into a hot pile of template instantiation callstack).

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, ...

I was an intern at CERN in mid 2010s and worked on this !