• Semperverus@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    5
    ·
    1 day ago

    If you had read Christoph’s reasoning, it wasn’t “just because it’s written in Rust.” He actually gave some decent technical reasoning for it that went beyond his original personal outburst (which I hold him to the same standard as Hector for, but he did shore up later and fixed his communication).

    • Muehe@lemmy.ml
      link
      fedilink
      arrow-up
      16
      arrow-down
      4
      ·
      17 hours ago

      How do you figure?

      The only two “technical” arguments I could see were firstly that code should

      [remain] greppable and maintainable

      which unless I’m missing something boils down to “I don’t speak Rust”, and secondly that

      The only reason Linux managed to survive so long is by not having internal boundaries, and adding another language complely breaks this

      which unless I’m missing something boils down to “I don’t speak Rust”, because ain’t nobody trying to add any other languages to the Linux code base.

      Surely this can’t be the “decent technical reasoning” you are referring to? I have to admit I don’t follow kernel development that closely, but I was under the impression that integrating Rust into the code base was a long discussed initiative having the “official” blessing of the higher ups among the maintainers by now, so it seems odd to see it opposed in such harsh terms by a subsystem maintainer here:

      I absolutely support using Rust in new codebase, but I do not at all in Linux.

      • DacoTaco@lemmy.world
        link
        fedilink
        arrow-up
        9
        ·
        edit-2
        14 hours ago

        You and i read different things. I hated how he worded them, but his arguments at greppable and understandable are valid arguments that go beyond rust and if he can read it or not or refuses to.
        Mixing languages in a part of a project brings complexity and is often a huge ass nono because it makes things unreadable and hard to manage on a large scale.
        He also argues that a c interface exists to connect 2 parts of a system. The person that changes the interface should not have to alter the users of that interface, if they do then you get intertwined dependencies, which is a huge ass red flag for developers that something has gone terrible wrong and the project is not going to scale or will be easy to change.
        So if he changes the interface, the rust team will need to fix it, specially since they are the minority.
        That also doesnt mean he can change it in whatever way without worry, it is an interface change, that needs discussions and approvals ahead of time ofc.