The MATE Desktop Environment may famously retain one foot in the traditional era of computing, cherishing the classic, reliable workflows that many long-time Linux users refuse to abandon, but that does not mean its community lacks an eye on the horizon. As the wider Linux ecosystem steadily marches toward a post-X11 future, the path forward for smaller desktop environments has often appeared daunting. However, a new independent project is seeking to bridge that generational divide by bringing native Wayland support to MATE without sacrificing the familiar look and feel that users have spent decades customizing and depending on.

Developed independently of the core MATE project by Kerem Söke, a new Wayland compositor called Polo has emerged on the scene. Polo is intentionally modeled after Marco, the existing X11-based window manager for the MATE desktop environment, which itself was famously forked from GNOME’s Metacity many years ago. By mirroring the architectural philosophy of Marco, Polo aims to provide a seamless transition for users who want to embrace modern display server technology without being forced into a completely alien desktop paradigm or workflow redesign.

The core motivation behind the project is straightforward and pragmatic. According to Söke, the overarching idea is to keep MATE behaving as closely as possible to how it operates on traditional X11 sessions, rather than altering the fundamental design of the desktop environment just to fit the constraints or expectations of a radically different compositor. This philosophy addresses a major anxiety within traditional desktop communities, where transitions to Wayland have frequently resulted in broken workflows, missing configurations, or entirely reimagined user experiences that alienate veterans of the platform.

Built using libweston—the reference implementation of a Wayland compositor library provided by the Wayland project—Polo has already achieved a surprising degree of functional maturity for an independent, early-stage undertaking. Despite its nascent status, the compositor already supports essential window management features, window tiling, multiple workspaces, clipboard integration, robust multiple monitor setups, display scaling, screen sharing capabilities, and comprehensive MATE session management.

Beyond core functionality, Polo even manages to incorporate classic desktop effects and visual eye-candy that have long defined the nostalgic golden era of Linux customization. Users running the compositor can experience legacy desktop effects such as the iconic 3D desktop cube, wobbly windows that dynamically react to movement, and classic window minimization animations like the famous Magic Lamp effect. These features demonstrate that moving to Wayland does not necessarily mean sacrificing the whimsical and highly personalized visual flair that many desktop enthusiasts grew up enjoying on Linux.

Despite its impressive feature set, Polo is still far from a complete or thoroughly tested piece of software. Because it is actively developing and occupies a complex niche, Söke is currently looking for adventurous volunteers willing to test the compositor on a wide variety of hardware configurations and alongside the core applications they rely on for their day-to-day computing tasks. Unfortunately, participating in this testing phase is not a trivial or plug-and-play endeavor. Polo currently needs to be compiled entirely from source code, ideally alongside the most up-to-date iterations of the MATE desktop components to ensure proper integration and stability.

The arrival of Polo highlights a broader, industry-wide transition occurring across the entire Linux operating system landscape. Over the past several years, many major Linux distributions and desktop environments have either dropped or actively begun phasing out support for the legacy X11 and Xorg display servers after maintaining dual support for both architectures for extended periods. For smaller open-source desktop environments that rely on older, more monolithic code bases and a significantly smaller pool of active volunteer developers, migrating toward Wayland is an exceptionally tall order requiring monumental engineering efforts.

For its part, the official MATE development team has been quietly and steadily preparing the groundwork for a eventual, full-scale transition to Wayland. Recent software releases have successfully introduced preliminary Wayland support into various native MATE applications, such as the Atril document viewer and the Pluma text editor, while core components like the Caja file manager are increasingly capable of rendering desktop icons under modern display server protocols. Nevertheless, this ongoing work has largely happened in dribs and drabs, often remaining hidden behind specific compilation flags rather than being exposed as a default, out-of-the-box user experience.

Prior to the introduction of Polo, MATE lacked any form of official native compositor or dedicated Wayland session. While Polo remains an entirely unofficial community project at this stage, its existence points to a viable path forward for the desktop environment. If independent projects like Polo can successfully prove that a faithful, Marco-inspired Wayland compositor can work reliably in real-world scenarios, there is inherent potential for such community-driven innovations to heavily influence or even be formally adopted by the broader MATE project in the future.

Developers and enthusiasts interested in reviewing the source code, tracking development progress, or contributing to the testing phase of Polo can find extensive documentation and technical details hosted directly on the official Polo GitHub repository.