From: arnold@skeeve.com
To: tuhs@tuhs.org, norman@oclsc.org
Subject: Re: [TUHS] Whither Usenix [was How To Kill A Technical Conference]
Date: Mon, 05 Apr 2021 12:31:20 -0600 [thread overview]
Message-ID: <202104051831.135IVKJS013930@freefriends.org> (raw)
In-Reply-To: <20210405162050.DBFDD640CB7@lignose.oclsc.org>
norman@oclsc.org (Norman Wilson) wrote:
> Arnold:
>
> But for several years now I have been increasingly dissatisfied with the
> research nature of most of the articles. Very few of them are actually
> useful (or even interesting) to me in a day-to-day sense.
>
> ===
>
> I guess it depends on your interests, and also on what you look at.
Yes, exactly. For me, Usenix provides little added value. I had
been debating leaving Usenix for several years already; the move
to soft copy ;login: clinched it for me. I'm not happy about it,
but I had to recognize my personal reality.
> Either way I think what USENIX does is worth while.
I agree. For example, I would not like to see Usenix disappear.
But I no longer am getting value for my membership dollars.
So, not a value judgement on Usenix as a whole, merely a statement
of my personal situation.
Arnold
next prev parent reply other threads:[~2021-04-05 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 16:20 Norman Wilson
2021-04-05 18:31 ` arnold [this message]
2021-04-06 5:54 ` Dave Horsfall
2021-04-06 6:01 ` Warner Losh
-- strict thread matches above, loose matches on Subject: below --
2021-04-01 14:50 [TUHS] Zombified SCO comes back from the dead, brings trial back to life against IBM Josh Good
2021-04-01 15:12 ` Warner Losh
2021-04-02 3:52 ` Wesley Parish
2021-04-04 2:46 ` Adam Thornton
2021-04-04 2:50 ` Adam Thornton
2021-04-04 5:29 ` [TUHS] How to Kill a Technical Conference (was: Zombified SCO comes back from the dead, brings trial back to life against IBM) G. Branden Robinson
2021-04-04 18:22 ` Clem Cole
2021-04-05 0:36 ` John Cowan
2021-04-05 7:48 ` [TUHS] Whither Usenix [was How To Kill A Technical Conference] arnold
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=202104051831.135IVKJS013930@freefriends.org \
--to=arnold@skeeve.com \
--cc=norman@oclsc.org \
--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).