Due to popular demand :) Maak is now also available as an experimental Docker container, from DockerHub (also compatible with Podman).

https://hub.docker.com/repository/docker/jjba23/maak/general

You can also build images of maak yourself, using guix pack. See the maak.scm file for more. To load these tarball images, you can do podman load < my.tar.gz

Then you can run Maak from the container, and bind your local filesystem to give access, for example:

docker container run -v /home/joe:/home/joe
docker.io/jjba23/maak:latest maak -f /home/joe/hacking/maak/maak.scm --list

Hey all I have an experimental Docker/Podman build here, which you can take for a spin, it works well for me, I don’t have any macOS devices to test on yet though, LMK.

Docker tarball hosted on 2 sites: https://limewire.com/d/IHVnx#Pz9q6EwDwL https://filebin.net/gevqik62yzwfxa8u/maak-docker.tar.gz

Once you downloaded this tarball, you can import it with docker load < my.tar.gz

Installing via Guix will always remain more convenient and powerful but docker/podman will work for cross-platform pretty good. Say for example you have a maak file with a task serve, at /home/joe/hacking/hygguile/maak.scm , you could run it as so:

docker container run -v /home/joe:/home/joe localhost/maak:latest maak -f /home/joe/hacking/hygguile/maak.scm serve

I find it funny that you call Lisps and Emacs obsolete and dead, when they are more alive than ever. I agree with most of the article, but I think you ignore what makes these two great

There are many reasons why a Lisp is a great fit for most software. More specifically, websites are tree like data structures, and you really can’t beat Lisps at that, due to homoiconicity and so much more. some thoughts here:

https://jointhefreeworld.org/blog/articles/lisps/why-i-program-in-lisp/index.html

v0.0.14 now uses libcurl and works nicely :)

         (file-port (open-input-file the-file))
         (handle (curl-easy-init))
         (_ (begin
              (curl-easy-setopt handle
                                'url
                                (format #f "smtp://~a:~a" access-server
                                        access-port))
              (curl-easy-setopt handle
                                'verbose #t)
              (curl-easy-setopt handle
                                'use-ssl 1)
              (curl-easy-setopt handle
                                'username access-key)
              (curl-easy-setopt handle
                                'password access-secret)
              (curl-easy-setopt handle
                                'mail-from from-address)
              (curl-easy-setopt handle
                                'mail-rcpt
                                (list to-address))
              (curl-easy-setopt handle
                                'readdata file-port)
              (curl-easy-setopt handle
                                'upload #t)))
         (r (curl-easy-perform handle #t))
         (rr (catch #t
                    (lambda ()
                      (bytevector->string r "utf-8"))
                    (lambda (key . args)
                      r))))

i understand the mixed feelings about AI, but I think we should stop and think that we sometimes have nice and fun use cases, like image generation

Sorry you feel this way ! my code is completely artisanal you might say, I only use AI for code comments and docstrings that is all. in that regard it is useful as a tool. i understand the world has now very mixed feelings about it, but it’s just another tool for us digital carpenters.

nice idea! it is definitely a better approach that i will consider, thanks

it’s quite a good idea actually to have inter-instance communication! i will have to put more thought into it, but definitely added to the TODOs

the like system is a sort of trust score, kinda like stars in ultimate guitar, so the community can downvote entries and that will help filter out bad content

I think it is certainly possible to do , but I think it is not really something interesting for most people. I therefore think that it is easier to handle it all on wikimusic side, also considering permissions and content per instance, etc