GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I never understood the technical argument for using Java in a probably-underpowered phone to begin with. (And I don't know of too many apps that actually stay in that environment.) I've always thought, "oh, you've got to be kidding. Java's such a pig that it doesn't even run particularly well on a 'respectable' computer." I think Apple has a much more robust strategy in Swift. (Likewise cross-platform languages such as Haxe/OpenFL.)
Last edited by sundialsvcs; 03-29-2018 at 08:59 PM.
I suspect Google used it because it was there and it was easier than coming up with something new and they could marshall it into something they could control.
As an aside, as you know, I'm not a big Google fan, but, next to Oracle, Google looks like a white knight on a noble charger.
I agree with the poster at Above the Law: the Federal Circuit got it wrong, because they don't get it.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by frankbell
I suspect Google used it because it was there and it was easier than coming up with something new and they could marshall it into something they could control.
As an aside, as you know, I'm not a big Google fan, but, next to Oracle, Google looks like a white knight on a noble charger.
I agree with the poster at Above the Law: the Federal Circuit got it wrong, because they don't get it.
Or did they get it stuffed into an envelope or donated to an account of their choice? With the abuses of these companies with regards to other "domains" any victory for them is most likely a padded wallet somewhere.
It's unclear whether Google "designed" Android with Java, since they basically just bought Android Inc. (with the existing code) in 2005. Since Apple was fast enough, they needed to push their new product into the market soon, so "it was there" probably was a good reason to stick with it for the time being.
At least Kotlin has become a first-class citizen with Android Studio 3.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.