Android is a Java VM and will NEVER EVER EVER be able to perform at NATIVE Linux/Windows/Unix/OSX speeds on ANY hardware

Android is a Java VM and will NEVER EVER EVER be able to perform at NATIVE Linux/Windows/Unix/OSX speeds on ANY hardware

Other urls found in this thread:

developer.android.com/ndk/index.html
twitter.com/NSFWRedditVideo

And it still works well enough to own the smartphone market.

quit being delusional half nigger

am i the only one who uses android on my desktop

Why you crying boy? Stockholm syndrome?

If you need something truly performance critical (you probably dont) you could write the engine in C or Assembly and just use jni and the difference would be tiny aside from a handful of specific circumstances. The portability of using the JVM is worth what amounts to a small speed difference.

Besides, regular Java isn't even that much slower it's not like it's Python. The speed of a program depends most heavily on the design of its algorithms with respect to big O.

Try Android x86. It's faster than Windows and Mac OS.

And yet still manages to BTFO iShit, lmao.

I can't believe Apple seriously thought that notch was a good idea.

>he prefers massive black bezels on the top and bottom of his phone instead of a single cutout

Is this the Ubuntu phone that canonical sold, or did you install ubuntu on your own device?

It took courage to ignore display standards.

...

>having shit taste

Anyone tried booting Ubuntu onto a windows phone?

Fuck off brainlet.

It's still slow as shit Java.
>bbut ART
Hotspot has an even better Ahead-of-Time compiler, it's still dogshit slow.

Java is and always will be dogshit slow.

yes

Second

you got better performance out of it?

>le java is slow maymay

Fuck off brainlet. Java is a shitshow for a lot of reasons, but speed is not one of them, especially at native speeds on Solaris/Android.

>brainlet thinks ART isn't a jvm

The whole point of ART/DALVIK is write once, run anywhere. A JVM makes that possible

Here,Knock yourself out:
developer.android.com/ndk/index.html

(Also yes, that's why there even is such thing as 3D games on android)

There are some problems but overall it feels snappier than android

JIT optimized code with GC is faster than your shitty C/C++ in most application level complex circumstances.

Why

>brainlet posts an article debunking his own bullshit

>mix of JIT, AOT and interpreted
>not a VM

Teheheheh

>android if a java vm
sound silly if you say
>android is a hyperviser
It start looking cool

>Nexus 5
My nigga you did good.

Clang is faster than Java, forever, it's not even a contest.
Google wishes they could move, but they're stuck with it for now (until they discontinue Android after the Fuchsia mobile port)

>Android's JVM implementation as of version 5.0 and up is known as the Android Runtime (ART).

>ART is specific to Android and is not historically Java bytecode compatible for reasons that have little to do with engineering and more to do with software licensing.

>Google is now embroiled in a legal quagmire with Oracle over it, and is in the process of actually making it more Java-like in the forthcoming Android "N" to address their legal situation.

Sometimes I wish this place had usernames so we could relentlessly shame retards like you

What you don't seem to understand is that Android does allow you to run native code, and most apps that care about performance do use that option. UI parts are written in Java, everything else in C++.

Make a non trivial benchmark, compare both development time and performance, and make sure there are no memory leaks.
A full gc stop is also faster than refcount.

>Google wishes they could move
Except. You know. Android does support running code compiled with clang, and with gcc, and Android Studio actually has one single checkbox when creating a new project that takes care of everything for you and lets you start writing C++ code right away in your android program. How is it possible for a person to be this uninformed? Explain.

You dumb cunt - the point of switching from Dalvik to ART was that Dalvik was JIT. ART on the first run of an application, compiles it to native instructions and then stores those instructions for next execution. This was done since storage is getting cheaper, would be unnoticeable on disk size, and the the improved performance in needed tasks outweighs it greatly

Then write in c++, problem solved. You don't actually think you're restricted to Java on Android, right? Plus it still ends up faster than the competition. Java is fast, it simply needs more memory to be fast.

Then why do Android phones have smoother UI than desktops? Smooth scrolling in desktop browsers is fucking atrocious.

With the way things are going all ""desktop"" software that's not triple A games will be electron garbage, so that should at least keep android close.