C++ is having trouble. Governments and huge corporations are moving quickly to transition to memory-safe languages.
But that’s not always an option, so we have to fight to improve our C++ toolchains and language bases.
In this episode, I want to share my thoughts about improving code (mainly C++, not only).
Some are in development, and some already exist. If you are interested in programming, especially for embedded systems.
Improve code quality and efficiency for better programming results!
I hope you enjoy that episode! And don't forget to share your thoughts in the comments!
Repositories:
[ Ссылка ] - my fixes already delivered
[ Ссылка ] - my fixes delivered, but without modules
[ Ссылка ] - modules on basicModulesSupport branch
[ Ссылка ] - dotfiles, vim configuration in common branch
[ Ссылка ] - idea of filtering h2/cpp2 files
Chapters:
00:00-00:45 Intro
00:45-03:17 Should we abandon C++?
03:17-05:18 Rust is not a solution for me ☹
05:18-12:04 Let’s make C++ great again!
12:04-15:18 Modules, why do you take so long?
15:18-18:07 Why defaults are so hard?
18:07-20:32 Analyze runtime in compile time
20:32-21:53 Wash your hands - sanitizers
21:53-22:45 How to break it? - tests
22:45-23:59 Make space for more code!
23:59-24:33 Guidelines, don’t need to follow, but at least know them!
24:33-25:00 Outro
Used others materials from:
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ].
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ] - :~:text=Abstraction%20without%20overhead%3A%20traits%20in%20Rust%201%20Background%3A,where%20all%20abstraction%20is%20compiled%20away%20statically.%20
[ Ссылка ] - :~:text=We%E2%80%99ve%20nicknamed%20this%20aspect%20of%20Rust%20fearless%20concurrency.,being%20more%20precise%20by%20saying%20concurrent%20and%2For%20parallel.
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
[ Ссылка ]
Cat with steampunk glasses: Designed by Freepik [ Ссылка ]
