From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: OT: Fighting bit rot
Date: Tue, 8 Jan 2013 10:42:08 -0500 [thread overview]
Message-ID: <CA+czFiDcxftrt43M2CDtwDN6nKyNo4Rkp6t4U08k9YftRbp5=g@mail.gmail.com> (raw)
In-Reply-To: <kche0o$8g1$1@ger.gmane.org>
On Tue, Jan 8, 2013 at 10:29 AM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> On 2013-01-08, Florian Philipp <lists@binarywings.net> wrote:
>> Am 08.01.2013 00:20, schrieb Alan McKinnon:
>>> On Mon, 07 Jan 2013 21:11:35 +0100
>>> Florian Philipp <lists@binarywings.net> wrote:
>>>
>>>> Hi list!
>>>>
>>>> I have a use case where I am seriously concerned about bit rot [1]
>>>> and I thought it might be a good idea to start looking for it in my
>>>> own private stuff, too.
>> [...]
>>>> [1] http://en.wikipedia.org/wiki/Bit_rot
>>>>
>>>> Regards,
>>>> Florian Philipp
>>>>
>>>
>>> You are using a very peculiar definition of bitrot.
>>>
>>> "bits" do not "rot", they are not apples in a barrel. Bitrot usually
>>> refers to code that goes unmaintained and no longer works in the
>>> system it was installed. What definition are you using?
>>
>> That's why I referred to wikipedia, not the jargon file ;-)
>
> The wikipedia page to which you refer has _two_ definitions. The
> "uncommon" on you're using:
>
> http://en.wikipedia.org/wiki/Bit_rot#Decay_of_storage_media
>
> and the the common one:
>
> http://en.wikipedia.org/wiki/Bit_rot#Problems_with_software
>
> I've heard the term "bit rot" for decades, but I've never heard the
> "decay of storage media" usage. It's always referred to unmaintained
> code that no longer words because of changes to tools or the
> surrounding environment.
Frankly, I'd heard of bitrot first as applying to decay of storage
media. But this was back when your average storage media decay
(floppies and early hard disks) was expected to happen within months,
if not weeks.
The term's applying to software utility being damaged by assumptions
about its platform is a far, far newer application of the term. I
still think of "crappy media and errors in transmission" before I
think of platform compatibility decay.
--
:wq
next prev parent reply other threads:[~2013-01-08 15:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 20:11 [gentoo-user] OT: Fighting bit rot Florian Philipp
2013-01-07 21:07 ` Paul Hartman
2013-01-07 22:05 ` Florian Philipp
2013-01-07 21:33 ` Michael Mol
2013-01-07 22:10 ` Florian Philipp
2013-01-07 23:20 ` Alan McKinnon
2013-01-08 7:27 ` Florian Philipp
2013-01-08 7:55 ` Alan McKinnon
2013-01-08 16:16 ` Florian Philipp
2013-01-08 16:42 ` Alan McKinnon
2013-01-08 17:41 ` Pandu Poluan
2013-01-08 19:02 ` Florian Philipp
2013-01-09 2:55 ` Pandu Poluan
2013-01-08 19:53 ` [gentoo-user] " Grant Edwards
2013-01-08 20:30 ` Florian Philipp
2013-01-08 21:45 ` Alan McKinnon
2013-01-08 22:15 ` Grant Edwards
2013-01-08 23:37 ` Alan McKinnon
2013-01-09 2:47 ` Grant Edwards
2013-01-09 8:31 ` Alan McKinnon
2013-01-09 14:48 ` Grant Edwards
2013-01-09 15:36 ` Holger Hoffstaette
2013-01-09 16:32 ` Pandu Poluan
2013-01-09 16:42 ` Grant Edwards
2013-01-09 20:52 ` Alan McKinnon
2013-01-09 20:53 ` Alan McKinnon
2013-01-08 15:29 ` Grant Edwards
2013-01-08 15:42 ` Michael Mol [this message]
2013-01-08 16:28 ` Florian Philipp
2013-01-08 17:35 ` [gentoo-user] " Volker Armin Hemmann
2013-01-08 19:06 ` Florian Philipp
2013-01-08 20:57 ` Joshua Murphy
2013-01-08 21:49 ` Alan McKinnon
2013-01-08 19:11 ` [gentoo-user] " James
2013-01-09 4:40 ` Volker Armin Hemmann
2013-01-09 15:17 ` walt
2013-01-09 18:57 ` Volker Armin Hemmann
2013-01-09 0:12 ` [gentoo-user] " Randy Barlow
2013-01-07 23:31 ` William Kenworthy
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='CA+czFiDcxftrt43M2CDtwDN6nKyNo4Rkp6t4U08k9YftRbp5=g@mail.gmail.com' \
--to=mikemol@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