This is pretty cool - especially that it's at the point where it can be used with a real window manager.
I'm curious why multiple screens is considered legacy baggage and thus out of scope, given how common multiple monitor setups are these days. I also have zero familiarity with X internals, so don't know if multiple monitor support is a horror show that'd be miserable to support.
I compiled it on Debian 13 and it works with XFCE4. Granted, things are a bit squirrely until you disable the compositor. No luck getting it to play nicely with LightDM so I ended up launching it from a TTY. This was on an AMD mini PC I had lying around the studio.
> dropping legacy baggage (multiple screens[...]
Looked nice, but crossed it off as soon as I saw that, as I'm working on a project currently that uses many screens. Can't just call a thing legacy because you and the people you directly know aren't using it.
It is kind of ironic that all the would be X successors waiting until Wayland took over before appearing.
Something like XLibre or Phoenix would have been taken very seriously 5 years ago.
I really wish people gave a damn about the “gui over the network” problem x11 solves. Wayland drops this use case entirely so we’re pretty much universally stuck with vnc. Microsoft rdp is a great solution for this in windows land.
Love seeing this. I'd be interested in seeing how much more could be shaved off by doing things like offering an xcb/xlib shim that moves more functionality to the client side (e.g. server-side font support are trivial to move client-side) as a means to deprecate features on the server side that most modern X11 apps don't use anyway.
The wayland.fyi people might have a point on the whole X11 vs Wayland thing [0].
At least it is worth reading.
- [0] https://wayland.fyi/
Projects like this really need to disclose how much ai was used. Otherwise my default assumption is it’s slop, which would be a bummer if someone carefully crafted this with some light ai assistance.
Why it "can't" work under nvidia?
Xorg worked under nvidias for years.
[dead]
[dead]
Yet another vide-coded, MIT-licenced Rust rewrite, yawn.
Why? Wayland hasn't been smooth sailing by any stretch but it's still time to let X die.
Also this is slop.
I'm really just tired of all these "projects" that in the end just turn out to be Claude.
There is no need to put this code on GitHub. Everyone with an API key can achieve the same if you hand them the prompt.
This is like committing build artifacts to version control.
On top it's such a lame idea. "What if rewrite in rust applied to X server". Fits on a napkin. Man what a nothingburger :(
Concerning the name "Yserver": be aware that there also existed (the implementation is still available for download) the "Y Window System"
> https://www.y-windows.org/
by Mark Thomas as an experimental sucessor of the "X Window System" (its development has been cancelled for a long time; the latest release that is available on this website is from 2004).
The German Wikipedia still mentions the "Y Window System":
> https://de.wikipedia.org/w/index.php?title=X_Window_System&o...