From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Computers were a mistake
Date: Tue, 5 Mar 2019 13:02:32 +0100 [thread overview]
Message-ID: <CAFSF3XNzVgQn=oJmdb=q=CfZ41DbahjF3bjSRb8fo0cnYW47Gw@mail.gmail.com> (raw)
In-Reply-To: <ef2df9e8-5a4b-4199-a3a5-db5b22902683@www.fastmail.com>
i don't like it if i'm honest. you missed out on lots of developments:
no mention of timewarped ioagents gone rogue, no hypercubes, also
docker isn't really that useful, so i doubt the borg would have come
far with it.
your domain on the other hand is very well picked. i'm in awe.
next prev parent reply other threads:[~2019-03-05 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 10:26 Jean-Luc Picard
2019-03-05 12:02 ` hiro [this message]
2019-03-05 12:03 ` [9front] " hiro
2019-03-05 12:03 ` The Rust Evangelism Strike Force
2019-03-05 12:34 ` hiro
2019-03-05 13:55 ` Rodrigo G. López
2019-03-05 15:20 ` Stanley Lieber
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='CAFSF3XNzVgQn=oJmdb=q=CfZ41DbahjF3bjSRb8fo0cnYW47Gw@mail.gmail.com' \
--to=23hiro@gmail.com \
--cc=9front@9front.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).