• wewbull@feddit.uk
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    5
    ·
    7 days ago

    The Rust kernel devs are …

    1. …asking the maintainers to lock down APIs which the C devs purposefully leave malleable, in part, to avoid binary blob drivers being feasible.
    2. …asking maintainers to accept code into their subsystem whilst being told, you don’t need to know Rust to an expert level…trust us. Cross language interfaces always have nuance and make good attack vectors. Understandable that maintainers are cautious.
    3. …creating quite a lot of hassle for no a lot of improvement. Systems are only as resilient as their weakest components. The cross language interface is always going to be weak. Introducing a weakness to get improvements probably only succeeds at making the whole weaker.
    • lad@programming.dev
      link
      fedilink
      English
      arrow-up
      3
      ·
      7 days ago

      What’s the reason to avoid binary blob drivers being feasible? Is that about not being able to use non-free binary blobs in kernel? I don’t quite understand what it even is about

    • refalo@programming.dev
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      7 days ago

      IIRC They were also trying to get kernel devs to let official structure definitions live in Rust instead of C, and got upset when they didn’t want to do that.