From: Luther Johnson <luther.johnson@makerlisp.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: SCCS roach motel
Date: Fri, 13 Dec 2024 17:37:01 -0700 [thread overview]
Message-ID: <3f27aaff-37e3-598c-62fa-3bf0997bf057@makerlisp.com> (raw)
In-Reply-To: <CAOkr1zWVtNgaOgkRU_i=QDnDfJg8O1aJBU4Qa2fhBgqexop1cQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]
When I just read your quote, this joke came to mind:
What's the difference between a public library and a software library ?
At the public library, everyone wants to check things out, but no-one
ever wants to return anything. In a source code library, everyone wants
to put something in the library, but programmers rarely want to take
anything in it out, and use it.
Maybe it doesn't seem as funny as the first time I heard it, but I think
it's still true. Maybe a similar thought is behind the 'source motel' quote.
On 12/13/2024 09:52 AM, Marc Rochkind wrote:
> IEEE Transactions on Software Engineering has asked me to write a
> retrospective on the influence of SCCS over the last 50 years, as my
> SCCS paper was published in 1975. They consider it one of the most
> influential papers from TSE's first decade.
>
> There's a funny quote from Ken Thompson that circulates from time-to-time:
>
> "SCCS, the source motel! Programs check in and never check out!"
>
> But nobody seems to know what it means exactly. As part of my
> research, I asked Ken what the quote meant, sunce I wanted to include
> it. He explained that it refers to SCCS storing binary data in its
> repository file, preventing UNIX text tools from operating on the file.
>
> Of course, this is only one of SCCS's many weaknesses. If you have
> anything funny about any of the others, post it here. I already have
> all the boring usual stuff (e.g., long-term locks, file-oriented, no
> merging).
>
> Marc Rochkind
> mrochkind.com <http://mrochkind.com>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2625 bytes --]
next prev parent reply other threads:[~2024-12-14 0:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 16:52 [TUHS] " Marc Rochkind
[not found] ` <A6DE3D0A-8ED7-4E82-87CF-F2BC7AE11761@seiden.com>
2024-12-13 17:58 ` [TUHS] " Marc Rochkind
2024-12-13 21:09 ` Dan Cross
2024-12-14 1:11 ` Marc Rochkind
2024-12-14 1:27 ` Dan Cross
2024-12-14 1:39 ` Larry McVoy
2024-12-14 6:20 ` Marc Rochkind
2024-12-14 1:38 ` Larry McVoy
2024-12-13 18:06 ` Larry McVoy
2024-12-13 18:32 ` Marc Rochkind
2024-12-13 18:39 ` Marc Rochkind
2024-12-13 18:49 ` Larry McVoy
2024-12-13 18:55 ` Larry McVoy
2024-12-13 19:55 ` Henry Bent
2024-12-14 18:29 ` arnold
2024-12-14 18:59 ` Larry McVoy
2024-12-13 21:46 ` Clem Cole
2024-12-13 21:22 ` Rob Pike
2024-12-13 21:27 ` Rob Pike
2024-12-13 21:37 ` Aron Insinga
2024-12-13 21:40 ` Aron Insinga
2024-12-14 0:37 ` Luther Johnson [this message]
2024-12-13 22:33 Norman Wilson
2024-12-17 0:21 ` andrew
2024-12-13 22:57 Norman Wilson
2024-12-13 23:19 ` Larry McVoy
2024-12-13 23:38 ` Warner Losh
2024-12-14 0:53 ` Larry McVoy
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=3f27aaff-37e3-598c-62fa-3bf0997bf057@makerlisp.com \
--to=luther.johnson@makerlisp.com \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).