From: goncholden <goncholden@protonmail.com>
To: Emanuel Berg <incal@dataswamp.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Indentation with spaces
Date: Fri, 10 Jun 2022 18:43:42 +0000 [thread overview]
Message-ID: <Kbst5_Gd33p2mda14AOAoyrrqJX73x-BsgnneJSmeyG_I6xvNizaa4AbqPgsWmHsjLJVEK1HxYiyBScbnWOeFeRqdVDN7q3MbQALCOpHJGc=@protonmail.com> (raw)
In-Reply-To: <87y1y4ke0c.fsf@dataswamp.org>
------- Original Message -------
On Friday, June 10th, 2022 at 10:29 PM, Emanuel Berg <incal@dataswamp.org> wrote:
> goncholden wrote:
>
> > Python is garbage as far as I am concerned.
>
>
> It doesn't look or feel cool like Lisp but development is
> super-fast. I think an experienced Lisp programmer writes the
> typical program in slightly more time than a Python
> novice does.
>
> It's the langauge itself, but also all the resources on the
> web and everywhere else including source, Q&As, books, you
> name it ... because of its popularity.
>
> I think for these and other reasons it's better than shell
> scripts (it's interactive, or can be) and it's much less of
> a learning curve (and again faster development) compared to
> Perl and other comparable languages for comparable
> applications and use cases that I know of.
>
> Lisp is cooler, looks better and might be more powerful in
> terms of the language's expressiveness, other than those things
> (which are important, no doubt) I think Python would win most
> other Progralympic disciplines vs Lisp ... TBH!
>
> > The designers thought it would be neat to give semantic
> > meaning to whitespace. Why on earth would they give semantic
> > meaning to something that cannot be seen? Who thought that
> > was a good idea?
>
>
> It makes the code uniform from person to person in a way that
> makes sense (in one particular "sense", the enforced one, but
> still) - there are advantages with this both reading, writing
> and understanding - advantages related not the least to what
> I just mentioned, Python's one killer advantage, the
> development speed.
>
> Trust me, I wrote a Python bot which is employed as we speak
> working well and not crashing, and I did this very fast
> knowing nothing about Python and even less about IRC. It just
> happens with Python ... somehow.
Have coded in Python as well. But as it has became mainstream, it has the tendency that its design becomes prescriptive to many.
I do not agree that "Simple is better than Complex". The design concept should be "there is more than one way to do it", rather than Python's "there should be only one way to do it".
For relatively simple tasks with quick solution, some python should do, but I avoid it.
> https://dataswamp.org/~incal/#sth
>
> --
> underground experts united
> https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-06-10 18:43 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 22:21 Indentation with spaces goncholden via Users list for the GNU Emacs text editor
2022-06-08 22:52 ` Skip Montanaro
2022-06-08 23:40 ` goncholden
2022-06-09 1:57 ` Skip Montanaro
2022-06-09 3:08 ` Emanuel Berg
2022-06-09 3:12 ` goncholden
2022-06-09 3:17 ` Emanuel Berg
2022-06-09 12:01 ` goncholden
2022-06-10 10:02 ` Emanuel Berg
2022-06-09 9:51 ` Skip Montanaro
2022-06-09 12:33 ` goncholden
2022-06-09 18:43 ` Lele Gaifax
2022-06-10 9:57 ` Emanuel Berg
2022-06-10 10:29 ` Emanuel Berg
2022-06-10 18:43 ` goncholden [this message]
2022-06-11 4:37 ` Christopher Dimech
2022-06-11 5:38 ` Emanuel Berg
2022-06-11 6:16 ` Christopher Dimech
2022-06-09 13:37 ` goncholden
2022-06-09 13:49 ` goncholden
2022-06-09 16:06 ` tomas
2022-06-10 10:08 ` Emanuel Berg
2022-06-10 9:45 ` Emanuel Berg
2022-06-10 17:57 ` goncholden
2022-06-10 18:08 ` tomas
2022-06-10 18:12 ` goncholden
2022-06-10 18:33 ` Emanuel Berg
2022-06-10 18:46 ` goncholden
2022-06-10 18:40 ` tomas
2022-06-10 18:53 ` Emanuel Berg
2022-06-10 19:05 ` goncholden
2022-06-10 19:27 ` goncholden
2022-06-11 0:56 ` goncholden
2022-06-10 18:29 ` Emanuel Berg
2022-06-09 13:27 ` Po Lu
2022-06-09 15:44 ` goncholden
2022-06-10 10:20 ` Emanuel Berg
2022-06-10 10:16 ` Emanuel Berg
2022-06-10 11:35 ` Po Lu
2022-06-10 18:26 ` goncholden
2022-06-11 0:57 ` Po Lu
2022-06-11 1:05 ` goncholden
2022-06-11 1:17 ` Po Lu
2022-06-11 1:33 ` goncholden
2022-06-11 1:36 ` goncholden
2022-06-11 7:38 ` Eli Zaretskii
2022-06-11 7:44 ` Emanuel Berg
2022-06-11 8:26 ` Eli Zaretskii
2022-06-11 7:57 ` goncholden
2022-06-11 8:27 ` Eli Zaretskii
2022-06-11 9:07 ` goncholden
2022-06-11 10:10 ` Eli Zaretskii
2022-06-11 15:43 ` [External] : " Drew Adams
2022-06-11 20:31 ` goncholden
2022-06-12 2:21 ` Drew Adams
2022-06-12 3:08 ` goncholden
2022-06-12 6:42 ` Eli Zaretskii
2022-06-11 1:49 ` Emanuel Berg
2022-06-11 2:05 ` goncholden
2022-06-10 23:01 ` Emanuel Berg
2022-06-11 0:00 ` goncholden
2022-06-11 7:31 ` Eli Zaretskii
2022-06-11 0:58 ` Po Lu
2022-06-11 1:41 ` Emanuel Berg
2022-06-09 19:01 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-06-09 20:16 ` [External] : " Drew Adams
2022-06-09 20:20 ` goncholden
2022-06-11 5:16 ` Emanuel Berg
2022-06-11 5:33 ` tomas
2022-06-11 5:44 ` Emanuel Berg
2022-06-11 5:51 ` goncholden
2022-06-11 15:43 ` Drew Adams
2022-06-12 4:45 ` RE: [External] : " Christopher Dimech
2022-06-13 5:04 ` [External] : " Emanuel Berg
2022-06-10 10:29 ` reinventing the wheel but not faculty, libraries (was: Re: Indentation with spaces) Emanuel Berg
2022-06-09 5:30 ` Indentation with spaces Eli Zaretskii
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='Kbst5_Gd33p2mda14AOAoyrrqJX73x-BsgnneJSmeyG_I6xvNizaa4AbqPgsWmHsjLJVEK1HxYiyBScbnWOeFeRqdVDN7q3MbQALCOpHJGc=@protonmail.com' \
--to=goncholden@protonmail.com \
--cc=help-gnu-emacs@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.
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).