Why Save MySQL Now?
holdenweb.blogspot.com
holdenweb.blogspot.com
The simple fact that it has a very low barrier to entry alone is one of its major selling points.
this is the same situation with asterisk. digium forces all users that contribute patches to hand over copyright so they can sell a private version of their open-source product to companies.
whether this is fair is up for debate (and is partly why many users hate gpl software, preferring more "open" licenses like bsd/isc). a company open sources an initial version of their product with the gpl, giving everyone access to it, its users contribute many bug fixes, new features, and free support (through forums, mailing lists, bug trackers, etc.) but are unable to sell their own versions of that software. the company that retains copyright and distribution rights is of course able to bundle up everything contributed and make a profit directly from it without having to give anything back to those users.
If that's what they need, perhaps to migrate their products to a BSD-licensed RDBMS like PostgreSQL. Or to a public-domain one like SQLite. Or a fully proprietary one. It's their software and, since, they have already licensed it as proprietary, their users were already robbed the freedoms GPL'ed MySQL would provide.
As it is now, those companies have licenses for specific versions. If they didn't get permanent unrevokable licenses and were happy with the cheaper ones they got, well... Phineas Barnum would be happy to use them as examples.
"whether this is fair is up for debate"
If handing over copyright is too expensive, companies are always free not to contribute or not to use Asterisk at all. They will, however, have to compete with other companies who do. Economics will dictate who wins.
"(and is partly why many users hate gpl software, preferring more "open" licenses like bsd/isc)"
The only freedom GPL denies a developer is to close up software that was once free. The only freedom the allegedly "more open" licenses give developers is to deny freedoms to their users. For the users (and software freedom is about them), those licenses give nothing.
But we are drifting from the original topic.
The topic is that MySQL is Oracle-proof and doesn't need saving the same way other GPL'ed products don't need saving. They are either good - and thus worthy of surviving - or bad - and thus will die natural deaths.
Many people have emotional attachment to their software. I must confess I am thinking and rethinking moving from Linux to OpenSolaris for much too long to explain it in strictly rational terms. I will miss it when Linux dies, but, by then, I expect GNU/HURD to run nicely on my 64-core ARM-based netbook. Or, at least, ZFS to be under GPLv3.
You can't "close up" software that was free. The software remains free.
The only freedom the allegedly "more open" licenses give developers is to deny freedoms to their users.
It gives developers the freedom to create an aggregate product without also releasing their own code under the GPL, allowing them to pursue a business model that they feel will fund the ongoing R&D necessary to produce that product.
For the users (and software freedom is about them), those licenses give nothing.
If users do not feel that a product does not provide a fair trade, they are under no obligation to purchase or use it, and the original code remains to do with what they will. However, as indicated by vast market success, users do feel that these licenses and the products produced using them do provide something of value.
It's far too common that the person who assigns value to software and that signs the check is not the same person who puts it to work.
Well -- I for one am happy with the licensing status of Mac OS X, and think I've received a perfectly fair trade.
My wife had to build an intranet on top of Sharepoint because a PHB said so. I have to read my e-mails off an Exchange server because corporate IT finds it nice. Far too many servers are Red Hat while I would prefer Debian (I am a fan of APT). Perhaps you have to make your presentations on PowerPoint for Mac, even knowing how much better they would look with Keynote. Life's not perfect.
And, while I love the NeXT side of OSX, I find the Unix side far too early 90's for my taste ;-)
What GPL prevents that BSD doesn't is closed forks. Obviously some people don't care about closed forks --- some people may even like them on principle --- or nobody would BSD-license anything.
The "big deal" is that only two things provide a revenue stream around MySQL sufficient to support the heavy R&D costs associated with building a database product:
- The name ("MySQL")
- The copyright.
If you own the name, you can sell branded binaries and services. If you own the copyright, you can sell non-GPL licenses to commercial interests. Without these, creating a viable revenue stream is incredibly difficult.
I think this ties into this discussion, as well: http://news.ycombinator.com/item?id=1028638 -- I Love the GPL (Except When it Applies to Me)
Yes, and Monty knew that when he chose to structure MySQL the product that way. Everything is proceeding exactly as he foresaw and intended.
On the other hand, if I thought my project was going to be a cash cow, I would have done exactly what Monty did, except the whining after the fact. I think if I buy a car, then sell it to someone and that person sells it later to my arch nemesis for a discount and he plans on wrecking the heck out of it, my screaming about how this is not right is not going to attract many supporters, is it?
If the same zeal and effort being spent to oppose Oracle were being spent to create a community around a fork, helped by the controversy it'd be a widely known thing already. Couple that with OS vendors choosing the fork over the "mainline", and in a few years the fork would be "the" MySQL, albeit with a different name.
All Sun got for their $1Bn was the domain name mysql.com...
MySQL's battle for the last decade has mostly been getting enough brand recognition that corporate environments consider it a serious, practical alternative. The brand IS the value of MySQL: it is a promise that the technology has been worked on by serious people, and will continue to be patched and improved for the forseeable future (however realistic that promise turns out to be).
Starting again with a new brand is possible, but by definition it would be a new company which would have to prove its chops and its longevity all over again.
Losing the MySQL brand would be a serious setback to MySQL adoption in corporate environments, and thereby a setback to the amount of money that gets invested in improving it. It is in the interests of all users of MySQL that the brand remain trusted.
All those people have quit Sun and work for Monty now...
Losing the mysql brand would mean less than nothing, in the corporate world a brand has value in the open source world the name changes and everybody moves on.
See joomla vs mambo and a ton of other examples.
The only person that really seems to have a problem with this is Monty himself since he can't let go of his baby even after selling it down the river. Which plenty of people spoke up about when he sold it to SUN in the first place.
Which kind of bothers me because I really like Sun hardware. Every blunder Sun makes pushed SPARC closer to extinction.
I hope Oracle keeps making the Type 7 keyboards with Control where God wanted it to be. That's not too much to ask...
I don't know of anything that embeds a relational database that has the requirements of a MySQL.
Supposing he actually is being Machiavellian, he wants MySQL not to be so strong a competitor for the middle and high end of commercial installations. He can afford to concede the very low end - Oracle doesn't play there, except perhaps with BDB (a minor sideline).
Sun's storage products are top notch but I doubt Oracle specifically wanted to move into the field. Selling replacement SPARCs to the banks that still have Solaris won't last long, Oracle know that.
They specifically cited Java and hardware in the acquisition announcement, and I have a really hard time seeing the strategic value of the MySQL asset. Oracle has much more to gain from a "come to us when you're ready to sit at the grown-ups table" position.
1: http://blogs.wsj.com/digits/2009/09/29/oracle-scolded-by-ind...
(Agree though - Oracle would want to keep mysql)
Postgres and SQL are great products and should fill any gaps should you consider switching from MySQL (or Oracle).