The State of MySQL
Jun 02, 2009, 17:33 (0 Talkback[s])
(Other stories by Jeremy Zawodny)
WEBINAR: On-demand Event
Replace Oracle with the NoSQL Engagement Database: Why and how leading companies are making the switch REGISTER >
"It has not been the smoothest of sailing recently. MySQL was
having problems even before the Sun acquistion shook the community.
In it's effort to help the product "grow up" and cater both to
enterprise users (which means adding more functionality) and newer,
less sophisticated users (which means making things more friendly
and approachable–and building more tools), the team seemed to
lose direction and ended up being spread too thin.
"The large gap of time between MySQL 5.0 and 5.1 is partly to
blame on management and priorities. But it's also largely the
result a codebase badly in need of a good cleanup and
refactoring--something that has not happened to this day (though
there are signs of that changing). The unnecessary complexity and
lack of clear standards not only slowed down existing developers
but was surely a barrier for new developers as well.
"These problems continued and people began to depart Sun not
long after the acquisition. Members of the senior management team
as well as some of the most experienced and talented developers are
no longer there to guide the development. A subset of those who've
left are actually contributing to the MySQL community in other
ways--more on that later."
- Linux Myth: No Simple, Easy Database Software(May 23, 2009)
- MySQL Forks(May 14, 2009)
- Harder, Better, Faster, Stronger: New Features in Postgres 8.4(Apr 24, 2009)
- Kickfire: Released for all the right reasons, but with the worst timing(Apr 23, 2009)
- MySQL 5.4 Released as Oracle Looms Large(Apr 22, 2009)
- Oracle buys Sun. Is MySQL doomed? Java? Solaris?(Apr 20, 2009)
- Which SQL is MySQL?(Apr 01, 2009)