#sbcl — Public Fediverse posts

Added video demonstration of DPTherm at https://gnulinux.tube/w/mVyrHiVmT568F3QAG45h6p

#freesoftware #libresoftware #sbcl #commonlisp #thermal #engineering #agplv3

Added video demonstration of DPTherm at https://gnulinux.tube/w/mVyrHiVmT568F3QAG45h6p

#sbcl #commonlisp #thermal #engineering #agplv3 #libresoftware

@djl So far I have learned and experimented with #SBCL only. Though I used it preliminary on Debian, I installed it on Windows also to make binaries for Window$

How about #GNU #Guile. I will try it when I use #Guix and I think my learning of Lisp would be useful for many dialects, right?

Btw, I released my first code under #AGPLV3

@djl So far I have learned and experimented with #SBCL only. Though I used it preliminary on Debian, I installed it on Windows also to make binaries for Window$

How about #GNU #Guile. I will try it when I use #Guix and I think my learning of Lisp would be useful for many dialects, right?

Btw, I released my first code under #AGPLV3

@djl So far I have learned and experimented with #SBCL only. Though I used it preliminary on Debian, I installed it on Windows also to make binaries for Window$

How about #GNU #Guile. I will try it when I use #Guix and I think my learning of Lisp would be useful for many dialects, right?

Btw, I released my first code under #AGPLV3

@djl So far I have learned and experimented with #SBCL only. Though I used it preliminary on Debian, I installed it on Windows also to make binaries for Window$

How about #GNU #Guile. I will try it when I use #Guix and I think my learning of Lisp would be useful for many dialects, right?

Btw, I released my first code under #AGPLV3

@djl So far I have learned and experimented with #SBCL only. Though I used it preliminary on Debian, I installed it on Windows also to make binaries for Window$

How about #GNU #Guile. I will try it when I use #Guix and I think my learning of Lisp would be useful for many dialects, right?

Btw, I released my first code under #AGPLV3

🚀 Ah, the riveting world of #SBCL #assembly code, where 5 whole bytes are shaved off for a more *efficient* space-wasting experience. Paul Khuong and friends #debate byte-lengths like they're splitting atoms, because clearly, optimizing a few machine instructions is the apex of #programming 🧠✨.
https://pvk.ca/Blog/2014/03/15/sbcl-the-ultimate-assembly-code-breadboard/ #byte-optimization #efficient #machine-instructions #HackerNews #ngated

🚀 Ah, the riveting world of #SBCL #assembly code, where 5 whole bytes are shaved off for a more *efficient* space-wasting experience. Paul Khuong and friends #debate byte-lengths like they're splitting atoms, because clearly, optimizing a few machine instructions is the apex of #programming 🧠✨.
https://pvk.ca/Blog/2014/03/15/sbcl-the-ultimate-assembly-code-breadboard/ #byte-optimization #efficient #machine-instructions #HackerNews #ngated

SBCL: The Assembly Code Breadboard (2014)

https://pvk.ca/Blog/2014/03/15/sbcl-the-ultimate-assembly-code-breadboard/

#HackerNews #SBCL #AssemblyCode #Breadboard #2014 #HackersNews #Programming

SBCL: The Assembly Code Breadboard (2014)

https://pvk.ca/Blog/2014/03/15/sbcl-the-ultimate-assembly-code-breadboard/

#HackerNews #SBCL #AssemblyCode #Breadboard #2014 #HackersNews #Programming

SBCL: The Assembly Code Breadboard (2014)

https://pvk.ca/Blog/2014/03/15/sbcl-the-ultimate-assembly-code-breadboard/

#HackerNews #SBCL #AssemblyCode #Breadboard #2014 #HackersNews #Programming

SBCL: The Assembly Code Breadboard (2014)

https://pvk.ca/Blog/2014/03/15/sbcl-the-ultimate-assembly-code-breadboard/

#HackerNews #SBCL #AssemblyCode #Breadboard #2014 #HackersNews #Programming

SBCL: The Assembly Code Breadboard (2014)

https://pvk.ca/Blog/2014/03/15/sbcl-the-ultimate-assembly-code-breadboard/

#HackerNews #SBCL #AssemblyCode #Breadboard #2014 #HackersNews #Programming

SBCL Fibers – Lightweight Cooperative Threads

https://atgreen.github.io/repl-yell/posts/sbcl-fibers/

#HackerNews #SBCL #Fibers #Lightweight #Cooperative #Threads #Technology #Innovation #Programming #Languages

SBCL Fibers – Lightweight Cooperative Threads

https://atgreen.github.io/repl-yell/posts/sbcl-fibers/

#HackerNews #SBCL #Fibers #Lightweight #Cooperative #Threads #Technology #Innovation #Programming #Languages

SBCL Fibers – Lightweight Cooperative Threads

https://atgreen.github.io/repl-yell/posts/sbcl-fibers/

#HackerNews #SBCL #Fibers #Lightweight #Cooperative #Threads #Technology #Innovation #Programming #Languages

SBCL Fibers – Lightweight Cooperative Threads

https://atgreen.github.io/repl-yell/posts/sbcl-fibers/

#HackerNews #SBCL #Fibers #Lightweight #Cooperative #Threads #Technology #Innovation #Programming #Languages

SBCL Fibers – Lightweight Cooperative Threads

https://atgreen.github.io/repl-yell/posts/sbcl-fibers/

#HackerNews #SBCL #Fibers #Lightweight #Cooperative #Threads #Technology #Innovation #Programming #Languages

I've been a #DoomEmacs user for some time, now, even having curated my own literate config out of their "static" files - along with all the extra stuff one adds to such a thing.

As one does, in the past I've also attempted to do my own #emacs config from scratch, usually falling into the "let's recreate doom!" hole, whether I wanted to or not (thus the reason I just went the route I did).

Over the past couple of months I've decided to - slowly - do the emacs bankruptcy declaration. Now, just to make things even more interesting I have decided against the use-package macro. Why? Because why not!

I've been using my scratch build for a month or so, haven't even opened my doom config up. It's been a great process, learning process, more understand of the process. It helps that I've been on a learn lisp quest for the past couple of years, too (#CommonLisp, #sbcl, #clojure, #elisp of course).

The large emacs distros are great an an excellent way to find curated packages. Doom is even a really nice framework. Sometimes you just want to do your own thing.

I've been a #DoomEmacs user for some time, now, even having curated my own literate config out of their "static" files - along with all the extra stuff one adds to such a thing.

As one does, in the past I've also attempted to do my own #emacs config from scratch, usually falling into the "let's recreate doom!" hole, whether I wanted to or not (thus the reason I just went the route I did).

Over the past couple of months I've decided to - slowly - do the emacs bankruptcy declaration. Now, just to make things even more interesting I have decided against the use-package macro. Why? Because why not!

I've been using my scratch build for a month or so, haven't even opened my doom config up. It's been a great process, learning process, more understand of the process. It helps that I've been on a learn lisp quest for the past couple of years, too (#CommonLisp, #sbcl, #clojure, #elisp of course).

The large emacs distros are great an an excellent way to find curated packages. Doom is even a really nice framework. Sometimes you just want to do your own thing.

I updated my "is #guile fast?" page with the new r7rs #benchmarks data and anchored Guile and #Chez in the benchmarksgame:

#Scheme benchmarks: https://www.draketo.de/software/guile-fast#other-schemes
Compared to other languages: https://www.draketo.de/software/guile-fast#other-languages

Chez is roughly factor 7 slower than C,
Guile roughly factor 18
(#Java 3.5, #SBCL 5, #Racket 12, #Ruby 60 and #Python 70)

I updated my "is #guile fast?" page with the new r7rs #benchmarks data and anchored Guile and #Chez in the benchmarksgame:

#Scheme benchmarks: https://www.draketo.de/software/guile-fast#other-schemes
Compared to other languages: https://www.draketo.de/software/guile-fast#other-languages

Chez is roughly factor 7 slower than C,
Guile roughly factor 18
(#Java 3.5, #SBCL 5, #Racket 12, #Ruby 60 and #Python 70)

The operating system is a Debian trixie derivative. Out of the box, it has Firefox 131.0.2 and Xfce 4.18. apt-get install build-essential gave me gcc-14; other items in the repos: nodejs 20.17.0, emacs 29.4, golang 1.23. Elixir's still at 1.14.0 (aside: erlang won't get a JIT for RISC-V any time soon), Python's at 3.12, rustc 1.80.1 (but of course you can use rustup).

Anyway, on to some benchmarks. glmark2-es2 reports a score of 1714, which is surprisingly 38% higher than @geerlingguy 's benchmark of the HiFive Premier P550.

My real test is compiling sbcl; it's not in Debian or Ubuntu's repositories for RISC-V. I bootstrap it with GNU CLISP, and then rebuild it with itself, with sh ./make.sh --with-sb-doc --without-sb-thread. Unfortunately, I believe the build is single-core; I'm not sure if it's possible to use all the cores on my system for it.

Times to rebuild sbcl with itself, including modules:

Lichee Pi 3A (Ubuntu 24.04 derivative): 30 minutes
VisionFive 2 (Ubuntu 24.04):            20 minutes
Megrez (Debian trixie derivative):      12 minutes
Ryzen 9900x (Ubuntu 24.04):              1 minute

So, progress, but a long way to go.

(Incidentally, both the Megrez and my desktop have 6400 memory.)

#milkv #megrez #riscv #sbcl

The operating system is a Debian trixie derivative. Out of the box, it has Firefox 131.0.2 and Xfce 4.18. apt-get install build-essential gave me gcc-14; other items in the repos: nodejs 20.17.0, emacs 29.4, golang 1.23. Elixir's still at 1.14.0 (aside: erlang won't get a JIT for RISC-V any time soon), Python's at 3.12, rustc 1.80.1 (but of course you can use rustup).

Anyway, on to some benchmarks. glmark2-es2 reports a score of 1714, which is surprisingly 38% higher than @geerlingguy 's benchmark of the HiFive Premier P550.

My real test is compiling sbcl; it's not in Debian or Ubuntu's repositories for RISC-V. I bootstrap it with GNU CLISP, and then rebuild it with itself, with sh ./make.sh --with-sb-doc --without-sb-thread. Unfortunately, I believe the build is single-core; I'm not sure if it's possible to use all the cores on my system for it.

Times to rebuild sbcl with itself, including modules:

Lichee Pi 3A (Ubuntu 24.04 derivative): 30 minutes
VisionFive 2 (Ubuntu 24.04):            20 minutes
Megrez (Debian trixie derivative):      12 minutes
Ryzen 9900x (Ubuntu 24.04):              1 minute

So, progress, but a long way to go.

(Incidentally, both the Megrez and my desktop have 6400 memory.)

#milkv #megrez #riscv #sbcl

The operating system is a Debian trixie derivative. Out of the box, it has Firefox 131.0.2 and Xfce 4.18. apt-get install build-essential gave me gcc-14; other items in the repos: nodejs 20.17.0, emacs 29.4, golang 1.23. Elixir's still at 1.14.0 (aside: erlang won't get a JIT for RISC-V any time soon), Python's at 3.12, rustc 1.80.1 (but of course you can use rustup).

Anyway, on to some benchmarks. glmark2-es2 reports a score of 1714, which is surprisingly 38% higher than @geerlingguy 's benchmark of the HiFive Premier P550.

My real test is compiling sbcl; it's not in Debian or Ubuntu's repositories for RISC-V. I bootstrap it with GNU CLISP, and then rebuild it with itself, with sh ./make.sh --with-sb-doc --without-sb-thread. Unfortunately, I believe the build is single-core; I'm not sure if it's possible to use all the cores on my system for it.

Times to rebuild sbcl with itself, including modules:

Lichee Pi 3A (Ubuntu 24.04 derivative): 30 minutes
VisionFive 2 (Ubuntu 24.04):            20 minutes
Megrez (Debian trixie derivative):      12 minutes
Ryzen 9900x (Ubuntu 24.04):              1 minute

So, progress, but a long way to go.

(Incidentally, both the Megrez and my desktop have 6400 memory.)

#milkv #megrez #riscv #sbcl

The operating system is a Debian trixie derivative. Out of the box, it has Firefox 131.0.2 and Xfce 4.18. apt-get install build-essential gave me gcc-14; other items in the repos: nodejs 20.17.0, emacs 29.4, golang 1.23. Elixir's still at 1.14.0 (aside: erlang won't get a JIT for RISC-V any time soon), Python's at 3.12, rustc 1.80.1 (but of course you can use rustup).

Anyway, on to some benchmarks. glmark2-es2 reports a score of 1714, which is surprisingly 38% higher than @geerlingguy 's benchmark of the HiFive Premier P550.

My real test is compiling sbcl; it's not in Debian or Ubuntu's repositories for RISC-V. I bootstrap it with GNU CLISP, and then rebuild it with itself, with sh ./make.sh --with-sb-doc --without-sb-thread. Unfortunately, I believe the build is single-core; I'm not sure if it's possible to use all the cores on my system for it.

Times to rebuild sbcl with itself, including modules:

Lichee Pi 3A (Ubuntu 24.04 derivative): 30 minutes
VisionFive 2 (Ubuntu 24.04):            20 minutes
Megrez (Debian trixie derivative):      12 minutes
Ryzen 9900x (Ubuntu 24.04):              1 minute

So, progress, but a long way to go.

(Incidentally, both the Megrez and my desktop have 6400 memory.)

#milkv #megrez #riscv #sbcl

Having been informed of the Autumn Lisp Game Jam coming up: how's #CommonLisp GC performance for games nowadays? Last I checked, it seemed like all the major libre CL impls (mainly #SBCL & #Clozure) went full stop-the-world, which feels like a recipe for latency spikes. I saw flashes of stuff on sbcl-devel a while back about someone working on a lower-latency GC, but I don't know whether it got anywhere.

#itch_io #itch #devlog mid-voting-week #gameDev
In which I #install and #play my #lisp #sbcl #clim #McCLIM #turtleDrawing #game
https://lispy-gopher-show.itch.io/logos-lisp-legend/devlog/738933/lll-success-mac-obsd-linux-and-live-videos-channel

https://toobnix.org/w/khxRivsFVFkpQKBAWvM2ek

#Inaugural #toobnix
#howTo #lisp #commonLisp #sbcl #quicklisp #McCLIM #openbsd #video #gameDevAdjacent
in so many words. Five relaxed minutes.

The rest of this week is going to be loosely #springlispgamejam2024 live->videos on here.

Thanks https://sdf.org

Follow @screwtape_channel

https://toobnix.org/w/khxRivsFVFkpQKBAWvM2ek

#Inaugural #toobnix
#howTo #lisp #commonLisp #sbcl #quicklisp #McCLIM #openbsd #video #gameDevAdjacent
in so many words. Five relaxed minutes.

The rest of this week is going to be loosely #springlispgamejam2024 live->videos on here.

Thanks https://sdf.org

Follow @screwtape_channel

#sbcl #lisp #commonLisp #asdf #executable #gui #build #tutorial #clim #mcclim #example I wrote for @theruran a while ago.

You could basically submit this with literally any modification as a game for the #springlispgamejam2024 and it will be pretty similar to mine. I think it's a great approach to featureful interactive user interfaces for games.

https://lispy-gopher-show.itch.io/logos-lisp-legend/devlog/735998/sbcl-lisp-executable-clim-gui-game-build

https://itch.io/jam/spring-lisp-game-jam-2024

Oh, I'm this 🤏 close to finishing up my work to convert #SBCL test coverage reports (`sb-cover:report`) to a format understandable by #Codecov 🕺

That would mean, to say the least, I can have test coverage report badges for my #CommonLisp projects on Github 🤤

Stay tuned 📻

Oh, I'm this 🤏 close to finishing up my work to convert #SBCL test coverage reports (`sb-cover:report`) to a format understandable by #Codecov 🕺

That would mean, to say the least, I can have test coverage report badges for my #CommonLisp projects on Github 🤤

Stay tuned 📻

Released an updated version (0.3.1) of sijo-doctest, a #doctest library for
#CommonLisp.

This includes some quality of life features, bugfixes and support for #SBCL, #ECL, #CCL and #ABCL.

https://github.com/simendsjo/sijo-doctest

Released an updated version (0.3.1) of sijo-doctest, a #doctest library for
#CommonLisp.

This includes some quality of life features, bugfixes and support for #SBCL, #ECL, #CCL and #ABCL.

https://github.com/simendsjo/sijo-doctest

Released an updated version (0.3.1) of sijo-doctest, a #doctest library for
#CommonLisp.

This includes some quality of life features, bugfixes and support for #SBCL, #ECL, #CCL and #ABCL.

https://github.com/simendsjo/sijo-doctest

Today I also officially forked #SBCL so I can transform my constant complaining into contributing. Officially.

Might as well put #GitHub #CopilotChat to work for the whole #CommonLisp community, right?

#GitHubCopilot #GitHubCopilotChat #GenerativeAI #Lisp #OpenSource

Today I also officially forked #SBCL so I can transform my constant complaining into contributing. Officially.

Might as well put #GitHub #CopilotChat to work for the whole #CommonLisp community, right?

#GitHubCopilot #GitHubCopilotChat #GenerativeAI #Lisp #OpenSource

@freakazoid

Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?

🧷 https://www.plover.com/~mjd/misc/hbaker-archive/home.html

🌺

🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt

🏷️ #Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp

@freakazoid

Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?

🧷 https://www.plover.com/~mjd/misc/hbaker-archive/home.html

🌺

🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt

🏷️ #Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp

@freakazoid

Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?

🧷 https://www.plover.com/~mjd/misc/hbaker-archive/home.html

🌺

🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt

🏷️ #Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp

@freakazoid

Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?

🧷 https://www.plover.com/~mjd/misc/hbaker-archive/home.html

🌺

🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt

🏷️ #Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp

@freakazoid

Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?

🧷 https://www.plover.com/~mjd/misc/hbaker-archive/home.html

🌺

🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt

🏷️ #Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp

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

I guess, while I am at it, which #lisp #commonlisp should I settle on

#ClozureCL, #GnuCommonLisp #gcl, #Clisp, #SteelBankCommonLisp (#sbcl)

I guess, while I am at it, which #lisp #commonlisp should I settle on

#ClozureCL, #GnuCommonLisp #gcl, #Clisp, #SteelBankCommonLisp (#sbcl)