On the one side I really like c and c++ because they’re fun and have great performance; they don’t feel like your fighting the language and let me feel sort of creative in the way I do things(compared with something like Rust or Swift).

On the other hand, when weighing one’s feelings against the common good, I guess it’s not really a contest. Plus I suspect a lot of my annoyance with languages like rust stems from not being as familiar with the paradigm. What do you all think?

  • mox@lemmy.sdf.org
    link
    fedilink
    arrow-up
    44
    ·
    7 months ago

    I’m just glad to see the White House listening to people who understand technology for a change.

    • jkrtn@lemmy.ml
      link
      fedilink
      arrow-up
      21
      ·
      7 months ago

      We need legislators who aren’t all literally older than cryptography. If they weren’t bought and paid for by billionaires that would be nice too.

        • jkrtn@lemmy.ml
          link
          fedilink
          arrow-up
          7
          ·
          7 months ago

          It requires score voting so that, even if heavily gerrymandered, one can still meaningfully express a preference without throwing one’s ballot in the garbage.

          • Hacksaw@lemmy.ca
            link
            fedilink
            arrow-up
            5
            arrow-down
            1
            ·
            7 months ago

            It’s never throwing your ballot in the garbage though. I used to think the same way, but every vote on the left, even if for the lesser evil, even if they lose, moves the conversation to the left. When we all stay home you get maga nutjobs stealing the show running unchecked.

            Last thing is that gerrymandered states are the EASIEST to upset by increasing voter turnout. To gerrymander effectively you have to put your opponent in dense areas they’ll win by a large margin, then spread your side so that you barely win the rest of the districts. That means that a 5% increase in votes on the left can take you from a loss to a nearly complete victory in a gerrymandered state.

            Vote splitting on the other hand is a trickier beast, but in the end if all the left votes go to a moderate then that gives the left a lot of leverage because if the moderate candidate doesn’t bend to the left then they’ll lose the next election.

            Always vote.

            • jkrtn@lemmy.ml
              link
              fedilink
              arrow-up
              0
              ·
              7 months ago

              You are correct. I hope nobody thought I am against voting. Everyone needs to vote.

              • fruitycoder@sh.itjust.works
                link
                fedilink
                arrow-up
                1
                ·
                7 months ago

                Mostly just saying it outload, I know I fall into the trap myself and just need reminding “perfect is the enemy of good” sometimes.

    • fruitycoder@sh.itjust.works
      link
      fedilink
      arrow-up
      6
      ·
      7 months ago

      This admin honestly has been consistently doing so IMHO. Having read a memo that felt like a crock of shit yet, except for maybe the unfunded nature of some of the demands.

    • Oliver Lowe@lemmy.sdf.org
      link
      fedilink
      arrow-up
      2
      ·
      7 months ago

      I feel this is a bit of a moot point from the White House. Memory-safe languages have been around for decades. I feel like the amount of C/C++ out there isn’t so much that people think having dangerous stuff around is good, but more that nobody really wants to pay to change it.

      • You don’t have to ban C or C++; you just have to prove your programs are memory safe. It’s been decades since I’ve coded in C, but surely Valgrind and ilk are now capable of providing reasonable proof of memory safety. You might have to turn up all the dials and set all-warnings-are-errors, but I’d be surprised if C tooling wasn’t available to provide sufficient proof for a given statically-linked program.

        • BaardFigur@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          7 months ago

          but surely Valgrind and ilk are now capable of providing reasonable proof of memory safety

          Reasonable, sure. But it’s still far from being perfectly “memory safe”

          • Nothing, and certainly not Rust, is “perfectly” memory safe. You get closer with Haskell. At some point, you define what “good enough” is, and it’s up to languages to provide tooling to either meet those standards (and be approved), or don’t.

            Granted, it’d be far harder for, say, Ruby to meet those proofs than a language like Rust, but the critical point is to have a defined standard of “good enough” for languages to work towards.

            • BaardFigur@lemmy.world
              link
              fedilink
              arrow-up
              2
              ·
              7 months ago

              Nothing, and certainly not Rust, is “perfectly” memory safe.

              I agree, which is one of the reasons I think it’s a stupid rule to put in place, to begin with. A lot of so called memory safe languages are just built on top of C anyways (which is not considered memory safe).

              Granted, it’d be far harder for, say, Ruby to meet those proofs than a language like Rust, but the critical point is to have a defined standard of “good enough” for languages to work towards.

              True, but that’s what the industry is already aiming for anyways. But vulnerabilities won’t stop happening any time soon