• KairuByte@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Open source inherently means you can compile the code locally, for free. You can’t necessarily redistribute it, depending on the license, but I’m not aware of a “you can compile this source for testing and code changes only but if you use it as your actual copy you are infringing” license.

        I am very much open to correction here.

        • ono@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          1 year ago

          Open source inherently means you can compile the code locally,

          Open Source means more than that. It is defined here:

          https://opensource.org/osd/

          If you use the phrase “open source” for things that don’t meet those criteria, then without some clarifying context, you are misleading people.

          for free.

          Free Software is not the same as “software for free”. It, too, has a specific meaning, defined here:

          https://www.gnu.org/philosophy/free-sw.html

          When the person to whom you replied wrote “free software”, they were not using it in some casual sense to mean free-of-charge.

  • 🇰 🌀 🇱 🇦 🇳 🇦 🇰 ℹ️@yiffit.net
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    I’ve wondered: Can you go deeper than assembly and code in straight binary, or does it even really matter because you’d be writing the assembly in binary anyway or what? In probably a less stupid way of putting it: Can you go deeper than assembly in terms of talking to the hardware and possibly just flip the transistors manually?

    Even simpler: How do you one up someone who codes in assembly? Can you?

    • CaptainBuckleroy@lemm.ee
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      1 year ago

      Yes, you can code in machine code. I did it as part of my CS Degree. In our textbook was the manual for the particular ARM processor we coded for, that had every processor-specific command. We did that for a few of the early projects in the course, then moved onto Assembly, then C.