managarm VS CppCoreGuidelines

managarm is pretty clean from what I remember.

Somewhat related, Managarm[0] also attempts to be Linux compatible, but has a microkernel, multiserver design.

0. https://github.com/managarm/managarm

Neat idea. There is some research done on fully async OSes like https://github.com/managarm/managarm

If you haven't already, I'd hang out with the Managarm crew. Prety friendly, and what they're doing with C++ and async is very cool!

But well, maybe you should look at Managarm.

You can find more information on the project on our github page here. It is mostly a hobby project, so me and the other developers like to work on it in our free time.

Not hosted on rust-osdev but the Managarm project (an OS that focuses on async and that is primarily written in C++ so far) recently gained a rustc port and ports of some basic utilities written in Rust (ripgrep, exa). Support for Rust drivers is in the works (but still requires adding support for some libraries first that wrap the low-level system call interface).

If you have never seen an async OS, then you must’ve missed Managarm, a fully asynchronous operating system written in c++20. It’s a cool thing to check out, runs on x86_64 (a port to a raspberry pi4 is in progress) and has an extensive userland with various Linux applications running on a custom written libc. In case you’re curious, the repo can be found here: https://github.com/managarm/managarm

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.