But hey, lets fork Java and do no evil.
[1] - https://en.wikipedia.org/wiki/List_of_Java_virtual_machines
In any case, I hardly think prolonged failed business negotiations constitute failing to "do no evil".
1: http://www.pcworld.com/article/253666/a_timeline_of_oracles_...
When Java 9 finally gets out, and looking forward to Java 10 roadmap, this situation is only going to get worse.
Are there any restrictions on what I can do with it?
OpenJDK is released under an well-known open-source licensing model, that places no restrictions on your
ability to run OpenJDK. Please check the legal section of the OpenJDK project site to understand the scope
of your rights and obligations.
The legal section contains the GNU General Public License, version 2, with the Classpath Exception.So you're wrong. This also explains why Oracle went for the hail mary copyright claim on the SSO of those 37 Java API's - because it's all they had.
https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibi...
Also, court documents in the Oracle/Google trial also showed that Oracle tried to develop a Java smartphone and failed repeatedly because of their, and I quote from a internal Oracle presentation slide, "Very limited internal expertise to make smart decisions".
How much Symbian development have you done?
I used to work for that little finish company.
Many small companies were doing J2ME on Symbian as a way to write portable code across multiple devices.
As for the Series 30+, the MRE was a market failure, never reaching a fraction of J2ME, Mediatek doesn't even support the SDK anymore.
None, but this doesn't change the fact that C++/Qt was the main development platform. I'd also wager that the C++/Qt apps were vastly superior to the J2ME apps.
>As for the Series 30+, the MRE was a market failure, never reaching a fraction of J2ME, Mediatek doesn't even support the SDK anymore.
Well, at least they're still making S30+ phones. The S30 stopped production in 2013.
Symbian C++ alongside J2ME were vastly more used than C++/Qt ever was.
The adoption of C++/Qt was still being ramped up when the switch to Windows Phone 7 took place. Qt Mobility APIs were still work in progress just as an example.
Actually this angered many Symbian developers as they were still evaluating the transition to C++/Qt SDK when the news came out.
I meant dead practically, not literally.
Don't mistake other languages growing as another language being dead. Not all of computing is an exercise in following trends.