HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
X11Libre
xserver
C2025–2026
X11Libre / xserver

xserver

XLibre Xserver

33Distinct people
47Mentions
0Explicit recommenders
4.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

XLibre Xserver

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

Favorable Commenters describe the x11libre/xserver fork as an active alternative to Xorg that offers features like easy restart and avoids corporate control. One user notes it is currently useful but requires more polishing and development effort.

This week’s discussion is favorable. This is not a standing endorsement. Read the supporting reply

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Favorable

Commenters describe the x11libre/xserver fork as an active alternative to Xorg that offers features like easy restart and avoids corporate control. One user notes it is currently useful but requires more polishing and development effort.

Supporting reply 1 · Supporting reply 2 · 1 discussions summarized

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 6:01:32 PM UTC.

IceWM direct repository linkDebated

Commenters debate whether modern display resolutions and refresh rates necessitate GPU offloading for transparency effects or if CPU performance should suffice, while simultaneously arguing over the viability of Wayland versus X11 and the role of GNOME/GTK in the Linux ecosystem.

52 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by month47 dated mentions

Observed mentions: 2025-06-06 10:35:10 UTC to 2026-10-12 17:27:30 UTC.

0510152025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 14 mentions; 3 submissions, 11 commentsJun 20252025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 20262026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2026-06-01 00:00:00 UTC to 2026-07-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2026-07-01 00:00:00 UTC to 2026-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-08-01 00:00:00 UTC to 2026-09-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-09-01 00:00:00 UTC to 2026-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-01 00:00:00 UTC to 2026-11-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC14311
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC101
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC101
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC101
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC101
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC404
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC404
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC514
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC000
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC303
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC000
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC413
Jun 20262026-06-01 00:00:00 UTC2026-07-01 00:00:00 UTC514
Jul 20262026-07-01 00:00:00 UTC2026-08-01 00:00:00 UTC101
Aug 20262026-08-01 00:00:00 UTC2026-09-01 00:00:00 UTC202
Sep 20262026-09-01 00:00:00 UTC2026-10-01 00:00:00 UTC000
Oct 20262026-10-01 00:00:00 UTC2026-11-01 00:00:00 UTC101

What Hacker News says

4 sources
Funding is nice, though ... why so much into KDE? Not other projects? I think KDE was better in the past. With its "wayland-only" future it will leave behind several linux users. > I also think it's worth reflecting on just how much stuff KDE gets done with so little money. I dropped them 50€ yesterday, and would encourage people to do the same So the donation daemon worked. Though, if they now have so much money, why would you recommend more money to KDE and not other projects? Why not xserver https://github.com/X11Libre/xserver or gtk2-ng https://git.devuan.org/Daemonratte/gtk2-ng? Granted, these have fewer users, but there should be more diversity among those receiving funding. I also donate a small part of my monthly income, but I don't feel a need to say where to or nudge others to do the same. It would not make any difference to me
Read the rest
personally if Joe donates to abc or xyz.
In Germany's Sovereign Tech Fund Backs KDE with €1.3M
> It's impossible to convince the "frequent upgrader" that maybe that's a risk in terms of introducing new issues. Well, you critisize people who run the latest software here. Two counter-arguments: 1) If you don't upgrade frequently, you end up with super stable debian stuck on ... ancient software. This in turn means that many more recent software, won't work, unless you recompile a lot. I had this issue with mesa for instance, then needing a more recent LLVM, spirv-components and so forth. No chance to have that easily on debian, unless you control what you compile. On my local system here I run gtk2, gtk3 and gtk4 just fine. Good luck having that with debian for recent version; even debian sid is slow compared to, say, gentoo or arch(linux) or void(linux) here. 2) Even debian systems would be vulnerable to copy.fail. So that strategy
Read the rest
is also not automatically better. Personally I am among the frequent update folks. I use ruby scripts to automatically update to the latest, in hope that the people who write code are not incompetent. There is no guarantee that newer software is automatically always better; it is a trade-off. I don't have the time and resource for infinite security audits. I need to get things done and this approach, different to the "everything is scary" crowd, works super-well for me. I use a versioned AppDir approach on linux though, so I don't run into many issues of "can not upgrade because of same .so name issue", so I can conveniently switch to other versions as-is, including the kernel. (Excluding ABI differences and glibc, but for about 98% of the programs this works very well. I am also not alone with the get-everything-working approach, see xserver or gtk2-ng: https://github.com/X11Libre/xserver https://git.devuan.org/Daemonratte/gtk2-ng - granted, for the linux kernel this does not work that well ... I think we need better strategies for the linux kernel, things such as copy.fail should not be possible. I have no good solution here, AI will find many more exploits. No clue how we can prevent this or mitigate this more easily. I was surprised when the local instructor showed us how easy it is to use python for gaining superuser access as-is.)
In Maybe you shouldn't install new software for a bit
> It’s inspired by GNOME Web (Epiphany) So basically, it will be useless. How many use epiphany please? That thing has been so extremely ineffective. It's like 1999 (not that everything was bad in 1999). > follows GNOME’s design guidelines: no menubar, a hamburger menu Oh. my. god. So Ladybird worships uselessness now. Also, GTK progressively gets worse and with GTK5 they will (try to) kill of xorg-server too. Some people disagree with that - https://github.com/X11Libre/xserver and https://git.devuan.org/Daemonratte/gtk2-ng; I get it that there are not that many folks using that, but the point is that the GNOME corporate mindset has a tiny bit of competition. Perhaps that seed of competition grows over time until the corporate gnomeys have to change course (won't happen, as they are paid to abolish what is "old", but more competition is g
Read the rest
ood, if only to try to "reason" with mr. ebassi and other hardcore gnomeys; sadly KDE also goes that way with wayland-only, thanks to anti Robin Hood Nate and his donation-pester daemon. Oldschool KDE devs didn't waylay people for money, now it is "pay or get nagged", thanks to Natey Nate). We kind of need competition in the browser landscape, so in some ways having Ladybird is good. I don't really have much hope that ladybird will be able to challenge the evil Google empire though. But perhaps more people realise that Google controlling so much of the www-ecosystem (again, just look at how they nerfed google search in the last years) is a huge problem.
In This Month in Ladybird – April 2026

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.