this post was submitted on 28 Aug 2024
802 points (97.9% liked)

linuxmemes

21304 readers
1197 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 53 points 2 months ago (2 children)

    I feel like most people base their decision on license purely on anecdotes of a handful of cases where the outcome was not how they would have wanted it. Yet, most people will never be in that spot, because they don't have anything that anyone would want to consume.

    If I had produced something of value I want to protect, I wouldn't make it open in the first place. Every piece of your code will be used to feed LLMs, regardless of your license.

    It is perfectly fine to slap MIT on your JavaScript widget and let some junior in some shop use it to get their project done. Makes people's life easier, and you don't want to sue anyone anyway in case of license violations.

    If you're building a kernel module for a TCP reimplementation which dramatically outperforms the current implementation, yeah, probably a different story

    [–] [email protected] 20 points 2 months ago* (last edited 2 months ago) (2 children)

    I once read that the license should be smaller than your code. Gives me a good baseline:

    • Permissive license for small projects and little tests

    • Copyleft license for big projects

    [–] [email protected] 1 points 2 months ago

    Cries in left-pad.

    [–] [email protected] 2 points 2 months ago

    I'm stealing this 👍

    [–] [email protected] 19 points 2 months ago (2 children)

    Well, ideally you're choosing your license based on the cases where it differs from others and not the majority of times where it doesn't make a difference.

    Someone aiming to make Free software should use a copyleft license that protects the four freedoms, instead of hoping people abide by the honor system.

    Also, no one can 100% accurately predict which of their projects will get big. Sure, a radical overhaul of TCP has good odds, but remember left-pad? Who could have foreseen that? Or maybe the TCP revision still never makes it big: QUIC and HTTP/3 are great ideas, and yet they are still struggling to unseat HTTP/2 as the worldwide standard.

    [–] [email protected] 1 points 2 months ago

    People who used left-pad deserved everything that happened to them. But, very valid point.

    There is no honor system. If your code is open for commercial reuse, that's it. If you have any expectations that are not in line with that, then yes pick a different license.

    I guess I agree with you, I'm just phrasing it from a different perspective.

    [–] [email protected] 7 points 2 months ago

    Seems like using a copyleft on the reference implementation of a new protocol is a great way to ensure the protocol is never widely adopted.