Falkon: A KDE Web Browser

Original Article ↗ Hacker News Discussion ↗

What Falkon Is (and Isn’t)

  • Built on QtWebEngine, which itself wraps the Chromium engine; several people argue this makes it more of a “KDE skin over Chromium” than a distinct browser.
  • Others note the irony in the lineage: Chromium → from WebKit → from KHTML (originally a KDE engine).

Security & Update Cadence

  • Concern that Qt doesn’t update QtWebEngine frequently enough, possibly leaving Falkon with unpatched vulnerabilities.
  • Question raised whether QtWebEngine has explicit, timely security support; no clear answer in the thread.

KDE Integration & User Experience

  • Long‑time users praise Falkon’s tight KDE integration: native dialogs, widgets, themeing, taskbar media/download integration, and KDE Connect support.
  • Some say Firefox/Chromium already integrate reasonably via portals and KDE browser-integration, while others argue portals are being misused and may regress.
  • Complaints: smoother scrolling and adblocking are weaker than major browsers; extension API is under-documented; download manager and advanced features are questioned.
  • User-agent quirks: some Google services and even KDE’s own forum warn Falkon users to “upgrade” their browser.

Extensions & Web Standards

  • Lack of Chrome/Firefox extension support is a downside for some; others say built‑in adblock and userscripts cover many needs.
  • Commenters note WebExtensions is an open spec and could be implemented, but Falkon hasn’t done so.

Gecko vs Chromium & Embeddability

  • Desire expressed for a KDE-native Gecko browser, but embedding support was largely removed from desktop Gecko, forcing some projects to switch to WebKit.
  • Mobile GeckoView exists but is Android-focused; adapting it to desktop is described as possible but unclear.
  • Debate over whether dropping embedding was wise: one side says it saved engineering resources and enabled better performance; another says it cost Gecko mindshare in embedded/webview and Electron-like use cases.

Mozilla, Electron, and Strategy

  • Discussion of abandoned Gecko-based app runtimes (XULRunner, Positron) and missed opportunity to counter Electron.
  • Disagreement over Mozilla’s resource allocation: some defend diversification (VPN, Pocket) to reduce dependence on search deals; others criticize executive pay, layoffs, and lack of focus on the browser.

KDE & Desktop History

  • Nostalgia for Konqueror as unified browser+file manager; mixed views on whether splitting into Dolphin + separate browsers was “enshittification” or necessary evolution.
  • Broader lament about Linux desktop fragmentation (toolkits, distros, portals), making “native” integration and app distribution hard.

Browser Monoculture & Alternatives

  • Several participants feel trapped between Chromium dominance and dissatisfaction with Firefox management, though many report Firefox itself is technically solid and improving.
  • Some note Firefox is held to higher “purity” standards while Chromium’s behavior is more readily tolerated.

Other Topics

  • Mention of Angelfish, another Qt/KDE browser, perhaps easier to contribute to.
  • One user wants a browser with minimal security restrictions (no CORS, Node.js in-page); others point out severe security and even legal risks.
  • Brief thread on container/tab isolation: Firefox’s containers are praised but criticized for weak sync and awkward UI, with suggestions that this is an area where alternative browsers could differentiate.