Skip to content

GUI Framework Decision and Comparison

Andrew Paolucci edited this page Nov 19, 2026 · 2 revisions

GUI Framework Decision & Ecosystem Comparison

This page captures the research, architectural trade-offs, and evolution behind robocopy2rust's dual-GUI architecture.


Evolution History

  1. v0.1.0 Initial Prototype (Commit 551aec3) — egui / eframe: The original UI crate (robocopy2rust-gui) was built on immediate-mode egui + eframe (glow OpenGL backend) for rapid cross-platform bring-up.
  2. Ecosystem Audit & Security/Stability Review: Because Microsoft Robocopy is primarily operated by systems administrators over Windows Server RDP, inside Hyper-V/VMware/Proxmox VMs, and elevated as Administrator, immediate-mode OpenGL GUIs introduce real-world risk (OpenGL 1.1 failures in Basic Render Driver sessions, frame redraw CPU overhead on large logs, and non-native Windows accessibility).
  3. Dual-GUI Architecture Adoption (Commit faa9b89) — winsafe + iced: Because core, runner, and report were already 100% UI-agnostic, robocopy2rust-gui was replaced cleanly by two specialized frontends:
    • robocopy2rust-win32 (winsafe 0.0.29) as the zero-GPU native Windows default.
    • robocopy2rust-iced (iced 0.14 with wgpu + tiny-skia) as the standardized cross-platform UI for Linux, macOS, and Windows (robocopy2rust gui --iced).

Rust GUI Ecosystem Side-by-Side Comparison

Framework Paradigm & Renderer Standard Widget Depth Windows Look & Feel License Pure-Rust / Toolchain Notes
WinSafe (winsafe) Native OS Win32 Controls (HWND) 100% Native Windows (ListView, Tab, MenuBar, COM dialogs, StatusBar) Authentic Windows (zero emulation, native DPI/accessibility) MIT Zero third-party deps; tiny binaries; compiles cleanly on both windows-gnu and windows-msvc; Windows-only
Winio (winio) Async (compio) over Win32 / WinUI 3 Native Windows (plus emerging WinUI 3 controls) Authentic Win32 or WinUI 3 MIT Windows-only UI; newer async abstraction with higher API churn than winsafe
Iced (iced 0.14+) Retained, Elm MVU (wgpu + tiny-skia CPU fallback) Medium-High (0.14 modernized to Rust 2024, reactive rendering, tables, IME) Clean custom cross-platform MIT Idiomatic 100% Rust; proven at OS scale by System76 (libcosmic); higher-level chrome built manually
Slint (slint) Retained, .slint DSL + Rust logic (Skia / FemtoVG / Software) Very High (std-widgets.slint, tables, tabs, menus, dialogs, dark/light) Fluent Design 2 default style Dual: GPLv3 / Royalty-Free (attribution) / Commercial Pure-Rust backends (femtovg/software) work on windows-gnu; attribution or GPLv3 constraint for permissive Apache-2.0/MIT ecosystems
GPUI + gpui-component (gpui-kit) Retained, GPU 120 FPS (DirectX / Metal / Vulkan) Very High (60–75+ desktop widgets: docking, virtual tables, trees, modals) Modern desktop (Zed / Longbridge Pro) Apache-2.0 100% Rust, heavy dependency tree, pre-1.0 churn, no mature CPU software rasterizer for Server RDP, prefers windows-msvc
Dioxus 0.7 (dioxus-native / Blitz) Declarative RSX + Signals (wgpu Blitz or WebView2) High (~28 ARIA primitives + Tailwind CSS) Web/Fluent/custom via CSS MIT / Apache-2.0 Blitz avoids WebView (~3 MB UI), though CSS edge cases still maturing
Relm4 (gtk4-rs) Retained, Elm MVU over GTK4 (C library) Very High (GNOME/GTK4 suite) Linux-native; foreign on Windows MIT / Apache-2.0 Requires bundling GTK4 C/C++ DLLs on Windows; larger C CVE surface
egui / eframe Immediate mode (glow / wgpu) Basic-Medium (custom-painted) Developer-tool aesthetic MIT / Apache-2.0 Lowest boilerplate, but glow fails on RDP/Basic Render Driver (wgpu WARP adds size) and redraws full frames during logs
Tauri v2 (non-pure-Rust baseline) OS WebView2 / WebKit + HTML/JS/TS frontend + Rust core Web ecosystem Web / custom HTML MIT / Apache-2.0 Excluded by 100% pure-Rust goal and elevated WebView2 security/IPC complexity

Emerging Rust UI Watchlist

Other notable pure-Rust efforts evaluated but deferred due to pre-1.0/alpha maturity:

  • Xilem / Masonry (Linebender's Vello + Parley + AccessKit architecture — strong long-term foundation, currently alpha).
  • Freya (Skia-backed declarative Rust UI — pulls C++ Skia footprint).
  • Floem (Lapce's fine-grained reactive UI over Vello).
  • Makepad (SDF shader-driven custom UI).

Why Dual WinSafe + Iced 0.14 Won for robocopy2rust

Combining WinSafe on Windows with Iced 0.14 cross-platform solves the classic dilemma where single-toolkit choices compromise either Windows Server RDP/admin safety or Linux/macOS parity:

  1. Zero Compromise on Windows (robocopy2rust-win32 via winsafe 0.0.29):
    • Pure MIT license.
    • Zero third-party UI dependencies; robocopy2rust-win32.exe links directly to standard Windows DLLs (user32, comctl32, ole32) at 2.78 MiB.
    • Works identically across Windows 10, Windows 11, Windows Server Core/Desktop, elevated Admin tokens, VMs, and thin RDP sessions.
    • Backed by Win32 APIs that Microsoft maintains with multi-decade binary compatibility.
  2. Zero Compromise Cross-Platform (robocopy2rust-iced via iced 0.14):
    • Pure MIT, 100% Rust 2024 architecture with clean Elm MVU state isolation.
    • Compiles natively on x86_64-unknown-linux-gnu, aarch64-apple-darwin, x86_64-apple-darwin, x86_64-pc-windows-msvc, and x86_64-pc-windows-gnu.
    • Includes both wgpu GPU rendering and tiny-skia software rendering, eliminating OpenGL 1.1/VM driver crashes while delivering identical UI behavior on Windows (--iced), macOS, and Linux.
  3. Zero Duplicated Core Logic: All quoting, command parsing, .rcj UTF-16LE/UTF-8 handling, 16-rule validation, bitmask exit decoding, preset definitions, profile/history JSON persistence, process orchestration, and audit reporting live once in core, runner, and report.

Clone this wiki locally