9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: saroj@bear.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] off topic: troff book
Date: Tue, 16 Jan 2001 16:31:00 +0000	[thread overview]
Message-ID: <941spm$s0r$1@nnrp1.deja.com> (raw)
In-Reply-To: <01b901c07cc8$bc634660$0ab9c6d4@cybercable.fr>

In article <01b901c07cc8$bc634660$0ab9c6d4@cybercable.fr>,
  boyd@planete.net (Boyd Roberts) wrote:
> From: <saroj@bear.com>
> >
> > No, that is not true. Knuth felt that troff was burdened with
> > couple of generations' legacy at Bell Labs, and he wanted to
> > start with a clean slate without fear of hurting any Bell Labs
> > colleague's feeling (about troff).
>
> nonsense, research does not work like that.  if you're afraid
> of 'hurting' people's feelings you'll get no research done
> at all.  do you understand the scientific method?
>

That was precisely the point! TeX was done from the ground up.

> do you think einstein would have held back not to 'hurt'
> newton's feelings?  are you mad?  admittedly, newton
> was dead, but it _could_ hurt his standing, retrospectively.
>
> > And finally, he demonstrated that even large programs can be
> > explained in full detail (unlike most programs written by early
> > Bell Labs guys), though Pascal is not a great language on which
> > WEB (the implementation language of TeX) is based.
>
> LP is nonsense.  you write the code.  the code is the 'truth'.
> you add comments to explain the global view and stuff that's
> not 'obvious'.  not 'obvious' is a judgement call.  you get
> 'judgement' after you've spent a few years in the caper.
>
> unfortunately, that last sentence is not always true.
>
> then again, no documentation is better than bad/incorrect
> documentation.
>
> i fought tooth and nail with my old man about what was
> the point of 'pure' research.  i thought it was pointless.
> finally, i realised he was _right_.
>

Sorry, how many programs written by you can be read from cover to
cover and fully understood?


[snipped]


Thank you,
Saroj Mahapatra


Sent via Deja.com
http://www.deja.com/


  reply	other threads:[~2001-01-16 16:31 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-07 15:17 rob pike
2001-01-08  9:54 ` Luis Fernandes
2001-01-08 16:18 ` Douglas A. Gwyn
2001-01-08 20:07   ` Dan Cross
2001-01-12  9:32     ` saroj
2001-01-12 17:17       ` Douglas A. Gwyn
2001-01-12 17:51         ` Boyd Roberts
2001-01-16 16:25         ` saroj
2001-01-12 18:20       ` William K. Josephson
2001-01-12 18:51       ` Boyd Roberts
2001-01-16 16:31         ` saroj [this message]
2001-01-08 17:19 ` James A. Robinson
2001-01-08 19:21   ` Howard Trickey
2001-01-09  9:38     ` Andy Newman
2001-01-09  9:54       ` Boyd Roberts
2001-01-10  0:16 ` Steve Kilbane
2001-01-11  9:50   ` Douglas A. Gwyn
  -- strict thread matches above, loose matches on Subject: below --
2001-01-08 15:17 John A. Murdie
2001-01-08 10:29 John A. Murdie
2001-01-08 15:06 ` Mark C. Otto
2001-01-02 10:54 steve.simon
2001-01-03  8:29 ` Boyd Roberts
2001-01-05  9:49   ` [9fans] " John E. Gwyn
2001-01-05 14:52     ` Boyd Roberts
2000-12-27 19:26 James A. Robinson
2001-01-02 17:44 ` John E. Gwyn
2001-01-05  9:48 ` Allan J. Heim
2001-01-05 14:54   ` Boyd Roberts
2001-01-05 19:29     ` Steve Kilbane
2001-01-06 17:53       ` Boyd Roberts
2001-01-07  1:20         ` Steve Kilbane
2000-08-19 21:44 Boyd Roberts

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='941spm$s0r$1@nnrp1.deja.com' \
    --to=saroj@bear.com \
    --cc=9fans@cse.psu.edu \
    /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).