0
Why Android (Google) choose kotlin insted of java.
4 Antworten
+ 2
Actually this is bad for Oracle, providing everyone else does the same. Since Oracle wants to lock Java up behind licensing walls, EVERYONE should just dump Java and let it rust into dust as warning to any other company that tries the same BS. You can read up on the whole case on the EFF website, but essentially when Google created their own version of Java they used existing names, declarations and functionality as existing Java api's in order to allow developers to easily create compatible software. Java sued and eventually won the right to copyright how Java essentially works. So imagine having to pay a license if you create software that is designed to work in relation to Java just because your software used common functionality found in Java. It's the equivalent of Oracle copyrighting the use of a for loop. Simply, where “where there is only one way to declare a given method functionality, [so that] everyone using that function must write that specific line of code in the same way,” that coding language should not be subject to copyright but now it is thanks to Oracle.
While a court DID rule the Androids use of Java api's was fair use, Oracle is planning to appeal AGAIN and so By dumping Java Google is telling Oracle we are not playing your anti-innovation games as well as freeing up resources fighting Oracle. Let Java rot. There are so many quality open source languages that we should NEVER need to license "code"
+ 1
because Google and Oracle are on a very expensive legal battle around the use of Java for android.
For that reason Goggle goes the Java-free way.
Another "big accomplishment" by Oracle.
+ 1
@James Edens
Thank you James for this post. I see that you have deep understanding of IS & IT market.
Suggestion: Maby a little shorter post wouls stimulate younger programmers to read your articles.
0
Because it's new 😎