#picolisp — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #picolisp, aggregated by home.social.
-
🌐 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 -
🌐 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 -
🌐 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 -
🌐 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
-
@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 -
@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 -
@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 -
@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 -
@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 -
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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.
-
@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! -
@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! -
@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! -
@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! -
@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! -
40 days left to the submission deadline of #EuropeanLispSymposium (#ELSConf) in #Amsterdam:
🧷 (Friendica) https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682
🦎 (Matrix) https://matrix.to/#/!gqlYAZsfzSnmFNEHAT:magdeburg.jetzt/$z7kGECRQluF1iZzNhW-0I1e3lUmg-pff8PcAh96gox4
🦎 (Telegram) https://telegram.me/FamilyOfLisp/309
🌺
🏷️ #Lisp #Scheme #CommonLisp #Clojure #Racket #Emacs #ACL2 #AutoLisp # ISLisp #DylanLang #SKILL #Hy #Shen #Carp #Janet #uLisp #Picolisp #Gamelisp #TXR #InterLisp #Medley #OpenGenera #Symbolics #ThinkingMachines #ConnectionMachine #MultiLisp #AMOP #CLOS #SICP #PAIP #AIMA #Lambda #CLtL2 #HTDP
-
40 days left to the submission deadline of #EuropeanLispSymposium (#ELSConf) in #Amsterdam:
🧷 (Friendica) https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682
🦎 (Matrix) https://matrix.to/#/!gqlYAZsfzSnmFNEHAT:magdeburg.jetzt/$z7kGECRQluF1iZzNhW-0I1e3lUmg-pff8PcAh96gox4
🦎 (Telegram) https://telegram.me/FamilyOfLisp/309
🌺
🏷️ #Lisp #Scheme #CommonLisp #Clojure #Racket #Emacs #ACL2 #AutoLisp # ISLisp #DylanLang #SKILL #Hy #Shen #Carp #Janet #uLisp #Picolisp #Gamelisp #TXR #InterLisp #Medley #OpenGenera #Symbolics #ThinkingMachines #ConnectionMachine #MultiLisp #AMOP #CLOS #SICP #PAIP #AIMA #Lambda #CLtL2 #HTDP
-
40 days left to the submission deadline of #EuropeanLispSymposium (#ELSConf) in #Amsterdam:
🧷 (Friendica) https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682
🦎 (Matrix) https://matrix.to/#/!gqlYAZsfzSnmFNEHAT:magdeburg.jetzt/$z7kGECRQluF1iZzNhW-0I1e3lUmg-pff8PcAh96gox4
🦎 (Telegram) https://telegram.me/FamilyOfLisp/309
🌺
🏷️ #Lisp #Scheme #CommonLisp #Clojure #Racket #Emacs #ACL2 #AutoLisp # ISLisp #DylanLang #SKILL #Hy #Shen #Carp #Janet #uLisp #Picolisp #Gamelisp #TXR #InterLisp #Medley #OpenGenera #Symbolics #ThinkingMachines #ConnectionMachine #MultiLisp #AMOP #CLOS #SICP #PAIP #AIMA #Lambda #CLtL2 #HTDP
-
While looking into how viable it is to write Android applications in something else than Java, Kotlin or <insert web technology>, I've found a neat #picolisp blog explaining Pilbox and adjacent topics:
-
While looking into how viable it is to write Android applications in something else than Java, Kotlin or <insert web technology>, I've found a neat #picolisp blog explaining Pilbox and adjacent topics:
-
On #Friendica and #Telegram:
›Call for Papers — 16th European #Lisp Symposium — #ELSConf —#Amsterdam — 2023-04-24/25‹
🔗 Friendica: https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682
🦎 Telegram: https://t.me/FamilyOfLisp/309
🌺
🏷️ #CommonLisp #Scheme #EmacsLisp #Clojure #Racket #ACL2 #AutoLisp #ISLISP #DylanLang #SKILL #Hy #Shen #Carp #Janet #Jank #uLisp #Picolisp #Gamelisp #TXR #FunctionalProgramming #AMOP #SICP #CLOS #PAIP #CLtL2 #AIMA #Emacs #VIM #LispWorks #AllegroCommonLisp #ACL #CLISP #SBCL #MetaObject #MetaObjectSystem
-
On #Friendica and #Telegram:
›Call for Papers — 16th European #Lisp Symposium — #ELSConf —#Amsterdam — 2023-04-24/25‹
🔗 Friendica: https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682
🦎 Telegram: https://t.me/FamilyOfLisp/309
🌺
🏷️ #CommonLisp #Scheme #EmacsLisp #Clojure #Racket #ACL2 #AutoLisp #ISLISP #DylanLang #SKILL #Hy #Shen #Carp #Janet #Jank #uLisp #Picolisp #Gamelisp #TXR #FunctionalProgramming #AMOP #SICP #CLOS #PAIP #CLtL2 #AIMA #Emacs #VIM #LispWorks #AllegroCommonLisp #ACL #CLISP #SBCL #MetaObject #MetaObjectSystem
-
@lispnik @lojikil @anticomputer
By ›the thick blue book‹, do you mean ›Lisp Lore‹?
→ https://t.me/FamilyOfLisp/389
🌺
🏷️ #LispMachine #InterLisp #LispLore #ISLisp #CommonLisp #Picolisp
-
@lispnik @lojikil @anticomputer
By ›the thick blue book‹, do you mean ›Lisp Lore‹?
→ https://t.me/FamilyOfLisp/389
🌺
🏷️ #LispMachine #InterLisp #LispLore #ISLisp #CommonLisp #Picolisp
-
@lojikil @jpreisendoerfer @anticomputer So jealous you have coworkers to discuss #lisp with at depth :-)
I've dabbled with ISLisp and InterLisp (have the thick blue book on InterLisp and have played with emulator). Mostly I use #commonlisp but lately I've been taking another look at #picolisp
-
@lojikil @jpreisendoerfer @anticomputer So jealous you have coworkers to discuss #lisp with at depth :-)
I've dabbled with ISLisp and InterLisp (have the thick blue book on InterLisp and have played with emulator). Mostly I use #commonlisp but lately I've been taking another look at #picolisp
-
16th #EuropeanLispSymposium
— #CallForPapers —EDIT:
For easier reading and dissemination, the content of this toot was moved to the following place in the #Fediverse:
🔗 https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682
It is also available on Telegram:
🦎 https://t.me/FamilyOfLisp/309
🏷️ #Lisp #CommonLisp #Scheme #Emacs #Clojure #Racket #ACL2 #AutoLisp #ISLISP #DylanLang #SKILL #Hy #Shen #Carp #Janet #uLisp #Picolisp #Gamelisp #TXR #MOP #CLOS #CfP
-
16th #EuropeanLispSymposium
— #CallForPapers —The #ELSConf invites high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way.
🏷️ #Lisp #CommonLisp #Scheme #Emacs #Clojure #Racket #ACL2 #AutoLisp #ISLISP #Dylan #SKILL #Hy #Shen #Carp #Janet #uLisp #Picolisp #Gamelisp #TXR #MOP #CLOS #CfP
-
16th #EuropeanLispSymposium
— #CallForPapers —🔭 Scope 🔭
The #ELSConf is a premier forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp dialects, including #CommonLisp, #Scheme, #Emacs #Lisp, #Clojure, #Racket, #ACL2, #AutoLisp, #ISLISP, #Dylan, #SKILL, #Hy, #Shen, #Carp, #Janet, #uLisp, #Picolisp, #Gamelisp, #TXR, and so on.
We encourage everyone interested in Lisp to participate!
-
16th #EuropeanLispSymposium
— #CallForPapers —April 24-25, 2023
Startup Village, #Amsterdam (NL)➡️ https://www.european-lisp-symposium.org/2023
📅 Important Dates 📅
➡️ 2023-02-26 — Submission deadline
➡️ 2023-03-26 — Author notification
➡️ 2023-04-09 — Final Papers Due
➡️ 2023-04-24 — Day 1, Monday
➡️ 2023-04-25 — Day 2, Tuesday🏷️ #ELSConf #Lisp #CommonLisp #Scheme #Emacs #Clojure #Racket #ACL2 #AutoLisp #ISLISP #Dylan #SKILL #Hy #Shen #Carp #Janet #uLisp #Picolisp #Gamelisp #TXR #MOP #CLOS #CfP #AMOP
