41–50 of 156 posts
Looking at gomobile and CLs on golang-dev etc I feel Go support in Android is worked on by small focussed team rather than order from top management.
Earlier quoted context omitted.
The fact is that Google forked Java, there is no difference at all.
But Google doesn't call its fork Java(TM), which makes all the difference between this case and J++. The practice of independently implementing and modifying an API has never been questioned until now. It was not in dispute in J++ and it's in fact the reason why software projects like GNU/Linux (which is at most an approximation of AT&T Unix and has never received any sort of certification) are able to exist.
I cannot take whatever piece of Java code I feel like it and run it on Android.
afaik, the real issue is that the dalvik-vm is api compatible with oracle(sun)-jvm. iirc, api is not 'copyrightable' which seems to suggest that it might not be so good for oracle. but then again, cases like these depend a lot on proficiency of presiding judges. wasn't there an earlier judge, who learned some elementary programming while preparing for this case, and who ended up favoring google...
If it were api compatible Java Android wouldn't be the second coming of J++, where apparently thanks to some strange events it is ok for Google to fork Java, break WORA where even many Java 6 libraries cannot run on Android, not to mention about later versions, and some devs seem to think it is ok. While with Microsoft everyone went out with their pitchforks. Android Java is nothing more than Google's J++.
They claimed that you can write Android apps in Java language, or reuse your existing libraries written in Java - like Google themselves did with Apache Commons.
On the contrary, J++ claimed to be Java implementation.
If APIs are going to be copyrightable, it will allow Oracle to hold all the third-parties using Java (or another JVM-based, like Kotlin or Scala) language hostage wrt where they can run their own software.
Earlier quoted context omitted.
To refresh your memory: "The complaint charges Microsoft with trademark infringement, false advertising, breach of contract, unfair competition, interference with prospective economic advantage, and inducing breach of contract."[1] You probably know this, but Java-the-language is not the same as Java-the-platform (VM); Google only uses the language bit, not the runtime. They created their own runtime (Dalvik, and lat…
I know pretty much what happened. The fact is that Google forked all of it. You cannot use anything besides a pseudo Java 6.5 (the language), because there isn't support for all features available. You cannot make use of the full Java SDK libraries, because Google's fork only supports cherry picked portions of the JDK, to the point that people have ported JDK classes to Android to close the gaps when porting Java cod…
The created a whole new language that happens to be mostly based on Java, for a very specific target OS where Java wasn't even available before.
The familiarity with Java is merely a bonus and boost for the adoption of Android programming from Java devs. It's wasn't meant (and it isn't) a jab at taking the Java development market (which is was Microsoft did -- going after the same people using Sun's Java, and for the same environments they used it in).
Earlier quoted context omitted.
I don't think anyone has used "hip and cool" and "Java" in the same sentence for at least 15 years (2001) and no amount of Android can fix that.
"Damn, that grotesque-looking android startled me and I spilled my cup of Java all over my hip, fortunately it was cool so I didn't get burnt".
Earlier quoted context omitted.
J++ got into trouble for trademark issues because MS called their incompatible implementation Java(TM) and caused brand confusion. Android does not do this.
The fact is that Google forked Java, there is no difference at all.
But there are tons of differences in other aspects of the issue -- which make all the difference as to the MS case.
Oracle should pay Google for using Java in Android and keeping the language somewhere around edge of hip and cool. I wonder how long it will be before Google flips to Go or JavaScript for Android.
I don't think anyone has used "hip and cool" and "Java" in the same sentence for at least 15 years (2001) and no amount of Android can fix that.
Earlier quoted context omitted.
Never say never, that's what I thought about Apple and objective-C, and they just invented a new language for it. True, it runs in the same runtime, but it does allow them to slowly move away from 20 years of history. Mind you, the obj-C runtime / Foundation isn't badly set up at all, I'd argue it's better than the Java SDK.
As the one that raised the Go support ticket for Android, back when I was still following Go I doubt it. That ticket was raised before Go 1.0, so I very much doubt it.
So unless you want to wage a perpetual war at the border between your app and Android base libraries, forget Go, or about any language that does not run on JVM.
Oracle should pay Google for using Java in Android and keeping the language somewhere around edge of hip and cool. I wonder how long it will be before Google flips to Go or JavaScript for Android.
Earlier quoted context omitted.
I'd say never. That would kind of be like an apple switching to Swift for iOS. This is even harder for the Android runtime because it's run on a virtual machine with characteristics that don't easily map to another language. Basically if they switch to any other language all the apps that currently use Java (ie. all of them) will have to practically use their own VM -which would be slow - or reprogram everything in a…
Why would maintaining two runtime make dalvik app slower? They're all interpreted anyway.