home.social

#clisp — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #clisp, aggregated by home.social.

  1. 64 core monster, half a TB of RAM, NVME disks…. And #sbcl takes 20 minutes to compile (#GNU #clisp — I like you but you’re slow!)

  2. 64 core monster, half a TB of RAM, NVME disks…. And #sbcl takes 20 minutes to compile (#GNU #clisp — I like you but you’re slow!)

  3. 64 core monster, half a TB of RAM, NVME disks…. And #sbcl takes 20 minutes to compile (#GNU #clisp — I like you but you’re slow!)

  4. 64 core monster, half a TB of RAM, NVME disks…. And #sbcl takes 20 minutes to compile (#GNU #clisp — I like you but you’re slow!)

  5. @lxsameer that's cool! I *recently* started using because I found file navigation annoying in other IDEs. I know how to touch type, so now I literally just have to type in what I want (with all the autocompletion benefits just like a shell). Still learning the basics but finding even that awesome!

    By the way, I've been programming a bit of too, although right now I prefer the vibes :clojure: :lisp:

  6. @lxsameer that's cool! I *recently* started using #emacs because I found file navigation annoying in other IDEs. I know how to touch type, so now I literally just have to type in what I want (with all the autocompletion benefits just like a shell). Still learning the basics but finding even that awesome!

    By the way, I've been programming a bit of #Clojure too, although right now I prefer the #clisp vibes :clojure: :lisp:

  7. @lxsameer that's cool! I *recently* started using #emacs because I found file navigation annoying in other IDEs. I know how to touch type, so now I literally just have to type in what I want (with all the autocompletion benefits just like a shell). Still learning the basics but finding even that awesome!

    By the way, I've been programming a bit of #Clojure too, although right now I prefer the #clisp vibes :clojure: :lisp:

  8. @lxsameer that's cool! I *recently* started using #emacs because I found file navigation annoying in other IDEs. I know how to touch type, so now I literally just have to type in what I want (with all the autocompletion benefits just like a shell). Still learning the basics but finding even that awesome!

    By the way, I've been programming a bit of #Clojure too, although right now I prefer the #clisp vibes :clojure: :lisp:

  9. @lxsameer that's cool! I *recently* started using #emacs because I found file navigation annoying in other IDEs. I know how to touch type, so now I literally just have to type in what I want (with all the autocompletion benefits just like a shell). Still learning the basics but finding even that awesome!

    By the way, I've been programming a bit of #Clojure too, although right now I prefer the #clisp vibes :clojure: :lisp:

  10. Interesting. Git head of #Lisp HTML-generating library CL-WHO running on #Clisp :

    [1]> (in-package "CL-WHO")
    #<PACKAGE CL-WHO>
    WHO[2]> (with-html-output-to-string (out) (:a (+ 1 2)))
    "<a></a>"
    WHO[3]> (with-html-output (*standard-output*) (:a (+ 1 2)))
    <a></a>
    "</a>"

    No content in the tag!

    Documentation says that the result of (+ 1 2) should be sent to the stream as if by PRINC, thus <a>2</a>.

    I don't see a test for this.

    Doesn't work in the oldest available git commit from 2009, either.

  11. Interesting. Git head of #Lisp HTML-generating library CL-WHO running on #Clisp :

    [1]> (in-package "CL-WHO")
    #<PACKAGE CL-WHO>
    WHO[2]> (with-html-output-to-string (out) (:a (+ 1 2)))
    "<a></a>"
    WHO[3]> (with-html-output (*standard-output*) (:a (+ 1 2)))
    <a></a>
    "</a>"

    No content in the tag!

    Documentation says that the result of (+ 1 2) should be sent to the stream as if by PRINC, thus <a>2</a>.

    I don't see a test for this.

    Doesn't work in the oldest available git commit from 2009, either.

  12. Interesting. Git head of #Lisp HTML-generating library CL-WHO running on #Clisp :

    [1]> (in-package "CL-WHO")
    #<PACKAGE CL-WHO>
    WHO[2]> (with-html-output-to-string (out) (:a (+ 1 2)))
    "<a></a>"
    WHO[3]> (with-html-output (*standard-output*) (:a (+ 1 2)))
    <a></a>
    "</a>"

    No content in the tag!

    Documentation says that the result of (+ 1 2) should be sent to the stream as if by PRINC, thus <a>2</a>.

    I don't see a test for this.

    Doesn't work in the oldest available git commit from 2009, either.

  13. What u will c is 21 languages #ada #awk #bash #basic #C #clisp #C++ #COBOL #Forth #FORTRAN #go #java #lisp (mine) #lua #Pascal #Perl #Python #R #Rust #Ruby #SED calc app srvs <=>stdinout. C,C++<=> sockets, 23 thin clients /w NO dep. besides C #xcb #sockets. 21 thin server in C,translate stdin/out to/from sockets in a language agnostic way. What you WON'T see are any #browsers (1000x footprint of my thin clients) or fonts, ask for #retro computer clients youtube.com/watch?v=Esv6xHwZRY

  14. What u will c is 21 languages ++ (mine) calc app srvs <=>stdinout. C,C++<=> sockets, 23 thin clients /w NO dep. besides C . 21 thin server in C,translate stdin/out to/from sockets in a language agnostic way. What you WON'T see are any (1000x footprint of my thin clients) or fonts, ask for computer clients youtube.com/watch?v=Esv6xHwZRYc

  15. What u will c is 21 languages #ada #awk #bash #basic #C #clisp #C++ #COBOL #Forth #FORTRAN #go #java #lisp (mine) #lua #Pascal #Perl #Python #R #Rust #Ruby #SED calc app srvs <=>stdinout. C,C++<=> sockets, 23 thin clients /w NO dep. besides C #xcb #sockets. 21 thin server in C,translate stdin/out to/from sockets in a language agnostic way. What you WON'T see are any #browsers (1000x footprint of my thin clients) or fonts, ask for #retro computer clients youtube.com/watch?v=Esv6xHwZRY

  16. What u will c is 21 languages #ada #awk #bash #basic #C #clisp #C++ #COBOL #Forth #FORTRAN #go #java #lisp (mine) #lua #Pascal #Perl #Python #R #Rust #Ruby #SED calc app srvs <=>stdinout. C,C++<=> sockets, 23 thin clients /w NO dep. besides C #xcb #sockets. 21 thin server in C,translate stdin/out to/from sockets in a language agnostic way. What you WON'T see are any #browsers (1000x footprint of my thin clients) or fonts, ask for #retro computer clients youtube.com/watch?v=Esv6xHwZRY

  17. What u will c is 21 languages #ada #awk #bash #basic #C #clisp #C++ #COBOL #Forth #FORTRAN #go #java #lisp (mine) #lua #Pascal #Perl #Python #R #Rust #Ruby #SED calc app srvs <=>stdinout. C,C++<=> sockets, 23 thin clients /w NO dep. besides C #xcb #sockets. 21 thin server in C,translate stdin/out to/from sockets in a language agnostic way. What you WON'T see are any #browsers (1000x footprint of my thin clients) or fonts, ask for #retro computer clients youtube.com/watch?v=Esv6xHwZRY

  18. I feel old, can chatgpt write me some code to give #powershell the same ability to stdin/stdout that #ada, #awk, #bash, #basic, #c, #cpp, #cobol, #clisp, #go, #Forth, #Fortran, #java, #lisp, #lua, #pascal, #python, #perl, #r, #rust, #ruby, #SED all share? also if you know these langs I have tons of code u could shorten for me/us calc under bitbucket.org/timcdoc/antibrow

  19. I feel old, can chatgpt write me some code to give the same ability to stdin/stdout that , , , , , , , , , , , , , , , , , , , , all share? also if you know these langs I have tons of code u could shorten for me/us calc under bitbucket.org/timcdoc/antibrow

  20. I feel old, can chatgpt write me some code to give #powershell the same ability to stdin/stdout that #ada, #awk, #bash, #basic, #c, #cpp, #cobol, #clisp, #go, #Forth, #Fortran, #java, #lisp, #lua, #pascal, #python, #perl, #r, #rust, #ruby, #SED all share? also if you know these langs I have tons of code u could shorten for me/us calc under bitbucket.org/timcdoc/antibrow

  21. I feel old, can chatgpt write me some code to give #powershell the same ability to stdin/stdout that #ada, #awk, #bash, #basic, #c, #cpp, #cobol, #clisp, #go, #Forth, #Fortran, #java, #lisp, #lua, #pascal, #python, #perl, #r, #rust, #ruby, #SED all share? also if you know these langs I have tons of code u could shorten for me/us calc under bitbucket.org/timcdoc/antibrow

  22. I feel old, can chatgpt write me some code to give #powershell the same ability to stdin/stdout that #ada, #awk, #bash, #basic, #c, #cpp, #cobol, #clisp, #go, #Forth, #Fortran, #java, #lisp, #lua, #pascal, #python, #perl, #r, #rust, #ruby, #SED all share? also if you know these langs I have tons of code u could shorten for me/us calc under bitbucket.org/timcdoc/antibrow

  23. An unfair line comparison of #ada #awk #bash #basic #c #COBOL #clisp #Forth #FORTRAN #lisp #Pascal #Perl #Python #R #Rust (straight and with junk DNA removed using C pre processor, ya I don't know rust well) #Ruby #SED the ada c and lisp can be used as guides for optimizing if you know any of these. I'm slowly going back through now that these all work for calc bitbucket.org/timcdoc/antibrow also note these all produce the same(mostly) tiny over the wire to thin client via stdin/out

  24. An unfair line comparison of (straight and with junk DNA removed using C pre processor, ya I don't know rust well) the ada c and lisp can be used as guides for optimizing if you know any of these. I'm slowly going back through now that these all work for calc bitbucket.org/timcdoc/antibrow also note these all produce the same(mostly) tiny over the wire to thin client via stdin/out

  25. An unfair line comparison of #ada #awk #bash #basic #c #COBOL #clisp #Forth #FORTRAN #lisp #Pascal #Perl #Python #R #Rust (straight and with junk DNA removed using C pre processor, ya I don't know rust well) #Ruby #SED the ada c and lisp can be used as guides for optimizing if you know any of these. I'm slowly going back through now that these all work for calc bitbucket.org/timcdoc/antibrow also note these all produce the same(mostly) tiny over the wire to thin client via stdin/out

  26. An unfair line comparison of #ada #awk #bash #basic #c #COBOL #clisp #Forth #FORTRAN #lisp #Pascal #Perl #Python #R #Rust (straight and with junk DNA removed using C pre processor, ya I don't know rust well) #Ruby #SED the ada c and lisp can be used as guides for optimizing if you know any of these. I'm slowly going back through now that these all work for calc bitbucket.org/timcdoc/antibrow also note these all produce the same(mostly) tiny over the wire to thin client via stdin/out

  27. An unfair line comparison of #ada #awk #bash #basic #c #COBOL #clisp #Forth #FORTRAN #lisp #Pascal #Perl #Python #R #Rust (straight and with junk DNA removed using C pre processor, ya I don't know rust well) #Ruby #SED the ada c and lisp can be used as guides for optimizing if you know any of these. I'm slowly going back through now that these all work for calc bitbucket.org/timcdoc/antibrow also note these all produce the same(mostly) tiny over the wire to thin client via stdin/out

  28. This goes for the rest of you, if you can improve on the Rosetta stone 17 languages (and it won't be hard on most of them :-P ) feel free to send me a shorter/clearer version. bitbucket.org/timcdoc/antibrow then #ada #awk #bash #basic #c #clisp #COBOL #Forth #FORTRAN #Pascal #Perl #Python #R #Rust #Sed (others but these are the easiest to grok under those dirs are calc and some other apps depending. What language should I abuse next?

  29. This goes for the rest of you, if you can improve on the Rosetta stone 17 languages (and it won't be hard on most of them :-P ) feel free to send me a shorter/clearer version. bitbucket.org/timcdoc/antibrow then (others but these are the easiest to grok under those dirs are calc and some other apps depending. What language should I abuse next?

  30. This goes for the rest of you, if you can improve on the Rosetta stone 17 languages (and it won't be hard on most of them :-P ) feel free to send me a shorter/clearer version. bitbucket.org/timcdoc/antibrow then #ada #awk #bash #basic #c #clisp #COBOL #Forth #FORTRAN #Pascal #Perl #Python #R #Rust #Sed (others but these are the easiest to grok under those dirs are calc and some other apps depending. What language should I abuse next?

  31. This goes for the rest of you, if you can improve on the Rosetta stone 17 languages (and it won't be hard on most of them :-P ) feel free to send me a shorter/clearer version. bitbucket.org/timcdoc/antibrow then #ada #awk #bash #basic #c #clisp #COBOL #Forth #FORTRAN #Pascal #Perl #Python #R #Rust #Sed (others but these are the easiest to grok under those dirs are calc and some other apps depending. What language should I abuse next?

  32. This goes for the rest of you, if you can improve on the Rosetta stone 17 languages (and it won't be hard on most of them :-P ) feel free to send me a shorter/clearer version. bitbucket.org/timcdoc/antibrow then #ada #awk #bash #basic #c #clisp #COBOL #Forth #FORTRAN #Pascal #Perl #Python #R #Rust #Sed (others but these are the easiest to grok under those dirs are calc and some other apps depending. What language should I abuse next?

  33. TIL: every run of #SBCL has the same initial `*random-state*`, so sequences of pseudo-random numbers are not so random. The solution is super simple: `(setf *random-state* (make-random-state t))`.
    It makes sense considering what a #Lisp image is... but it's still pretty surprising compared to other programming languages. (And doesn't happen in #ECL or #clisp 😅)

    #CommonLisp

  34. TIL: every run of #SBCL has the same initial `*random-state*`, so sequences of pseudo-random numbers are not so random. The solution is super simple: `(setf *random-state* (make-random-state t))`.
    It makes sense considering what a #Lisp image is... but it's still pretty surprising compared to other programming languages. (And doesn't happen in #ECL or #clisp 😅)

    #CommonLisp

  35. TIL: every run of #SBCL has the same initial `*random-state*`, so sequences of pseudo-random numbers are not so random. The solution is super simple: `(setf *random-state* (make-random-state t))`.
    It makes sense considering what a #Lisp image is... but it's still pretty surprising compared to other programming languages. (And doesn't happen in #ECL or #clisp 😅)

    #CommonLisp

  36. TIL: every run of #SBCL has the same initial `*random-state*`, so sequences of pseudo-random numbers are not so random. The solution is super simple: `(setf *random-state* (make-random-state t))`.
    It makes sense considering what a #Lisp image is... but it's still pretty surprising compared to other programming languages. (And doesn't happen in #ECL or #clisp 😅)

    #CommonLisp

  37. TIL: every run of #SBCL has the same initial `*random-state*`, so sequences of pseudo-random numbers are not so random. The solution is super simple: `(setf *random-state* (make-random-state t))`.
    It makes sense considering what a #Lisp image is... but it's still pretty surprising compared to other programming languages. (And doesn't happen in #ECL or #clisp 😅)

    #CommonLisp

  38. Where are my #clisp peeps? I suspect most lisps can do these kinds of self surgery on themselves, hopefully close to just as easily as the lisps I've written? Not the right way to write factorial, but hints at ways to write self compilers etc. I never did add macros, but I've never needed them.

  39. Where are my peeps? I suspect most lisps can do these kinds of self surgery on themselves, hopefully close to just as easily as the lisps I've written? Not the right way to write factorial, but hints at ways to write self compilers etc. I never did add macros, but I've never needed them.

  40. Where are my #clisp peeps? I suspect most lisps can do these kinds of self surgery on themselves, hopefully close to just as easily as the lisps I've written? Not the right way to write factorial, but hints at ways to write self compilers etc. I never did add macros, but I've never needed them.

  41. Where are my #clisp peeps? I suspect most lisps can do these kinds of self surgery on themselves, hopefully close to just as easily as the lisps I've written? Not the right way to write factorial, but hints at ways to write self compilers etc. I never did add macros, but I've never needed them.

  42. Where are my #clisp peeps? I suspect most lisps can do these kinds of self surgery on themselves, hopefully close to just as easily as the lisps I've written? Not the right way to write factorial, but hints at ways to write self compilers etc. I never did add macros, but I've never needed them.

  43. #clisp mostly working #altair emulator runs 4K #BASIC but sin() is broken, should fix it today. 5717 bytes of human readable over the wire to a 252K footprint thin client with no fluffy dependencies. and no 300M footprint browser. Shown are all the commands including 5 RLE HRBitmaps over the thin client on the other end of the cloud/network. code on bitbucket timcdoc antibrowser clisp altair

  44. mostly working emulator runs 4K but sin() is broken, should fix it today. 5717 bytes of human readable over the wire to a 252K footprint thin client with no fluffy dependencies. and no 300M footprint browser. Shown are all the commands including 5 RLE HRBitmaps over the thin client on the other end of the cloud/network. code on bitbucket timcdoc antibrowser clisp altair