Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.windows.x
Subject: Re: Wayland Is Coming
Date: Sat, 11 May 2024 03:25:25 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 24
Message-ID: <v1mof5$1qt05$2@dont-email.me>
References: <v1f0ja$3ot7f$2@dont-email.me>
	<v1lh0c$215e$1@nnrp.usenet.blueworldhosting.com>
	<v1mkia$1ft4i$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 11 May 2024 05:25:26 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="35cd064a09c147145ba6425e37519214";
	logging-data="1930245"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+LsQknS5zlzJQ4aczpgdQn"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:RYCRGNlI93/rYXtHbUmN0PZE8Go=
Bytes: 2050

On Sat, 11 May 2024 02:18:51 -0000 (UTC), Alastair Hogge wrote:

> Was unfortunate on the license choice tho.

I thought from your statement that they had picked something non-Free, but 
it’s only LGPL! Nothing wrong with that.

On the technical side, CORBA seems like an unfortunate choice for IPC. Of 
course this was before D-Bus became the Free Desktop standard.

> I would love to know why Wayland, or how it came to be, to push the 
> complexity of compositing further out from the Display Server into the 
> client, like the window manager. Why is the complexity moved up the 
> software stack, instead of down, into the core.

The philosophy at the lower layers of any software stack should be 
“mechanism, not policy”. The lower layers provide the flexibility for the 
higher layers to build on, so the latter can be configured however the 
user/admin wants.

> On FreeBSD, none of my AMD, or Intel GPUs can handle switching to the
> vty from X, or even display suspension ...

How come? Linux systems solved this problem years ago.