Some entity, AKA "B. Pym" <No_spamming@noWhere_7073.org>,
wrote this mindboggling stuff:
(selectively-snipped-or-not-p)
On 12/16/2023, cor@clsnet.nl wrote:
Any marginally usable programming language approaches an ill
defined barely usable re-implementation of half of common-lisp
The good news is, it's not Lisp that sucks, but Common Lisp.
--- Paul Graham
Just to set the record straight;
This is not My line.
I quoted it but don't know who the originator of that remark is.
Cor
On 5/27/2024 7:18 AM, Cor wrote:
Some entity, AKA "B. Pym" <No_spamming@noWhere_7073.org>,
wrote this mindboggling stuff:
(selectively-snipped-or-not-p)
On 12/16/2023, cor@clsnet.nl wrote:
Any marginally usable programming language approaches an ill
defined barely usable re-implementation of half of
common-lisp
The good news is, it's not Lisp that sucks, but Common Lisp.
--- Paul Graham
Just to set the record straight;
This is not My line.
I quoted it but don't know who the originator of that remark is.
Cor
a few years ago... when i started learning Python...
it was so exciting...
Every day i thought...
--- THis is Lisp in a thin-disguise ... SO Everyone gets it now.
Everyone is a Lisper now.
In some ways, Python is aggressively anti-Lispy, in a way that cannot be reconciled. Just one example: if you've built up a list comprehension
and suddenly you need to reference the result of the same computation
twice, now you need to turn the whole thing into a for loop because you
can't introduce variables in the middle of an expression.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 55:55:07 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,712 |