Linux people doing Linux things, it seems.

  • refalo@programming.dev
    link
    fedilink
    arrow-up
    13
    ·
    edit-2
    2 months ago

    People prefer what’s familiar to them. Rust is completely foreign to them, the syntax is very different, the community is different (and often much younger), it still has many issues and is not ubiquitous, and many people are just slow/averse to change in general. So I absolutely understand the hesitation. And some just don’t like it for other reasons like the syntax, learning curve or other reasons. There’s also still a host of memory-related things Rust doesn’t fix like stack overflows, leaks, bitflips, unsafe context code, and just bad coding practices in general.

    • Octorine@midwest.social
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      5
      ·
      2 months ago

      I blame C++. When these kernel hackers hear about how they should switch to this shiny new language that’s going to make their code so much cleanser and more manageable, I don’t blame them for thinking it’s all bullshit. It was last time.

      • refalo@programming.dev
        link
        fedilink
        arrow-up
        6
        arrow-down
        1
        ·
        edit-2
        2 months ago

        To be fair, there’s nothing wrong with only using the parts of C++ you want. If you avoid things like templates, exceptions, RTTI etc. then e.g. your compile times will not suffer like people always complain about, your error messages will not be cryptic, plus you’ll have stronger typing, easier/safer lifetime management with ctor/dtors and easier to read code from class usage.

        Personally I think Swift has great potential if it can get past the speed and cross-platform issues, as it was designed by (among others) some C++ committee folks, and so it feels a lot more familiar than say, Rust, plus it fixes a lot of long-standing issues.

        There is also an Indian kernel fork that allows C++ drivers.