From: Christopher Dimech <dimech@gmx.com>
To: Emanuel Berg <incal@dataswamp.org>
Cc: emacs-devel@gnu.org
Subject: Emacs website, Lisp, and other
Date: Wed, 7 Aug 2024 13:24:03 +0200 [thread overview]
Message-ID: <trinity-1ee93a2f-236d-4ff4-88c5-201dd3f19a63-1723029843571@3c-app-mailcom-bs15> (raw)
In-Reply-To: <87ikwc6bd2.fsf@dataswamp.org>
> Sent: Wednesday, August 07, 2024 at 7:27 PM
> From: "Emanuel Berg" <incal@dataswamp.org>
> To: emacs-devel@gnu.org
> Subject: Re: Emacs website, Lisp, and other
>
> Abraham S.A.H." via "Emacs development discussions. wrote:
>
> >> Lisp is stronger at universities.
> >
> > Not in Asia! I can't name a university in Asia where Lisp
> > is taught. Lisp was never taught in our universities. Not
> > in Asia and not in the Middle East. Perhaps in Japan?
>
> Emacs-w3m is from Japan <3
>
> Seriously, I can't name any universities anywhere except mine
> but I can guarantee 100% that Lisp is stronger relatively in
> CS classes and the like than it is everywhere else.
>
> Emacs and a few other important applications are written in
> Lisp (Emacs is partly written in Elisp), other than that Lisp
> is a hobby for some part of the computer elite.
>
> >> In some instances the indented style and excessive use of
> >> () makes working with lisp code harder than
> >> other languages.
> >
> > Are you sure? I'm a Python programmer and I don't
> > think so.
>
> I am sure. Edit something here in Lisp, you have to edit it
> somewhere else as well, often. This, in combination with the
> stacking of parenthesis that happens, has caused more syntax
> errors than I would like to know.
>
> > My father basically hates whitespace sensitive
> > languages. Perhaps it's about taste difference?
>
> No. Just think, remove this line in Lisp
>
> some-item))
>
> then you have to find the right place if that is to be removed
> as well. Not only that, you have to identify the right
> parenthesis and remove them and nothing else. When there are
> a lot, it is difficult to see.
>
> I know there is matching, commands to automate, yada yada.
> But it is still much more difficult than just killing lines
> in Python.
>
> As an example, have you ever had a syntax error when doing
> `let' in Elisp?
>
> (let ((x 5)
> (...))
> ...)
>
> Have you ever had a similar situation when doing x = 5
> in Python? Why not?
>
> The Python syntax is ugly but for all practical purposes it is
> faster and less error prone, and much, much easier to maintain
> for other people or for you x years from now.
I know a few large university python projects that are almost impossible
to build from source. So I do not contribute. But its developers still
think they are some new kind of geniuses. They can do everything except
write code to standard expectations. I call these people hacks of trivia.
https://docs.obspy.org/
> --
> underground experts united
> https://dataswamp.org/~incal
>
>
>
next prev parent reply other threads:[~2024-08-07 11:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 13:13 Emacs website, Lisp, and other Abraham S.A.H. via Emacs development discussions.
2024-08-07 7:27 ` Emanuel Berg
2024-08-07 11:24 ` Christopher Dimech [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-04 22:27 Jeremy Bryant
2024-08-04 22:55 ` Emanuel Berg
2024-08-05 4:29 ` Emanuel Berg
2024-08-05 9:23 ` Christopher Dimech
2024-08-05 10:43 ` Emanuel Berg
2024-08-05 11:37 ` divya
2024-08-05 11:56 ` Christopher Dimech
2024-08-05 12:33 ` Eli Zaretskii
2024-08-05 11:45 ` Christopher Dimech
2024-08-05 12:56 ` Dr. Arne Babenhauserheide
2024-08-05 13:16 ` Dr. Arne Babenhauserheide
2024-08-05 14:46 ` Christopher Dimech
2024-08-05 21:28 ` Dr. Arne Babenhauserheide
2024-08-05 14:55 ` Eli Zaretskii
2024-08-05 12:28 ` Eli Zaretskii
2024-08-05 11:56 ` Eli Zaretskii
2024-08-06 19:09 ` Jeremy Bryant
2024-08-06 19:50 ` Christopher Dimech
2024-08-07 11:13 ` Eli Zaretskii
2024-08-07 12:03 ` Andrea Corallo
2024-08-07 12:16 ` Christopher Dimech
2024-08-08 2:01 ` Richard Stallman
2024-08-08 6:51 ` Joel Reicher
2024-08-07 12:31 ` Christopher Dimech
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-1ee93a2f-236d-4ff4-88c5-201dd3f19a63-1723029843571@3c-app-mailcom-bs15 \
--to=dimech@gmx.com \
--cc=emacs-devel@gnu.org \
--cc=incal@dataswamp.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://git.savannah.gnu.org/cgit/emacs.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).