3 ms·
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.
by 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 agoYeaaahhh... 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 agoHuh, 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 agoI 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.