It does work well logically but performance is pretty bad. I had a nontrivial Rust project running on Cloudflare Workers, and CPU time very often clocked 10-60ms per request. This is >50x what the equivalent JS worker probably would've clocked. And in that environment you pay for CPU time...
replyThe rust-js layer can be slow. But the actual rust code is much faster than the equivalent JS in my experience. My project would not be technically possible with javascript levels of performance
replythe JS layer is slow, indeed, but it shouldn't be that much slower that it meaningfully impacts frontend apps
replyA demonstration of that by the creator of Leptos:
That's fair and makes sense. In my case it was just a regular web app where the only reason for it being in Rust was that I like the language.
replydid you profile what made it so slow specifically? sounds waaaaay worse than I would expect
replyI did. I don't remember the specifics too well but a lot of it was cold starts. So just crunching the massive wasm binary was a big part of it. Otherwise it was the matchit library and js interop marshalling taking the rest of the time.
replyedit: and it cold started quite often. Even with sustained traffic from the same source it would cold start every few requests.