Linus Torvalds Speaks on the the divide between Rust and C Linux developers and the future Linux. Will things like fragmentation among the open source community hurt the Linux Kernel? He's learned to say YES more and how to get past dramas. We'll listen to the Creator of Linux.

My Linux Bundle is here:
📚 https://savvynik.com

Share this free tool and support Small YouTubers
https://editbulk.com
(I made this tool to help creators)

Useful Links/Commands:
Discord Link - https://discord.gg/zZD5q92
Summit - https://www.youtube.com/watch?v=tWx769t1JKg

#opensource #linus #linux

SavvyNik

Linus Torvalds discusses the ongoing integration of Rust into the Linux kernel, acknowledging the friction and maintainer pushback it has created over the past five years. He defends the decision as necessary to prevent kernel stagnation and attract new contributors, noting his role has shifted from saying 'no' to encouraging maintainers to embrace new ideas. While Rust has generated controversy including maintainer resignations and debates over code review processes, Torvalds believes the disruption is worthwhile and that Rust is finally transitioning from experimental to a real part of the kernel, though it took longer than expected.

Linus Torvalds — Speaks up on the Rust Divide and saying NO

<p>When Linus said he likes “boring”, that resonated with me. I am a Senior Systems Engineer with 45+ years experience and while I do love technological advancement, and it is necessary to advance in order to improve, I have always believed in a modicum amount of caution when introducing new way of doing things into a technological arena that should an “issue” arise would affect a huge amount of people and potentially shake the trust and confidence of users as a whole. I in my extensive career have coded in numerous languages, sometime by desire to try it out and sometimes by necessity of a particular project, some of these have been assembler, C, C++, and yes to a lessor extent Rust. For code, especially in certain critical areas, and an operating systems kernel I believe as critical, you should consider certain things when choosing a language. First would be how long the language has been used in that particular facet of technology, and second consideration is how many good quality developers are available in a language.
For the Linux kernel, in my opinion, which is a rewrite, clone if you will, of UNIX that is used by tens of thousands of systems world wide, a solid well understood development language is key, as such UNIX itself was coded in C, and as an interesting side note C was created originally to help develop UNIX when assembler became to ownerious. And Linux for the most past is also written in C, and while I’m sure there have been many challenges in the Linux development cycle they are many developers, coders and maintainers that know C very well and C being extremely versatile, these challenges have been over come and a very good and solid code base has been created and has served the Linux kernel well. Rust on the other hand is significantly newer, but non the less very capable coding language that has been used with great eagerness and has enjoyed great success. And while I do not know exactly how many quality developers know Rust to the level required to work on code require in the Linux kernel, I would hazard to guess that there would be less than the number that know C. While that is immaterial as long as you have sufficient persons on hand for the required work it can be a consideration knowing the pool of available developers is smaller. Like wise there is also something to be said that a code base be kept in as few a languages as possible for consistency of design.
While it has been something around 3 years that Rust has been used in some Linux kernel areas, and to date I don’t believe there has been any major and prolonged kernel degradation caused by the use of Rust, I think the use of the language should be advanced with tenuous caution and with keen oversight until a time where absolute trust and required experience has developed and been proven. But then if it good enough for Linus then it’s good enough for me.</p>


<p>I trust linus… ok not really in this case I still say No to rust for most of the time.</p>
