git404hub

what is wie fr?

vladislav-kalinkin/wie — explained in plain English

Analysis updated 2026-05-18

1RustAudience · developerComplexity · 5/5Setup · hard

tl;dr

An experimental Rust project that tries to run 64-bit Windows console programs directly on an Apple Silicon Mac by translating them on the fly.

vibe map

mindmap
  root((WIE))
    What it does
      Windows PE64 emulator
      Runs on Apple Silicon
      Written in Rust
    Scope
      64 bit only
      Partial WinAPI support
      Research prototype
    Features
      JIT and interpreter modes
      Basic multithreading
      Real 7-Zip support
    Use cases
      Emulation research
      Running small Windows tools
      Engine performance testing

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Study how Windows PE64 binaries can be translated to run on Apple Silicon

VIBE 2

Run small test Windows console programs on macOS without a Windows install

VIBE 3

Experiment with running the real Windows build of 7-Zip on a Mac

VIBE 4

Compare just-in-time translation performance against a simple interpreter mode

what's the stack?

RustCraneliftJIT

how it stacks up fr

vladislav-kalinkin/wieabc3dz/mixxxabyo-software/ferro-stash
Stars111
LanguageRustRustRust
Setup difficultyhardmoderatemoderate
Complexity5/52/54/5
Audiencedevelopergeneralops devops

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · hard time til it works · 1h+

Requires building from source with Cargo and, for full testing, separately obtaining a real Windows binary.

in plain english

WIE is an early, experimental project that tries to run 64-bit Windows programs directly on an Apple Silicon Mac, without Windows itself being installed. It is written in Rust and works by translating the Windows program's instructions and memory operations into something the Mac's own processor and operating system can execute, rather than by running a Windows program. The author is upfront that this is a research prototype and not yet something that can run ordinary Windows applications. It focuses narrowly on small, self-contained programs of a specific type, plus the small set of Windows system calls that real command-line tools tend to use. Many of the underlying interfaces the project needs to imitate are only partly built out for now, just enough to support its test programs and prove the core engine works. It does not try to support older 32-bit Windows software or aim for complete historical compatibility. One of the more developed examples in the project is running the real Windows version of the 7-Zip archive tool, used for compressing and extracting files. To try this, a user has to separately download the official Windows build of 7-Zip themselves, since it is not included in the project. Once provided, WIE can create archives, list their contents, and extract them, including using multiple threads at once, with files read from and written to a designated folder standing in for the Windows C: drive. The project also has working support for basic Windows-style multithreading features such as creating and waiting on threads, critical sections, events, and semaphores, though the underlying processor emulation itself currently runs one instruction stream at a time even when multiple guest threads are active. Settings exist to switch between a faster just-in-time translation mode and a simpler step-by-step interpreter, mainly for testing and comparison. The full README is longer than what was shown.

prompts (copy fr)

prompt 1
Help me build the wie-cli tool from source and run one of the included micro-exes test programs.
prompt 2
Explain how WIE's bottle folder maps to a Windows C: drive for guest programs.
prompt 3
Walk me through downloading and running the real Windows 7-Zip console tool inside WIE.
prompt 4
Show me how to compare WIE_CPU=jit versus WIE_CPU=iced performance on the test suite.

Frequently asked questions

what is wie fr?

An experimental Rust project that tries to run 64-bit Windows console programs directly on an Apple Silicon Mac by translating them on the fly.

What language is wie written in?

Mainly Rust. The stack also includes Rust, Cranelift, JIT.

How hard is wie to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is wie for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.