3 ms·

That time is now. I've been shipping Rust code to browsers for years...

• berkes 2y ago
  Rust is still the only language with decent tooling and an ecosystem to compile to WASM. Many other languages haven't passed the PoC stage. Several are ready, and doable (C#, Go?) but hardly as easy and common as with rust. At least that was the state when I looked six months ago. It's a fast moving area. So, yes, that time is now. But the only practical option is rust. Which may be enough, idk.
  • pjc50 2y ago
    C# Blazor certainly exists and works, although it feels really clunky. Only suitable for a true application, not for integrating with web pages. It's almost the inheritor of the Java "applet" and the HotJava browser.
  • randomdata 2y ago
    > Many other languages haven't passed the PoC stage. Wouldn't it be more accurate to say that WASM hasn't passed the PoC stage? There are quite a few languages that have great WASM support, to the extent WASM allows, but have to bring all kids of workarounds to deal with the shortcomings of WASM as it sits. An especially challenging problem as it relates to browser use with those workarounds is that they bloat the artifact size. Few are willing to subject users to multi-megabyte downloads. Work is being done on WASM to address those shortcomings, but hands are pretty much tied until that arrives. Until then, the "lower level" and heavily constrained languages will be left to stand alone.
• marcosdumay 2y ago
  Yeah, but Rust is not great for UI code full of global values.