Copyright (c) 4-digit year, Company or Person's Name
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
You don't need this line, since if you remove the copyright notice, you will lose the rights that the copyright owner has given you. This line as no point. Also,
substantial portions of the Software
is totally vague and can be interpreted in a lot of different ways.BSD doesn't explicitly allows sublicensing, but you can do it as long as what is said in the license is respected. Same for ISC and MIT. The MIT use a lot of superfluous language to explicitly give you rights that the ISC would also give you implicitly, but no one would put these implicit rights in doubt. For example, both license have a similar sentence:
This implicitly protects you from people who own patents and would put them into your code. They can't sue you, because since they've put their patented code under this license, as the copyright owner, they give you the right to use it.
ISC is a very simple license. If you like it, you can also take a look at the 0-clause BSD license. It's the same license, but with
provided that the above copyright notice and this permission notice appear in all copies
removed. It gives aways you code, without requiring that future users keep the copyright notice.