public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Barry Schwartz <chemoelectric@chemoelectric.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Wayland and X-Window
Date: Sat, 19 Oct 2013 10:11:40 -0500	[thread overview]
Message-ID: <20131019151140.GA29488@crud> (raw)
In-Reply-To: <pan$ce544$4845679f$dfc275d9$ba5f4223@cox.net>

Duncan <1i5t5.duncan@cox.net> skribis:
> * In practice, much like the story we're seeing play out with systemd, 
> while xorg will remain around for some time and existing features will 
> probably continue to work in general as they always have, just as the 
> various alternative init systems are, it's likely many of the newer 
> features will only function as designed and/or will only be "supported" 
> on wayland.  And, as we're seeing with gnome and systemd already, I 
> predict they'll be dropping support for anything but wayland/weston 
> sooner rather than later, basically leaving the non-linux platforms and 
> those who aren't ready to make that change out in the cold, at least as 
> far as gnome goes.  Just as we're seeing with systemd, distros such as 
> gentoo who want to continue to support gnome with xorg will be able to do 
> so for a couple releases, but at some point upstream gnome's code base 
> will have diverged significantly enough that it'll force distros into 
> only supporting wayland/weston for their gnome users, as well.

The between the lines here is that you have certain people for whom
backwards compatibility is an afterthought, stability is ‘not fun’,
and competition of different approaches is to be squelched by peer
pressure. All these points are really, to me, arguments for getting
away from Gnome as soon as one can (which I have already done, and
also switched to eudev).


  parent reply	other threads:[~2013-10-19 15:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19  1:36 [gentoo-amd64] Wayland and X-Window Frank Peters
2013-10-19  7:11 ` [gentoo-amd64] " Duncan
2013-10-19 15:10   ` David Klann
2013-10-19 15:38     ` Duncan
2013-10-19 15:11   ` Barry Schwartz [this message]
2013-10-19 16:09     ` Duncan
2013-10-19 16:24       ` Barry Schwartz
2013-10-19 17:35         ` Frank Peters
2013-10-20  0:15           ` Barry Schwartz
2013-10-20 14:15             ` Paul Jewell
2013-10-21  3:09               ` Barry Schwartz
2013-10-21 12:18                 ` Rich Freeman
2013-10-19 17:01   ` Frank Peters
2013-10-20 13:36     ` Duncan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131019151140.GA29488@crud \
    --to=chemoelectric@chemoelectric.org \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox