Author here. I'm compiling Rust to WASM on another project, so I can address this question. I haven't studied relative perf, so can't make any claims there. B

Author here. I'm compiling Rust to WASM on another project, so I can address this question. I haven't studied relative perf, so can't make any claims there. But for this application your guess is correct: It's iterop. It's easier to go with Rust via Neon rather than WASM because Finda needs to: + Walk the filesystem for file results + Call OS X CoreGraphics APIs to list windows + Run a websocket server to collect results from browsers and VSCode All of this requires leaving the browser sandbox, and so can't be done in WASM.