From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] Need help with configuring the Internet
Date: Mon, 10 Jun 2019 13:47:00 +0100 [thread overview]
Message-ID: <7ae07b53-1087-45c5-838d-5b429859e8d2@www.fastmail.com> (raw)
In-Reply-To: <BFDFEBCA512ACD777C575D014DCC93D5@kvik.link>
On Mon, Jun 10, 2019, at 9:43 AM, vp@kvik.link wrote:
>
> The papers in /sys/doc, the supplemental choice of documents
> on cat-v.org, the manual pages, the source code itself, and
> spending some time hanging out with and getting to know the
> community and its ways should, in no particular order, be
> enough to jeopardize your (prospective) computer-themed
> career.
Tell me about it! I ended up in Forth, which is possibly even worse. ;)
Thinking Forth 1994 edition contains:
> A line from a typical Forth application might read:
> 20 ROTATE LEFT TURRET
> Few other languages would encourage you to concoct a subroutine called LEFT,
> merely as a modifier, or a subroutine called TURRET, merely to name part of
> the hardware.
There's a nice little quote in the last chapter:
> The idea of “human scale” is, I think, today’s seminal concept in software
> design. This isn’t specifically a Forth development; the great joy of UNIX,
> in its youth at least, was that you could read it (since it was written in C),
> understand it (since it was small), and modify it (since it was simple). Forth
> shares these virtues, although it’s designed to tackle a different sort of problem.
--
Experts working at the FSB and E centers are able to detect "signs of extremism" even in the borscht recipe.
next prev parent reply other threads:[~2019-06-10 12:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 6:43 vp
2019-06-10 12:47 ` Ethan Gardener [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-17 7:24 cinap_lenrek
2019-06-17 8:59 ` 염준혁
2019-06-17 6:58 cinap_lenrek
2019-06-17 7:21 ` 염준혁
2019-06-17 4:19 cinap_lenrek
2019-06-17 5:01 ` 염준혁
2019-06-17 6:45 ` 염준혁
2019-06-14 1:16 cinap_lenrek
2019-06-17 3:56 ` 염준혁
2019-06-13 8:48 ori
2019-06-14 0:52 ` 염준혁
2019-06-14 13:35 ` hiro
2019-06-11 16:15 ori
2019-06-12 1:14 ` 염준혁
2019-06-12 9:25 ` hiro
2019-06-11 9:49 vp
2019-06-11 13:26 ` 염준혁
2019-06-10 15:51 ori
2019-06-11 11:10 ` 염준혁
2019-06-10 6:59 ori
2019-06-10 8:44 ` 염준혁
2019-06-10 10:58 ` 염준혁
2019-06-10 6:54 ori
2019-06-07 5:00 ori
2019-06-10 4:46 ` 염준혁
2019-06-10 5:30 ` 염준혁
2019-06-07 4:46 염준혁
2019-06-07 5:34 ` [9front] " 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=7ae07b53-1087-45c5-838d-5b429859e8d2@www.fastmail.com \
--to=eekee57@fastmail.fm \
--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).