home.social

#babashka — Public Fediverse posts

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

  1. Every time I want to leave #lisp or #scheme based language I stumble across awesome talk which reminds me why I love it in the first place.

    fosdem.org/2026/schedule/event

    Damn #repl driven development is so damn awesome. Now a days If I need to write some automation scripts I use #babashka lot instead of #bash or #python

  2. Every time I want to leave #lisp or #scheme based language I stumble across awesome talk which reminds me why I love it in the first place.

    fosdem.org/2026/schedule/event

    Damn #repl driven development is so damn awesome. Now a days If I need to write some automation scripts I use #babashka lot instead of #bash or #python

  3. Every time I want to leave #lisp or #scheme based language I stumble across awesome talk which reminds me why I love it in the first place.

    fosdem.org/2026/schedule/event

    Damn #repl driven development is so damn awesome. Now a days If I need to write some automation scripts I use #babashka lot instead of #bash or #python

  4. I finally took the leap and started using #stow for managing my dotfiles.

    This is so amazing and once you get past the horrifying GNU documentation, it gets pretty easy, And it is simply AWESOME.

    I also created a simple helper script for stow with #babashka to make managing my dotfiles simpler.

    Now I manage dotfiles for different devices in a cohesive and super clean manner.
    Take a peek

    codeberg.org/alirezaalavi/dotf

    #dotfiles #unix #arch

  5. @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

  6. I have some scripts still in bash rather than #babashka because all they are doing is calling other programs. But the one that is in my #guix #mcron was apparently suffering for lack of controlled #ExitStatus. Oi, Bash, I never knew thee.

  7. Ek is 'n groot aanhanger van babashka om projekte mee aan te pak. Teen die einde van laasweek het ek weer na 'n AWS SAM (Serverless) projek gekyk wat op ys is, en toe probeer ek nbb in die projek gebruik. 'n Paar keer se kop krap en stoei met konsepte, maar ek is nou heel gelukkig hoe dinge uitdraai. Ek gaan waarskynlik al die Vanilla JavaScript dele vervang met ClojureScript!

    #AWS #SAM #Serverless #babashka #nbb #ClojureScript

    Ek het hier begin: github.com/babashka/nbb/blob/m

  8. Die klein gelukkies! Gister moes ek inderhaas weer 'n ou stuk kode wat ek aan gewerk het uit die argief krap en wou aanteken funksionaliteit (logging functionality) byvoeg. Voorheen het ek geweet van #MuLog vir #Clojure en wou dit in die #Babashka kode sit. Na 'n gespook leer ek van #Timbre en alles is weer reg! ❤️

    Ek moes net rond-speel hoe om die "spit appender" funksionaliteit self te doen want core appenders blyk nie beskikbaar te wees nie.

    github.com/babashka/babashka/d

  9. Die aantreklikheid van LISP-tale is dat wanneer iets werk, dit 'n redelike hoë waarborg het dat dinge nie sommer gou weer hoef te verander nie. Ek kyk byvoorbeeld na al die veranderinge in #ECMA ( #JavaScript, #TypeScript ), #Java en #Python en daar is voortdurend verbeteringe en veranderinge, en die waarborg dat dat iets MOET verander is redelik onvermydelik.

    Net nog 'n rede hoekom ek van #Clojure #ClojureScript en #Babashka hou. Goed werk en die konsepte verander bitter min.