[ncmncm]

If coding C++ feels like fighting "bureaucratic overhead", I promise you are Doing It Wrong. The type system should be performing the overhead, on your behalf, at compile time, leaving your attention for the actual problem.

C++ coded like C or like Java will be exactly as miserable as coding C or Java, but that is entirely a matter of choice.

[__d]

The work to have the type system do stuff for you doesn't happen for free. You need to define a whole bunch of scaffolding to support the application functionality. Sure, once it's set up, using it can be pretty painless, but the design, implementation and testing of the supporting code is a non-trivial effort.

In contrast, Python (and other dynamically-typed languages) avoid all of that.

In addition, the compile-time cost of all this is significant. Cup-of-coffee builds are a definite burden on productivity.

[AnimalMuppet]

What do you see as the difference between C++ and Java that lets C++ be less miserable?

[ncmncm]

The type system in C++ as in Haskell, and to lesser degree Rust, is not just for checking arguments. It can do useful work, and routinely does in better libraries.