dioxus VS container2wasm

Dioxus Labs (http://dioxuslabs.com) | Founding Rust Engineer | San Francisco | in-person | Full-time | 125-150k | 0.5-3% equity

I'm Jonathan, the creator of Dioxus (YC S23). Dioxus is a popular crossplatform GUI library for Rust that, imo, is the easiest way to ship apps that are beautiful, fast, and robust.

Dioxus is quite popular, almost 20k stars on GitHub, and we recently raised a sizable seed round from "top vcs." We have a lot of exciting projects on the horizon:

- in-place binary patching for rust hotreloading (http://github.com/jkelleyrtp/ipbp)

- a WGPU powered HTML/CSS renderer (http://github.com/dioxusLabs/blitz)

- experiments with LLM-based component generation (http://github.com/dioxusLabs/dioxus-ai)

- upcoming mobile tooling

- TUI-based devtools for a ruby-on-rail like experience

- a deploy platform for web/desktop/mobile/backend and all the fun that entails...

I'm looking for a founding systems engineer passionate about Rust, WASM, apps, the web, compilers, linkers, and devex - basically someone who's not afraid of anything. Dioxus is a very lean organization and we've been able to move so quickly since we keep our team small and high trust. No annoying standups or corporate bureaucracy. If you want to contribute to OSS, move the needle, and work in a startup that's closer to deeptech with hard problems, this role is for you.

I'm specifically looking for people who are excited by this space and doing this type of work. If you're just looking for a job then this probably isn't the right role for you.

Apply on our yc page or are reach me directly at jon at dioxuslabs dot com

https://www.ycombinator.com/companies/dioxus-labs/jobs/dRPOo...

We have a web components example here: https://github.com/DioxusLabs/dioxus/blob/fd21c971038840130f...

Everything should work like normal except: attributes are not typed, custom event listeners must be implemented with web-sys

I think something like https://dioxuslabs.com could deliver native, cross platform apps and win back mobile.

While we took an in-depth look at Dioxus in this tutorial, there is still so much to learn. Luckily, Dioxus provides detailed documentation with references and cookbooks to guide developers. Make sure you check it out, and feel free to comment below with any questions.

You can probably imagine the challenges of integrating such a system in a robust way that does a good job and improves on the status quo. We felt like the Tauri implementation worked well for Tauri apps. But there’s a problem: it was so tightly coupled to Tauri that the work couldn’t be enjoyed by other projects (not even the ones like Dioxus who were using Tauri’s underlying technology of Tao + Wry).

Maybe have a look at https://github.com/ktock/container2wasm, it most likely could boot into a customized container with all golang tools installed.

The existence of vscode.dev always makes me wonder why Microsoft never released an iOS version of VSCode to get more users into its ecosystem. Sure, it's almost as locked down as the web environment, but there's a lot of space in that "almost" - you could do all sorts of things like let users run their code, or complex extensions, in containers in a web view using https://github.com/ktock/container2wasm or similar.

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).