Rust

=== youtube ===
https://www.youtube.com/watch?v=TJTDTyNdJdY
https://www.youtube.com/watch?v=CHRNj5oubwc implementation.
=== Kernel ===
https://www.youtube.com/watch?v=FwXmv6b9614 This is this fear that rust is going to destroy the future of the Linux 
kernel but many are heavily in favour of it's introduction, I'm not a kernel developer so let's hear 2 polar opposite opinions and make a decision for ourselves. Series of links to pro con arguments etc. https://lwn.net/Articles/862193/ 
Rust is Haskell(for which you need Category theory). Rust pretends that it's C-family language, but deep under it all it's a bunch of ideas from the functional languages brought to C-style world. What I find surpising about Rust is the fact that while it's language construct look totally alien to C/C++/Java developers at first… after some digging around you find, to your astonishment, that they map exactly not on the language constructs of of C/C++/Java but on design patterns used by C/C++/Java developers. E.g. dynamic trait objects is precisely how kernel does oop. While ownership and borrows is what so-called “modern C++” (with std::unique_ptr and rvalue references) tries to push. P.S. It doesn't yet have monads and other higher kind things from Haskell. But they are working on it.
https://drewdevault.com/2022/10/03/Does-Rust-belong-in-Linux.html 
=== compile times ===
200,000 lines takes over a minute to compile, vlang a few seconds.
=== generics ===
I’m new to rust, and rusty on C++, so while I barely understand what’s being discussed here, it sounds an awful lot like what Mike Acton talked about in his CppCon 2014 talk: both templating in Cpp and generics in Rust represent a pre-compilation mixture of concerns that are best solved by text-preprocessing entirely separate from the compilation itself. Many things handled by generics within language could be handled just as well if not better by implementing for a concrete type and making a python/JavaScript/Perl template string out said code with fields for the type you wish to make more generic, then have that script generate specific code only for the concrete types actually used in your codebase. The only thing such dynamically generated code would lack is checking against traits/interfaces during code generation, or integration of such checks into your IDE of choice but I imagine that would not be a massive lift to fix. Javascript’s babel may already provide a model for such dynamic code generation. From: 
https://hirrolot.github.io/posts/rust-is-hard-or-the-misery-of-mainstream-programming.html You can only read this stuff using graph morphisms from category theory. Fearless concurrency” – a formally correct but nonetheless misleading statement. Yes, you no longer have fear of data races, but you have much pain. See 
https://smallcultfollowing.com/babysteps/blog/2019/10/26/async-fn-in-traits-are-hard/ 
https://news.ycombinator.com/item?id=31601040 replies to article 
=== links ===
https://medium.com/@slimm609/checksec-d4131dff0fca
https://kerkour.com/rust-functional-programming 
c coding 
vlang 
Software 
Category:Rust