With all the news about the fork to MySQL to the new lean-mean drizzling machine, I might have been the only one that actually didn't really like the idea.
Taking out views, triggers, stored procedures, events and everything else since MySQL 4.1 didn't really appeal to me. But this coming from the guy that wrote "Using Business Rules in MySQL" and "Useful Ways to use Views", can you really blame me?
I not happy, but they are probably right
Well, it seems to me like its going backwards. Albeit I completely understand that its for the purpose of going forwards.
Take out the stuff that the vast majority of MySQL users don't use - mainly web site developers - and make it very fast and light weight. Monty is completely right when he said that 1% of the users (big businesses that use MySQL) cannot dictate how MySQL will turn out.
For example, people who use ORM (object-relational mapping) could not care less about how many features a database has or not, since they (probably) don't use any of them.
I think it would help if...
The problem for me is that I thought it would be a lot better to add more to the database instead of taking away from it.
Adding features that will try to estimate how the database will be used and pre-fetch certain data ahead of time. Emphasizing more on stored procedures (or making them easier to use) to offset problems with speed from web platforms (like RoR). Using views (or even better, materialized views) to help speed up analytical reports.
MySQL community edition is still there, right?
Having said that, it does not necessaringly mean that MySQL will completely stop working on MySQL and move to Drizzle. However, it will defiantly take away resources from it. As well as take away confidence from big businesses and maybe big websites that relied on the extra features like stored procedures to use MySQL.
I can tell you from personal experience that it was very much an uphill strugle to persuade companies I worked for to use MySQL while claiming that it has good-enough features compared to commercial databases.
Even if you can say Drizzle is only a micro-kernel and you will be able to add plugins for businesses, its not a very convincing arguement. "Maybe one day you will have features in Drizzle that will be good for you"... thats nice.. I'd go with something that has 10 year tested and working features for my business right now.
While this is probably a rant, I really had to give my opinion about it.
I recognize that its an important step to take for MySQL, but I am dis-heartened by it.
Did I also mention that it took me a while to learn stored procedures??
Anyway, I hope that I am wrong and everything will be ok with MySQL and/or Drizzle and I am sure that 99% of the (web) developers will probably benefit from Drizzle. I'm just complaining for the 1%.