It's useful to others. It's just not useful to enterprises. This may be a positive or a negative depending on your intentions. You can read such a license as a kind of non-commercial use license.
In fact this is exactly the business model of the SQLite project. They have a "cute" public domain declaration and then they sell actual licenses for a fee to enterprises that want to distribute SQLite worldwide.
What is the business risk about disregarding a clause that says you merely should do something, with no carrot or stick if you do or don't?
Re:License to Use JSLint for Evil
by colechristensen on Thursday April 14, 2022 @06:04PM
(#31033895)
Copyright holders suing the licensee for a breach. Regardless of if the suit has merit there will be significant legal costs in defending against it and significant engineering costs in replacing the software, often quickly. Likewise there could be image issues for the company violating license terms.
It will not deter everyone from using it. Who will it deter and who will it not? Maybe that split is intentional.
Re:License to Use JSLint for Evil
by pessimizer on Thursday April 14, 2022 @06:59PM
(#31034516)
It will deter people who are accidentally telling on themselves.
If you want your software to be usable, choose standard licenses and don’t modify them. Unless you find value entirely in creating something and not in being useful to others, be extremely careful with creative licensing.