MySQL as packaged by Oracle is quite literally a corpse. MariaDB is a reanimated corpse.
And such is the tale of an open-source product acquired by a multi-billion-dollar company who made those multiple billions of dollars entirely on selling a commercial product against which the open-source product competed. Competition-elimination-by-acquisition at its finest.
Looks like to me, like it is far from a corpse: https://github.com/MariaDB/server/commits/10.1
I agree with you on both PostgreSQL and MongoDB, but saying MariaDB is a corpse is ignorant at best.
Ever heard of the fasted embedded database engine called Berkeley DB. Doesn't matter came from where, Sun or what ever is still being developed and contributed in the open source environment.
From Wikipedia:
-----
Oracle Corporation makes versions 2.0 and higher of Berkeley DB available under a dual license.[15] The sleepycat license license is a 2-clause BSD license with an additional copyleft clause similar to the GNU GPL version 2's Section 3, requiring source code of an application using Berkeley DB to be made available for a nominal fee.
As of Berkeley DB release 6.0, the Oracle Corporation has relicensed Berkeley DB under the GNU AGPL v3.[16]
As of July 2011, Oracle's list price for non-copyleft Berkeley DB licenses varies between 900 and 13,800 USD per processor.
-----
And the Java topic is not different altogether, it is disturbing to claim to be "open-source friendly" when you release an open-source implementation for the JVM but sue on the basis that the API is copyrighted.
What is off-topic it talking about Oracle at all in this thread ;-)
Initially I was partnering with Google, but now I side with Oracle's decision, as it is now proven how Google just pulled a Microsoft and fragmented the Java eco-system.
Now we are stuck with partial Java 7 assuming 4.4 devices, good luck using try-with resources in lower versions and no plan for future versions as of the Android Developers Fireside at Google IO 2014.
The Android team seems more interested in porting the whole Eclipse/Ant infrastructure, building more Google APIs or making Android run everywhere instead of improving the language support.
[0] http://nighthacks.com/roller/jag/entry/my_attitude_on_oracle...
I'm not sure that's a good enough reason so say that it's "ok" to claim that an API is copyrightable. The idea that I might have to ask someone permission just to make API-compatible alternate implementation seems ridiculous.
http://www.theverge.com/2012/4/26/2977858/former-sun-ceo-jon...
"Google totally slimed Sun. We were all really disturbed, even Jonathan: he just decided to put on a happy face and tried to turn lemons into lemonade, which annoyed a lot of folks at Sun."
Actually:
> Just because Sun didn't have patent suits in our genetic code doesn't mean we didn't feel wronged
implies just the opposite.
The rest of your post has nothing to do with whether APIs should be copyrightable or not.
If you remove what they got from Sun, what reminds?