Kagi releases alpha version of Orion for Linux

Original Article ↗ Hacker News Discussion ↗

Engine choice & platform focus

  • Orion uses WebKit; reasons inferred include: alignment with iOS/iPadOS (where only WebKit is allowed), good battery/performance on macOS, and avoiding Chromium’s dominance.
  • Some note that Firefox’s engine is harder to embed; others just want anything non-Chromium to slow Google’s control.
  • On Linux, people see value in a third major engine alongside Gecko and Blink, especially if it drives WebKitGTK forward.

Apple search lock‑in and Kagi

  • Several comments vent about iOS Safari’s locked search engine list, which excludes Kagi.
  • Workarounds via extensions exist but are seen as clumsy; some users say this is the main reason they won’t subscribe to Kagi.
  • Comparisons are made to Android and even HarmonyOS, where adding custom search engines is easier.

Closed source on Linux: controversy

  • A large subthread debates Orion’s proprietary status.
  • Many Linux users say they won’t run a closed-source browser at all, citing trust, privacy, and free‑software principles—especially for such a central application.
  • Others are pragmatic: they already use proprietary apps on Linux and care more about breaking Chromium hegemony than licensing purity.
  • The team explains they’re small, view Orion as significant IP, fear large-company appropriation, and plan to open‑source once the browser is financially self‑sustaining. Some find this reasonable; others call it a deal-breaker.

Linux alpha, quality, and DRM limits

  • The Linux build is alpha-only, initially limited to paying supporters; a direct Flatpak link is shared and early testers report rough edges and high CPU use.
  • Discussion highlights that, for mainstream adoption, support for DRM/Widevine (Netflix, etc.) may be decisive; others counter they don’t care about DRM playback and would use such a browser for “serious” work only.

Features, UX, and privacy details

  • Fans praise: strong built‑in ad blocking, ability to use both Chromium and Firefox extensions, and tight Kagi integration.
  • Some report past instability on macOS/iOS; others say recent 1.0 releases feel much more solid.
  • Concerns surface around online installers and default Kagi referrer headers; both can be mitigated but defaults and opacity worry privacy‑focused users.