rust-web-framework-comparison VS container2wasm

First is the size. Writing a server-side and client-side program is possible with Rust, and the resulting WASM package will be small enough. At the same time, Microsoft Blazor converts C# code to WASM, but the client delivery has to include the reduced .NET runtime, taking several megabytes for a script. The same is true for GoLang, even with an attempt to reduce the runtime delivery in TinyGo WASM. Developers want to work with their favorite languages, whether it is Java, Kotlin, Dart, C#, F#, Swift, Ruby, Python, C, C++, GoLang, or Rust. These languages produce groups of runtimes. For example, JVM and .NET have many common parts, Ruby and Python are dynamically interpreted at runtime, and all mentioned depend on automatic garbage collection. For smaller WASM packages, browser vendors can include extended runtime implementations, for example, by delivering a general garbage collector as part of WASM. Garbage collection support by WASM is currently in progress: WASM GC, .NET WASM Notes.

I'm currently reading up on Leptos and what looks like its major contender, Dioxus [1] in planning for next project. (acknowledging here that Yew [2] is maybe the OG Rust full stack / frontend framework, but I'm not considering it at this time)

Here's a nice comparison of the Rust frontend frameworks: https://github.com/flosse/rust-web-framework-comparison#fron...

Note that Leptos is interesting because it _does not use a virtual DOM_, unlike Yew and Dioxus which are React-like.

We already write our backend in Rust; why not use it for the whole stack and stop worrying about e.g. the Typescript object falling out of sync with the API struct?

[1] https://github.com/DioxusLabs/dioxus/

I want to push for using rust & wasm for a small experimental project at my job. I have reviewed the rust web frameworks comparison document, I'd be interested in Yew because I'm familiar with React, and I am interested in Sycamore and Leptos because they are recommended for use in Tauri and I'm personally interested in trying Tauri at some point.

Check out https://github.com/flosse/rust-web-framework-comparison for some options.

The web framework comparison is a good start.

This repository has some nice comparison tables for different web libraries and frameworks: https://github.com/flosse/rust-web-framework-comparison

Unfortunately cosmopolitan wouldn't work for dockerc. Cosmopolitan works as long as you only use it but container runtimes require additional features. Also containers contain arbitrary executables so not sure how that would work either...

As for WASM, this is already possible using container2wasm[0] and wasmer[1]'s ability to generate static binaries.

[0]: https://github.com/ktock/container2wasm

[1]: https://wasmer.io/

Really impressed by the depth and breadth of this project, well done!

A particularly interesting part is the socket layer inside the browser. Other people solving this problem have previously used a proxy to a server that does the real socket implementation. This means you can't have a "browser-only" solution.

The author has solved this (for HTTP/S only) by proxying HTTP requests and then re-creating them as fetch requests (details here: https://github.com/ktock/container2wasm/tree/main/examples/n...). I'm very interested in using this approach for my own project Runno (https://runno.dev).