Re: Collaboration on standard Wayland protocol extensions
- From: Daniel Stone <daniel fooishbar org>
- To: Drew DeVault <sir cmpwn com>
- Cc: "Kwin, NET API, kwin styles API, kwin modules API" <kwin kde org>, "wayland-devel lists freedesktop org" <wayland-devel lists freedesktop org>, desktop-devel-list gnome org, Carsten Haitzler <raster rasterman com>
- Subject: Re: Collaboration on standard Wayland protocol extensions
- Date: Tue, 29 Mar 2016 13:18:11 +0100
Hi,
On 29 March 2016 at 13:11, Drew DeVault <sir cmpwn com> wrote:
or just have the compositor "work" without needing scripts and users to have to
learn how to write them. :)
Never gonna happen, man. There's no way you can foresee and code for
everyone's needs. I'm catching on to this point you're heading towards,
though: e doesn't intend to suit everyone's needs.
If a compositor implementation can never be sufficient to express
peoples' needs, how could an arbitrary protocol be better? Same
complexity problem.
(And, as far as the 'but what if a compositor implementation isn't
good' argument goes - don't use bad compositors.)
Cheers,
Daniel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]