Luckily, You Don’t Have to Rewrite Everything in Rust
summary
Rust reaches stable ten years ago but maintains six‑week releases and a small ecosystem—about 15% developer usage on Stack Overflow versus Java’s 30%—with over half of Rust users building server‑side backends. Cargo manages ~200k crates while Maven Central lists millions of Java packages. Interop options shown include JNI, C bindings plus Java’s Foreign Function & Memory API (Project Panama), and generated bindings (Mozilla style) with examples of calling Rust from Java and tradeoffs around ownership, lifetimes, and unsafe blocks.
AI-written summary · about
chapters (11)
- 0:00Rust Java interoperability
- 8:43Rust memory management
- 16:18Java vs Rust code structure
- 23:08Rust dev experience
- 25:16Rust vs Java libraries
- 26:41Maven Gradle vs Cargo
- 27:42Why Java with Rust
- 29:49Java Rust interoperability approaches
- 37:55Java Rust interoperability challenges
- 38:37No need to rewrite in Rust
- 39:21Q&A
related talks
43mRust intro for Java Developers
27mRust for Java developers
45mSustainability with Rust
19mHow to use a Rust library inside the JVM application
50mConfessions of a Rusty Java developer
56mWhen to Choose Rust
12mWhy you should be checking out Rust
12mHow Rust Makes Advanced Type Systems Accessible to the Masses