- 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.
by socketcluster
9 subcomments
- 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...
- This is a great project! I like and use Wayland but the portal protocols and extension mechanism does leave a lot to be desired. Wayland is still quite a way behind Windows and macOS in terms of what productivity users need
An X11 rewrite with some security baked in is an awesome approach. Will be watching!
by AndyKelley
0 subcomment
- As the application author you can set the release mode in the build script so that the release flag looks like `zig build --release` instead, and the user doesn't choose the optimization mode.
As a user you can pass `--release` to `zig build` to request release mode. If the application doesn't want to pick for you, you'll get an error and then you can pick for yourself.
In this case, it looks like the author of Phoenix wants to choose ReleaseSafe as the official release mode of the application.
Phoenix is the name of my hometown, btw.
by iamnothere
2 subcomments
- This is the kind of initiative I’d prefer to see from X preservationists. Great job, I hope it succeeds. I prefer Wayland, but there’s still a place in the world for X; it just needs new dev teams to shoulder the burden.
by cardanome
2 subcomments
- Please prioritize to keep accessibility features working.
This is really the main issue with wayland. Yes, it might be more stable these days and work fine for you. We can talk how how it makes writing you own WM needlessly complicated and all that but the one thing that makes wayland unacceptable is its lacking accessibility story. After so many years.
Accessibility is not something you can worry about adding later. It is the first thing you should think about when designing new software.
- Same author behind https://git.dec05eba.com/gpu-screen-recorder/about/ , the best screen recorder for wayland imo (I had tried other alternatives but none of them helped in recording at 4k 60fps, this worked out of the box).
by shevy-java
0 subcomment
- I have no idea how well this one works, but I am all up for
more projects that can compete against the singularization
that corporations currently try (see paid developers for
wayland, GNOME and now also KDE). I wonder how much money
would be needed to make the xorg server adapt to the modern
era; I don't even know the featureset that is missing for
this either. But I also know that wayland, after 20 years
(!!!), will never cover those requests users had over tohse
20 years, simply because it tries to cater to a narrow
specification wanted by corporations rather than the people -
so much is now clear (wayland protocol was released in
2008, so it is soon 20 years actually; in a few days we
have 2026, so it will be 18 years).
- So … does xterm work? emacs? xfig? ghostview? xload? xev? oclock? xmodmap? xpilot?
by superb_dev
1 subcomments
- > The compositor will get disabled … if the client runs a fullscreen application and disabled vsync in the application.
This is interesting to me, why would vsync being enabled mean that the desktop compositor needs to stick around for a full screen app?
- I finally caved and switched to Wayland 6 months ago or so. Things just work so much more smoothly.
- Multiple screens support is listed as non-goal. Would that prevent its usage with window managers which support virtiaul desktops? I am i3 user and it is a critical feature for me.
by smj-edison
0 subcomment
- Bit of an observation, but I've noticed that there's been quite a few pragmatic projects started in Zig. Bun vs Deno comes to mind (one focused on DX, the other on security), and now this vs Wayland. Not to say that designing something properly is wrong, just that it tends to throw away a lot of important interoperability.
- Nice! We do need more X servers, since Wayland refuses to incorporate essential protocol elements due to religion.
- Another potentially interesting project is zigx, an X11 client library for Zig applications:
https://github.com/marler8997/zigx
https://www.youtube.com/watch?v=aPWFLkHRIAQ
Compared to libX11, it avoids dynamic dependencies, uses less memory, and provides better error messages.
- If you are not going to implement X11 drawing ops and XRender (which I, and many others, still use heavily), what's even the point? Any 'modern' program that only does client-side rendering already supports Wayland. AFAIK GTK 3 doesn't even support DRI on X11 unless you somehow trick it into using the abandoned OpenGL Cairo backend, but that's not modern enough apparently.
by HolyFenrir
0 subcomment
- Between this and zigx zig can become the whole x11 stack
https://github.com/marler8997/zigx
- This is cool. What X is really missing though is a little bit of love from the toolkit side, e.g. proper latency hiding using XCB, support for dis- and reconnect or support for moving windows to display on different devices.
by s08148692
4 subcomments
- First my mind went to Phoenix (elixir framework), then to X (twitter) before it clicked what this was actually about. Some very overloaded names
by Shekelphile
1 subcomments
- Does this mean we can finally be done with the farce of pretending that Wayland is a serious contender for replacing X11?
- Seems interesting that they're not using the XML protocol specs for code gen, the way the Xorg server does.
- Complements XLibre[0], an active fork of the X11 server from Xorg.
XLibre is trying to advance the existing implementation which Xorg abandoned, whereas Phoenix is writing a new, compatible server from scratch.
0. https://github.com/X11Libre/xserver
- Cool project I guess, don't see the point but technically interesting. Will be cool to have another modern display protocol/server. I personally would have rewritten Wlroots in Zig or something, but I guess this is more interesting.
- the xserver implementation itself is only part of the problem. the other part is the X11 protocol is just bad, and IMHO can't be solved by subsetting.
this might make a good alternative to Xwayland though, which can be exciting.
by morshu9001
0 subcomment
- Funny that this shows up now. I just started trying to write an entire window server + DE combined in Rust, for educational purposes.
by webprofusion
2 subcomments
- Nice but 2008 called and want their git web UI back. I can't take anything "modern" seriously if it seems firmly archaic, my problem I get it.
- Are different DPIs for different monitors supported too?
- This is very good.
We can see innovation in this space.
Next I suppose is porting Motif to Windows.
- So this can be an interesting option for XWayland?
- Look, my setup works for me. Just add an option to reenable spacebar heating.
- The Wayland people were right about everything
by Levitating
0 subcomment
- No active development in the last 4 months?
- It's christmas and not april fools!
by fleroviumna
0 subcomment
- [dead]
by maximgeorge
0 subcomment
- [dead]
- [flagged]
by sergiotapia
2 subcomments
- This is a really really bad name. There's already a Phoenix that is well known in tech. https://phoenixframework.org/
OP if you're the author I suggest you rename to avoid confusion. Don't name it Rails either haha!
Hacker News