1.1--- a/.hgsub	Fri Dec 29 00:45:18 2023 -0500
     1.2+++ b/.hgsub	Wed Jan 10 19:02:43 2024 -0500
     1.3@@ -1,2 +1,2 @@
     1.4-blog=https://lab.rwest.io/comp/blog
     1.5-docs=https://lab.rwest.io/comp/docs
     1.6\ No newline at end of file
     1.7+blog=https://vc.compiler.company/comp/blog
     1.8+docs=https://vc.compiler.company/comp/docs
     1.9\ No newline at end of file

     2.1--- a/.hgsubstate	Fri Dec 29 00:45:18 2023 -0500
     2.2+++ b/.hgsubstate	Wed Jan 10 19:02:43 2024 -0500
     2.3@@ -1,2 +1,2 @@
     2.4 b6380832df99ead6c390a664bdf3b5623444a978 blog
     2.5-46fb6a10d2e14a3aee504f5597e0fd79a80ac590 docs
     2.6+2601788ab8056c66fed0fb2c63acbda1fb617576 docs

     3.1--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     3.2+++ b/notes/20240103.org	Wed Jan 10 19:02:43 2024 -0500
     3.3@@ -0,0 +1,27 @@
     3.4+* [[https://github.com/sigmf/SigMF][SigMF]]
     3.5+#+begin_quote
     3.6+Sharing sets of recorded signal data is an important part of science
     3.7+and engineering. It enables multiple parties to collaborate, is often
     3.8+a necessary part of reproducing scientific results (a requirement of
     3.9+scientific rigor), and enables sharing data with those who do not have
    3.10+direct access to the equipment required to capture it.
    3.11+
    3.12+Unfortunately, these datasets have historically not been very
    3.13+portable, and there is not an agreed upon method of sharing metadata
    3.14+descriptions of the recorded data itself. This is the problem that
    3.15+SigMF solves.
    3.16+
    3.17+By providing a standard way to describe data recordings, SigMF
    3.18+facilitates the sharing of data, prevents the "bitrot" of datasets
    3.19+wherein details of the capture are lost over time, and makes it
    3.20+possible for different tools to operate on the same dataset, thus
    3.21+enabling data portability between tools and workflows.
    3.22+#+end_quote
    3.23+
    3.24+the-spec: https://github.com/sigmf/SigMF/blob/sigmf-v1.x/sigmf-spec.md
    3.25+* [[https://www.libvolk.org/][LibVOLK]]
    3.26+Vector-Optimized Library of Kernels (simd)
    3.27+* [[https://docs.kernel.org/fb/framebuffer.html][/dev/fb*]]
    3.28+framebuffers, used by fbgrab/fbcat program
    3.29+* [[https://docs.kernel.org/block/ublk.html][ublk]]
    3.30+https://github.com/ming1/ubdsrv

     4.1--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     4.2+++ b/notes/20240104.org	Wed Jan 10 19:02:43 2024 -0500
     4.3@@ -0,0 +1,6 @@
     4.4+goals:
     4.5+make problems smaller.
     4.6+
     4.7+sections:
     4.8+why lisp?
     4.9+- doesn't need mentioning more and more

     5.1--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     5.2+++ b/notes/vocab	Wed Jan 10 19:02:43 2024 -0500
     5.3@@ -0,0 +1,19 @@
     5.4+;;; docs/vocab --- project glossary -*- mode:outline;outline-regexp:"[-]+" -*-
     5.5+- wrt : With Respect To
     5.6+- nyi : Not Yet Implemented
     5.7+- rt : Regression Testing
     5.8+- vm : Virtual Machine
     5.9+- asm : Assembly
    5.10+- comp : Compiler
    5.11+- eval : Evaluate
    5.12+- alloc : Allocate
    5.13+- ret : Return
    5.14+- tco : Tail-call Optimization
    5.15+- reg : Register
    5.16+- sbcl : Steel Bank Common Lisp
    5.17+- rs : Rust (the language)
    5.18+- el : Emacs Lisp
    5.19+- cl : Common Lisp
    5.20+- pcl : Practical Common Lisp
    5.21+- taomop : The Art of the Meta Object Protocol
    5.22+- lol : Let Over Lambda