Yeah, plus just think about all those job sites and resumes that would have to change from "LAMP Developer" to "LAxP Developer" if MySQL forked and changed names! Myself included. All those poor recruiters would need to be trained to know that dbXYZ == MySQL. LOL.
How many "LADP Developsers" do you ever hear about?! ;-) (for those that live in a cave, the "D" would be for "http://drizzle.org/";) ;-) > -----Original Message----- > From: John Daisley [mailto:mg_s...@hotmail.com] > Sent: Monday, December 14, 2009 2:52 PM > To: f...@thefsb.org ; claudio.na...@gmail.com > Cc: mysql@lists.mysql.com > Subject: RE: Help saving MySQL > > MySQL is a huge and trusted brand, yes you could run with a > fork but at the end of the day it will never be MySQL. Its > that MySQL brand name which sells the underlying software, > support packages, books, training, certifications and the > services of a huge number of Sun and independent consultants. > > There are already a few forks out there but you rarely hear > about them because they are not MySQL. MySQL is more than > just some code, its hundreds of developers, its a huge > community, its this list, its a trusted brand name, etc, etc, > etc. Theres so many things which make MySQL what it is and > you could copy every last line of code into a fork, give it a > fancy name and spend millions on advertising and promotion > but you still won't have anything even close to MySQL. > > The MySQL code will always survive in some form, regardless > of who owns it but MySQL could be coming to an end if we > don't support it. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
