<story><title>Reality Check for Cloudflare Wasm Workers and Rust</title><url>https://nickb.dev/blog/reality-check-for-cloudflare-wasm-workers-and-rust</url></story><parent_chain></parent_chain><comment><author>dgreensp</author><text>I think the one-sentence version of this is that Workers are meant for small, undemanding tasks (for example, they have tight memory limits and don’t have great performance), so using them to do “serious number crunching” at the edge, which is the advertised use case, seems questionable.&lt;p&gt;I think the blurb about the downsides of Wasm is just too generic, it’s a sort of “why Wasm isn’t preferable to JS in all cases” for the uninitiated.  It may not be meant to imply that number crunching is the use case.</text></comment>
<story><title>Reality Check for Cloudflare Wasm Workers and Rust</title><url>https://nickb.dev/blog/reality-check-for-cloudflare-wasm-workers-and-rust</url></story><parent_chain></parent_chain><comment><author>brundolf</author><text>&amp;gt; I guess I’ll stick with my error prone Javascript Workers or, more likely, spend an afternoon migrating to a minimal Typescript setup.&lt;p&gt;If the OP wants a zero-config typescript experience (assuming Deno isn&amp;#x27;t available on Cloudflare workers), I can&amp;#x27;t recommend esbuild enough</text></comment>