From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: Re: Re: x86_64 optimization patches for glibc.
Date: Tue, 02 Aug 2005 03:21:45 -0700 [thread overview]
Message-ID: <pan.2005.08.02.10.21.44.643464@cox.net> (raw)
In-Reply-To: ac342b0a0508011003686becfc@mail.gmail.com
Karol Krizka posted <ac342b0a0508011003686becfc@mail.gmail.com>, excerpted
below, on Mon, 01 Aug 2005 10:03:13 -0700:
>> Never-the-less, I added the strings patch here, and have the new KDE 3.4.2
>> stuff at least, compiled against it... Computing is my hobby; if I
>> wanted something that would predictably "just work", I'd be doing TiVos or
>> the like! Much of the fun is the occasional breakage in mysterious ways,
>> never knowing quite when it'll happen, and the challenge of figuring out
>> how to get back to a working system, again!
>>
> So if you wanted something to just work you would be running Linux on
> TiVo? I think a intel computer would be better for that...
> Never-the-less, I added the strings patch here, and have the new KDE 3.4.2
> stuff at least, compiled against it... Computing is my hobby; if I
> wanted something that would predictably "just work", I'd be doing TiVos or
> the like! Much of the fun is the occasional breakage in mysterious ways,
> never knowing quite when it'll happen, and the challenge of figuring out
> how to get back to a working system, again!
>
So if you wanted something to just work you would be running Linux on
TiVo? I think a intel computer would be better for that...
No... perhaps I didn't choose a far out enough example. I usually choose
a refrigerator or TV instead... The point is, if I wanted something that
predictably "just worked", computing wouldn't be my hobby in the /first/
place, I'd have chosen something better known for its "just working"
qualities.
In point of fact, before I got my first PC (in fact, the /only/ whole PC I
ever got, a 486sx25 w/ the CPU soldered to the mobo, 4 meg RAM, and a 130
meg hard drive -- I just counted myself lucky to get a 486 over a 386), I
had two VCRs hooked up to my TV, such that I could watch previous shows
while recording the current nite's shows, allowing me to FF over the
commercials. That, and I could rent movies and record them to the second
VCR while playing them from the first. Interactivity was pretty much
limited to that FF button -- and hitting back when I overshot a bit. Now,
I don't even own a TV (other than a tiny 2.5" TFT version, bought back in
the day..., that I have around somewhere, don't even know where...), as
I've grown to despise the lack of control one has over a TV program, and
the fact that the programmers must cater to their paying customers, the
advertisers, which in turn are happiest with the zombies easiest
programmed to buy their warez even when they are twice the cost or more of
the generic brand and even when they don't need them and can't really
afford them. Thus, there's actually a DIS-incentive to program for the
discerning intellect -- those that actually /like/ to think, and can't be
so easily programmed to buy expensive stuff they don't need.
So... I've switched to a more interactive and intellectually rewarding
hobby, computers, and enjoy the challenges they sometimes present. I
simply chose TiVos as the example above, because that'd be the modern
equivalent of the VCRs I was using before I got into computers. While
personally significant, that choice of example was obviously less than
clear to those who have no way of knowing my history and who have a
different one of their own, and the usual TV or refrigerator example would
have been rather more effective at making my point.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-02 10:25 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 14:48 [gentoo-amd64] x86_64 optimization patches for glibc Simon Strandman
2005-07-23 16:36 ` Allan Wang
2005-07-23 17:08 ` Simon Strandman
2005-07-23 17:30 ` Allan Wang
2005-07-23 18:11 ` Jared Lindsay
2005-07-23 18:19 ` Allan Wang
2005-07-27 10:09 ` netpython
2005-07-27 16:11 ` [gentoo-amd64] " Duncan
2005-07-23 18:44 ` [gentoo-amd64] " Brian Litzinger
2005-07-25 22:24 ` Luke-Jr
2005-07-25 22:38 ` Olivier Crete
2005-07-26 15:40 ` Luke-Jr
2005-07-26 16:50 ` [gentoo-amd64] " Duncan
2005-07-26 17:02 ` Raffaele BELARDI
2005-07-26 17:49 ` Michael Edwards
2005-07-26 18:42 ` [gentoo-amd64] " Duncan
2005-07-27 0:05 ` [gentoo-amd64] " Sami Samhuri
2005-07-27 2:50 ` Matt Randolph
2005-07-26 2:54 ` [gentoo-amd64] " Brian Litzinger
2005-07-23 16:39 ` Sean Johnson
2005-07-23 22:15 ` Matt Randolph
2005-07-23 22:36 ` Matt Randolph
2005-07-24 1:47 ` Sean Johnson
2005-07-24 3:36 ` Matt Randolph
2005-07-24 5:36 ` Ian McCulloch
2005-07-24 7:42 ` Jared Lindsay
2005-07-24 14:35 ` Simon Strandman
2005-07-24 18:13 ` Jared Lindsay
2005-07-25 20:08 ` Jeremy Huddleston
2005-07-25 21:34 ` Simon Strandman
2005-07-25 22:00 ` Jared Lindsay
2005-07-31 14:24 ` [gentoo-amd64] " Duncan
2005-07-31 14:56 ` Brian Hall
2005-07-31 16:23 ` [gentoo-amd64] " Duncan
2005-07-31 17:42 ` Ben Skeggs
2005-07-31 18:46 ` Jared Lindsay
2005-07-31 18:52 ` Nuitari
2005-08-01 13:51 ` [gentoo-amd64] " Duncan
2005-07-31 19:21 ` [gentoo-amd64] " Simon Strandman
2005-08-01 9:04 ` Jan Jitse Venselaar
2005-08-01 13:45 ` [gentoo-amd64] " Duncan
2005-08-01 17:03 ` Karol Krizka
2005-08-02 10:21 ` Duncan [this message]
2005-08-02 19:41 ` [gentoo-amd64] " Matt Randolph
2005-08-02 23:27 ` [gentoo-amd64] hijacked! :) television (was: x86_64 optimization patches for glibc.) Sami Samhuri
2005-08-04 2:28 ` Luke-Jr
2005-08-05 0:28 ` Sami Samhuri
2005-08-05 7:43 ` Arm Suwarnaratana
2005-08-09 10:29 ` [gentoo-amd64] Re: x86_64 optimization patches for glibc Simon Strandman
2005-07-26 17:40 ` [gentoo-amd64] " ardour
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=pan.2005.08.02.10.21.44.643464@cox.net \
--to=1i5t5.duncan@cox.net \
--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