• newIdentity@sh.itjust.works
      link
      fedilink
      arrow-up
      14
      ·
      10 months ago

      A decompiler won’t give you the source code. Just some code that might not even necessarily work when compiled back.

      • amki@feddit.de
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        10 months ago

        From the point of view of the decompiler machine code is indeed the source code though

      • over_clox@lemmy.world
        link
        fedilink
        arrow-up
        4
        arrow-down
        6
        ·
        10 months ago

        And? Decompilers aren’t for noobs. So what if it gives you variable and function names like A000, A001, etc?

        It can still lead a seasoned programmer where to go in the raw machine code to mod some things.

      • over_clox@lemmy.world
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        10 months ago

        No, it’s actually better when you can read the machine code.

        Most folks don’t care to recompile the whole thing when all they wanna do is bypass the activation and tracker shit.

        • SpaceNoodle@lemmy.world
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          10 months ago

          Having access to the source code actually makes reading machine code easier, so you’re also wrong on this entirely different thing you’re going on about.

          • over_clox@lemmy.world
            link
            fedilink
            arrow-up
            1
            arrow-down
            2
            ·
            10 months ago

            I never said disassembly or decompiling was easier in any way. I’ll agree with you on that, it’s way more difficult.

            Back to the point of the meme though, if you can read assembly, you can read it all.

              • over_clox@lemmy.world
                link
                fedilink
                arrow-up
                1
                arrow-down
                1
                ·
                10 months ago

                I’ve written drivers in 65 bytes of code. I don’t tend to use high level languages that hide what’s going on behind the scenes.

          • over_clox@lemmy.world
            link
            fedilink
            arrow-up
            1
            arrow-down
            2
            ·
            10 months ago

            You’ve clearly never used a disassembler such as HIEW have you? You get the entire breakdown of the assembly code.

              • over_clox@lemmy.world
                link
                fedilink
                arrow-up
                1
                arrow-down
                1
                ·
                10 months ago

                I didn’t say it was. I just said loosely what the OG meme said, if you know how to read assembly, you know how to read (and write) what some of the code does.