Oracle Is a Licensing Culture
The license is the product. The software is how you find out.
[ essay ]
Oracle’s talent is not a database. It is a culture that treats the license as the asset and the binary as the sample.
I am a remote builder in Auckland, not an Oracle shop. I still inherited the weather. In 2010 Oracle closed the Sun deal and with it Java and MySQL. Ellison called Java the most important software asset they had ever acquired. That sentence is the culture in one line: a language used by millions, recast as property to be licensed.1 Google v. Oracle spent a decade arguing whether APIs could be copyright-locked; the Supreme Court eventually called Google’s use fair, which is a relief and not a strategy. You do not want your stack to depend on a fair-use opinion. MySQL’s dual-license history, the MariaDB fork, and later Oracle JDK subscription changes taught the same lesson at a smaller scale: the download is easy. The terms are the product.
The caution is procurement, not mockery. If a tool is “free” until a sales motion, budget the motion. Prefer licenses you can read without a lawyer on retainer. Postgres and OpenJDK exist because enough people treated Oracle’s weather as climate.
Read the license before you read the benchmark.
— JV · Dark Heart Labs.
-
Oracle’s 2009–2010 acquisition of Sun Microsystems; Google LLC v. Oracle America, Inc., 593 U.S. 1 (2021). Public record of Java and MySQL as licensed assets, and of API copyright as a litigation strategy — the caution, not the joke. ↩