How is it "killing MySQL"? If you're using it and then a bunch of people turn out another release under a different name (and it might even be a better release with different people doing it, if the reports are accurate), and you can migrate to it without much bother, how has it gone away in any sense?
I prefer to use PostgreSQL and haven't seen much, if any, negative advocacy from the PostgreSQL community about MySQL going away, despite the remark up-thread - I'm sure most PostgreSQL advocates are comfortable advocating the technical superiority of their favourite database system rather than making up gossip about rival products - but amongst the many reasons for switching away from MySQL, the Free Software licensing really isn't one of them.
If you're using MySQL under a proprietary licence, you might be worried, but I can't say I have that much sympathy for proprietary software vendors. I'm sure Oracle will be quite happy to meet their every need at the right price.
Posted Oct 8, 2009 19:50 UTC (Thu) by man_ls (subscriber, #15091)
[Link]
A regular fork is bad enough. A hostile fork from the parent company staged by some of the core developers (with an accompanying name change) is probably disastrous. If the company is bought by its worst arch-rival -- well, I don't think the outlook is good. I also prefer postgres, but hey, MySQL has its place (and it is not as an unsupported grassroots offering IMHO).
Classic FUD
Posted Oct 9, 2009 10:15 UTC (Fri) by liljencrantz (subscriber, #28458)
[Link]
[Citation needed]
The only similar situations I know of are Joomla and foswiki, two projects that seem to be significantly more alive than they were before the fork.