• Anna@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      2 months ago

      Because FreeBSD uses MIT license whereas GNU/Linux uses GPLv2. The difference between them is that with GPLv2 you have to share source code if you modify anything but in MIT license you can change anything you want and charge ppl and not share source code. That’s why a lot of corps like to use FreeBSD. I know that Netflix contributes to FreeBSD but I’m also sure they hide a lot of things.

      • loathesome dongeater@lemmygrad.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 months ago

        White what you say is true, I feel like this has more to do with their engineers being better at or more comfortable with FreeBSD or something like that.

        • lemmyreader@lemmy.mlOP
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 months ago

          I’d say we don’t know unless we ask Netflix engineers but the comments about license look like a good one to me. Then there is in my opinion the “bloated” Linux versus the more clean BSD experience (I am a Linux user and I like to tinker with BSD sometimes). Maybe it is still true that BSD will not run on as much hardware as Linux does but have you ever compiled a custom kernel on BSD and compared it to compiling a custom kernel on Linux ? On BSD it is in comparison much easier and the documentation is usually really good.

      • Onno (VK6FLAB)@lemmy.radio
        link
        fedilink
        arrow-up
        0
        ·
        2 months ago

        Uhm. AFAIK, you only have to share code under the GPL if you distribute binaries outside your organisation.

        If it stays in-house, there’s no distribution, thus no requirement to share the source.

        I’m happy to be wrong, feel free to point out what I missed.