The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Alan Coopersmith <alan.coopersmith@oracle.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: ATC'25 is the last ATC?
Date: Tue, 6 May 2025 19:55:26 -0700	[thread overview]
Message-ID: <20250507025526.GC17185@mcvoy.com> (raw)
In-Reply-To: <2e5ee2ad-84b5-4aed-9eda-c9ee7a55e26f@oracle.com>

On Tue, May 06, 2025 at 07:11:26PM -0700, Alan Coopersmith via TUHS wrote:
> On 5/6/25 15:52, Dan Cross wrote:
> >I just heard that, after ATC'25, USENIX will be sunsetting the annual
> >technical conference: this will apparently be the last one.
> >
> >I can't find any reference for it, though, and the web site mentions
> >ATC'26 in Seattle?
> 
> See https://www.usenix.org/blog/usenix-atc-announcement

I might regret this in the morning but I'd like to share when Usenix
ceased to matter to me.  I was the program committee chair for the 1999
Linux Expo which was a Usenix alternative.

Before I go on, there is some back story.  I reviewed papers for Usenix
a bunch.  One of the best papers I ever reviewed is this one:

http://www.mcvoy.com/lm/papers/rtlmanifesto.pdf

It got rejected, not on merit, but because Victor was not in the club, he
was an unknown.  Rob Gingell, someone I feared and respected, said he 
rejected it "because it wasn't posix".  Not Rob's best day, the whole
point was posix couldn't do what Victor did.  Read that paper, it did
real time right, nobody else has come close to do real time and time
sharing.  They fight each other.

In 1999 when I was going to that conference, Ellie reached out to me
and begged me to bring Linux to Usenix.  She said I could have whatever
I wanted, on the program committee for life, whatever I wanted.

I asked for blind peer reviews.  She said no.

I used to love Usenix, I've written papers that were published there,
but Usenix is dead to me.  They did it to themselves.
-- 
---
Larry McVoy           Retired to fishing          http://www.mcvoy.com/lm/boat

  reply	other threads:[~2025-05-07  2:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 22:52 [TUHS] " Dan Cross
2025-05-07  2:11 ` [TUHS] " Alan Coopersmith via TUHS
2025-05-07  2:55   ` Larry McVoy [this message]
     [not found]     ` <20250514133336.GD9943@mit.edu>
     [not found]       ` <20250514145452.GE17185@mcvoy.com>
2025-05-14 19:16         ` Alan Coopersmith via TUHS
     [not found]         ` <43a0a867-522a-f953-c6c5-9be9383a6bd9@riddermarkfarm.ca>
2025-05-15 21:33           ` Rod Bartlett via TUHS

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=20250507025526.GC17185@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=alan.coopersmith@oracle.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).