So let me be very clear: if you as a maintainer feel that you control who or what can use your code, YOU ARE WRONG.

    • @RavuAlHemio@lemmy.world
      62•1 month ago

      Yeah… I kinda wish he had provided it before all those devs quit, though.

      Of course, he might have kept silent as a test to see if the project can remain healthy without his active stewardship, which makes sense for such a large and important project. I’m sure he’s unimpressed by the result.

        • @robinm@programming.dev
          2•1 month ago

          The issue I see is that Greg did spoke in a way that would not undermind Linux leadership. If Linux was out, I’m sure Greg would have said stuff publicly much earlier.

          • Rowan Thorpe
            2•1 month ago

            That makes sense too. I guess it’s a very difficult balance to hit, for all concerned. I think a lot of the famous outbursts that happen on LKML are probably an inevitable side-effect of that balancing-act, and of maintainers being stretched in multiple directions.

  • @deur@feddit.nl
    65•1 month ago

    What the fuck is with the person in the email chain implying not all drivers can be written in Rust? Rust does literally everything C can, nothing stopping you from using unsafe properly to achieve that.

      • @barsoap@lemm.ee
        11•1 month ago

        That’s a performance optimisation which llvm is likely to do for you anyways, jump tables aren’t exactly rocket science. Gazing into my crystal ball, might have to turn your enum variant Foo(u8) with possible values 0…15 into Foo0 through Foo15 (or maybe better Foo(EnumWith16Variants)) so that the compiler doesn’t have to evaluate code to figure out that it doesn’t need to NOP the rest of the jump range out, or bail out of generating a jump table, whatever it would do.

  • Rentlar
    45•1 month ago

    Holy moly that is a man page of a roast. Linus has gotten extremely good at making himself clear while maintaining his temper just enough.

    His argument is applicable to much of FLOSS: your code and contributions you have say over, but you can’t complain about how people used your FLOSS code endpoints downstream. In exchange, any changes you make are the accessors’ responsibility to keep up with.

  • @devfuuu@lemmy.world
    36•1 month ago

    Well, would you look at that, after all forcing things to be discussed and bringing them to the news and social is actually a good thing to get more clear things when there’s problems.

    • trevor (he/they)English
      22•1 month ago

      Exactly. Airing-out Hellwig’s successful attempt to sabotage Rust efforts (and it was successful, given that at least two important maintainers have already resigned) was good, actually.

      Unfortunately, it seems that Linus doesn’t have the maturity to recognize that, and this cycle is likely to continue, barring something good and unforeseen happening.

      • @sugar_in_your_tea@sh.itjust.works
        9•1 month ago

        I think it’s a positive cycle. There’s unfortunately a lot of emotion in kernel maintenance, and this attacks a huge part of it. Subsystem maintainers are maintainers, they don’t own the project, they just make sure the code stays in a good state. In other words, they serve the users.

  • magic_lobster_party
    29•1 month ago

    Not a follower of kernel development, but I agree with Linus. The latest drama is just full of unprofessional toxicity (from both sides).

    Linus had said for years that he wants to see Rust in some form in the kernel. You might not like it, but sometimes you just have to disagree and commit.

    • SGGEnglish
      1•1 month ago

      Some people pay for that you know, make sure to cash in!