[Alupis]

There are several. And no, just because a license appears on the site I linked to does not make it "solid".

* The codebase in question neglected to include the "No Warranty" clause, which implicitly means his code is fit for use. So, if I run it on my machine and my machine crashes, he is liable.

* Just because a license has yet to be challenged, does not make it solid. That would be rather dangerous in a corporate environment.

* This license does not forbid me from re-assigning copyright to myself, then pursuing the original author.

As I said before, licensing is serious business. There is a reason most licenses are pretty long, even the "do what you want" licensing like MIT or BSD.

[xj9]

How often are you going to use an IRC bot written in BrainFuck in a corporate environment?

[Alupis]

I was more speaking about the license in general, not the specific codebase example.

[xj9]

The entire situation is context sensitive. Hobby projects with no practical value don't need serious licensing because they aren't serious projects. Things that other people might actually use are a different story, one that the author of the codebase in mention seems to be aware of.