Conversation
jarkko

Jarkko Sakkinen

Edited 2 months ago
Two years of being in the mainline is a short durationin kernel. Some feature patch sets take longer. For most part I'm wondering why people go crazy of not much happening on Rust side.

More patch sets like this are best possible effort for Rust enablement (and BTW, it is in C ;-) ):

https://lore.kernel.org/lkml/20240815173903.4172139-21-samitolvanen@google.com/

Once GCC-Rust catches up I'd expect more to happen as that will unlock for instance embedded toolchains and give at least theoretical chance to have something with Rust in a defconfig.

I'd contribute and/or wait another 3-5 years before making any fast conclusions. Linux is no worse in this than any other operating system, which decades of legacy to worry about. There is no unfortunately fast path here anywhere.
2
1
2
jarkko

Jarkko Sakkinen

Reply to @jarkko
In any project, not just open source, more robust you can get the builds, more useful developments will foster from that. It is factors more important than any specific feature.
1
0
0
vbabka

Reply to @jarkko
Edited 2 months ago
@jarkko
1
4
16
jarkko

Jarkko Sakkinen

Reply to @vbabka
@vbabka LOL, I was going to sleep and remembered this. I thought that if I wake up early you won't have a window put that comment 🤣 I knew this was coming on me...
1
0
2
vbabka

Reply to @jarkko
@jarkko the lore police never sleeps...
0
0
3
jarkko

Jarkko Sakkinen

Reply to @jarkko
Also for anything totally new in core architecture of any large platform: tooling tends to always lag at minimum couple of years behind ;-) Narrative of this story is always excitement, disappointment and finally growing up. Thus, I have zero doubts that Rust would not grow up as essential part of Linux core architecture over time.

It would be ultimate stupidity to make any other prediction. Even if I hated Rust I would make the same analysis because I'm a pragmatic realist.
0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: