Re:Why Save MySQL Now?
by sabat on Sunday January 03, 2010 @01:35PM
(#1028818)
Perl programmer Tim Bunce (DBI/DBD) has been sending mass emails to support this cause, and I didn't understand it either. There's some mumbling about how you can't really fork mysql but no clear explanation as to why. GPL is GPL, and the whole codebase is under GPL. You can do what you want. If they need to come up with a new name, because Oracle starts asserting a trademark issue, so be it. Mandriva survives, doesn't it? I had to think for a second to remember that it used to be called Mandrake.
[ Parent
| on HN ]
Re:Why Save MySQL Now?
by james2vegas on Sunday January 03, 2010 @02:18PM
(#1028910)
You'd think a DBI programmer would know how awful MySQL is and how it would be better left to die.
MySQL does the job pretty well for applications in which stored procedures and other advanced features are not needed. It is really fast and very effective at doing what is absolutely needed: INSERTS, UPDATES, and SELECTS. I don't think it is "awful" or ready to die.
If it was that awful it wouldn't have the installed base it's got.
The simple fact that it has a very low barrier to entry alone is one of its major selling points.
Re:Why Save MySQL Now?
by prodigal_erik on Monday January 04, 2010 @03:38AM
(#1030019)
Quality rarely drives market share in software. In this case I blame nearly all of the 5.2 million PHP and MySQL tutorials out there for exemplifying shoddy practices that inevitably lead to quietly truncated fields, phantom reads, and SQL injection attacks.