vindarel vindarel

Install

typst
tinymist

Run Preview Server

tinymist preview main.typ

Compile To PDF

The ReadLine Wrapper (rlwrap) utility is actually a must have when you want to run SBCL from the command line, because by default, SBCL in the terminal:

doesn't offer symbol completion
doesn't offer a history of commands
doesn't even understand the arrow keys, left and right (they input [[[A instead), nor any default readline keybindings, the ones we find in bash et all: C-e, C-a, C-u, C-k, Alt-b, Alt-f etc.

We can actually fix this with rlwrap options.

How to uninstall guix

Date of creation: 2022-12-27

First of all, if the install script referenced here was used to install guix, ideally the output of that script as well as the script itself should have been saved somewhere. This makes it easier to see which components were installed and where and thus makes it easier for you to uninstall them.

As for me personally, I used the install script to install guix on a debian derivative distribution with systemd. This guide thus focuses on uninstalling guix from a debian derivative distribution but will probably work for your distribution as well with some slight changes.

Why not: from Common Lisp to Julia

This article is a response to mfiano’s From Common Lisp to Julia which might also convey some developments happening in Common Lisp. I do not intend to suggest that someone coming from a Matlab, R, or Python background should pickup Common Lisp. Julia is a reasonably good language when compared to what it intends to replace. You should pickup Common Lisp only if you are interested in programming in general, not limited to scientific computing, and envision yourself writing code for the rest of your life. It will expand your mind to what is possible, and that goes beyond the macro system. Along the same lines though, you should also pickup C, Haskell, Forth, and perhaps a few other languages that have some noteworthy things to teach, and that I too have been to lazy to learn.

/I also do not intend to offend anyone. I’m okay with criticizing Common Lisp (I myself have done it below!), but I want t

sb-simd: Multiplying a 4x4 matrix with a 4-length vector (AVX)

(require 'sb-simd)
(defpackage :simd-pack-user
  (:use :sb-simd-avx :cl))
(in-package :simd-pack-user)

I'm assuming you are referring to the following operation:

quick survey of swank interfaces in order to see what could be broken out into proper portability libraries or, more optimistically, language extensions.

this is preliminary. i pretty much just went down swank.lisp looking for definterfaces. Some other portability related things are not covered yet.

Encoding/decoding

Babel

Encode a Lisp string to an octet vector of its UTF-8 encoding
Decode an octet vector of UTF-8 to a Lisp string

Features of a Common Lispy approach to (better) Numpy

Numpy is great, in fact it’s one of the things that pulls people to Python. But can it be better?

Common Lisp is great, in fact it’s one of the things that pulls people to Common Lisp. But can it be better? Indeed Python can’t be better than Common Lisp without it becoming another Lisp. The closest we have is Julia. And while it gets some things right, Julia lacks certain features that limit the goodness of a numerical computing library.

All combined, below I will highlight some of the features that I wish a numerical computing library or ecosystem had. I also want to request the readers for their own inputs about how things can be even better. The goal amidst this is solely to keep things numpy-like. I do not intend to - nor have the background to - make a DSL like April or Petalisp.

While I take some interest in performance and numerical computing, I have m

I don't know Julia!

I saw devs leaving CL for a new graal (and eventually coming back). Grass may not be greener on the other side…

Long compilation times

You can't make it a CLI script, because it compiles the whole code WITH dependencies every time, and as soon as you import some serious libraries, compile times will skyrocket. I quickly hit 40 seconds of compilation with just geospatial lib and dataframes. These 40 seconds turned out to be A LOT when you develop interactively. And you can't build everything in a Jupyter Notebook, because eventually you'll have to switch to a CLI script.

https://news.ycombinator.com/item?id=36755618, 2023

	(defun print-dependency-graph (system-name &key (level 0))
	(loop repeat level
	do (format t " "))
	(format t "~A~%" system-name)
	(typecase system-name
	((or string symbol)
	(let ((system (asdf/system:find-system system-name)))
	(loop for dep in (asdf/system:system-depends-on system)
	do (print-dependency-graph dep :level (1+ level)))))))

	(in-package :yobabank)

	(defparameter 1pw-secure-note-name "Yobabank Data")
	(defparameter 1pw-vault "Personal")

	(defun 1pw-get-field (object name)
	(when (typep object 'st-json:jso)
	(st-json:getjso name object)))

	(defun 1pw-get-id (object)