Oracle is not screwing MySQLTue, Apr 5, 2011 in Commentary Databases
People keep asking me “what is going to happen to MySQL now that Oracle has screwed MySQL?” I bluntly disagree that any such thing has happened. This blog post is just my personal view and does not reflect my employer’s opinion, but Oracle might have saved MySQL from what I can see. There is no evidence that supports the hysterical doomsday theories. (Witness MySQL 5.5, probably the best MySQL release in history. Not exactly what I’d call “screwing.”)
I believe that a product with such a large, diverse, and important market presence needs a variety of companies involved with it in many different ways. One of the absolutely key things is a company to make money from it. MySQL needs Oracle, because no one else involved is both capable and trying to make MySQL, the product, a large-scale commercial success. It looks like Oracle is doing what I wish Sun could have done.
Now, is Oracle going to be community friendly, and hold all our hands in a circle while singing songs and accepting our patches? No, of course not, and what an opportunity that creates for someone else. I have no issue with Oracle ignoring the community because they have decided it doesn’t fit into their plans. If you go to the hardware store to buy bread, you won’t find any. Bake a loaf if you want to eat.
About The Author
Baron is the founder and CEO of VividCortex. He is the author of High Performance MySQL and many open-source tools for performance analysis, monitoring, and system administration. Baron contributes to various database communities such as Oracle, PostgreSQL, Redis and MongoDB.