• chuck@lemmy.ca
    link
    fedilink
    arrow-up
    1
    ·
    3 months ago

    I mean you’re not wrong but I’d argue you can get more interesting cve’s using a higher more performant language such as c++. Where there are are ways to include CVE 's from C and introduce new ones to each level of your program using inheritance.

  • 0x0@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    Ah yes, the rust zealots shitting on one of the most important languages of all time… again.

    Kinda weird how the number one way to promote Rust has been to downplay C and others.

  • Richard@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    3 months ago

    C is the hardware language N°1 of the high-level languages. If you actually want to know and control what happens in the machine, you write in C. Rust, C++ and all the other abstractions are for people who do not understand how computers and computer memory work.

    Edit: grammar

    • frezik@midwest.social
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      CPUs are for people who don’t know how to melt their own sand into transistors.

      Sand is for people who don’t know how to create their own silicon from hydrogen and a neutron emitter.

    • witx@lemmy.sdf.org
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      I wrote loads of firmware in c++ and some on highly constrained boards. You’re just stuck in the past and spewing bs

    • FizzyOrange@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      3 months ago

      This is a misconception that’s common among beginner C programmers. They think C is high level assembly and don’t understand the kinds of optimisations modern compilers make. And they think they’re hardcore and don’t make mistakes.

      Hope you figure it out eventually.

    • Ethan@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      I’ve written programs in C. I’ve written programs in assembly, for x86 and for microcontrollers. I’ve designed digital logic and programmed it into an FPGA. I’ve built digital logic circuits with transistors.

      I’ll still take Go over C any day of the week. If I’m doing embedded, I’ll use TinyGo.

        • Ethan@programming.dev
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 months ago

          Why? I see no reason to go through the hassle of learning yet another language when Go serves my purposes perfectly and I’m happy with it.

          • crispy_kilt@feddit.de
            link
            fedilink
            arrow-up
            0
            ·
            3 months ago

            Same reason as learning anything. It makes you better at what you do and broadens your horizons.

                • Ethan@programming.dev
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  3 months ago

                  Programming languages are tools. I couldn’t care less about learning a new tool just for the sake of learning. My interest in learning tools is exclusively practical - if they help me do my work better.

                  I find functional languages interesting, but that’s because I find the underlying theory interesting and worth learning for its own sake, not because I actually care about the specific language it’s written in. Even then these days I’d rather learn about woodworking (which is currently my main hobby) than a programming paradigm I’m probably never going to use.