5 ms·

> nasty, naasssssty GPL! What does that mean? Why would scanning for gpl code be looked at badly? It presumably means a company is proactively abiding by gpl l

by andy99 3y ago

> nasty, naasssssty GPL! What does that mean? Why would scanning for gpl code be looked at badly? It presumably means a company is proactively abiding by gpl licensing. The only thing better would be to use gpl and share their source as well. But of course it's a legit choice to just not use any gpl'd code. It's probably more common to just turn a blind eye to gpl code, so it's good to see companies making sure they're on the right side of it.

ChrisMarshallNY 3y ago
It was a joke. I'm not a fan of "viral" licenses, and agree that, if a company doesn't want to abide by the license, they should not include them, but I am also not a fan of trying to force others to force others, to force others, etc., ad nauseam. I tend to use MIT, which isn't always everyone's cup of tea, but means that you can use my code, and it would be nice to be credited, but I won't cry myself to sleep, if you don't.
- Thorrez 3y ago
  The MIT license requires giving credit. The difference between MIT and GPL is that GPL requires sharing the modified source code and licensing it the same.
  - ChrisMarshallNY 3y ago
    Yeaaahhh... I'm not going to argue about this. It's basically "Religion and politics," in this crowd, and discussions don't end well. I apologize for my joke.
    - Thorrez 3y ago
      Huh, I wasn't trying to argue one license is better than the other. I was just trying to clarify what the licenses require. I didn't want someone to see your comment and think that it would be ok to use someone else's MIT-licensed code in a product without giving credit.
      - xigency 3y ago
        I take the MIT license and excise the credit clause for publishing my least important personal projects. I feel it gives me just enough cover (no warranty etc.) and avoids requiring people to stick my name into whichever unaffiliated project. For work, I’ve definitely had to bury the fineprint MIT credits on some random help screen. It’s easy enough to do. Re TFA: it’s kind of nice doing a bit of open source work on the job when you can reference or use random utility code later. There’s only so many times I want to write code for walking a dictionary in JavaScript or whatever. As with anything, there are shades of gray and certainly more or less scrupulous ways to behave. Stealing GB’s of code is a bit much.

by andy99 3y ago

ChrisMarshallNY 3y ago

It was a joke. I'm not a fan of "viral" licenses, and agree that, if a company doesn't want to abide by the license, they should not include them, but I am also not a fan of trying to force others to force others, to force others, etc., ad nauseam. I tend to use MIT, which isn't always everyone's cup of tea, but means that you can use my code, and it would be nice to be credited, but I won't cry myself to sleep, if you don't.

Thorrez 3y ago
The MIT license requires giving credit. The difference between MIT and GPL is that GPL requires sharing the modified source code and licensing it the same.
- ChrisMarshallNY 3y ago
  Yeaaahhh... I'm not going to argue about this. It's basically "Religion and politics," in this crowd, and discussions don't end well. I apologize for my joke.
  - Thorrez 3y ago
    Huh, I wasn't trying to argue one license is better than the other. I was just trying to clarify what the licenses require. I didn't want someone to see your comment and think that it would be ok to use someone else's MIT-licensed code in a product without giving credit.
    - xigency 3y ago
      I take the MIT license and excise the credit clause for publishing my least important personal projects. I feel it gives me just enough cover (no warranty etc.) and avoids requiring people to stick my name into whichever unaffiliated project. For work, I’ve definitely had to bury the fineprint MIT credits on some random help screen. It’s easy enough to do. Re TFA: it’s kind of nice doing a bit of open source work on the job when you can reference or use random utility code later. There’s only so many times I want to write code for walking a dictionary in JavaScript or whatever. As with anything, there are shades of gray and certainly more or less scrupulous ways to behave. Stealing GB’s of code is a bit much.