• jj4211@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      13 hours ago

      Well, depends.

      Software is subject to copyright. Yes you can implement the same APIs, but when you get into the visual presentation, things can get copyright related even if the code isn’t being ripped off.

      If you decompile rather than clone, well then the code is copyrighted even if transformed into plausible source code.

      Of course then there are patents…

      • LH0ezVT@sh.itjust.works
        link
        fedilink
        arrow-up
        2
        ·
        10 hours ago

        The way I unterstand it, at least in European practice, the code itself is copyrighted, as in, the actual text, not the concept behing it. Decompiled source is not the same as original source, it goes through rounds of compiler optimisations and the process of reversing that includes a lot of guesswork. So, in practice, decompiling and working on the decompiled source was at least tolerated, probably because it would have been a grey area at worst.

        • jj4211@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          3 hours ago

          In terms of whether the ‘clean room’ approach is as critical in Europe or not, I can’t be sure. It might be more permissable for someone to use a decompile as a reference and also directly work on a replacement. However I’m pretty sure starting with a decompile of proprietary software as a direct codebase would run afoul of issues.

          Otherwise, imagine you have an HEVC encoded rip of a 4K blu ray. You transcode it to AV1. The bytes are totally different, and even the resultant frames are likely not even pixel for pixel identical. I don’t think copyright law would deem that not a violation, regardless of jurisdiction.