Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It is ironic how so many [1] JDK vendors were able to work together with Sun, now with Oracle, just Google seems to have some issues following the same rules and licenses.

But hey, lets fork Java and do no evil.

[1] - https://en.wikipedia.org/wiki/List_of_Java_virtual_machines



Given that Java licensing seems to have been negotiated and was likely very different per company, the fact that some licensed versions exist doesn't actually give too much info. There are accounts of what happened when from the court filings though, and people have distilled that[1].

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_...


Doing a business without the necessary licenses in place, forking the Java eco-system by creating an implementation that isn't able to run any random Java library due to partial implementation, is surely the contrary of "do no evil".

When Java 9 finally gets out, and looking forward to Java 10 roadmap, this situation is only going to get worse.


Everybody has rights to fork Java. Oracle gave those rights with OpenJDK under the GPL+classpath exception license. As long as you follow this license, you are free to do what ever you like with OpenJDK. Essentially it means you must stay GPL+classpath exception, but you can add/change/remove any part you like.


Better read it again, it does not apply to embedded systems, because Sun wanted to sell J2ME licenses.


You are talking about Oracle JDK and it's "field of use" restriction which prohibits usage on embedded systems (see http://www.oracle.com/technetwork/java/javase/terms/license/...). But I am talking about Open JDK which does not have this restriction (see http://openjdk.java.net/legal/gplv2+ce.html) and can therefore be used by Google for Android.


I also checked and there is no mobile restriction on the OpenJDK.

  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.


Well, it's not like they called it java. It was marketed as omer hung different, so it's not like you would expect all of Java to work when coding for it or for code targeting Android to work under a normal java implementation.


Funny how the search results for Android documentation speak otherwise.


There are over 4600 references to MySQL in the MariaDB codebase. There are also 56 pages of search results in the MariaDB documentation that contain "MySQL". Is that also supposed to be funny?


Maybe, how compatible is MySQL SQL with MariaDB SQL?


They're compatible for the most part as MariaDB is supposed to be a drop in replacement for MySQL, but there is a list of incompatibilities.

https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibi...


Why didn't you post a link to all of the successful smartphones that used the JVM? Oh, that's right there aren't any and the ones that Oracle tried to make internally all failed.


Series 30 and Symbian smartphones were quite successful in Europe and already offered most of the features that american consumers think that were "invented" by Apple.


The S30 does support J2ME, but its successor, the S30+ completely abandoned J2ME and replaced it with MRE. As for Symbian, J2ME wasn't even the primary development platform - it was C++/Qt.

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".


> As for Symbian, J2ME wasn't even the primary development platform - it was C++/Qt.

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.


>How much Symbian development have you done? Many small companies were doing J2ME on Symbian as a way to write portable code across multiple devices.

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.


So vastly superior that no mobile OS has been successfully with C++/QT on the market.

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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: