memory-control VS sycamore

Indeed, webassembly is moving extremely slowly. I started a project years ago expecting https://github.com/WebAssembly/memory-control/blob/main/prop... and https://github.com/WebAssembly/memory64 to be fixed at some point. Neither are yet, and the project still suffers from it to this day.

I think wasm is still great without these fixes, but I have lost confidence in the idea that wasm will reach its full potential any time soon.

Additionally, googlers are championing memory control https://github.com/WebAssembly/memory-control/blob/main/prop..., which provides memory protection.

But researching it a bit I found this issue, so it clearly seems to be a problem for a bunch of people out there. And apparently both V8 and Spidermonkey have already addressed this quite recently, see this issue.

FWIW there is a proposal in the works to add page-based protection, which will allow unmapping the 0 page, restoring the trap-on-null-deref behavior that is important for many languages with safety checks.

https://github.com/WebAssembly/memory-control

Perseus is a fast frontend web development framework for Rust with built-in support for reactivity using Sycamore, server-side rendering, and much more. Sycamore is a frontend library that allows you to build interactive user interfaces with Rust. I’d say that Perseus is to Sycamore as Next.js is to React, so it’ll be helpful for you to have a fair understanding of Sycamore before jumping into using Perseus — although it’s not necessary to follow along in this article.

Now, I considered whether to spend more time fixing everything that now failed in sycamore 0.9. But there are major changes ahead which would require yet another major refactoring, to the point where I am not sure whether it would not be more of a rewrite than a refactoring, given my previous experiences with sycamore.

Sycamore.

Sycamore, Yew, or Seed if you want a full-stack solution. (Or Leptos if you want something that's faster but less mature.)

There are others, like Sycamore, similar story as Leptos but imo Leptos is (currently) more ergonomic.

Sycamore is a reactive library for creating web apps in Rust and WebAssembly. https://github.com/sycamore-rs/sycamore

I tried my first project with yew as frontend. And my experience was after some time similar to the already mentioned ones: It is a little more to take on than I actually wanted. And some things were not straightforward to achieve. I switched to sycamore for the other projects now and I am much more satisfied (but this could also be since I have some more experience in the Rust ecosystem by now). Changing from yew to sycamore was pretty easy and I can achieve most of the tasks with less code.

If you want to do fullstack/SPA stuff, check out Sycamore, Seed, and Yew.

If you want to do front-end SPA development, take a look at Yew, Seed, or Sycamore.

I have written a front-end (website) application in Rust that is used internally in production. I wouldn't recommend to use something like sycamore, leptos, dioxus, yew for you next puplic web-app now but i can absolutely see how this is used in the future as those libs mature.