unixzii/Champagne

Productivity & Utilities

Runs Snow Leopard apps like TextEdit as ordinary desktop windows on macOS and Windows, without a virtual machine.

87
3
C++
LGPL-2.1
3 days old

Champagne is an early research project, not a productivity upgrade: it is worth a look only if you specifically want to experiment with old Snow Leopard software on a modern desktop. TextEdit is the one application the README describes as fully usable; the rest are open questions.

The problem

Opening a Mac OS X 10.6 application normally means keeping an old Mac, booting a virtual machine, or accepting that the file simply cannot run. Each route adds friction: a VM needs its own window, disk image and guest OS, and the app no longer sits beside your current work. Champagne changes that step by running the Snow Leopard binary directly and presenting its windows like any other desktop window. The result is a TextEdit or Finder window among your existing apps, with documents kept in a separate overlay rather than written back into the Snow Leopard image.

What's different

The mechanism is explicitly compared by the author to how Wine runs Windows programs: there is no virtual machine, and the applications appear as ordinary windows. That is the practical benefit. You start an executable by its path inside the Snow Leopard tree, and on Windows the Ctrl key maps to Command and Alt to Option, so common shortcuts such as Ctrl+S and Ctrl+Q work. The README shows a single command-line launcher; there is no graphical installer or app browser described there.

The trade-off is scope. Champagne is described as an early research project. TextEdit works for typing, menus, keyboard shortcuts and window movement; Calculator, Stickies, Font Book, Dictionary and Finder open. Many other applications may or may not work. Separately, the project does not distribute Apple's software: you must supply your own Mac OS X 10.6.7 install DVD image and use a Mac to unpack it. So the unusual part is not just the absence of a VM, but also that you are assembling the runtime yourself before anything launches.

Who should try it

This fits a developer or retro-computing hobbyist who already owns a 10.6.7 install image, has a Mac available for initial preparation, and wants to see whether a particular old app can open as a desktop window. Someone whose actual goal is to get work done in Snow Leopard applications will find the one-confirmed-app status too narrow. It is also a poor fit for anyone without a Mac to run the unpacking step: Windows users need to pack the prepared root on a Mac first, then copy the resulting file over. The README's development notes are the place to check status and options before investing time.

Requirements and limitations

Building needs CMake, Ninja and a C++ compiler, with Xcode command-line tools on macOS or Visual Studio's C++ workload started from the x64 Native Tools prompt on Windows. More importantly, setup requires your own Snow Leopard 10.6.7 DVD image and a Mac to run the extraction script; Windows cannot prepare the tree by itself. After that, applications are launched by path from a command line, and quitting means quitting the app or pressing Ctrl+C in the terminal.

Ongoing upkeep is another consideration. Documents and settings live in ~/.champagne/overlay (or .champagne\overlay under the user folder on Windows), which keeps Snow Leopard unchanged, but it is not a statement about compatibility across applications. The licence has a practical wrinkle: Champagne itself is LGPL-2.1, yet builds include Unicorn under GPLv2, so a built Champagne as a whole is distributed under GPLv2. Those building on it should account for that before redistributing binaries.

HotRepo's take

HotRepo recorded 87 total stars and rank #24 on its NEW-REPOSITORY board for cpp on 2026-10-24; that is a new-project-board position, not a daily Trending rank or a growth measurement. With only one recorded date, persistence cannot be judged from these signals. The thing to verify in the project README is whether the applications you care about are among the ones known to open, since only TextEdit is described as usable.

Written by AI from the project's README, updated October 25, 2026. The project's own docs are the source of truth.