At one end of the binder sit the shortest documents in the collection. The MIT license is a single paragraph. The two-clause BSD license is barely longer. Even the Apache License, which runs to several pages because it handles patents carefully, is permissive at heart: take the code, keep the notices, and owe nothing back.

These licenses dominate the modern shelf. By most counts of public repositories, MIT alone covers more projects than every copyleft license combined. Understanding why the shortest texts won is one of the binder's oldest questions.

What permissive actually means

A permissive license grants the four freedoms with almost no conditions. You may use the code for any purpose, copy it, modify it, and distribute it, including inside proprietary products you sell. The one surviving obligation is attribution: keep the copyright notice and the license text with the code. The BSD family adds a clause against using the author's name to endorse your product. That is roughly the entire apparatus.

Where copyleft says you must give back, permissive licensing says you may keep. Both are legitimate choices about what kind of commons to build.

MIT, the shortest sentence that works

The MIT license originated at the Massachusetts Institute of Technology in the 1980s and became the default license of the package-manager era. Its virtues are friction. A developer can paste it into a repository in seconds, a company can adopt the code without a legal review, and a downstream user never has to wonder whether the license reaches their product. The cost of that simplicity is that nothing flows back: a trillion-dollar product can embed MIT code and contribute nothing.

The text's brevity is also its teaching. Where the GPL takes four pages to describe the commons it protects, the MIT license trusts the reader to understand that the whole point is the absence of conditions. That trust is why it spread, and why it is also the license most often pasted into a repository without the author having thought about the choice at all.

BSD and the advertising clause history

The BSD story is the binder's reminder that license drafting is a living craft. The advertising clause seemed reasonable in 1980 and became a burden by 1999, when a single program might carry dozens of attribution lines. The clause was removed by public agreement, which is why the modern BSD text is shorter than its ancestor and why the family is a case study in licenses being revised under pressure.

The BSD licenses descend from the University of California at Berkeley, where they governed the releases of the BSD operating system in the early 1980s. The original four-clause version required that advertising materials mention Berkeley, which became unworkable once a program accumulated dozens of contributors. The later versions dropped the advertising clause, leaving the two- and three-clause forms still in use. The family is old enough that its history explains half the quirks of license drafting.

Apache and the patent layer

The Apache License 2.0, published in 2004, is permissive with a lawyer's attention to detail. It grants the same freedoms as MIT but adds an explicit patent license from each contributor, plus a retaliation clause that terminates your patent rights if you sue over the code. It also requires you to mark modified files. The result is the license of choice for large corporate projects and foundations, where patent exposure matters more than brevity.

Why the shortest texts won

The permissive side won for a reason the binder keeps returning to: licenses are adopted by the people who reuse code, not just the people who write it. Companies prefer licenses that impose no homework. Developers choosing a license for a weekend project reach for the one they already know. The network effect favored the shortest possible text, and the ecosystem sorted itself accordingly, with copyleft surviving where the authors deliberately wanted it.

There is also a quieter cause. The permissive licenses are the only ones that let a company adopt the code without calling a lawyer, and in large organizations the legal review is often the real barrier, not the fee. Removing the review is worth more to adoption than removing the price.

What the permissive choice says

Choosing MIT or Apache is not an absence of position. It is a wager that adoption and goodwill will return more than enforced reciprocity would. Many of the most-used programs on earth, from web servers to machine-learning libraries, run on that wager. The permissive licenses also make the clearest counterexample to the idea that sharing needs royalty clauses or usage gates to be sustainable. The commons they built is enormous, and it is also entirely unprotected against enclosure, which is why the binder files it beside, not above, the texts that asked for more.

The permissive licenses also carry the oldest lesson on the shelf: a license's brevity is not a lack of care but a different kind of care. The MIT text chose to spend its authority on one sentence rather than four pages, and the sentence has held up for forty years.

What the text grants

All four freedoms with a single condition: keep the copyright notice and license text attached to the code.

What a reader should check

Whether the license handles patents, as Apache does, or stays silent, as MIT and BSD do.

The limit of this reading

Permissive texts protect the code's availability, not its future openness; nothing stops downstream closure.