From: Jon Steinhart <email@example.com>
To: TUHS main list <firstname.lastname@example.org>
Subject: Re: [TUHS] FYI: Internet Old Farts Club
Date: Sat, 29 Jan 2022 09:15:51 -0800 [thread overview]
Message-ID: <202201291715.20THFpLW2308457@darkstar.fourwinds.com> (raw)
Andy Kosela writes:
> On 1/29/22, Larry McVoy <email@example.com> wrote:
> > If we need another place for old farts to hang out, there are many.
> > I like groups.io, it's free for most stuff, it's super easy to be
> > a moderator, I moderate 12 groups there and am a member of a bunch
> > more. What they call groups, we would call an email list with a
> > bunch of knobs that help keep things sane.
> I can speak only for myself, but I love that TUHS/COFF mailing lists
> are still _the real_ mailing lists managed the old school way. I hate
> all those modern web 2.0 technologies with extremely bloated js stacks
> which you can only use if you have the latest version of Chrome. I am
> still using old Atari DOS, Amiga Workbench, MS-DOS/Win9x/WinXP and of
> course Linux/FreeBSD.
> This is probably one of the last places on the Internet that is still
> preserving one of its core ideas in the 80s/90s -- plain text
> communication. It has been slowly dying in the last 15 years. Text
> based Internet of the 80s and 90s has slowly been replaced by binary
> protocols and image based interaction with a computer.
> I still just love using text based protocols and command line and read
> it on a real CRT monitor in full screen text mode. We lost something
> when the world moved on.
> So please do not go anywhere....
I completely agree with you. Maybe one of the problems is the
book-burners opposed to CRT. Don't know if any of you have
ever run across this guy: http://unixsheikh.com/index.html
Seems to be a younger-ish person who seems to get it.
next prev parent reply other threads:[~2022-01-29 17:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 0:36 Rich Morin
2022-01-27 1:55 ` Jan Schaumann via TUHS
2022-01-29 1:59 ` Charles Anthony
2022-01-29 2:24 ` Theodore Y. Ts'o
2022-01-29 2:36 ` Larry McVoy
2022-01-29 8:48 ` Andy Kosela
2022-01-29 17:15 ` Jon Steinhart [this message]
2022-01-29 17:20 ` Seth J. Morabito
2022-02-01 2:12 ` Grant Taylor via TUHS
2022-02-01 2:21 ` Steve Nickolas
2022-02-01 2:23 ` Larry McVoy
2022-02-01 2:31 ` Steve Nickolas
2022-02-01 2:51 ` Grant Taylor via TUHS
2022-02-01 18:19 ` Clem Cole
2022-02-01 18:24 ` Steffen Nurpmeso
2022-02-01 12:45 ` Blake McBride
2022-01-29 17:20 ` Blake McBride
2022-01-30 1:20 ` Adam Thornton
2022-01-30 2:10 ` Will Senn
2022-01-27 2:07 ` Grant Taylor via TUHS
2022-01-27 2:40 ` Larry McVoy
2022-01-27 21:11 ` Tomasz Rola
2022-01-27 2:52 Norman Wilson
2022-01-27 23:20 ` Nemo Nusquam
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).