Rewriting a large codebase with many years of work behind it to a totally new language is a pretty big task, and often ends up introducing new bugs. But I do a

Rewriting a large codebase with many years of work behind it to a totally new language is a pretty big task, and often ends up introducing new bugs. But I do agree Java has downsides. A more practical conversion would be to Kotlin. That's a much closer language to Java, and it can interop, which means you can rewrite it incrementally, like adopting TypeScript in a JavaScript project. Also, Kotlin uses WasmGC, which avoids the downsides of linear memory - it can use the browser's memory management instead of shipping its own, etc., which is an improvement over C++ and Rust.