Drizzle's Future Moving To Rackspace? 41
abartels writes "It seems like there's been nothing but bad news and resignations coming from Oracle since it finally managed to close the deal on Sun. Finally, there's good news in that Drizzle seems to have a bright future ahead. It just isn't with Oracle, but with the Rackspace Cloud."
It's still basically MySQL. (Score:3, Insightful)
Sure, the Drizzle crew has made some minor changes, but Drizzle is essentially still MySQL. That means it still has many of MySQL's many, many flaws and thousands of unfixed bugs.
Their work is interesting and innovative, but they should have built it off of PostgreSQL or even SQLite, rather than MySQL. I'm well aware of the developer connections with MySQL, but that's no reason to continue using what should be a dead project due to its lack of quality.
did it ever have a future with Oracle? (Score:3, Insightful)
It will be too bad if Drizzle's the only place where exciting development takes place on the MySQL base. Say what you will about MySQL, there are a lot of shops that rely on it and would love to see it come closer to parity with other database programs.
PostreSQL (Score:3, Insightful)
Re:It's still basically MySQL. (Score:2, Insightful)
but that's no reason to continue using what should be a dead project due to its lack of quality.
Maybe the user base of millions upon millions of web sites is enough motivation to continue developing developing the "low quality" project.
Re:It's still basically MySQL. (Score:3, Insightful)
Sure, but as a practical matter, until that $7/month hosting provider offers PostgreSQL as an option instead of MySQL, and then Wordpress will install with a couple clicks and set up its own tables on PostgreSQL... until that happens, Joe Sixpack who just wants to host his own blog isn't going to be interested in PostgreSQL. And if Joe Sixpack isn't interested, and he's the customer, why should a hosting provider push him toward PostgreSQL?
Furthermore, is Wordpress so terrible, running as it does on countless sites, that we must save it from MySQL? As another AC poster said, "Blogs with cached content that make a DB query every 10 minutes aren't a real test of quality." OK fine, but that argument sounds pretty much like saying, "MySQL does absolutely everything a trivial Wordpress site needs to do, and flawlessly, and MySQL is available for free everywhere, therefore we must pull out all the MySQL code from Wordpress and replace it with PostgreSQL." It doesn't hold water.
A programmer who tries to use MySQL for things it isn't suited for is going to end up feeling dumb. A non-techy customer who tries to use MySQL for things it's very well-suited for will end up feeling like he's master of his own destiny. Let's not confuse the two.