blog_os VS CppCoreGuidelines

but it seems to be flawed because even the example: https://github.com/phil-opp/blog_os/tree/post-02

I suggest looking at the 3rd edition of Philipp Oppermann's blog OS that I mentioned. It's still very much a work-in-progress, but the section on UEFI booting is pretty much done. It's not hosted anywhere yet, so you'll have to clone the repo and switch to the edition-3 branch, then install Zola 0.13 (cargo install zola --git https://github.com/getzola/zola.git --tag v0.13.0) and run zola serve in the blog directory.

RedoxOS, an OS written in Rust A tutorial on making an OS in Rust, complwte with bootable source

I'm currently working on a tutorial for (1). It's still in a very early stage, but maybe it helps you to get started: https://github.com/phil-opp/blog_os/blob/edition-3/blog/content/edition-3/posts/02-booting/uefi.md

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.