Compare this to Yew, a Rust framework that does this correctly. Yew's Link component only accepts values from a Routable enum. This enforces compile-time guarantees that a route is valid and internal. You cannot accidentally pass in a user-controlled string and redirect them to a malicious site. That's type safety. That's Rust's promise. And that's what Dioxus breaks. - Source: dev.to / 5 days ago

Rust? It's built clean from the ground up. The crates.io registry is full of modern, safe, composable libraries. You've got Axum, Rocket and Actix for backends, Leptos, Dioxus, and Yew for frontend, and more. Every library you use follows the same philosophy: safety, performance, and zero tolerance for ambiguity. - Source: dev.to / about 1 month ago

> To my knowledge there is not a Vue/React-WASM-type framework out there yet or any framework for building web apps in WASM (without starting from a blank canvas). Not sure if these qualify, but these Rust web frameworks use wasm: https://dioxuslabs.com/ https://yew.rs/. - Source: Hacker News / about 2 months ago

Leptos, Yew and Dioxus are modern frameworks for building front-end web apps in Rust. These all compile to Wasm. - Source: dev.to / 3 months ago

This has already been done; there are multiple languages/frameworks that compile directly to WASM with no JS such as https://yew.rs/. - Source: Hacker News / 5 months ago

Working on Runno (https://runno.dev/) as a side project. It's a tool for running code in the browser for educational use. I've been playing around with turning it into a sandbox for running code in Python (https://runno.dev/articles/sandbox-python/). This would allow you to safely execute AI generated code. Generally thinking about more ways to run code in sandbox environments, as I think this will become more... - Source: Hacker News / 2 months ago

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... - Source: Hacker News / over 1 year ago

This is the use case I've been tackling with Runno (https://runno.dev), it's more performant than OP's approach but not as flexible. - Source: Hacker News / over 1 year ago

I love these kinds of interactive code/sandbox projects! The author's example page [1] gives some more background on the design of Codapi as well [2]. Another similar project is Runno which runs entirely client-side in the browser [3]. [1] https://antonz.org/code-examples/ [2] https://codapi.org/ [3] https://runno.dev/. - Source: Hacker News / over 1 year ago

I'm working on this problem as well and would be happy to sling you some thoughts and notes. Check my website https://runno.dev and send an email to the address on that website! - Source: Hacker News / over 1 year ago