not-yet-awesome-embedded-rust VS CppCoreGuidelines

And a list of things missing: https://github.com/rust-embedded/not-yet-awesome-embedded-ru...

Building a portfolio is a great idea. Also you can find various areas to contribute to Rust. That would give you great exposure. Check out the not yet awesome rust repo (https://github.com/rust-embedded/not-yet-awesome-embedded-rust) for ideas. Also take a look at the rust foundation grant program, it’s open for applications now. There’s also the “this week in Rust” newsletter (https://this-week-in-rust.org) where job openings relative to Rust are also listed. Lastly, you can check my bio for a link where I provide a list of project ideas for different areas in embedded including Rust.

See Not Yet Awesome Embedded Rust for some ongoing work to build out the ecosystem, it's not ready yet. (this is a play on various "Awesome XYZ Rust" lists that have resources for different topics)

Not Yet Awesome Embedded Rust

Here's an interesting discussion, consolidated here. My view is you should use a restricted scope atomic (as best as can be supported) and interact with that through a handler struct. I.e. no global state.

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.