• exocortex
    link
    fedilink
    arrow-up
    10
    ·
    5 hours ago

    What is the problem with a BSD-license? I’m not familiar with the different open source licensing models and their problems.

    • Allero@lemmy.today
      link
      fedilink
      arrow-up
      28
      arrow-down
      1
      ·
      5 hours ago

      Basically, it allows you to steal all the code and use it in your closed-source programs, giving a green light for corporations to use open-source code without giving anything back.

      GPL doesn’t allow that, forcing you to open-source anything that was produced using other GPL-licensed code. That’s, for example, why so much of Linux software is open-source - it commonly relies on various dependencies that are GPL-licensed, so there is no other legal option other than sharing the code as well.

    • ColdWater@lemmy.ca
      link
      fedilink
      arrow-up
      15
      arrow-down
      1
      ·
      4 hours ago

      Apple, Sony, N*****do, Netflix all use BSD but they don’t contribute any code to the BSD project itself, because of the BSD allow other people/company to close source their code when using with BSD

    • phlegmy@sh.itjust.works
      link
      fedilink
      arrow-up
      5
      ·
      4 hours ago

      It’s not a viral copyleft license, so you’re free to use the source code without giving anything back.

      This has pros and cons over something like GPL, but people like to circlejerk GPL and pretend it’s always the best option 100% of the time.
      For situations where you have to sign an NDA and are unable to release source code (eg; console game dev), MIT and BSD licensed projects are a godsend.

      • communism@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        1 hour ago

        MIT/BSD also makes the most sense for small/minimal projects where GPL is likely overkill. A 100 line script does not need to be GPL’ed. A small static website does not need to be GPL’ed.