MySQL is turning out to be one big soap opera as far as I can tell and as Bruce Momjian has mentioned.
Lets go over some of the interesting episodes of this saga:
First Sun buys MySQL
Falcon storage engine creator Jim Starkey leaves MySQL/Sun
Brian Aker heads Drizzle which is a fork of MySQL that hopes to be a stream-lined
implementation of MySQL that leaves out all that nonsense we don't need such as views and stored procs
and targeting it self for running on the cloud, optimizing for massive concurrency, and ease of install. I presume Brian still works for MySQL/Sun though.
I'm not sure what all these things say about the stability of the MySQL core. I mean should I stick with MySQL 5 or run for the Drizzle, but I think I'll stick with PostgreSQL
where ever I can. PostgreSQL may not be quite as interesting from a soap opera perspective,
but it seems a tad bit more dependable and I really like my views and stored functions.
Jim continues to work with the Falcon team and was at the developer meeting. Monty and his team continue to work on the Maria engine (which has been their project for a couple of years now). Monty does not work on Drizzle, Maria is enough to keep him busy.
I am employed by Sun and Drizzle is what you describe it as. We have had a number of people working on it part time for a while now, some inside of Sun and many outside of. In Jay's case he can best describe it himself, but I think I can sum it up by saying that he wanted to do more development, and there is certainly a lot of active work being done on drizzle.
I love PostgreSQL but I don't think your comments above make sense. MySQL code quality and its future direction are quite stable and mature but it needs evolution that leads to staff move. Drizzle is a very good thing to see on the web.
Sun is a very big corporation and it can offer enough engineers to move MySQL forward.
What I want to see is after the merge, if MySQL is as community friendly as usual. It should.
Good point. I guess many people felt I over-reacted and thought I was just making a case for PostgreSQL.
I apologize. I didn't quite mean it that way. As I have said before - we make a lot of money on MySQL consulting and our PostgreSQL business is growing but still behind MySQL. My concern was actually more as a MySQL user than a PostgreSQL advocate.
I guess the main point of my article, is not that MySQL is not stable, but that when key people - seem to sway in another direction - it leaves a bit of a hazy cloud as to what the direction of the product is. Do I treat Drizzle as a separate entity altogether or as a subset of MySQL. Either way it seems to divide the group, though it will probably increase use among people who were not happy with the current MySQL direction.
I guess my point is that its a little hazy right now and hard to tell what's going on.
True PostgreSQL has undergone many private forks, but the community doesn't seem that divided in a meaningful way. E.g. even though EnterpriseDb is a separate private product with its own objectives, I would say its very integrated with the PostgreSQL group and tries to keep in step with the rest of the PostgreSQL progression and not a complete fork like Drizzle is.
I would say Brian's comments were very helpful. If truth be known I like a lot of the MySQL core group and think they are really great people. The way news around the globe reads - its like they abandoned ship or something.
As to the FUD comment from the other guy - you can have a 1000 people on a project, but a 1000 people with no direction is worse than 2 people with a clear direction is my point. I just wasn't clear if those 100 engineers had a clear direction.