MAUI Is Coming to Linux

Original Article ↗ Hacker News Discussion ↗

What’s being announced

  • Avalonia is providing a Linux (and WASM) backend for .NET MAUI, using Avalonia as the rendering/UI layer.
  • This is not a Microsoft effort; it’s an open‑source integration that lets existing MAUI apps target Linux.

Licensing and pricing

  • Avalonia UI and Avalonia MAUI are MIT‑licensed and free to use.
  • The expensive pricing cited in the thread refers to Avalonia XPF, a commercial product to run existing WPF apps cross‑platform with minimal changes.
  • You only need the paid XPF offering if you want to reuse legacy WPF “as‑is,” not if you build directly on Avalonia UI or Avalonia MAUI.

Why people care about .NET on Linux

  • Many organizations already run substantial .NET backends on Linux (often in containers) and want a unified stack including desktop clients.
  • A Linux target allows reuse of MAUI/WPF codebases and skills across Windows, macOS, mobile, web (via WASM), and now Linux.

Avalonia vs MAUI vs other UI stacks

  • Several comments argue Avalonia is technically more solid and more responsive to the community than MAUI, which is seen as buggy and under‑resourced (thousands of open issues).
  • Some see this move as Avalonia “coming for MAUI’s turf” by attracting MAUI developers and third‑party control vendors.
  • Others question why Avalonia invests in MAUI at all when Avalonia UI already fills the “cross‑desktop WPF‑like” niche.

Wayland, X11, and Linux GUI complexity

  • Large subthread debates Wayland vs X11:
    • Critics: Wayland is complex, poorly documented, inconsistent across compositors, hard to target directly, and makes tasks like screenshots, automation, and window management harder than X11.
    • Defenders: Wayland is conceptually simpler than X11, better aligned with modern GPUs and security, and intended as a low‑level protocol behind toolkits (GTK, Qt, Avalonia), not for most apps to use directly.
    • There is concern over compositor‑specific extensions and GNOME diverging from the wider ecosystem.

Accessibility

  • Avalonia MAUI’s accessibility bridge is currently limited; some see this as “not production ready.”
  • Others note this is an early preview targeting .NET 11 with time to improve, but also acknowledge accessibility is often deprioritized despite legal and business requirements.

Misc technical notes

  • On macOS, MAUI uses Mac Catalyst (UIKit‑based bridge) rather than pure AppKit.
  • Avalonia’s WASM story relies on Skia compiled to WebAssembly and rendering to a canvas.
  • There is mention of future stacking of technologies (MAUI on Avalonia on Flutter’s Impeller on WebGPU), partly tongue‑in‑cheek.