From: "Dr. Arne Babenhauserheide" via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists <emacs-tangents@gnu.org>
To: "Abraham S.A.H." via "Emacs tangentdiscussions."
<emacs-tangents@gnu.org>
Cc: "Abraham S.A.H." <arash.sah@tuta.io>, incal@dataswamp.org
Subject: Re: 10 problems with Elisp, part 10
Date: Thu, 08 Aug 2024 08:00:23 +0200 [thread overview]
Message-ID: <87y157a70o.fsf@web.de> (raw)
In-Reply-To: <O3hwhNN--7-9@tuta.io> (Abraham S. A. H.'s message of "Wed, 7 Aug 2024 20:57:29 +0200 (CEST)")
[-- Attachment #1.1: Type: text/plain, Size: 3651 bytes --]
"Abraham S.A.H." writes:
> Emanuel Berg wrote:
>> I didn't say that. You know why? Because I didn't mean it.
>> It doesn't take much experience to do cool things fast
>> in Python, it is a fact.
>
> I agree to disagree, Emanuel! Sorry, but I do not think “Python is
> a generally better programming language”. Perhaps Python is very good
> in some aspects but not in general, and I know Python better than any
> other language.
>
> I think that Python is popular in the sense of “there are more Python
> programmers than most other languages”. And I think “In the software
> industry, technical merits of a programming language do not make it
> popular.”! Java and C and JS didn't become popular only due to their
> technical merits.
While this is true (with the caveat "only" which you do include), there
is actually something strange about how Python spread.
When looking at how Python spread: compared to other languages and
before Python 3 (2008) it was the odd one out. It was slowly but
constantly growing in popularity. It didn’t have one killer feature, but
it was growing organically from genuine fans:
https://www.tiobe.com/tiobe-index/python/
In 2008 it had a boost in popularity and then actually has been losing —
in 2013 when I switched on to Guile,¹ many others seem to have done the
same. The TIOBE rating of Python *halved* between 2013 and 2014.
And then came the whole AI craze. 2017 Tensor Flow 1.0 was released and
2018 popularity of Python started going off the roof, but not in one
step, but still incrementally (though less constant than before 2008).
Before 2008 and after 2018 there has been something not seen in other
languages. Other languages have a cycle of an event pushing popularity
up, then waning popularity. Python didn’t.
It grew more continuously and that may point to an actual quality of the
language.
https://www.tiobe.com/tiobe-index/
¹ why and how I switched from Python to Guile Scheme:
https://www.draketo.de/py2guile
> Do you know Python and Lisp and acknowledge their difference?
I do. Since 2013 I’ve been using Guile as my main hobby-language.
Between around 2006 and 2013 I’ve been using Python almost exclusively —
and a lot, 2011 to 2013 full-time.
> For removing a statement in Python, use `kill-line` (C-k) or
> `kill-whole-line`. For removing a statement in Lisp, use `kill-sexp`
> (C-M-k).
This often moves the parentheses to the previous line, so the diff
you’ll be looking at to review the change will show a changed line and a
deleted line.
> You are using your own presumptions to reason out, and convince
> others. Your presumptions are not mine, and your facts are not facts
> to me.
Either they are facts or they are not. Please don’t go mixing this up.
You cannot say “these are not my facts” without leaving the grounds of
logic.
The Tiobe index I linked above is a fact, but its interpretation is not.
Whether it is genuinely better can’t be established as fact, but that it
spread differently from other languages is clearly visible.
That it doesn’t take much time to do things fast in Python is a fact,
proven over and over again, but the interpretation *why* that is and
whether it means that Python is a better language is not.
And all that still doesn’t mean that I prefer it (why else would I use
Guile instead and write in an emacs-devel channel — now emacs-tangent?).
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
[-- Attachment #2: Type: text/plain, Size: 92 bytes --]
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
next parent reply other threads:[~2024-08-08 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <O3hwhNN--7-9@tuta.io>
2024-08-08 6:00 ` Dr. Arne Babenhauserheide via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists [this message]
2024-10-23 20:06 ` 10 problems with Elisp, part 10 Jean Louis
2024-10-29 13:42 ` Abraham S.A.H. via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
[not found] ` <877ccq5g2u.fsf@dataswamp.org>
2024-10-23 20:11 ` Jean Louis
[not found] <87sevj9b50.fsf@jeremybryant.net>
[not found] ` <871q33rj7v.fsf@dataswamp.org>
[not found] ` <trinity-dae5eb6f-9f3b-451e-ac64-5d82d5ea1bef-1722849793865@3c-app-mailcom-bs04>
[not found] ` <86ed73qhly.fsf@gnu.org>
[not found] ` <87frrjoryg.fsf_-_@dataswamp.org>
2024-10-23 19:25 ` 10 problems with Elisp, part 10 (was: Re: Emacs website, Lisp, and other) Jean Louis
2024-10-23 21:13 ` Emanuel Berg
2024-10-23 21:36 ` Jean Louis
2024-10-25 6:44 ` Emanuel Berg
2024-10-28 3:27 ` 10 problems with Elisp, part 10 Joel Reicher
2024-10-24 6:48 ` Dr. Arne Babenhauserheide via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2024-08-09 7:21 Johan Myréen
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=87y157a70o.fsf@web.de \
--to=emacs-tangents@gnu.org \
--cc=arash.sah@tuta.io \
--cc=arne_bab@web.de \
--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).