Public domain / DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE for snippets that really should not be licensed
MIT for projects I want to be truly free
LGPL if I'm feeling a bit jealous
GPL if I want companies to pay me to use my work
Commercial if companies are actually willing to pay to use my work
with a side-note that GPL/LGPL allow you to re-integrate 3rd party improvements back into your code without issue. So for projects you intend to maintain and improve for a longer period of time it is probably better than MIT.
Sweating the differences between MIT, BSD3, etc. seems like a waste of time and sink for happiness. Worst case scenario, somebody uses something I made in a way I don't want them to, I don't have to let that affect me.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
As far as I care, there are 5 licenses:
with a side-note that GPL/LGPL allow you to re-integrate 3rd party improvements back into your code without issue. So for projects you intend to maintain and improve for a longer period of time it is probably better than MIT.
Sweating the differences between MIT, BSD3, etc. seems like a waste of time and sink for happiness. Worst case scenario, somebody uses something I made in a way I don't want them to, I don't have to let that affect me.
Excellent advise and breakdown thank you 👏