From: Leah Neukirchen <leah@vuxu.org>
To: Eric Wong <e@yhbt.net>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] doc: add technical/whyperl
Date: Thu, 09 Apr 2020 00:37:08 +0200 [thread overview]
Message-ID: <87lfn5ioyz.fsf@vuxu.org> (raw)
In-Reply-To: <20200408221741.GA10142@dcvr> (Eric Wong's message of "Wed, 8 Apr 2020 22:17:41 +0000")
Eric Wong <e@yhbt.net> writes:
> Leah Neukirchen <leah@vuxu.org> wrote:
>
> Did you forget reply-all? Re-adding Cc: meta@public-inbox.org
> since you've already posted there in the past.
I was more meant as a off-side remark, but we can also do this on the
list.
>> Eric Wong <e@yhbt.net> 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.
>
> ?
This sounds better to me.
> 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
> trial-and-error.
So I just looked into perlintro and the word context appears like
three times and is not explained. I think picking up some core
concepts is super hard from the included docs.
cu,
--
Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org
prev parent reply other threads:[~2020-04-08 22:37 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] ` <87r1wyjlop.fsf@vuxu.org>
2020-04-08 22:17 ` Eric Wong
2020-04-08 22:37 ` Leah Neukirchen [this message]
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfn5ioyz.fsf@vuxu.org \
--to=leah@vuxu.org \
--cc=e@yhbt.net \
--cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).