@1:05:17 The plan is that Rust will be a fully fledged Linux kernel language. There are no licensing problems - you can license Rust code under any license you like. Initially Rust code will be targetted at device drivers only, but it won't be limited to "out-of-tree" stuff, and will have the same status as any Linux device driver written in C. As an aside, Linux is GPLv2-only (not GPLv3). Also some more permissive licenses (including "The MIT License" AKA "The X11 License") are "GPL compatible" - that is because they are less restrictive than the GPL licenses, code licensed under the MIT license can be included in GPL projects (including linking against GPL code - as is the case in the Linux kernel). See for instance the Wikipedia GPL page "Compatibility and multi-licensing", and also the Linux kernel docs "Linux kernel licensing rules".
@@samuelemmettbray "I'm interested in the project, but I think it's driven by people who are very excited about Rust, and I want to see how it actually then ends up working in practice." (Oct 2021). You can also see him reviewing proposed patches to add Rust support in the last few weeks (his comments request minor tweaks to ensure provenance/licensing is obvious to people looking at code history in the future). It's still possible that future work will uncover problems which lead to Rust's part in the kernel being limited to certain areas, or even backed-out entirely, after all this is the first time a second compiled language has been added to the code base (except for build tools). Rust was originally designed to co-exist in large C++ code bases within the Mozilla code base, so interoperability wasn't an afterthought in the language design.
I have trouble watching a presentation by a guy who is not smart or less self-centered enough to lower the resolution of his screen so that his presentation can be readable on TH-cam. What I do, I just move on! Not worth it.
@@sayakchatterjee4454! I was not watching it from a phone. I started watching it from a laptop. He is not alone to do that. It looks like many of these guys are more concerned about showcasing their large monitors than making their videos readable. Often these TH-camrs shoot these videos just to showcase their "skills" and working environment to potential employers. This issue almost never happen to those who are trained in creating tutorials. That's why I prefer getting my tutorials from places like PluralSight, Coursera, Udacity, EggHead, etc, where these kinds of details (display resolution) are taking care of.
@@sayakchatterjee4454! Beside that, I tend not to watch tutorials where the authors put their face in the video. Not-only it distract viewers from focusing on the content, it is egotistic/narcissistic.
@@notoriouslycuriouswombat interesting. I will need to do some benchmark tests. I thought the whole “zero cost abstractions” would fix that at compile time…
The price we pay for memory safety, it's damn ugly syntax. I prefer C++ over, Rust, because, looks more like JS and I never jump on that bandwagon thing, wow memory safety, so much...
In my opinion, languages like JS Java or C++ are ugly. It simply depends on what you are used to. In my case: I learned languages like C and Python, but I still think Rust is a much better language.
Functional Programming starts at 52:20
thanks!
Jesus! Miss named is right.
Thanks a lot
@1:05:17 The plan is that Rust will be a fully fledged Linux kernel language. There are no licensing problems - you can license Rust code under any license you like. Initially Rust code will be targetted at device drivers only, but it won't be limited to "out-of-tree" stuff, and will have the same status as any Linux device driver written in C. As an aside, Linux is GPLv2-only (not GPLv3). Also some more permissive licenses (including "The MIT License" AKA "The X11 License") are "GPL compatible" - that is because they are less restrictive than the GPL licenses, code licensed under the MIT license can be included in GPL projects (including linking against GPL code - as is the case in the Linux kernel). See for instance the Wikipedia GPL page "Compatibility and multi-licensing", and also the Linux kernel docs "Linux kernel licensing rules".
@@samuelemmettbray "I'm interested in the project, but I think it's driven by people who are very excited about Rust, and I want to see how it actually then ends up working in practice." (Oct 2021). You can also see him reviewing proposed patches to add Rust support in the last few weeks (his comments request minor tweaks to ensure provenance/licensing is obvious to people looking at code history in the future). It's still possible that future work will uncover problems which lead to Rust's part in the kernel being limited to certain areas, or even backed-out entirely, after all this is the first time a second compiled language has been added to the code base (except for build tools). Rust was originally designed to co-exist in large C++ code bases within the Mozilla code base, so interoperability wasn't an afterthought in the language design.
Thanks for the talk. 10 minutes allocated to Functional Programming.
Awesome talk! Thank you very much!
Thank you 🙏 🙌
You kind write macros that enable you to write pipeline style code.
"Rust is like a Talking Head's song, for sure"
once in a lifetime....
Houston
I have trouble watching a presentation by a guy who is not smart or less self-centered enough to lower the resolution of his screen so that his presentation can be readable on TH-cam. What I do, I just move on! Not worth it.
It’s very readable? Are you watching on a phone? This was live streamed so I doubt he considered that case
@@sayakchatterjee4454! I was not watching it from a phone. I started watching it from a laptop.
He is not alone to do that. It looks like many of these guys are more concerned about showcasing their large monitors than making their videos readable. Often these TH-camrs shoot these videos just to showcase their "skills" and working environment to potential employers.
This issue almost never happen to those who are trained in creating tutorials. That's why I prefer getting my tutorials from places like PluralSight, Coursera, Udacity, EggHead, etc, where these kinds of details (display resolution) are taking care of.
@@sayakchatterjee4454! Beside that, I tend not to watch tutorials where the authors put their face in the video. Not-only it distract viewers from focusing on the content, it is egotistic/narcissistic.
fp in rust is way slower than doing it imperatively...so i feel like the cost has to be extremely worth it
Slower? To write?
@@lyingcat9022 runtime
@@notoriouslycuriouswombat interesting. I will need to do some benchmark tests. I thought the whole “zero cost abstractions” would fix that at compile time…
The price we pay for memory safety, it's damn ugly syntax. I prefer C++ over, Rust, because, looks more like JS and I never jump on that bandwagon thing, wow memory safety, so much...
In my opinion, languages like JS Java or C++ are ugly. It simply depends on what you are used to.
In my case: I learned languages like C and Python, but I still think Rust is a much better language.
C++ looks like JS? ...
@@FADHsquared every language looks like js
@@MrEnsiferum77 Yes, C++ has let and const, JS has namespaces > etc, JS convention is snake case like C++, sorry I missed it
@@FADHsquared I mean c++ Is more functional in nature, even rust...