public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: amarok fade down
Date: Sun, 5 Feb 2012 21:42:23 +0200	[thread overview]
Message-ID: <20120205214223.1611064a@khamul.example.com> (raw)
In-Reply-To: <CADPrc80RQiOFYAs3OS++Q82voauwJw9Aw6mWO9xJTmgPjttGkA@mail.gmail.com>

On Sun, 5 Feb 2012 11:18:41 -0600
Canek Peláez Valdés <caneko@gmail.com> wrote:

> On Sun, Feb 5, 2012 at 11:01 AM, Nikos Chantziaras <realnc@arcor.de>
> wrote:
> > On 02/05/2012 06:02 PM, Canek Peláez Valdés wrote:
> >>
> >> In short, both GStreamer and VLC can do anything that Xine do, and
> >> they probably do it better. If something is not working properly,
> >> it probably is a problem with the integration with KDE (via
> >> phonon). This should be fixed by them in a short time.
> >
> >
> > Stuff doesn't get fixed. Instead, new bugs keep piling up. KDE is
> > going down the drain. If the trend continues, KDE 4.9 will be of
> > the same stability as 4.0.
> 
> When Totem (the GNOME media player) changed its backend from Xine to
> GStreamer (way back in 2004 or 2005), it took a while to fix all the
> regressions. 

Remember the first release of Ubuntu (warty)? Remember how it shipped
with Totem + Gstreamer? Remember the gigantic amount of flak
Shuttleworth got from the "oh noes! you change stuff!" crowd?

It looks like he's now been vindicated for several years already, as
gstreamer does work nicely. True, his reasons for using it then were
licensing reasons, not so much technical ones, but it's still nice to
see projects start off with somewhat patchy support for "stuff" and
gradually improve to supporting almost everything.


> But eventually it got really, really nice. And back then
> GStreamer was not as nice as it is now. Have a little faith in the
> devs and do your part (fill bugs, use the betas, follow upstream
> closely), and in the end everything sorta kinda maybe will work out.
> 
> Sixteen years using Linux as my exclusive OS has taught me that's the
> only sane way to see things. The alternative is to get angry a lot and
> grow ulcers and maybe cancer.
> 
> Regards.



-- 
Alan McKinnnon
alan.mckinnon@gmail.com




  reply	other threads:[~2012-02-05 19:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-04 15:04 [gentoo-user] amarok fade down Stephane Guedon
2012-02-04 16:52 ` [gentoo-user] " Nikos Chantziaras
2012-02-05 13:40   ` Stephane Guedon
2012-02-05 16:02     ` Canek Peláez Valdés
2012-02-05 17:01       ` Nikos Chantziaras
2012-02-05 17:18         ` Canek Peláez Valdés
2012-02-05 19:42           ` Alan McKinnon [this message]
2012-02-05 17:19         ` James Broadhead
2012-02-05 17:20           ` James Broadhead
2012-02-05 19:37       ` Alan McKinnon

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=20120205214223.1611064a@khamul.example.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@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