Sujet : on levels of disappointment (Was: Re: Lisp history: IF, etc.)
De : jshem (at) *nospam* yaxenu.org (Julieta Shem)
Groupes : comp.lang.lispDate : 04. Apr 2024, 01:37:56
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <878r1uuiej.fsf_-_@tudado.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Kaz Kylheku <
643-408-1753@kylheku.com> writes:
On 2024-04-03, Kaz Kylheku <643-408-1753@kylheku.com> wrote:
On 2024-04-03, Alan Bawden <alan@csail.mit.edu> wrote:
Kaz Kylheku <643-408-1753@kylheku.com> writes:
If you think about it, it's actually kind of ignorant to invent a
programming language with imperative if statements, but in which where
the math conditional is missing.
>
If you think like a historian, you don't describe this as "ignorant".
It's just not something that was above the horizon in the mind set of
the time. After all, that mathematical notation you are referring to
isn't something that mathematicians get very formal about.
>
That is a fair observation; roughly speaking, higher languages first
evolved from that of the machine. Why we have an if /statement/ is that
the machine has testing and branching in its instruction set, which are
also statements. The imperative language that works by jumping around
and shuffling mainly word-sized quantities inside a Von Neumann machine
is an abstraction of machine language, not an abstraction of functions.
>
The abstraction of machine language isn't ignorant, it's just different.
>
But, right, okay; I lost a thoguht I had some hours earlier about this.
By the time we have a higher level language inspired by math formulas in
which you can do A * B + C, and define math-like functions, you would
think that the right synapse would fire between the right two brain
cells, so that a value-yielding conditional would be supplied. When you
have translation of arithmetic formulas to machine language, the scene
is ripe for such an operator. So maybe ignorance is a strong word, but
there is a margin for disappointment.
But it's not the same disappointment as in having to use JIRA, right? :-)
``Writing bug reports on napkins and keeping them crumpled in a large
black garbage bag is better than this fucking piece of crap called
JIRA.'' -- Kaz Kylheku, 2016.
(*) Full source
--8<---------------cut here---------------start------------->8---
X-Received: by 10.200.47.116 with SMTP id k49mr3706471qta.61.1474251695757;
Sun, 18 Sep 2016 19:21:35 -0700 (PDT)
X-BeenThere:
comp.programming@googlegroups.comReceived: by 10.157.2.1 with SMTP id 1ls4320407otb.4.gmail; Sun, 18 Sep 2016
19:21:33 -0700 (PDT)
X-Received: by 10.157.2.104 with SMTP id 95mr3727234otb.133.1474251693667;
Sun, 18 Sep 2016 19:21:33 -0700 (PDT)
MIME-Version: 1.0
Path: b4ni5152iti.0!nntp.google.com!news.glorb.com!2.us.feeder.erje.net!feeder.erje.net!1.eu.feeder.erje.net!enother.net!enother.net!news.mixmin.net!aioe.org!.POSTED!not-for-mail
From: Kaz Kylheku <
221-50...@kylheku.com>
Newsgroups: alt.comp.os.linux,comp.programming,comp.software-eng
Subject: Re: Favourite Software Development Tools for Teams?
Followup-To: comp.programming
Date: Mon, 19 Sep 2016 02:21:29 +0000 (UTC)
Organization: Aioe.org NNTP Server
Lines: 11
Message-ID: <
20160918192003.449@kylheku.com>
References: <
E9HDz.15308$LX2.8752@fx36.iad>
NNTP-Posting-Host: OGJi3KNpFOhM58UHZwXj0w.user.gioia.aioe.org
X-Complaints-To:
ab...@aioe.orgUser-Agent: slrn/pre1.0.0-18 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
["Followup-To:" header set to comp.programming.]
On 2016-09-19, Triscal Islington <
trust.your...@mail.ru> wrote:
I'm finally heading my own software engineering project at work and,
since I call the shots, it's up to me to decide on what collaboration
and review tools we utilize on the project.
>
I'm pretty well decided on git for source code management but what are
your favourite linux tool for bug tracking, code review, collaboration, etc?
Writing bug reports on napkins and keeping them crumpled in a large
black garbage bag is better than this fucking piece of crap called JIRA.
--8<---------------cut here---------------end--------------->8---
Date | Sujet | # | | Auteur |
2 Apr 24 | Lisp history: IF, etc. | 56 | | Alan Bawden |
2 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Kaz Kylheku |
3 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Gijs Hillenius |
3 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Gijs Hillenius |
3 Apr 24 | Re: Lisp history: IF, etc. | 49 | | Madhu |
3 Apr 24 | Re: Lisp history: IF, etc. | 48 | | Alan Bawden |
3 Apr 24 | Re: Lisp history: IF, etc. | 35 | | Paul Rubin |
3 Apr 24 | Re: Lisp history: IF, etc. | 34 | | Alan Bawden |
4 Apr 24 | Re: Lisp history: IF, etc. | 32 | | Paul Rubin |
4 Apr 24 | Re: Lisp history: IF, etc. | 5 | | Lawrence D'Oliveiro |
4 Apr 24 | Re: Lisp history: IF, etc. | 3 | | Axel Reichert |
4 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Lawrence D'Oliveiro |
4 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Paul Rubin |
4 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Kaz Kylheku |
4 Apr 24 | Re: Lisp history: IF, etc. | 26 | | Alan Bawden |
5 Apr 24 | Re: Lisp history: IF, etc. | 25 | | Paul Rubin |
5 Apr 24 | Re: Lisp history: IF, etc. | 24 | | Julieta Shem |
5 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Julieta Shem |
6 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Lawrence D'Oliveiro |
15 Apr 24 | Re: Lisp history: IF, etc. | 21 | | Paul Rubin |
16 Apr 24 | Re: Lisp history: IF, etc. | 20 | | Jeff Barnett |
16 Apr 24 | Re: Lisp history: IF, etc. | 2 | | Lawrence D'Oliveiro |
16 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Jeff Barnett |
16 Apr 24 | Re: Lisp history: IF, etc. | 16 | | Paul Rubin |
16 Apr 24 | Re: Lisp history: IF, etc. | 15 | | Jeff Barnett |
16 Apr 24 | Re: Lisp history: IF, etc. | 14 | | Lawrence D'Oliveiro |
16 Apr 24 | Re: Lisp history: IF, etc. | 12 | | Paul Rubin |
17 Apr 24 | Re: Lisp history: IF, etc. | 11 | | Lawrence D'Oliveiro |
17 Apr 24 | Re: Lisp history: IF, etc. | 10 | | Paul Rubin |
17 Apr 24 | Re: Lisp history: IF, etc. | 9 | | Jeff Barnett |
17 Apr 24 | Re: Lisp history: IF, etc. | 8 | | Lawrence D'Oliveiro |
17 Apr 24 | Re: Lisp history: IF, etc. | 7 | | Paul Rubin |
17 Apr 24 | Re: Lisp history: IF, etc. | 3 | | Madhu |
18 Apr 24 | Re: Lisp history: IF, etc. | 2 | | Lawrence D'Oliveiro |
18 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Paul Rubin |
17 Apr 24 | Re: Lisp history: IF, etc. | 3 | | Ben Bacarisse |
18 Apr 24 | Re: Lisp history: IF, etc. | 2 | | Lawrence D'Oliveiro |
18 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Stefan Monnier |
17 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Jeff Barnett |
17 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Stefan Ram |
4 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Ben Bacarisse |
3 Apr 24 | Re: Lisp history: IF, etc. | 7 | | Kaz Kylheku |
4 Apr 24 | Re: Lisp history: IF, etc. | 5 | | Alan Bawden |
4 Apr 24 | Re: Lisp history: IF, etc. | 3 | | Kaz Kylheku |
4 Apr 24 | Re: Lisp history: IF, etc. | 2 | | Kaz Kylheku |
4 Apr 24 | on levels of disappointment (Was: Re: Lisp history: IF, etc.) | 1 | | Julieta Shem |
4 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Julieta Shem |
5 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Spiros Bousbouras |
4 Apr 24 | Re: Lisp history: IF, etc. | 3 | | Lawrence D'Oliveiro |
4 Apr 24 | Re: Lisp history: IF, etc. | 2 | | Alan Bawden |
4 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Kaz Kylheku |
12 Apr 24 | Re: Lisp history: IF, etc. | 2 | | Alan Bawden |
12 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Lawrence D'Oliveiro |
4 Apr 24 | Re: Lisp history: IF, etc. | 3 | | Kaz Kylheku |
4 Apr 24 | Re: Lisp history: IF, etc. | 2 | | Alan Bawden |
4 Apr 24 | Re: Lisp history: IF, etc. | 1 | | Lawrence D'Oliveiro |