this post was submitted on 12 Sep 2024
843 points (95.5% liked)

linuxmemes

23099 readers
1066 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    843
    Linux rule (lemmy.world)
    submitted 5 months ago by ShaggySnacks@lemmy.myserv.one to c/linuxmemes@lemmy.world
    57 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] MajorHavoc@programming.dev 8 points 5 months ago (1 children)

    Lol. If Rust fans want a Rust kernel, no one is stopping them from building one.

    [–] TimeSquirrel@kbin.melroy.org 11 points 5 months ago (2 children)

    It's hard to overcome the Hurd problem though. Although it would be fascinating to see how it would diverge on the design of the Linux kernel. How much can you still act like Linux while not being Linux? Or would it just be a direct algorithmic translation, basically doing the same processes under the hood with the same architecture? I'm sure there's more than a few things Linux is doing in C that the Rust compiler would frown upon.

    [–] WalnutLum@lemmy.ml 9 points 5 months ago

    Main issue is drivers. One of the best places to take advantage of rust's memory safety is in hardware drivers, and those would be hard to share between separate kernels.

    That entire talk, and the complaint that Ts'o responded to was that to continue with rust, there needs to be some responsibility from the guys working on the underlying C bindings to not break downstream dependencies if they refactor code.

    The answer from some of the Kernel developers, and vocally by Ts'o was: lol no fuck you and your toy language.

    [–] MajorHavoc@programming.dev 7 points 5 months ago* (last edited 5 months ago)

    Yeah. The idea of an automated C to Rust replacement of the Linux kernel is fascinating. As you say, there's probably stuff in the Kernel that Rust's compiler won't allow.

    I imagine it wouldn't work at all, out of the box, but it might reduce the cost curve enough to make a dedicated team of very clever engineers able to cross the last mile, given time.

    As cynical as I am of both Rust and AI generated code, it honestly feels like trying an automated conversion might be less of a long shot than expecting the existing Linux kernel developers to switch to Rust.

    And I'm sure a few would kick in some thought cycles if a promising Kernel clone could be generated. These are certainly interesting times.