Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #229948
| From | Nicolas George <george@nsup.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Future of X, fvwm and wayland |
| Date | 2020-12-23 17:40 +0100 |
| Message-ID | <Bpfl8-53n-17@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <BouYW-z5-9@gated-at.bofh.it> <Bovii-Fn-13@gated-at.bofh.it> <Box0K-1Jm-7@gated-at.bofh.it> <Boxk5-1PX-1@gated-at.bofh.it> <Boyga-2oJ-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Reco (12020-12-21): > You're right. Xorg is a server, any window manager on top of it is > merely an X client (a special one, but an interchangeable client). > Wayland is not a server, it's a set of protocols. An implementation of > these protocols inherently provides a set of functions that are provided > by window manager on top of X, X itself, panel, copy-paste to name a > few. > Running a window manager in Xwayland is theoretically possible, but > practically it'll be worthless. Being a server has nothing to do with allowing window managers or not, it is just a kind of RPC; X11 is a protocol, but it is designed like an API. The X11 Window system itself is very bare: windows are just plain rectangles. The window manager is just an application like many others that takes upon itself to add decorations on windows and move them around. Nothing would prevent the same UI design with a non-client-server API design. But obviously Wayland chose otherwise. (Which is not surprising, since Wayland comes from Freedesktop, and Freedesktop are awed by Apple's policy of restricting user choice for the good of the user.) Regards, -- Nicolas George
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Future of X, fvwm and wayland Kamil Jońca <kjonca@poczta.onet.pl> - 2020-12-20 18:50 +0100
Re: Future of X, fvwm and wayland Greg Wooledge <wooledg@eeg.ccf.org> - 2020-12-21 14:20 +0100
Re: Future of X, fvwm and wayland Tixy <tixy@yxit.co.uk> - 2020-12-21 16:10 +0100
Re: Future of X, fvwm and wayland Tixy <tixy@yxit.co.uk> - 2020-12-21 16:30 +0100
Re: Future of X, fvwm and wayland Stefan Monnier <monnier@iro.umontreal.ca> - 2020-12-21 18:20 +0100
Re: Future of X, fvwm and wayland Greg Wooledge <wooledg@eeg.ccf.org> - 2020-12-21 18:40 +0100
Re: Future of X, fvwm and wayland Reco <recoverym4n@enotuniq.net> - 2020-12-21 19:40 +0100
Re: Future of X, fvwm and wayland Nicolas George <george@nsup.org> - 2020-12-23 17:40 +0100
Re: Future of X, fvwm and wayland Jude DaShiell <jdashiel@panix.com> - 2020-12-22 02:30 +0100
Re: Future of X, fvwm and wayland Greg Wooledge <wooledg@eeg.ccf.org> - 2020-12-22 14:10 +0100
Re: Future of X, fvwm and wayland Javier Barroso <javibarroso@gmail.com> - 2020-12-22 14:20 +0100
Re: Future of X, fvwm and wayland Nicolas George <george@nsup.org> - 2020-12-21 18:40 +0100
csiph-web