Announcement

Collapse
No announcement yet.

Google Supports Getting Rust Into The Linux Kernel

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • cl333r
    replied
    Originally posted by birdie View Post
    Linus does not and Rust developers agree with his reasoning. Once the voiced issues are resolved, it may be greenlit.
    I was wondering myself. For example Rust's answer to aliased mutability is to crash and thus crash the whole kernel, this is the same as when a cop sees any random human shoots him instantly on the premise that "security is very important - a human can be a terrorist - thus needs to be killed asap".
    This crazy logic is supported by all of the Rust community, I'm glad Linus is hiliting Rust's crazy approaches to programming.

    Leave a comment:


  • ssokolow
    replied
    Originally posted by ThoreauHD View Post
    And like all comedy, it's funny because it's true.
    It was accurate to a part of the community (that we old-timers are very irritated by since we are left running damage control) until the "this is just compiler source code" came along.

    Rust is currently defined by the set of accepted RFCs.
    Last edited by ssokolow; 15 April 2021, 04:10 PM.

    Leave a comment:


  • cynical
    replied
    Originally posted by milkylainen View Post
    On the whole, a lot of Rust code makes my eyes hurt.
    Some of it is not that bad, but damn can Rust look like somebody puked all over the place.

    As per usual, I guess it's a property of whomever is writing, not the language.
    I hope the readability level doesn't degrade.
    I had a big problem with this as well. They have improved the compiler's ability to infer types and lifetimes though. It's not nearly as bad as it used to be. My understanding of Rust has improved also, and this lets some of the syntax (in particular, lifetimes) fade into the background a bit. The biggest thing that helps imo is type aliasing:

    Code:
    type Link<K> = Box<Node<K>>;    // much nicer!
    
    struct Node<K>
    where
    K: PartialEq + Clone + Ord,
    {
    pub key: K,
    next: BTreeMap<K, Link<K>>,
    ends_here: bool,
    }

    Leave a comment:


  • Veto
    replied
    Originally posted by AnAccount View Post
    "on the whole I don't hate it"
    Is Finnish for: "I am deeply in love with it"

    ... OK your explanation was more nuanced

    Leave a comment:


  • SvenK
    replied
    Originally posted by Alexmitter View Post
    Google should invest in https://rust-gcc.github.io/ if they even wanna see rust in the kernel.
    They should invest development power, If they want to see it before next year. There is some progress done but one man alone can't so it as fast as a team.

    Leave a comment:


  • 60Hz
    replied
    Originally posted by sn99 View Post
    I think most people here and even in the linux community have little to no experience with Rust, they should try porting some of their projects into Rust
    You should try taking your own advice.... but you can't because you don't have any projects.

    Next!

    Leave a comment:


  • sn99
    replied
    I think most people here and even in the linux community have little to no experience with Rust, they should try porting some of their projects into Rust and see how it goes and then decide. It is fait o say Rust does have some advantages but it can still be considered a bit "new".

    Leave a comment:


  • 60Hz
    replied
    Originally posted by bug77 View Post
    C won't go away in the next decade or two, but looking at Rust it's pretty clear it has grown from a language loved by enthusiasts to something the big players are starting to take stock of.
    Rust will be discarded before it ever reaches widespread adoption. It leaves a HUGE amount of room for improvement and their "our way or the highway" attitude towards build systems continues to burn bridges.

    Some other, more pragmatic language will come along and eat their lunch and nothing of value will have been lost.

    Leave a comment:


  • 60Hz
    replied
    Originally posted by birdie View Post
    Linus does not
    Rust trannies absolutely and irredeemably btfo. Hopefully they'll 41% themselves now.

    Leave a comment:


  • Zan Lynx
    replied
    Originally posted by milkylainen View Post
    On the whole, a lot of Rust code makes my eyes hurt.
    Some of it is not that bad, but damn can Rust look like somebody puked all over the place.

    As per usual, I guess it's a property of whomever is writing, not the language.
    I hope the readability level doesn't degrade.
    A lot of that is just not being used to reading it. A second part is that Rust programmers are in love with lambdas and so you end up with function calls that include functions, and in those functions are more function calls with their functions... sometimes it is nice to write it that way but I do wish more people would make a named function. This is actually a problem for C++ as well.

    Leave a comment:

Working...
X