Slashdot Mirror
Widenius Warns Against MySQL Falling Into Oracle's Hands
jamie sends in a blog post from MySQL co-founder Monty Widenius calling for help to "save MySQL from Oracle's clutches." While the US DoJ approved Oracle's purchase of Sun back in August, the European Commission has been less forthcoming. Widenius points out that Oracle has been using their customers to put pressure on the EC, and he questions Oracle's commitment to MySQL, saying their vague promises aren't good enough. He writes:
"Oracle has NOT promised (as far as I know and certainly not in a legally binding manner): To keep (all of) MySQL under an open source license; Not to add closed source parts, modules or required tools; To not raise MySQL license or MySQL support prices; To release new MySQL versions in a regular and timely manner; To continue with dual licensing and always provide affordable commercial licenses to MySQL to those who needs them (to storage vendors and application vendors) or provide MySQL under a more permissive license; To develop MySQL as an Open Source project; To actively work with the community; Apply submitted patches in a timely manner; To not discriminate patches that make MySQL compete more with Oracle's other products; To ensure that MySQL is improved also in manners that make it compete even more with Oracle's main offering."
Fork it and then name it MariaDB, specifically. Sun buys MySQL. Monty complains about Sun's treatment of MySQL. Monty leaves MySQL. Monty forks MySQL. Monty complains about Oracle. This isn't exactly a surprising development.
No OS on the planet can protect itself from a user with the admin password. - Yvan256
Wrong. It's all the the same code. (Not counting readline in one vs libedit in the other.)
We (yes, I work for MySQL/Sun) do NOT maintain separate GPL and commercial codebases.
On the contrary, it is not a problem at all. MySQL can be forked and the people dependent on it can use the forked version indefinitely. The commercial users who want to stick with the evolution of "MyOracle" can pay for the privilege. Everyone is happy. The EC has no need to worry. A fork of MySQL could provide all the necessary competition, to say nothing of PostgreSQL.
I encourage anyone who mistakes Monty for a friend of Open Source to do a little reading...
The case against the case against Oracle-MySQL
MySQL and a tale of two biases
Monty Program AB's Suggestion to EU Commission to Get Rid of the GPL on MySQL
How Many Times Can Monty Sell MySQL?
Old-timers never pronounced it "squeal" or "sequel" - that's a give-away that you're either a newbie or you come from a Microsoft background. Real old-timers pronounce it "ess queue ell".
Just saying ...
As long as there was a company behind it, there was always potential that it could be bought. Switch to PostgreSQL. Nobody owns it.
I don't work for Oracle, and I would like to see other databases to get into the same league inf every material respect. Take Oracle RAC (formerly Oracle Parallel Server) for example, Oracle's shared everything database clustering technology. There are no open source equivalents. MS SQL, PostgreSQL, and MySQL don't have anything like it. Apparently IBM DB2 does, but only in the mainframe editions.
There are often things that can be done to work around these limitations (replication works in some cases, for example), it is just a question of cost effectiveness. There is no reason to buy Oracle just because it is "Oracle". Only if it does what you need better than the alternatives. For many businesses that is the case. Oracle doesn't dominate the business because of FUD. It dominates due to true technical superiority. A business would be positively stupid to pay a large premium for a database that doesn't have any real superiority to much less expensive (if not free) alternatives. That is one of the reasons why it would be great if the alternatives caught up. Transparent clustering for PostgreSQL would be outstanding.
I *can* use PostgreSQL to do everything I could with Oracle 7 back in the early 90s. That is saying something (MySQL doesn't come close). A lot of people don't need much of what Oracle has added since then. If that is the case, there is a great case to be made for using something else. It is certainly a lot less expensive.
I wish the parent could be modded higher - Widenius is a hypocrite and does not give a rat's ass about MySQL. He simply wants it under a closed source friendly license so he can build another business around everyone else's hard work that is in MySQL. Widenius has complained that the GPL prevents other companies from competing. This simply isn't true. PJ at Groklaw sheds the light on this rather well.
Online upgrades. Suppose you have a service that needs to be available on a 24 x 7 basis. Is there any reason to shut everything down just because the upgrade script needs to add a new column, drop an old one, or increase the precision or maximum length of an existing one?
We do software as a service, for example, and generally speaking, we don't take our site down *ever*, certainly not for application software updates. Logged in users stay logged in and continue their work without noticing.
First came QUEL. The followup developed at IBM was jokingly called SEQUEL. It was changed to SEQL and then SQL for trademark reasons. See Wikipedia.
So it was originally called "sequel". Pronouncing it as S-Q-L came later.
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
That's one of the reasons we have open source licenses. So we can fork if we have to.
He did already - it's called MariaDB. He just doesn't like the fact that his fork has to be GPL only - he can't integrate any commercial code like he did when he owned MySQL AB. I don't think I can put it any better here than I did at Groklaw (see this comment. Basically:
Monty just doesn't like the hand that he dealt himself - one he had every opportunity to change while he owned MySQL AB, probably even would have been able to influence while he was a Sun Employee too; but never complained (that we know of while he was at Sun) and never did (when he had the chance himself - he could of done it as part of the sale to Sun).
Yeah - he could just setup a services-oriented company around MySQL; but he doesn't want that - he wants his MySQL back, as well as the money he took from Sun. It's all about his wallet; nothing else.
Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
Oracle has announced a statement today making commitments concerning MySQL that may (or may not) address some of these concerns -- of both Widenius and the EU.
http://www.marketwire.com/press-release/Oracle-Corporation-NASDAQ-ORCL-1090000.html
These include:
* Continued Availability of Storage Engine APIs
* Commitment to enhance MySQL in the future under the GPL
* Support not mandatory
* Increase spending on MySQL research and development
* Continuing to maintain the MySQL Reference Manual
* Preserve Customer Choice for Support
And some other things about preserving the conditions of licenses currently held by storage vendors.
Healthy skepticism is of course always a good idea. On first reading, I can't tell how binding these commitments are (the statement says "Oracle hereby publicly commits to the following", and that's about it), and it doesn't exactly make Widenius' commitment to the timeliness of new releases and patches, except for the commitment to increase spending, which Oracle presumably would like to have result in new revenue.
But Oracle is evidently trying to address the EU's concerns in an effort to get the deal approved, and the EU might get them to make these commitments binding. The EU's initial reaction appears to be positive:
http://www.bloomberg.com/apps/news?pid=20601087&sid=a4SRxTHKHzTA&pos=7
Always keep a sapphire in your mind