• affiliate@lemmy.world
    3·
    17 hours ago

    please don’t make me read another bjarne book. the last time i read one it made me want to stop programming

  • Magister@lemmy.world
    671·
    23 hours ago

    Linux is C only, ever read the rant by Linus last century about C++ ? I was there, in usenet

      • m_f@midwest.socialEnglish
        3·
        18 hours ago

        C is definitely still king, but I wonder if crABI will eventually be able to dethrone it:

        https://github.com/rust-lang/rust/issues/111423

        If they can define a useful ABI that manages to include lifetimes, that might just be enough of an improvement to get people to switch over from assuming the C ABI everywhere.

        • esa@discuss.tchncs.de
          2·
          5 hours ago

          Still remains to be seen if a potential rust ABI can avoid becoming a chain to the wall the way the C++ ABI seems to have become. When a lot of C++ers apparently agree with “I’m tired of paying for an ABI stability I’m not using” it’s not so clear it would really be a boon to Rust.

          That said no_std appears to be what people go to for the lean Rust.

          And a lot of us are happy not having to juggle shared dependencies, but instead having somewhat fat but self-contained binaries. It’s part of the draw of Go too; fat binaries come up as a way to avoid managing e.g. Python dependencies across OS-es. With Rust and Go you can build just one binary per architecture/libc and be done with it.

        • Possibly linux@lemmy.zipEnglish
          1·
          18 hours ago

          The problem is that both Rust and Go are huge. The compiled binaries are bigger and the compilers themselves and slower and more resource intensive. The current benefit to C is that is lean and compiles quickly.

          • Zangoose@lemmy.world
            3·
            5 hours ago

            Rust is only huge because it doesn’t have an ABI. If you had an ABI (and didn’t have to compile every single dependency into the binary) the binary sizes would probably drop a lot to the point where they’re only slightly bigger than a C counterpart

            Edit: I don’t know if Go has an ABI but they also include a runtime garbage collector in their binaries so that probably has something to do with it.

    • TootSweet@lemmy.worldEnglish
      712·
      23 hours ago

      Right? It’s in the kernel and everything now. Linus likes it. Linus hates everything. HOW MUCH ARE THEY PAYING HIM?

      • Ephera@lemmy.mlEnglish
        241·
        22 hours ago

        Did he actually say that he likes it? My impression was that it’s not his comfort zone, but he recognizes that for the vast majority of young programmers, C is not their comfort zone. And so, if they don’t hop on this Rust train, the Linux kernel is going to look like a COBOL project in a not too distant future. It does not happen very often that a programming language capable of implementing kernels gains wide-spread adoption.

    • Lucy :3@feddit.org
      92·
      20 hours ago

      I’ll never touch Rust.

      I hate the syntax and cargo too much for that. If that means that I’ll never write mission critical, low level code, so be it.

      • m_f@midwest.socialEnglish
        7·
        20 hours ago

        What don’t you like about Cargo? Is there another package manager you like more?

        • Lucy :3@feddit.org
          41·
          8 hours ago

          Well - of course I prefer a centralized package manager like pacman, which I also use for python packages etc., but I mainly dislike the building process of rust, which is usually done with cargo. No libraries, not even a global cache for already compiled dependencies, no distcc. This makes it infinitely slower than most C/C++ projects. Compiling the kernel is literally faster than compiling a “simple” project like spotify_cli (500+ dependencies, depending on configuration).

          So it’s ass from a user perspective, waiting for stuff to compile (just for it to fail, and start from scratch, as some stuff needs a clean build/src dir), and imo very weird from a dev perspective.

  • UnhingedFridge@lemmy.worldEnglish
    2·
    17 hours ago

    Am I going too hard by making shortcuts to start and stop SSH on my steamdeck desktop for easier file transfer? Feels like a basic security step when connecting to other networks, while not wanting to remember the commands to enable, also wanting to avoid keeping the perms permanently open for the sake of unknown backdoors. Even added windows stating if it was started or stopped in the case of extra sauce or herb.

    Ayy girl, we’re going over and beyond with your network security, because we all do a fucky wucky from time to time.