Phoenix: A modern X server written from scratch in Zig

Post by loeg » Thu, Dec 25, 2025, 5:09 PM UTC

wakawaka28 wrote: post #123

socketcluster wrote: post #116

The name Phoenix is overused. There is an Elixir framework called Phoenix. I think I also heard of other projects with that same name before. It's a bit like the name 'Apollo'; besides the moon landing project, I know like 2 dev projects called that and also there is a sales SaaS platform with that name. Surely people should run a search first before choosing a name...

Firefox tried to use it and was sued for trademark infringement. wxPython also has a Phoenix project. It's definitely a catchy, but overused, name.

Post by yxhuvud » Thu, Dec 25, 2025, 5:14 PM UTC

mihular wrote: post #301

vladvasiliu wrote: post #202

Earlier quoted context omitted.

Well, isn't this compositor related? I've never had any window placement issues running Sway (i3 for Wayland). I never used night light on that machine, so I can't comment on that particular point, but the thing seems to work just as well as i3. The only problem I have is with JetBrains IDEs, which seem to have shaky support. They're usable (meaning you can code), but the experience is so wonky that I basically consi…

Wayland intellij ide support is in the works, IDEs support X11 out of the box, but you can enable Wayland support explicitly (just search for it). As per Windows placement, Firefox won't restore windows on original positions supposedly because of Wayland, somebody please correct me if I'm wrong.

Post by ptx » Thu, Dec 25, 2025, 5:27 PM UTC

imtringued wrote: post #231

PunchyHamster wrote: post #162

Earlier quoted context omitted.

I think the problem is that people wanting to build that and being in position to (being paid for by their employer), are fed up with X11. It learned no lessons from X11. It made most things harder to write and pushed more things that really every WM needs and doesn't care much to implement differently to WMs making them harder. For example, stuff like "WM need to manage raw inputs, so they can have more power over t…

https://news.ycombinator.com/item?id=46382947 Read this including my response. A lot of X features are actually Xorg features and they only work because there is a single implementation that everyone tried to integrate with. Turns out the moment there are two implementations, which is hard on X and easy on Wayland, you can no longer rely on targeting a single implementation for direct integration anymore. This means…

Post by bitwize » Thu, Dec 25, 2025, 5:39 PM UTC

sho_hn wrote: post #11

Pretty interesting approach to make an X server that is essentially "Wayland-like" (merging display server/compositor by default, isolated apps by default, no remoting of GLX, dropping legacy protocol features to the point of breaking compat with the core protocol, etc.). Not sure who this is for, but by itself it looks like a fairly reasonable set of choices.

Post by cons0le » Thu, Dec 25, 2025, 5:50 PM UTC

someguyiguess wrote: post #91

glzone1 wrote: post #51

Earlier quoted context omitted.

Python 3 was actively antagonistic to Python 2 code for no reason other than to lecture us about how we were doing things wrong, writing code to support 2 and 3 to help transition was dumb etc etc. For example, in python 2 you could explicitly mark unicode text with u"...". That was actively BLOCKED with python 3.0 which supposedly was about unicode support! The irony was insane, they could of just no-oped the u"". I…

Python is really one of the worst designed languages. It always baffles me that people recommend it to beginners.