python-functions VS CppCoreGuidelines

You can see look at my custom python settings here. You can also look into the recommended extensions there.

You can see my customizations for Python in PowerShell in Dark+ theme here, but it's just my personal preference, probably not everyone would like that ;).

szymonos/python-functions (github.com)

But if you're writing PS script in Windows it will most likely work on Linux if there is PS installed. This is my PS script to provision and manage Python virtual environments: python-functions/pysetup.ps1 at main · szymonos/python-functions (github.com) or my psprofile: powershell-functions/profile.ps1 at main · szymonos/powershell-functions (github.com)

Here are my tweaks to Dark+ theme: settings.json

If you're on Linux/Windows with WSL2 you can try it by yourself ( szymonos/python-functions (github.com) ) - there is a complete environment with Azure Functions in Python configured. You can debug it out of the box, there are configured linting with pylint, flake8, mypy, formatting with black, unit test with pytest, installed VSCode extensions for python development and so on.

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.