Cocoa-Way – Native macOS Wayland compositor for running Linux apps seamlessly

Original Article ↗ Hacker News Discussion ↗

Primary use cases discussed

  • Running Linux-only GUI apps on macOS, especially niche/professional tools (e.g., IC design software, building-management configuration tools, old Fortran/X11 tools) that lack good macOS ports.
  • Using GUI apps inside Linux containers/VMs for isolation, per-project environments, and security while still getting “native-ish” windows.
  • Accessing GUIs on remote Linux servers (e.g., MATLAB, VS Code, Emacs, lab and cluster tools) with potentially lower latency and better integration than VNC/RDP.
  • Having a tiling or alternative desktop experience (KDE, GNOME, Hyprland, custom WMs) while staying on macOS for other reasons.

Comparisons to existing solutions

  • XQuartz: described by some as ugly, awkwardly integrated, or slow; others report it works well and has for years. Rooted/full-desktop mode was appreciated by some.
  • VNC/TurboVNC/FastX: widely used and considered solid but more “full desktop” than per-window integration.
  • SSH X11 forwarding + xpra: cited as the closest X11 analogue to what this Wayland setup might offer.

macOS UI and workflow opinions

  • Multiple commenters strongly prefer KDE or GNOME over modern macOS, criticizing macOS for reduced customizability, “syrupy” feel, poor window management, Finder limitations, and recent visual changes.
  • Others point out macOS has historically had a higher desktop share than Linux and doubt this kind of project changes that dynamic.

Keyboard shortcut debate

  • Some want macOS to adopt Windows/Linux-style shortcuts; others argue macOS’s Command-based system is superior, especially in terminals where Control is reserved for control codes.
  • Several note that macOS shortcuts can be extensively remapped (often via Karabiner) to mimic Linux/Windows behavior, or vice versa.

Technical questions and limitations

  • Interest in whether it could support Android/Waydroid, EGL surfaces, multi-monitor, and “seamless” individual windows instead of a single host window.
  • Clarification that Wayland doesn’t natively do network forwarding like X11; tools like waypipe provide that, and this project could act as the macOS-side compositor.

Skepticism about project quality

  • Some see the README and architecture description as shallow or incoherent, question the latency claims, note reliance on OpenGL 3.3, and suspect LLM-generated code.
  • Confusion over whether it depends on a specific hypervisor vs any Linux host; documentation is viewed as unclear.