The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: markus schnalke <meillo@marmaro.de>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] run commands at login in v6 and stty
Date: Mon, 28 Feb 2022 22:25:25 +0100	[thread overview]
Message-ID: <1nOnWH-7qi-00@marmaro.de> (raw)
In-Reply-To: <CAEoi9W7wawmp_i0YeQKoaBscvZkNJYMyrPoJtwwwjw2cwv7gtA@mail.gmail.com>

Hoi.

[2022-02-28 14:25] Dan Cross <crossd@gmail.com>
>
> On a personal note, when I was learning to write C for Unix, I read a lot of
> open source code to see how to do it. So much of it was riddled with complex #
> ifdefs that I kind of got the impression that that was how things were
> _supposed_ to be written. Then I read the Spencer/Collyer paper, and modified
> some program that I'd written to use abstract interfaces; it was so much easier
> to reason about that I was kind of shocked that others didn't do the same.
> 
> I suppose the point is that many programmers learn by copying what has come
> before. However, so much of what's out there is a poor example of how to do
> things; we're stuck with a feedback loop of poor design.

... and I am very happy that I found my way into a different feedback
loop, called Unix philosophy ... with sources meant to be read, great
documentation, and books that actually feature real life code (already
a thing by itself) but also that the production code is on the same
``acts as a good example'' level.

If programmers have never experienced such wonderful worlds -- how
poor their programming lifes must be!


meillo

  reply	other threads:[~2022-02-28 21:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28  1:04 Douglas McIlroy
2022-02-28  7:22 ` Rob Pike
2022-02-28 14:07   ` Larry McVoy
2022-02-28 18:47     ` Dan Cross
2022-02-28 19:25       ` Dan Cross
2022-02-28 21:25         ` markus schnalke [this message]
2022-02-28 19:26       ` Clem Cole
2022-02-28 20:03         ` Adam Thornton
2022-02-28 18:18 ` Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2022-02-27  7:48 Noel Chiappa
2022-02-26 21:45 Brian Walden
2022-02-26 22:16 ` Rob Pike
2022-02-27 20:32 ` Sven Mascheck
2022-02-26 20:39 Will Senn
2022-02-26 21:03 ` Michael Kjörling
2022-02-26 22:49 ` Clem Cole
2022-02-26 23:12   ` Rob Pike
2022-02-27  0:46     ` Clem Cole
2022-02-27 15:01     ` Larry McVoy
2022-02-27 17:10       ` Clem Cole

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=1nOnWH-7qi-00@marmaro.de \
    --to=meillo@marmaro.de \
    --cc=tuhs@minnie.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).