Hikari (compositor)

Hikari (compositor)
Name	Hikari
Occupation	Compositor
Notable works	Hikari Wayland, Hikari X11
Influenced by	Wayland, X.Org Server, Weston, Mutter

Hikari (compositor) is a display server compositor designed for Wayland and X11 environments, combining modern rendering techniques with modular architecture. It targets users of Linux, FreeBSD, OpenBSD, and NetBSD systems while interoperating with projects such as Wayland, X.Org Server, Weston, Mutter, and compositors from the GNOME and KDE ecosystems. Hikari emphasizes extensibility, performance, and compatibility with toolchains like GCC, Clang, LLVM, and build systems including CMake and Meson.

Overview

Hikari emerged as a lightweight yet feature-rich compositor supporting Wayland, X11, EGL, GLX, Vulkan, and integration with display servers and protocols such as XWayland, DRM, GBM, and DRI. The project aligns with display-stack efforts from KDE Plasma, GNOME Shell, Sway, and Weston while aiming to interoperate with toolkits and libraries like GTK, Qt, SDL, EFL, and Clutter. Hikari targets desktop environments and embedded platforms used by organizations such as Red Hat, Canonical, SUSE, and Intel.

History and Development

Development of Hikari traces influence to historical projects including Wayland, X.Org Server, Weston, Mutter, KWin, and research from institutions such as Xerox PARC and MIT. Early contributors referenced implementations like XCB, libinput, libdrm, and Mesa while drawing on standards from OpenGL, Vulkan, EGL, and X11 protocol. The codebase has seen contributions from independent developers and organizations, intersecting with repositories maintained on platforms such as GitHub, GitLab, and SourceForge; collaboration patterns mirror those of Wayland, Sway, and wlroots. Hikari's roadmap incorporated ideas from compositor research papers, discussions at conferences like FOSDEM, LinuxPlumbers Conference, and X.Org Developer's Conference, and feedback from distributions including Arch Linux, Fedora, Debian, and Gentoo.

Architecture and Features

Hikari's architecture layers include a Wayland protocol implementation, XWayland compatibility, a renderer supporting EGL, OpenGL, and Vulkan, and a hardware abstraction built atop DRM and libdrm. The compositor integrates input handling via libinput, session management using systemd-logind or ConsoleKit, and policy enforcement compatible with Polkit. Window management features echo concepts from i3, Sway, KWin, and Mutter while offering tiling, stacking, and compositing modes inspired by Awesome, XMonad, and Fluxbox. Extensions enable integration with PipeWire, PulseAudio, ALSA, BlueZ, and hardware acceleration stacks from NVIDIA, AMD, and Intel.

Configuration and Usage

Hikari uses configuration formats and tools familiar to users of swaymsg, i3-config, Xresources, and Wayland compositors, with optional declarative layers resembling Wayland protocols and configuration managers like systemd. Administrators and users interact via command-line utilities compatible with bash, zsh, fish, and graphical control panels from GNOME Control Center and KDE System Settings. Session startup and integration follow conventions of Display Manager, LightDM, GDM, and SDDM, and Hikari supports scripting through bindings for languages such as Python, Lua, and Rust.

Performance and Compatibility

Benchmarks for Hikari focus on latency, frame pacing, and GPU utilization compared with Mutter, KWin, Weston, and Sway across drivers like Mesa with ANV and RADV, proprietary NVIDIA drivers, and hybrid stacks used by Intel integrated graphics. Compatibility matrices include testing on distributions such as Ubuntu, Fedora, Arch Linux, openSUSE, and Alpine Linux as well as BSDs like FreeBSD, with hardware profiles covering Intel, AMD, NVIDIA, and ARM-based boards like Raspberry Pi. Performance tuning leverages DRI3, present extension, buffer age, and techniques used by compositors in reducing tear, jitter, and input lag.

Community and Development Status

Hikari's community organizes via channels and platforms such as GitHub, GitLab, IRC, Matrix, Reddit, Discourse, and issue trackers modeled on projects like Wayland, wlroots, and Sway. Development cadence follows pull request workflows similar to Linux kernel and Mesa contributions, with CI practices referencing Travis CI, GitHub Actions, and GitLab CI/CD. Licensing and governance draw lessons from MIT License, GPLv2, GPLv3, and contributor models used by Freedesktop.org, X.Org Foundation, and community-driven projects such as KDE Community and GNOME Foundation. Active maintainers and contributors include independent developers, distribution packagers from Debian, Fedora, and Arch Linux, and corporate contributors from Red Hat, Canonical, and Intel.

Category:Wayland compositors