The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Anyone ever heard of teaching a case study of Initial Unix?
Date: Fri, 5 Jul 2024 09:20:52 -0400	[thread overview]
Message-ID: <CAKH6PiV3qg8cjPxS3kj+k+kHwL0tsTC4T65B71cjKFLvbA5k0w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

> Peter J Denning in 2008 wrote about reforming CACM in 1982/83. [ extract
at end ]
>  <https://cacm.acm.org/opinion/dja-vu-all-over-again/>

That "accomplishment" drove me away from the ACM. I hope the following
explanation does not set off yet another long tangential discussion.

The CACM had been the prime benefit of ACM membership. It carried generally
accessible technical content across the whole spectrum of computing. The
"Journal for all Members" (JAM) reform resulted in such content being
thinly spread over several journals. To get the perspective that CACM had
offered, one would have had to subscribe to and winnow a mountain of
specialst literature--assuming the editors of these journals would accept
some ACM-style articles.

I had been an active member of ACM, having serving as associate editor of
three journals, member of the publications planning committee, national
lecturer, and Turing-Award chairman. When the JAM reform cut off my window
into the field at large, I quit the whole organization.

With the advent of WWW, the ACM Digital Library overcame the need to
subscribe to multiple journals for wide coverage. Fortunately I had
institutional acess to that. I rejoined ACM only after its decision to
allow free access to all 20th century content in the DL. This
public-spirited action more than atoned for the damage of the JAM reform
and warranted my support.

I have been happy to find that the current CACM carries one important
technical article in each issue and a couple of interesting columnists
among the generally insipid JAM content. And I am pleased by the news that
ACM will soon also give open access to most 21st-century content.

Doug

[-- Attachment #2: Type: text/html, Size: 2054 bytes --]

             reply	other threads:[~2024-07-05 13:21 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-05 13:20 Douglas McIlroy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-03 14:46 [TUHS] " Norman Wilson
2024-07-03 15:45 ` [TUHS] " Clem Cole
2024-07-03 15:52   ` Clem Cole
2024-07-03 16:12   ` Chet Ramey via TUHS
2024-07-03  4:51 [TUHS] " sjenkin
2024-07-03  5:02 ` [TUHS] " Al Kossow
2024-07-03  6:46   ` arnold
2024-07-03 14:04   ` Clem Cole
2024-07-03 15:22     ` Theodore Ts'o
2024-07-03 15:36       ` Larry McVoy
2024-07-03 14:59   ` Marc Rochkind
2024-07-03 23:35     ` G. Branden Robinson
2024-07-04 13:00       ` Marc Donner
2024-07-03  9:04 ` A. P. Garcia
2024-07-03 15:17 ` Vincenzo Nicosia
2024-07-03 15:35   ` Marc Donner
2024-07-03 17:39     ` Jon Forrest
2024-07-03 17:49       ` segaloco via TUHS
2024-07-03 18:16         ` Erik E. Fair
2024-07-03 19:58         ` Rich Salz
2024-07-03 23:15     ` Dave Horsfall
2024-07-03 23:23       ` Marc Donner
2024-07-03 23:26       ` Rik Farrow
2024-07-04 23:26         ` Dave Horsfall
2024-07-03 15:37   ` Al Kossow
2024-07-03 16:01     ` Al Kossow
2024-07-03 16:05       ` Warner Losh
2024-07-03 23:29   ` Marc Rochkind
2024-07-03 23:50     ` G. Branden Robinson
2024-07-04  8:23     ` Vincenzo Nicosia
2024-07-04 20:34       ` Nevin Liber
2024-07-04 20:44         ` segaloco via TUHS
2024-07-04 21:41           ` sjenkin
     [not found]             ` <7AC009E5-C985-44AD-A55E-E0BFC05CDD31@serissa.com>
2024-07-05  9:41               ` Steve Jenkin
2024-07-05  9:47               ` Steve Jenkin
2024-07-05  0:03         ` Stuff Received
2024-07-05  0:12           ` Larry McVoy
2024-07-05  2:24             ` Adam Thornton
2024-07-05  2:42               ` Bakul Shah via TUHS
2024-07-05  7:13                 ` arnold
2024-07-05  7:42                   ` Bakul Shah via TUHS
2024-07-05  8:20                     ` arnold
2024-07-05  8:52                       ` G. Branden Robinson
2024-07-05  7:36               ` Dave Horsfall
2024-07-05 10:18                 ` Peter Yardley
2024-07-07 22:00                   ` Dave Horsfall
2024-07-07 23:28                     ` Brad Spencer
2024-07-08  6:17                       ` Dave Horsfall
2024-07-08  6:27                       ` Lars Brinkhoff
2024-07-08  6:51                         ` Dave Horsfall
2024-07-08  9:36                           ` David Arnold
2024-07-08  6:59                       ` arnold
2024-07-08 13:22                         ` Larry McVoy
2024-07-08 15:37                           ` Al Kossow
2024-07-08 17:22                             ` Tom Lyon
2024-07-08 17:04                           ` Clem Cole
2024-07-08 15:28                         ` Brad Spencer
2024-07-08 15:33                           ` Al Kossow
2024-07-08  0:21                     ` John Levine
2024-07-08  0:35                       ` Dave Horsfall
2024-07-08 12:29                     ` Peter Yardley
2024-07-05 16:40                 ` Jon Steinhart
2024-07-06 13:20                   ` Dave Horsfall
2024-07-05  0:08       ` Marc Rochkind
2024-07-04  1:53 ` John Levine
2024-07-04  2:59   ` segaloco via TUHS
2024-07-04  6:53     ` Rob Pike
2024-07-04 15:07       ` 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=CAKH6PiV3qg8cjPxS3kj+k+kHwL0tsTC4T65B71cjKFLvbA5k0w@mail.gmail.com \
    --to=douglas.mcilroy@dartmouth.edu \
    --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).