Thomas Brand (@[email protected])
mastodon.mit.edu
Attached: 1 image The license file for Slack, an electron app, for Mac is 15,190,831 bytes (15.2 MB on disk) in size and 272,516 lines in length.
    • schnurrito@discuss.tchncs.de
      12·
      21 hours ago

      And given that the filename starts with LICENSES.chromium, it is probably just the one copied from Chromium which is the base of all Electron apps. Nothing we didn’t know yet.

      • sugar_in_your_tea@sh.itjust.works
        3·
        15 hours ago

        The text-only GPL is 34K, and that doesn’t have any markup (the screen shot says it’s HTML, so that would likely double it). Multiply that by however many dependencies it has and 15MB doesn’t seem unreasonable for a naive amalgam of licenses. If they’re all plain text, then that’s approx 441 deps if they’re all 34K. Web browsers are complex beasts, so it’s not surprising that they have a lot of deps.

        • schnurrito@discuss.tchncs.de
          1·
          15 hours ago

          I don’t think Chromium actually has any GPL code in it, only LGPL (mostly from KDE because Chromium is ultimately descended from KHTML) and less restrictive ones. If it had GPL code in it, Google Chrome and Edge would also need to be FOSS, which they aren’t.

          • sugar_in_your_tea@sh.itjust.works
            1·
            15 hours ago

            Sure, but the LGPL modifies the GPL and directly refers to it, so you’d want to include both. Section 1 states:

            1. Exception to Section 3 of the GNU GPL.

            You may convey a covered work under sections 3 and 4 of this License without being bound by section 3 of the GNU GPL.

            I can absolutely see a lawyer requesting that both be included even if only the LGPL is used.

            For the record, the LGPL is ~7.3K on its own as plain text. Add that to the GPL and you have >40K w/o formatting. Multiply that for each project that just changes the copyright owner part and you’re in multiple MB territory.

            And Chromium probably uses GPL licensed code in its build process (e.g. gcc), which would also be included in the license file if that’s a standard way to build the project according to its documentation, esp. if there’s a way to install it via a script or something (pretty common for Google and Mozilla projects).

            • mkwt@lemmy.world
              1·
              14 hours ago

              GCC in particular comes with the Runtime Library Exception to the GPL. The exception carves out runtime code from the GPL vital licensing condition, and it doesn’t require software compiled by GCC to attribute back to GCC.

              So there’s no legal reason to copy in the GPL text into this notice on account of GCC.

              Yes, do convey GPL text if you’re also conveying LGPL text.

              • sugar_in_your_tea@sh.itjust.works
                1·
                12 hours ago

                So there’s no legal reason to copy in the GPL text into this notice on account of GCC.

                That license file doesn’t describe the license governing chromium they have a separate license file for that (and it’s very small, since it’s an MIT/BSD style license). This license file covers all software used in the making of chromium.

    • VicksVaporBBQrub@sh.itjust.worksM
      3·
      19 hours ago

      From this quora webpage and using 128 characters in one line…
      128 x “272,516 lines of text” = 34,882,048 megabytes of pure text. Hmm, odd. – the meme 15.2 megabyte… is smaller?

      For pages, I simply used “40 lines per page” and it’s…
      272,516 ÷ 40 = 6,812.9
      But legal pages have lots of blank paragraph double spaces. So 6,813 pages is underestimating it.

      • brbposting@sh.itjust.worksEnglish
        1·
        11 hours ago

        Yay, they did the math! And by they I mean the person with the funniest username I’ve seen this week. Thank you.

        Anyway, give or take that’s just absurd!