book VS CppCoreGuidelines

Are you saying that this book is a hallucination? And this? And all of this?

4) C++: it’s often overly complicated for many projects. Use with caution, although it’s definitely useful in very large projects. But there’s a reason Rust is increasingly popular for embedded — here’s an engineer’s view.

If you come from the embedded C community then maybe something like Phil Oppermann's writing an OS in Rust series. There's also the embedded Rust book and the embedded Rust working group github that has a lot of resources.

I genuinely don't know why you would say that and I know you were talking about microcontrollers

The rust embedded book: https://docs.rust-embedded.org/book/

It’s not a job, but I’m guessing you would like this book: https://docs.rust-embedded.org/book/

There's a page on the Rust website on embedded systems. Given that you are already familiar with embedded programming, you can probably start with the embedded rust book.

If you aren't aware of the c++ core guidelines[1] - it should be on your radar.

Also, it might not be a popular opinion, but I think Bjarne's books are just fine.

A Tour of C++ (3rd edition) [2]

Principles and Practice Using C++ (3rd Edition) was just published in april 2023 [3]

[1] https://github.com/isocpp/CppCoreGuidelines/blob/master/CppC...

You need to talk to Bjarne and Herb...

"C++ Core Guidelines" - https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

In addition to the other comments -

TypeScript deliberately takes a "good enough" approach to improving JavaScript, instead of designing an ideal but incompatible approach. For example, its handling of [function parameter bivariance](https://www.typescriptlang.org/docs/handbook/type-compatibil...) is unsound but works much better with the existing JavaScript ecosystem. By contrast, a more academic functional programming language would guarantee a sound type system but would be a huge shift from JavaScript.

By analogy, Herb Sutter is arguing that something like the [C++ Core Guidelines](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines), with tooling help in this new Cpp2 syntax, can bring real improvements to safety. Something like Rust's borrow checker would bring much stricter guarantees, backed by academic research and careful design, but would be incompatible and a huge adjustment.

https://www.youtube.com/watch?v=2olsGf6JIkU

Take a look at Effective Modern c++ by Scott Meyers and the ISO c++ core guidelines. These resources are great for learning how to write better, more modern C++. I don't think it would be hard to grasp if you're already familiar with the language, just make sure to actually write some code which makes use of this stuff, otherwise it's easy to forget.

Look to the C++ Core Guidelines. It's not perfect, it has some flaws, including some sabotaging advice apparently adopted for political reasons. But at least it has some C++ authorities (Bjarne and Herb) as authors.