rust-web-framework-comparison VS v86

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

> As a thought experiment, we're almost there! We could technically have `win95.img + bochs86vm.wasm + autorun.inf + msword.exe` wrapped in a "browser evaluator"

I looked into this and... holy crap! We are there. Not for modern programs quite yet, sure, but this is amazing. You can use Windows 2000 from your browser.

https://copy.sh/v86/?profile=windows2000

I think you are looking for Shadow.

https://shadow.goose.icu

Or just the whole kitchen sink. Why not?

http://copy.sh/v86/?profile=windows98

Also: https://github.com/copy/v86 - more productized browser x86 runtime, used by eg https://github.com/snaplet/postgres-wasm

Wonder if you could put all those databases in a Linux image and boot it using v86 [0], eliminating the need for a server.

[0] https://github.com/copy/v86

Trying it out in https://copy.sh/v86/?profile=kolibrios , it's also clearly a love letter to Windows 95 in particular. That could be an unstated goal here, create a very particular PC experience under very particular constraints. I don't know anything about the creator but it's very possible that this kind of work was actually their career in the 90s.

It's incredible how much work was done. Maybe this should be an internet curiosity like how TempleOS has become, though Terry's personality was a unique factor.

hmm, why would people still use VMWare? Isn't vbox open source, or even things such as https://copy.sh/v86/ would do most virtualization trick now days?

Oh, there are more OSes one can use at the parent page:

https://copy.sh/v86/

My highlights:

- First version of Windows (1.01)

- SerenityOS <3

- and even ReactOS