// the find
yewstack/yew
Rust / Wasm framework for creating reliable and efficient web applications
Yew is a React-style component framework for building client-side web apps in Rust compiled to WebAssembly. It uses a JSX-like macro for templating and supports web workers for offloading CPU work off the main thread. Target audience is Rust developers who want to write front-end code without touching JavaScript, or teams who need performance-critical browser apps.
The html! macro is genuinely well-designed — it feels close enough to JSX that React devs can read it immediately, but it catches type errors at compile time rather than at runtime. Web worker support is first-class, not bolted on: you can spawn agents that run in separate threads and communicate via message passing, which is something React can't do natively. The example suite is unusually complete — SSR with both Actix and Axum, TodoMVC, routing, portals, contexts, file upload — basically every pattern you'd hit in a real app has a working reference. CI runs benchmarks on both rendering and SSR and posts size comparisons on PRs, so regressions don't sneak in.
WASM binary sizes are still a problem in practice. Even with size optimization flags, a non-trivial app can ship several hundred KB of compressed WASM before you've added any real logic — the examples directory has explicit min-size configs for a reason. The ecosystem is thin compared to React or Vue: no mature component library, no battle-tested form validation library, no state management solution with the mindshare of Redux or Zustand. SSR story is functional but awkward — you need separate binaries for server and hydration, coordinated by you, which means the deployment surface is larger than it looks. JavaScript interop works but the ergonomics are rough; calling anything non-trivial from NPM requires writing wasm-bindgen glue by hand, which quickly becomes its own project.