@thinkberg I am a huge fan of #PicoLisp. Small, fast, and pragmatic. The assembler among Lisps. :-) Unfortunately, it is not available in the #OpenBSD ports. However, I have written a short manual: https://rt.fm/picolisp.txt

@mousebot ... unless you take FEXPRs like in #PicoLisp - they are better than #Lisp macros because they are normal functions, more readable, and can be debugged (e.g. single-stepped).

#PicoLisp version 25.3 is now in Debian testing

#Lisp

@tiang I write 90% of my scripts in #PicoLisp.

@symbolics @weekend_editor @rzeta0 In #PicoLisp probably the shortest way is with 'cnt':

: (cnt t '(a b c d))
-> 4

('t' is a function which always returns 'T')

@rzeta0 In #PicoLisp it is 'conc'. IIRC that is 'nconc' in CL

@pedromj @rzeta0 I think so too. Tail recursion is just an obfuscated loop. That's why I hesitated nearly 40 years to implement it in #PicoLisp.

@rzeta0 Oops, found a typo. The last 'cadr' must be 'caddr' :

http://pb1n.de/?3c4b41

Did not test all braches ;)

#PicoLisp #Lisp

@rzeta0 In #PicoLisp it could be http://pb1n.de/?c3be0c

#Lisp

🌗 PicoLisp Wiki: 文件
➤ PicoLisp 資源豐富，從基礎教學到進階應用皆有涵蓋。
✤ https://picolisp.com/wiki/?Documentation
PicoLisp Wiki 包含豐富的程式碼和知識，在這裡可以找到從入門到高手的指導、教學和範例，並鼓勵社羣分享成果。
+ 我對 PicoLisp 的這個 Wiki 的組織結構印象深刻，提供了很全面的資訊。
+ 這份摘要簡潔明瞭地展示了 PicoLisp Wiki 的重要性和價值，吸引人去深入瞭解。
#PicoLisp 資源

🌐 Ah yes, the #mystical PicoLisp—a veritable treasure trove of code so scattered across the interwebs that someone just had to corral it into yet another #wiki nobody asked for. 📚✨ Dive into this endless abyss of "coherent" #documentation and maybe, just maybe, you'll emerge as a wizard in a language nobody uses. 🧙‍♂️🔮 Good luck, brave soul!
https://picolisp.com/wiki/?Documentation #PicoLisp #Coding #Languages #HackerNews #ngated

Everything Picolisp can do, and more

https://picolisp.com/wiki/?Documentation

#HackerNews #Picolisp #Everything #PicolispCanDo #Programming #Languages #Lisp #Community

@simon_brooke Testing bignums in a REPL is noisy due to the huge outputs. In #PicoLisp I then do things like

: (bench (fact 10000)) T
0.163 sec
-> T

because only the result of the last expression is printed

@Regenaxer @borkdude @vindarel Thanks! Right, so my comparable in-REPL times for iterative factorial 1000 are

#PicoLisp: (bench (apply * (range 1 1000)))
0.000 sec
#Clojure: user=> (time (apply *' (range 1 1000)))
"Elapsed time: 2.428199 msecs"
#SBCL: CL-USER[1]: (time (apply #'* (alexandria:iota 1000 :step 1)))
Evaluation took:
0.000 seconds of real time
0.000015 seconds of total run time (0.000000 user, 0.000015 system)
100.00% CPU
45,990 processor cycles
0 bytes consed

#Lisp

@simon_brooke @borkdude @vindarel It is the #PicoLisp 'bench' function:

$ pil +
: (bench (do 9999999 (* 3 4)))
0.209 sec
-> 12

@borkdude @vindarel @Regenaxer #PicoLisp doesn't have macros, by design. Its `time` function returns the time of day. So while there may be a way of timing a computation in the REPL, I've not found it yet.

#Lisp

https://software-lab.de/doc/refT.html#time

@borkdude @vindarel @Regenaxer Again, this is true and fair. I haven't yet learned enough #PicoLisp to do a comparison timing in the REPL.

What's interesting (to me) is that PicoLisp is also doing recursive computations at very high speeds. I need to explore further but it's an *extremely* impressive system, and I'm amazed I wasn't aware of it before today.

@vindarel That's true. The startup time issue is particularly harsh on #clojure, and @borkdude's #Babashka would probably do a lot better.

But (a) this is very rough timing, and (b) startup time is some sort of proxy for the compactness of the runtime system; and
(c) the thing that's still astounding me is that #PicoLisp is (sort-of) an interpreter, while all the others execute compiled code, so bloody should be faster!

#Lisp

@simon_brooke I would also say that bignums implemented internally in cells are the way to go. I did so in #PicoLisp too. #lisp