zlacker

[return to "Arcan-A12: Weaving a Different Web"]
1. stopli+QG[view] [source] 2026-02-04 18:53:10
>>ingeni+(OP)
Arcan scratches the same kind of itch that nix does for me but for the gnu/linux graphics stack and everything that has to interact with it.
◧◩
2. sho_hn+EK[view] [source] 2026-02-04 19:09:03
>>stopli+QG
I remain confused by Arcan, even having looked into it a few times over the years.

Ultimately it appears to be software with more fans than productive users.

◧◩◪
3. somat+f71[view] [source] 2026-02-04 20:54:31
>>sho_hn+EK
Arcan is a display server, in the category of X, wayland or rio

The focus of arcan is to make the final display target super flexible.

So X was designed to be network agnostic, the programmer could use the same protocol and depending on how the end user had it configured it could be displaying on the same machine as the program via local shared objects or on a remote machine via tcp. But X never was able to dynamically transition between the two, there was no way for X to move a window from one machine to another. This is a core goal of the arcan project. I think the thing that gets people confused is along the way there is also a lot of adjacent experimentation in really wild window managers and control scripts. That is, what crazy things can you do once you have this amazing window location flexibility.

[go to top]