undefined | Better HN

0 pointspjmlp4mo ago0 comments

Some people rather reach out for first party support, instead of filling in the gaps for the big boys.

0 comments

By first party support, would you be expecting a Rust toolchain shipped in the NDK, or maybe Rust bindings shipped in the NDK?

I could see the latter, although I'd still question whether they should be special cased in terms of a Rust dependency compared to bindings being hosted on crates.io.

Or maybe they should ship scripts that shell out to an existing Rust toolchain.

pjmlpOP4mo ago

I expect Rust being documented here,

https://developer.android.com/ndk

I expect the whole Rust build process being part of Android Studio, including mixed language debugging between Java, Kotlin and Rust.

I expect all NDK APIs to have Rust bidding crates.

I expect that Android developer forums also care to support devs using Rust.

And anything else that I forgot to mentioned, that is provided for Java, Kotlin, C and C++.

flohofwoe4mo ago

The Android NDK just barely supports C and C++ either, unless you're ok with 1990's tooling standards. The whole thing feels like it's maintained by two dudes locked in a Google basement somewhere. I doubt they have the capacity to deal with Rust support in the NDK, unless there's a big strategic change in Android tooling.

3 more replies

eggy4mo ago

Don't forget this list of expectations for SPARK [1] too, if you want even safer, high-integrity, and formally verified code on Android!

[1] https://www.adacore.com/about-spark

2 more replies

j / k navigate · click thread line to collapse