public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] lazy gcc switching
Date: Wed, 21 Jul 2010 19:03:14 -0400	[thread overview]
Message-ID: <20100721230314.GB19975@waltdnes.org> (raw)
In-Reply-To: <4C475A51.4020702@gmail.com>

On Wed, Jul 21, 2010 at 03:36:33PM -0500, Dale wrote

> My last KDE upgrade made KDE a little faster here as well.  It won't be 
> as fast as e17 tho.  Since I upgraded gcc a little before that, I wasn't 
> sure if it was gcc building better code or KDE got rid of some garbage.  
> It is a little faster tho.
> 
> I suspect gcc.  When as larger programs ever got faster?  I'm sure they 
> added code to KDE, not taking code away.   ;-)

  I have a neutral attitude in the KDE/GNOME battle... the pox on both
your houses<g>.  I don't run desktops, I run applications.  KDE/GNOME
represent a lot of why I left Windows in the first place.

-- 
Walter Dnes <waltdnes@waltdnes.org>



  reply	other threads:[~2010-07-21 23:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21  8:53 [gentoo-user] lazy gcc switching fajfusio
2010-07-21  9:10 ` Alan McKinnon
2010-07-21 10:22   ` Dale
2010-07-21 15:49     ` Bill Longman
2010-07-21 19:39       ` Alan McKinnon
2010-07-21 20:36         ` Dale
2010-07-21 23:03           ` Walter Dnes [this message]
2010-07-21 22:18         ` Bill Longman
2010-07-21 23:08           ` Alan McKinnon
2010-07-22  0:03             ` Dale
2010-07-22  8:09               ` Alan McKinnon
2010-07-22 14:55                 ` Bill Longman
2010-07-22 19:49           ` [gentoo-user] " walt
2010-07-22 20:27             ` Grant Edwards
2010-07-22 21:04             ` Bill Longman
2010-07-22 21:32               ` walt
2010-07-22 21:54                 ` Grant Edwards
2010-07-23  7:28               ` 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=20100721230314.GB19975@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --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