86
Licenses are boring but you really need one! (distractedmind.home.blog)
submitted 1 year ago by to c/programming@programming.dev
29 comments fedilink hide all child comments
 

It seems people have a hard time understanding the implications of licenses, so I have written a something to help with that.

you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 1 year ago* (last edited 1 year ago) (1 child)

you don’t care that much about the AGPL clauses (e.g. because your app isn’t a server).

I've been thinking about this recently... Let's say you develop some local CLI. You think it's not a server, so you license as GPL.

Later someone comes and offers your CLI as SaSS. They write the server piece that just calls your local CLI on their server and pipes the input and output between the user.

So... should you always prefer AGPL over GPL?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 1 year ago

    I have thought about this a lot and done some research on it. Bear in mind, I'm far from an expert, just a curious dev, but I've found no reasons to favor GPL over AGPL when AGPL exists. I personally see AGPL as closing a loophole GPL didn't think of.

    One thing I'd wondered if if maybe AGPL hasn't been tested in court. It has. Not as much as GPL, and I don't remember if it specifically was the online part, but I definitely found at least one court case involving AGPL code.

  • permalink
  • fedilink
  • source
  • parent