user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
To: Leah Neukirchen <>
Subject: Re: [PATCH] doc: add technical/whyperl
Date: Wed, 8 Apr 2020 22:17:41 +0000	[thread overview]
Message-ID: <20200408221741.GA10142@dcvr> (raw)
In-Reply-To: <>

Leah Neukirchen <> wrote:

Did you forget reply-all?  Re-adding Cc:
since you've already posted there in the past.

> Eric Wong <> writes:
> > Some people don't like Perl; but it exists, there's no
> > avoiding it with everything that depends on it.  And
> > nearly all code still works unmodified after 20 years.
> > +  Furthermore, Perl documentation is typically installed as
> > +  manpages, allowing users to quickly access and learn it
> > +  offline.
> I absolutely don't mind using Perl, but I cannot say this is true.
> I tried to learn Perl from the man pages, and things got sooo much
> clearer once I picked up the Camel book.  The man pages are good for
> reference, but not for learning from scratch.

Interesting, thanks for the comment.  I'll reword it, how about:

	Furthermore, Perl documentation is typically installed
	locally as manpages, allowing users to quickly refer
	to documentation as needed.


Fwiw, I guess my own learning experiences are atypical.  I've
never picked up a book on Perl or any language/skill I'm
familiar with.  Mainly source diving, manpages, lurking on
mailing lists, archives, newsgroups, etc. along with lots of

It's all very scattered (like my brain :x), and I suppose it's
reflected in how public-inbox works and gets developed;
including my aversion to centralization and unnecessary
structure in things such as trackers with labels/priorities.

  parent reply	other threads:[~2020-04-08 22:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07  9:49 [PATCH] doc: add technical/whyperl Eric Wong
2020-04-08  0:41 ` Kyle Meyer
2020-04-08 22:26   ` Eric Wong
2020-04-09  1:14     ` Kyle Meyer
     [not found] ` <>
2020-04-08 22:17   ` Eric Wong [this message]
2020-04-08 22:37     ` Leah Neukirchen

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200408221741.GA10142@dcvr \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).