5 ms·
At that point, why not use Rust or Go or D or whatever with significantly smaller binary sizes and (un-optimized) faster speeds.
by dtech 6y ago
At that point, why not use Rust or Go or D or whatever with significantly smaller binary sizes and (un-optimized) faster speeds.
- saagarjha 6y agoThose compile to native.
- tasubotadas 6y agoNot on Android
- ChrisRR 6y agoC or C++ then
- FlyingSnake 6y agoRust has first class support for Android.
- eptcyka 6y agoCool, so I can start a new service and bind activities to it from Rust without having to deal with a nasty JNI or an unstable ABI that changes under my feet?
- dgellow 6y agoWhat do you mean by "first class support" here? Some quick searches doesn't give me results that goes in this sense (nothing official from the rust and/or android projects).
- untog 6y agoThat's hardly the full story. Rust provides all the support it is able to provide for Android, yes. But it still relies on the NDK and has to sit behind a JNI layer. A "Kotlin vs Rust" comparison for Android is apples and oranges.
- fnord123 6y agoOn Android you are stuck with Java8 so GP's point melts away.
- vips7L 6y agoI love D but it's ecosystem just isn't there. If you need the jvm ecosystem you're probably better off with Graal.
- Jake_Wharton 6y agoThe goal here was to get the binary size to be small enough, not the smallest it could possibly be. The tool was written in 2 hours because I used a language I was proficient in. While I love me some Rust it would easily double if not triple the time it would take me to build the thing in the first place
- tasubotadas 6y agoIf that's the real Jake Wharton, I have to say I am a big fan of the tools/libs (and their quality) you wrote for Android. They were especially useful 7-5 years ago, when the "official" libs were pathetically crappy :).