Comments on: Looking back at the MySQL news from last year http://www.xaprb.com/blog/2009/03/08/looking-back-at-the-mysql-news-from-last-year/ Stay curious! Thu, 09 Feb 2012 09:56:43 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Michael Renner http://www.xaprb.com/blog/2009/03/08/looking-back-at-the-mysql-news-from-last-year/#comment-16086 Michael Renner Wed, 25 Mar 2009 00:11:33 +0000 http://www.xaprb.com/blog/?p=906#comment-16086 I find it saddening that MySQL has failed with so many (non-)functional requirements one expects of a "Enterprise" Database despite having the money and resources which are necessary for accomplishing this task. The whole situation is even more disappointing when one looks at the current market penetration of the project and the amount of knowledge (or rather - experience) the current (web) development community has with the database product. The lack of a clear vision (or at least it was never publicly communicated) to get out of the mess the current codebase is, seems like a mark of death for the project, which is only underlined by the high fragmentation of the codebase which has occurred during the last 2 years. And without deep insight in the organization I can only account this to a complete failure of management, both development- and product management-wise. But as always - technical convincing solutions hardly ever get to be market leader, but they get a chance to correct history once the succeeding but flailing technology is eventually overtaken by technological and sociological advancements... I find it saddening that MySQL has failed with so many (non-)functional requirements one expects of a “Enterprise” Database despite having the money and resources which are necessary for accomplishing this task. The whole situation is even more disappointing when one looks at the current market penetration of the project and the amount of knowledge (or rather – experience) the current (web) development community has with the database product.

The lack of a clear vision (or at least it was never publicly communicated) to get out of the mess the current codebase is, seems like a mark of death for the project, which is only underlined by the high fragmentation of the codebase which has occurred during the last 2 years. And without deep insight in the organization I can only account this to a complete failure of management, both development- and product management-wise.

But as always – technical convincing solutions hardly ever get to be market leader, but they get a chance to correct history once the succeeding but flailing technology is eventually overtaken by technological and sociological advancements…

]]>