winit VS wasmtime

Compare winit vs wasmtime and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
winit wasmtime
48 172
4,390 14,407
6.7% 2.8%
9.7 10.0
5 days ago 4 days ago
Rust Rust
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

winit

Posts with mentions or reviews of winit. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-02-22.
  • Linux version of Warp terminal is here
    4 projects | news.ycombinator.com | 22 Feb 2024
    Hi! I’m Aloke, an engineer at Warp.

    I’m really excited to share that Warp is now available on Linux! If you’re interested in trying it out, you can download Warp: https://warp.dev/

    Building Warp on Linux was quite an undertaking. Warp uses a custom Rust-based UI framework that we built in house and renders natively on the GPU. To get Warp running on Linux, we built a version of our UI framework that supports winit [1] as a windowing backend. We also built a version of our renderer that uses wgpu [2]. Reducing complexity by using these well-supported, cross platform, frameworks let us bootstrap a version of Linux quicker than expected and should make it easier to build Warp for other platforms (like Windows).

    Please let me know what you think! Happy to answer any questions, either about the product or about technical challenges.

    [1] https://github.com/rust-windowing/winit

  • Container2wasm: Convert Containers to WASM Blobs
    16 projects | news.ycombinator.com | 3 Jan 2024
  • Can't get winit sample to compile
    1 project | /r/learnrust | 18 Oct 2023
    This link: https://github.com/rust-windowing/winit has this code:
  • Hey Rustaceans! Got a question? Ask here (28/2023)!
    2 projects | /r/rust | 12 Jul 2023
    Have you seen the official example?
  • Hey Rustaceans! Got a question? Ask here (20/2023)!
    4 projects | /r/rust | 15 May 2023
    That's a bit shortsighted given that there is an active discussion about reducing the interior mutability.
  • File dialog with ImGui?
    1 project | /r/rust | 23 Apr 2023
    I really need a file dialog for my ImGui-based project in Rust. I tried using this crate but it's wayyyyyyy too old. I also saw this but considering the date it was last updated and the look of the repo, it's not gonna work either. Also I maintain my own library for such things, but it's currently blocked by this issue. What options do I have?
  • Announcing async-winit, a new way to use winit as an async runtime
    1 project | /r/rust | 17 Apr 2023
    In this case, I used the "A"GPL because this crate could feasibly run on the web. winit has a web backend. At the moment I don't support it (there's a PR that needs to land first), but in the near future it's not implausible that this crate could be used in a web environment.
  • XUL Layout has been removed from Firefox
    18 projects | news.ycombinator.com | 1 Apr 2023
    There are a number of up-and-coming Rust-based frameworks in this niche:

    - https://github.com/iced-rs/iced (probably the most usable today)

    - https://github.com/vizia/vizia

    - https://github.com/marc2332/freya

    - https://github.com/linebender/xilem (currently very incomplete but exciting because it's from a team with a strong track record)

    What is also exciting to me is that the Rust GUI ecosystem is in many cases building itself up with modular libraries. So while we have umpteen competing frameworks they are to a large degree all building and collaborating on the same foundations. For example, we have:

    - https://github.com/rust-windowing/winit (cross-platform window creation)

    - https://github.com/gfx-rs/wgpu (abstraction on top of vulkan/metal/dx12)

    - https://github.com/linebender/vello (a canvas like imperative drawing API on top of wgpu)

    - https://github.com/DioxusLabs/taffy (UI layout algorithms)

    - https://github.com/pop-os/cosmic-text (text rendering and editing)

    - https://github.com/AccessKit/accesskit (cross-platform accessibility APIs)

    In many cases there a see https://blessed.rs/crates#section-graphics-subsection-gui for a more complete list of frameworks and foundational libraries)

  • Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.68]
    10 projects | /r/rust | 10 Mar 2023
    Name: Francesca! Location: Portland, OR (UTC-7) Looking for: Remote only, full-time or contract. Contact: [email protected] LinkedIn: https://www.linkedin.com/in/francesca-lovebloom/ GitHub: https://github.com/francesca64 Experience: 4+ years of professional Rust experience; former lead maintainer of winit and creator of cargo-mobile.
  • Ubuntu alternatives?
    4 projects | /r/linuxquestions | 17 Feb 2023
    Window manager: https://github.com/rust-windowing/winit

wasmtime

Posts with mentions or reviews of wasmtime. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-29.
  • Backdoor in upstream xz/liblzma leading to SSH server compromise
    49 projects | news.ycombinator.com | 29 Mar 2024
    Just a documentation change, fortunately:

    https://github.com/bytecodealliance/wasmtime/commits?author=...

    They've submitted little documentation tweaks to other projects, too, for example:

    https://learn.microsoft.com/en-us/cpp/overview/whats-new-cpp...

    I don't know whether this is a formerly-legitimate open source contributor who went rogue, or a deep-cover persona spreading innocuous-looking documentation changes around to other projects as a smokescreen.

  • Unlocking the Power of WebAssembly
    3 projects | dev.to | 10 Mar 2024
    WebAssembly is extremely portable. WebAssembly runs on: all major web browsers, V8 runtimes like Node.js, and independent Wasm runtimes like Wasmtime, Lucet, and Wasmer.
  • Howto: WASM runtimes in Docker / Colima
    5 projects | dev.to | 12 Jan 2024
    cpu: 4 disk: 60 memory: 12 arch: host hostname: colima autoActivate: true forwardAgent: false # I only tested this with 'docker', not 'containerd': runtime: docker kubernetes: enabled: false version: v1.24.3+k3s1 k3sArgs: [] network: address: true dns: [] dnsHosts: host.docker.internal: host.lima.internal # Added: # - containerd-snapshotter: true (meaning containerd will be used for pulling images) docker: features: buildkit: true containerd-snapshotter: true vmType: vz rosetta: true mountType: virtiofs mountInotify: false cpuType: host # This provisioning script installs build dependencies, WasmEdge and builds the WASM runtime shims for containerd. # NOTE: this takes a LOOONG time! provision: - mode: system script: | [ -f /etc/docker/daemon.json ] && echo "Already provisioned!" && exit 0 echo "Installing system updates:" apt-get update -y apt-get upgrade -y echo "Installing WasmEdge and runwasi build dependencies:" # NOTE: packages curl, git and python3 already installed: apt-get install -y make gcc build-essential pkgconf libtool libsystemd-dev libprotobuf-c-dev libcap-dev libseccomp-dev libyajl-dev libgcrypt20-dev go-md2man autoconf automake criu pkg-config libdbus-glib-1-dev libelf-dev libclang-dev libzstd-dev protobuf-compiler apt-get clean -y - mode: user script: | [ -f /etc/docker/daemon.json ] && echo "Already provisioned!" && exit 0 # # Setting vars for this script: # # Which WASM runtimes to install (wasmedge, wasmtime and wasmer are supported): WASM_RUNTIMES="wasmedge wasmtime wasmer" # # Location of the containerd config file: CONTAINERD_CONFIG="/etc/containerd/config.toml" # # Target location for the WASM runtimes and containerd shims ($TARGET/bin and $TARGET/lib): TARGET="/usr/local" # # Install rustup: # echo "Installing rustup for building runwasi:" curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- --default-toolchain none -y source "$HOME/.cargo/env" # # Install selected WASM runtimes and containerd shims: # [[ -z "${WASM_RUNTIMES// /}" ]] && echo "No WASM runtimes selected - exiting!" && exit 0 git clone https://github.com/containerd/runwasi echo "Installing WASM runtimes and building containerd shims: ${WASM_RUNTIMES}:" sudo mkdir -p /etc/containerd/ containerd config default | sudo tee $CONTAINERD_CONFIG >/dev/null for runtimeName in $WASM_RUNTIMES; do case $runtimeName in wasmedge) echo "Installing WasmEdge:" curl -sSfL https://raw.githubusercontent.com/WasmEdge/WasmEdge/master/utils/install.sh | sudo bash -s -- -p $TARGET echo echo "`wasmedge -v` installed!" ;; wasmtime) echo "Installing wasmtime:" curl -sSfL https://wasmtime.dev/install.sh | bash sudo cp .wasmtime/bin/* ${TARGET}/bin/ rm -rf .wasmtime echo "`wasmtime -V` installed!" ;; wasmer) echo "Installing wasmer:" curl -sSfL https://get.wasmer.io | sh sudo cp .wasmer/bin/* ${TARGET}/bin/ sudo cp .wasmer/lib/* ${TARGET}/lib/ rm -rf .wasmer echo "`wasmer -V` installed!" ;; *) echo "ERROR: WASM runtime $runtimeName is not supported!" exit 1 ;; esac cd runwasi echo "Building containerd-shim-${runtimeName}:" cargo build -p containerd-shim-${runtimeName} --release echo "Installing containerd-shim-${runtimeName}-v1:" sudo install ./target/release/containerd-shim-${runtimeName}-v1 ${TARGET}/bin sudo ln -sf ${TARGET}/bin/containerd-shim-${runtimeName}-v1 ${TARGET}/bin/containerd-shim-${runtimeName}d-v1 sudo ln -sf ${TARGET}/bin/containerd-shim-${runtimeName}-v1 ${TARGET}/bin/containerd-${runtimeName}d echo "containerd-shim-${runtimeName} installed." cd .. echo "[plugins.\"io.containerd.grpc.v1.cri\".containerd.runtimes.${runtimeName}]" | sudo tee -a $CONTAINERD_CONFIG >/dev/null echo " runtime_type = \"io.containerd.${runtimeName}.v1\"" | sudo tee -a $CONTAINERD_CONFIG >/dev/null done echo "containerd WASM runtimes and shims installed." # # Restart the systemctl services to pick up the installed shims. # NOTE: We need to 'stop' docker because at this point the actual daemon.json config is not yet provisioned: # echo "Restarting/reloading docker/containerd services:" sudo systemctl daemon-reload sudo systemctl restart containerd sudo systemctl stop docker sshConfig: true mounts: [] env: {}
  • MotorOS: a Rust-first operating system for x64 VMs
    7 projects | news.ycombinator.com | 7 Jan 2024
    When you say wasm container, you mean something like wasmtime that provides a non-browser wasm runtime?

    https://github.com/bytecodealliance/wasmtime

  • Lightweight Containers With Docker and WebAssembly
    1 project | dev.to | 18 Dec 2023
    We can't run this directly from the command line unless we install some runtime like wasmtime:
  • Prettier $20k Bounty was Claimed
    16 projects | news.ycombinator.com | 27 Nov 2023
    The roadmap I linked above. The WASI folks have done a poor job at communicating, no doubt, but I'm surprised someone like yourself literally building a competitor spec isn't following what they are doing closely.

    Just for you I did some googling: see here[0] for the current status of WASI threads overall, or here[1] and here[2] for what they are up to with WASI in general. In this PR[3] you can see they enabled threads (atomic instructions and shared memory, not thread creation) by default in wasmtime. And in this[4] repository you can see they are actively developing the thread creation API and have it as their #1 priority.

    If folks want to use WASIX as a quick and dirty hack to compile existing programs, then by all means, have at it! I can see that being a technical win. Just know that your WASIX program isn't going to run natively in wasmtime (arguably the best WASM runtime today), nor will it run in browsers, because they're not going to expose WASIX - they're going to go with the standards instead. so far you're the only person I've met that thinks exposing POSIX fork() to WASM is a good idea, seemingly because it just lets you build existing apps 'without modification'.

    Comical you accuse me of being polarizing, while pushing for your world with two competing WASI standards, two competing thread creation APIs, and a split WASM ecosystem overall.

    [0] https://github.com/bytecodealliance/jco/issues/247#issuecomm...

    [1] https://bytecodealliance.org/articles/wasmtime-and-cranelift...

    [2] https://bytecodealliance.org/articles/webassembly-the-update...

    [3] https://github.com/bytecodealliance/wasmtime/pull/7285

    [4] https://github.com/WebAssembly/shared-everything-threads

  • Spin 2.0 – open-source tool for building and running WASM apps
    13 projects | news.ycombinator.com | 4 Nov 2023
    Thanks for the question!

    Spin could definitely run in more places than what we have pre-built binaries for. Specifically, we could run on all platforms Wasmtime supports today (https://github.com/bytecodealliance/wasmtime/releases/tag/v1...), including RISC and S390X, for example.

    And while we have been experimenting a bit with running Spin on RISC, we haven't really had the bandwidth or requirement to build a production build for those yet.

    Are you interested in a specific operating system or CPU architecture? Would love to understand your scenario.

  • Dave Cutler: The Secret History of Microsoft Windows [video]
    2 projects | news.ycombinator.com | 22 Oct 2023
    > I used to think we'd eventually get to capability based security, but now I see we'll always be stuck with application permission flags, the almost worthless bastard cousin, instead.

    My hope is that WASI will introduce capability based security to the mainstream on non-mobile computers [0] - it might just take some time for them to get it right. (And hopefully no half-baked status-quo-reinforcing regressive single—runtime-backed alternatives win in the meantime.)

    [0]: https://github.com/bytecodealliance/wasmtime/blob/main/docs/...

  • Requiem for a Stringref
    4 projects | news.ycombinator.com | 19 Oct 2023
    WasmTime finished finished the RFC for the implementation details in June: https://github.com/bytecodealliance/wasmtime/issues/5032
  • Should You Be Scared of Unix Signals?
    8 projects | news.ycombinator.com | 16 Oct 2023
    [3]: https://github.com/bytecodealliance/wasmtime/pull/2611

What are some alternatives?

When comparing winit and wasmtime you can also consider the following projects:

rust-sdl2 - SDL2 bindings for Rust

wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten

wgpu - Cross-platform, safe, pure-rust graphics api.

SSVM - WasmEdge is a lightweight, high-performance, and extensible WebAssembly runtime for cloud native, edge, and decentralized applications. It powers serverless apps, embedded functions, microservices, smart contracts, and IoT devices.

learn-wgpu - Guide for using gfx-rs's wgpu library.

quickjs-emscripten - Safely execute untrusted Javascript in your Javascript, and execute synchronous code that uses async functions

tauri - Build smaller, faster, and more secure desktop applications with a web frontend.

wasm3 - 🚀 A fast WebAssembly interpreter and the most universal WASM runtime

raw-window-handle - A common windowing interoperability library for Rust

wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript

minifb - MiniFB is a small cross platform library to create a frame buffer that you can draw pixels in

wasm-pack - 📦✨ your favorite rust -> wasm workflow tool!