• SharkAttak
    link
    fedilink
    818 days ago

    Seriously though, anyone knows the source of the pic? I’ve been wondering for a while.

  • @affiliate@lemmy.world
    link
    fedilink
    318 days ago

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

    • @TootSweet@lemmy.world
      link
      fedilink
      English
      7118 days ago

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

      • Anna
        link
        fedilink
        315 days ago

        I’m pretty sure Linus dissed on RUST, but then again he disses on everything and everyone.

      • Ephera
        link
        fedilink
        English
        2618 days 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.

        • esa
          link
          fedilink
          318 days 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
          link
          fedilink
          English
          118 days 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
            link
            fedilink
            4
            edit-2
            18 days 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.

  • UnhingedFridge
    link
    fedilink
    English
    218 days 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.

  • Juice
    link
    fedilink
    618 days ago

    Could’ve got me there quicker by telling me the truth