Also refactoring is Rust is simpler than any other of the listed languages (because it self documents more assumptions).ģ. Unlike other languages, you’ll end up with fewer iterations of the interface because it’ll push the author to really understand the complete interface, rather than shipping a buggy interface that needs iteration. Relative to everything else creating/maintaining these types of internal abstractions is a super minority of time spent reading and writing code.Ģ. Yes it’ll take the writer 3x as long in the short term to create the ergonomic interface but:ġ. Rust is frankly better than most in the list above at allowing the writer to create an ergonomic interface. The goal is to appropriately abstract away the super minority of code that deals with the non-trivial parts into a nice ergonomic interface. None of them are ergonomic for non-trivial applications! I’ve worked professionally with Java, Scala, C++, Python, Rust, JavaScript, Typescript, Ruby. So lets not pretend it is the same effort using Rust on Android, as it is for the official SDK languages. Maybe Rust will get on some day, but it isn't there today, even despite the fact that it is being used for Android internals, there is zero documentation on how to write Android drivers in Rust. In both cases, official support from Android team if there are issues with the above tooling.Īpparently you haven't tried enough, if you think bare bones NDK integration with cargo is enough for Android shops. ![]() packaging of Android libraries for native codeĪnd for game developers, if they so which, plugins for Visual Studio with similar capabilities. two way editing between native JNI wrappers and Java/Kotlin native method declaration Has out of the box support on Android Studio for: Since when does Rust appear as language selection on the NDK installer? ![]() Maybe it will replace C as the de facto low level language. But I think Rust will eventually be used at many/most other companies for anything security or performance critical. Swift might have been another contender, but Apple kept things too close to their chest for too long IMO.Īs another poster wrote, Swift certainly won’t die at Apple (and their ecosystem), and Google will certainly keep Go alive. Rust has a lot going for it (faster than C sometimes, excellent WASM support etc). And I think that’s what will happen at most companies eventually. MS is interesting - they tried to write memory safe C and invested heavily, but admitted defeat eventually - and started using Rust. To address that, Google invented Go, Apple made Swift, Mozilla gave us Rust etc. It turned out though that C‘s memory management is so problematic that many/most security issues are caused by it. ![]() I watched a Rust intro video recently that provided a perspective I liked, so I’ll share that here: MS, Apple, Google (and more) all relied heavily on C for low level code that needed to be as performant as possible.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |