Hacker News new | ask | show | jobs
by klyrs 2220 days ago
> When I write any code, I take 2 options: 1) Don't share it publicly or 2) Completely release it as public domain. No need for MIT license or any of that crap. Here, just take the code and go win the world, I don't need any credit. Ask yourself how you've benefited from someone crediting you if at all it comes back to you.

I had a similar philosophy in my youth, and it still resonates with me. Hanging around Slashdot and doing oss development, I learned enough about IP law to understand that it's not as simple as we'd like.

There's actually a risk that your unlicensed code will be picked up by somebody in a jurisdiction with different IP laws than you're familiar with. They can copyright the code (did you say "free for any use or modification?), and issue C&D to anybody hosting your code online. You could find yourself in a very awkward position where you published it first but they've done so in a legally defensible manner. CC0 and MIT are prudent licenses -- not to ensure that you get credit, but to cover your own ass.

1 comments

I can get behind CYA license use. I think all of them have some kind of a clause - “You have no rights to sue me and no implied warranty” sounds logical.
I use MIT for everything. I don't like coercive licenses, but that CYA is important.

America is the Land of the [Lawyers'] Fee. I can't remember the site, but someone has a site, dedicated to all the stupid, ridiculous, double-facepalm lawsuits the US "enjoys."

It is quite common for people to be [successfully] sued for trying to help someone else.

I remember taking a CPR class, where we were told that, if we gave CPR, we could be sued.

So there's actually a reason why someone might stand back, and watch you die...

+1 We gotta get this lawyer gig economy shutdown. What a waste of human talent.