From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: help-guix@gnu.org, raghavgururajan@disroot.org
Subject: Re: Help with Learning Programming and LISP
Date: Thu, 12 Sep 2019 08:34:30 +0200 [thread overview]
Message-ID: <a3f313e3-af78-fcc6-dbb8-a2ec50481eb0@fastmail.net> (raw)
In-Reply-To: <05840a988fb0592a67f8372650aba5cdc81b499e.camel@disroot.org>
On 12/09/2019 03:16, Raghav Gururajan wrote:
> I have a doubt though, do I have to learn dialects of LISP in a
> particular order?
No, you can learn each of them on its own, and proceed in any order if
you want to learn all three of them.
If your main goal is to learn about the core features of the Lisp
family, I'd start with Scheme, which is the smallest and most coherent
Lisp dialect. Common Lisp is huge in comparison, but if you try to write
real-life programs in Scheme, you will discover that there are actually
good reasons for having a large standardized language. The other main
difference is that Common Lisp implementations tend to have much better
development environments and in particular much better debuggers, which
is also a consequence of the minimalist vs. practical tool approaches
taken by the two dialects.
In my opinion, there is exactly one reason for learning Emacs Lisp: to
configure and extend Emacs. Some people also use Emacs Lisp for text
processing tasks, because Emacs provides an excellent support library
for that. But as a language, Emacs Lisp is mostly considered outdated
and inferior to either Scheme or Common Lisp. I would definitely not
recommend learning Emacs Lisp as a typical modern Lisp.
Konrad.
next prev parent reply other threads:[~2019-09-12 6:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 16:18 Help with Learning Programming and LISP Raghav Gururajan
2019-09-09 16:38 ` John Soo
2019-09-09 17:04 ` Raghav Gururajan
2019-09-09 17:20 ` Jesse Gibbons
2019-09-09 16:50 ` Tobias Geerinckx-Rice
2019-09-09 16:53 ` Tobias Geerinckx-Rice
2019-09-09 17:05 ` John Soo
2019-09-09 17:04 ` Raghav Gururajan
2019-09-09 17:20 ` Pierre Neidhardt
2019-09-09 17:18 ` Vladimir Sedach
2019-09-09 20:11 ` Ricardo Wurmus
2019-09-12 1:16 ` Raghav Gururajan
2019-09-12 6:34 ` Konrad Hinsen [this message]
[not found] <mailman.370.1568090751.2189.help-guix@gnu.org>
2019-09-10 20:31 ` Zelphir Kaltstahl
2019-09-11 20:53 ` Viet Le
2019-09-11 21:24 ` Zelphir Kaltstahl
2019-09-11 22:15 ` Viet Le
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3f313e3-af78-fcc6-dbb8-a2ec50481eb0@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=help-guix@gnu.org \
--cc=raghavgururajan@disroot.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 read-only IMAP folder(s) and NNTP newsgroup(s).