• Cethin@lemmy.zip
      link
      fedilink
      English
      arrow-up
      16
      ·
      3 months ago

      It’s probably not because it’s sucks. It’s because they’re trying to perfectly replicate an existing target. They have to read the assembly, digest it, then create the identical solution in C++. If they were just creating a new game, it likely would be much faster.

    • BigDanishGuy@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      3
      ·
      edit-2
      3 months ago

      #include // because writing to the console is not included by default.
      int main()
      {
      std::cout << "C++ is simple and fun ... you cretin\n";
      return 0;
      }

      I had a machine language course in uni, parallel with a C++ course. Not a fun semester to be my wife, or a relative of any of my classmates. Best case our brains were in C++ mode, worst case you needed an assembler to understand us.

      And yes I know my code format will piss people off, I don’t care, it’s the way I write when other less informed people don’t force me to conform to their BS “Teh oPeNiNg bracket shouwd bwee on teh sam line ass teh declawation

      Edit: added a \n for the sake of pedantry :)

          • raspberriesareyummy@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            3 months ago

            Interesting… today I learned. But since I only ever use std::cout in my debugging code (i.e. DURING debugging) or for status outputs of the application (for small apps), and for everything else I use my own logging framework that uses printf & syslog udp messages… luckily nothing I need to refactor :D