MySQL Founder Monty Quits Sun (Or Not)
Paul Boutin writes "A reliable source tells Valleywag that MySQL inventor Michael Widenius, better known as Monty, has resigned from Sun. Sun bought Monty's MySQL company in a billion-dollar deal last January. Brian Aker, who forked the Web 2.0-friendly Drizzle SQL database (and former Slashdot engineer!), remains at Sun." Kaj Arnö and Sheeri Cabral share their thoughts.
If I'd just made a billion-dollar deal for my company, I'd sure look long and hard at not working anymore.
I am surprised Sun didn't tie Monty to the company with golden handcuffs (deferred compensation). His departure could have a negative effect on customer loyalty. And it sure does look bad for the founder to be leaving so quickly.
Actually, it's going to turn into a white dwarf in most likeliness.
But I understand where you're coming from.
Dedicated Cthulhu Cultist since 4523 BC.
Now now. PHP is a pain but a dang useful pain. Just like MySQL.
PHP and MySQL are both good but not great tools. What makes them useful is all the stuff that works with them.
I would drop MySQL in a second for Postgres except that too many CMS and other packages use it. The same is true of PHP.
There happy now?
See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
isn't build a company, sell it to big guys and go into early retirement the ultimate dream of every nerd?
Sun has the money, and the engineering, however their marketing people will surely screw it up big.
I imagine it going something like "All new versions will use a new and restrictive license" and "The new MySQL will be called Java Relational Database Engine and be pronounced "Drede"
Couldn't agree more. My other big pet peeve is applications that are database-specific (which obviously is related to the fact that app designers don't have much choice in the matter). I don't want to install my own MSSQL server for the sake of the one application that can't run on my company's enterprise scale server farm running some other RDBMS. I don't want to pick a different application that doesn't meet my user's needs simply because it handles the other RDBMS.
Oh, and if we actually had some standards perhaps there would also be a chance that every time Oracle releaes a new software releaes it wouldn't break half the applications I manage...