# HG changeset patch # User Richard Westhaver # Date 1714348305 14400 # Node ID 87b04952fb18f2eb67d3ca17ae1c745c6aa91c44 init diff -r 000000000000 -r 87b04952fb18 .hgignore --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/.hgignore Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,1 @@ +[.]html \ No newline at end of file diff -r 000000000000 -r 87b04952fb18 20230730.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20230730.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,36 @@ +* VC infrastructure +In heptapod we have a root group named =comp=, containg a variety of +subgroups. Some of these groups should be public, while others are +internal to comp members exclusively. Within each subgroup, we should +have the root group members automatically granted privileged access to +projects. This is relevant for the =startup= subgroup in particular, +where each project is potentially maintained by multiple non-root +contributors. + +We also need to consider how we will manage subrepos across the +organization. It is about time we start integrating HG bundles and +potentially mirrors. For our core VC pipeline we should have no +reliance on Git, but this may be difficult. It depends on the behavior +of HG bundles. + +Bookmarks/tags should be used for milestones in the root group and are +infrequent. They are more frequent in projects with a regular release +life-cycle. +* Approaching Webapps +I started poking around in the webapp space again so that I can launch +a landing page for NAS-T quickly. The Rust situation has improved +somewhat on the frontend side, and the axum backend stack is nice. + +This might seem like a lot of Rust and not a lot of Lisp, which it is, +but there's still room for Lisp wherever we need it. It mostly plays a +role in the backend, servicing the database and responding to requests +from the Rust edges. All of the important tests for the web APIs are +also written in Lisp. We will almost certainly use Lisp for all static +processing and HTML generation at compile-time. + +This I believe, is the appropriate way to integrate Lisp into a +cutting-edge web-app. You get the good parts of Lisp where you need +them (interactive debugging, dynamic language, REPL) and avoid the bad +parts (OOB optimization, RPS performance) in areas where the customer +would be impacted. In this domain, Lisp takes the form of a glue +rather than the bricks and mortar it sometimes appears to us as. diff -r 000000000000 -r 87b04952fb18 20231024.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231024.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,59 @@ +* virt +** QEMU +** KVM +** Hyper-V +** Firecracker +** Docker +** Vagrant +** LXC +** LXD +** containerd +** systemd-nspawn +** VirtualBox + +* Concatenative +** Factor :factor: +- [2023-07-04 Tue] + Factor is a cool concatenative lang but unfortunately the C interface + (vm/master.h) no longer exists on the master branch. +** Joy :joy: + +*** https://hypercubed.github.io/joy/html/j02maf.html + +*** [[https://builds.openlogicproject.org/content/incompleteness/arithmetization-syntax/arithmetization-syntax.pdf][arithmetization of syntax]] +* Lisp :lisp: +These notes pertain to Lisp. More specifically, ANSI Common Lisp in +most places. + +- https://github.com/lispnik/iup/ - doesn't support MacOS yet, looks + cool though + - what we really need is wasm compiler.. TBD +* Rust +** Serde +- [2023-07-05 Wed] \\ + important part of the Rust ecosystem, another dtolnay + contribution. If you want to program a /data/ format in the Rust + ecosystem, this is how you do it. + + The way it works is that you define some special structs, a + Serializer and a Deserializer which implement the Serialize and + Deserialize traits provided by serde, respectively. + + You can use these structs to provide your public API. The + conventional choice is public top-level functions like from-str + and to-string. That's it, your serialization library can now read and + write your data format as Rust data types. + + [[https://serde.rs/enum-representations.html][enum-representations]] + - the default behavior is an externally tagged representation (verbose) + + The docs use strings as core IO when implementing a custom format, + but the convention is to implement for T where T is bound by std::io + Read or Write trait. Then you can provide a more robust public API + (from_bytes, from_writer, etc). +* C +* CPP +* Nu +[[https://www.nushell.sh/][~]] +[[https://www.nushell.sh/cookbook/][cookbook]] +[[https://github.com/nushell/nu_scripts][nu_scripts]] diff -r 000000000000 -r 87b04952fb18 20231101.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231101.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,18 @@ +* AWS usage +We're leveraging AWS for some of our public web servers for now. It's +really not realistic to expect that my home desktop and spotty Comcast +internet can serve any production workflow. What it /is/ capable of is +a private VPN, which can communicate with AWS and other cloud VPN +depots via WireGuard ([[https://dev.to/gabrieltetzner/setting-up-a-vpn-with-wireguard-server-on-aws-ec2-4a49][article]]). + +I currently use Google Domains for nas-t.net, otom8.dev, and +rwest.io - but that business is now owned by squarespace, so I would +rather move it to Route53. + +We have archlinux ec2 image builds [[https://wiki.archlinux.org/title/Arch_Linux_AMIs_for_Amazon_Web_Services][here]] and [[https://gitlab.com/anemos-io/archlinux-ec2][here]] - only half work and not +maintained, but it's a start. I'm not even sure if I should stick with +arch or cave and use Ubuntu or AWS Linux. We can serve the static +services with little cost, the only big spender will be the heptapod +instance which requires a larger instance and some workers. + +We'll try to keep the cost at or around $30/month. diff -r 000000000000 -r 87b04952fb18 20231102.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231102.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,82 @@ +* IDEAS +** TODO shed +:PROPERTIES: +:ID: fc9a94e1-91c5-4915-90b8-73218fa3b8bc +:END: +:LOGBOOK: +- State "TODO" from [2023-04-07 Fri 23:24] +:END: +rlib +> ulib +> ulib +> ulib +> ulib + +*** TODO sh* tools +:PROPERTIES: +:ID: c0613a13-7ccb-4af9-b47e-e14a41c782c2 +:END: +:LOGBOOK: +- State "TODO" from "TODO" [2023-04-07 Fri 23:22] +:END: +shc,shx,etc +** WIP packy +:LOGBOOK: +- State "TODO" from [2023-04-07 Fri 23:33] +:END: +*** WIP rust +*** WIP common-lisp +*** WIP emacs-lisp +*** python +*** julia +*** C +*** C++ +** TODO tenex +:LOGBOOK: +- State "TODO" from [2023-04-07 Fri 23:52] +:END: +** TODO mpk +:LOGBOOK: +- State "TODO" from [2023-04-07 Fri 23:52] +:END: +** TODO cfg +:LOGBOOK: +- State "TODO" from [2023-04-07 Fri 23:34] +:END: +** TODO obj +:LOGBOOK: +- State "TODO" from [2023-04-07 Fri 23:51] +:END: +split out from rlib to separate package +- a purely OOP class library +** TODO lab +:LOGBOOK: +- State "TODO" from [2023-04-07 Fri 23:34] +:END: +** TODO source categories +- need a way of extracting metadata from a repo +- need ability to search and query libs/packages +- separate modules based on where they belong in our stack? + - app + - lib + - script? + - dist + - software distros +** TODO generic query language +from obj protocol? +sql compatibility? + +/check out kdb/ +** TODO bbdb +:LOGBOOK: +- Note taken on [2023-10-24 Tue 22:16] \\ + graph database, build on rocksdb +:END: +insidious Big Brother database. +- an application built with obj +- sql + +** TODO NAS-TV :nas:t: +- media streaming +- gstreamer backend +- audio/video diff -r 000000000000 -r 87b04952fb18 20231105.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231105.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,136 @@ +* DRAFT dylib-skel-1 +- State "DRAFT" from [2023-11-05 Sun 22:23] +** Overview +Our core languages are [[https://www.rust-lang.org/][Rust]] and [[https://lisp-lang.org/][Lisp]] - this is the killer combo which will allow NAS-T +to rapidly develop high-quality software. As such, it's crucial that these two very +different languages (i.e. compilers) are able to interoperate seamlessly. + +Some interop methods are easy to accomodate via the OS - such as IPC or data sharing, +but others are a bit more difficult. + +In this 2-part series we'll build a FFI bridge between Rust and Lisp, which is something +that /can/ be difficult, due to some complications with Rust and because this is not the +most popular software stack (yet ;). This is an experiment and may not make it to our +code-base, but it's definitely something worth adding to the toolbox in case we need it. + +** FFI +The level of interop we're after in this case is [[https://en.wikipedia.org/wiki/Foreign_function_interface][FFI]]. + +Basically, calling Rust code from Lisp and vice-versa. There's an article about calling +Rust from Common Lisp [[https://dev.to/veer66/calling-rust-from-common-lisp-45c5][here]] which shows the basics and serves as a great starting point +for those interested. +*** Rust != C +The complication(s) with Rust I mentioned early is really just that /it is not C/. =C= +is old, i.e. well-supported with a stable ABI, making the process of creating bindings +for a C library a breeze in many languages. + +For a Rust library we need to first appease the compiler, as explained in [[https://doc.rust-lang.org/nomicon/ffi.html#calling-rust-code-from-c][this section]] +of the Rustonomicon. Among other things it involves changing the calling-convention of +functions with a type signature and editing the Cargo.toml file to produce a +C-compatible ABI binary. The Rust default ABI is unstable and can't reliably be used +like the C ABI can. + +*** Overhead +Using FFI involves some overhead. Check [[https://github.com/dyu/ffi-overhead][here]] for an example benchmark across a few +languages. While building the NAS-T core, I'm very much aware of this, and will need a +few sanity benchmarks to make sure the cost doesn't outweigh the benefit. In particular, +I'm concerned about crossing multiple language barriers (Rust<->C<->Lisp). + +** Rust -> C -> Lisp +*** Setup +For starters, I'm going to assume we all have Rust (via =rustup=) and Lisp (=sbcl= only) +installed on our GNU/Linux system (some tweaks needed for Darwin/Windows, not covered in +this post). +**** Cargo +Create a new library crate. For this example we're focusing on a 'skeleton' for +/dynamic/ libraries only, so our experiment will be called =dylib-skel= or *dysk* for +short. +src_sh[:exports code]{cargo init dysk --lib && cd dysk} + +A =src/lib.rs= will be generated for you. Go ahead and delete that. We're going to be +making our own =lib.rs= file directly in the root directory (just to be cool). + +The next step is to edit your =Cargo.toml= file. Add these lines after the =[package]= +section and before =[dependencies]=: +#+begin_src conf-toml +[lib] +crate-type = ["cdylib","rlib"] +path = "lib.rs" +[[bin]] +name="dysk-test" +path="test.rs" +#+end_src + +This tells Rust to generate a shared C-compatible object with a =.so= extension which we +can open using [[https://man.archlinux.org/man/dlopen.3.en][dlopen]]. +**** cbindgen +***** install +Next, we want the =cbindgen= program which we'll use to generate header files for +C/C++. This step isn't necessary at all, we just want it for further experimentation. + +src_sh[:exports code]{cargo install --force cbindgen} + +We append the =cbindgen= crate as a /build dependency/ to our =Cargo.toml= like so: +#+begin_src conf-toml +[build-dependencies] +cbindgen = "0.24" +#+end_src +***** cbindgen.toml +#+begin_src conf-toml :tangle cbindgen.toml +language = "C" +autogen_warning = "/* Warning, this file is autogenerated by cbindgen. Don't modify this manually. */" +include_version = true +namespace = "dysk" +cpp_compat = true +after_includes = "#define DYSK_VERSION \"0.1.0\"" +line_length = 88 +tab_width = 2 +documentation = true +documentation_style = "c99" +usize_is_size_t = true +[cython] +header = '"dysk.h"' +#+end_src +***** build.rs +#+begin_src rust :tangle build.rs +fn main() -> Result<(), cbindgen::Error> { + if let Ok(b) = cbindgen::generate(std::env::var("CARGO_MANIFEST_DIR").unwrap()) { + b.write_to_file("dysk.h"); Ok(())} + else { panic!("failed to generate dysk.h from cbindgen.toml") } } +#+end_src +*** lib.rs +#+begin_src rust :tangle lib.rs +//! lib.rs --- dysk library +use std::ffi::{c_char, c_int, CString}; +#[no_mangle] +pub extern "C" fn dysk_hello() -> *const c_char { + CString::new("hello from rust").unwrap().into_raw()} +#[no_mangle] +pub extern "C" fn dysk_plus(a:c_int,b:c_int) -> c_int {a+b} +#[no_mangle] +pub extern "C" fn dysk_plus1(n:c_int) -> c_int {n+1} +#+end_src +*** test.rs +#+begin_src rust :tangle test.rs +//! test.rs --- dysk test +fn main() { let mut i = 0u32; while i < 500000000 {i+=1; dysk::dysk_plus1(2 as core::ffi::c_int);}} +#+end_src +*** compile +#+begin_src sh +cargo build --release +#+end_src +*** load from SBCL +#+begin_src lisp :tangle dysk.lisp +(load-shared-object #P"target/release/libdysk.so") +(define-alien-routine dysk-hello c-string) +(define-alien-routine dysk-plus int (a int) (b int)) +(define-alien-routine dysk-plus1 int (n int)) +(dysk-hello) ;; => "hello from rust" +#+end_src +*** benchmark +#+begin_src shell +time target/release/dysk-test +#+end_src +#+begin_src lisp :tangle test.lisp +(time (dotimes (_ 500000000) (dysk-plus1 2))) +#+end_src diff -r 000000000000 -r 87b04952fb18 20231124.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231124.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,33 @@ +* cl-dot examples +#+begin_src lisp +(defmethod cl-dot:graph-object-node ((graph (eql 'example)) (object cons)) + (make-instance 'cl-dot:node + :attributes '(:label "cell \\N" + :shape :box))) +(defmethod cl-dot:graph-object-points-to ((graph (eql 'example)) (object cons)) + (list (car object) + (make-instance 'cl-dot:attributed + :object (cdr object) + :attributes '(:weight 3)))) +;; Symbols +(defmethod cl-dot:graph-object-node ((graph (eql 'example)) (object symbol)) + (make-instance 'cl-dot:node + :attributes `(:label ,object + :shape :hexagon + :style :filled + :color :black + :fillcolor "#ccccff"))) +(let* ((data '(a b c #1=(b z) c d #1#)) + (dgraph (cl-dot:generate-graph-from-roots 'example (list data) + '(:rankdir "LR" :layout "twopi" :labelloc "t")))) + (cl-dot:dot-graph dgraph "test-lr.svg" :format #+nil :x11 :svg)) +#+end_src + +#+RESULTS: + +#+begin_src lisp +(let* ((data '(a b)) + (dgraph (cl-dot:generate-graph-from-roots 'example (list data) + '(:rankdir "LR")))) + (cl-dot:print-graph dgraph)) +#+end_src diff -r 000000000000 -r 87b04952fb18 20231205.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231205.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,5 @@ +* global refs +need a way of indexing, referring to, and annotating objects such as +URLs, docs, articles, source files, etc. + +What is the best way to get this done? diff -r 000000000000 -r 87b04952fb18 20231209.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231209.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,5 @@ + +* doc best practices +https://rust-lang.github.io/api-guidelines/documentation.html + +also: https://lisp-lang.org/style-guide/ diff -r 000000000000 -r 87b04952fb18 20231212.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231212.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,89 @@ +* On Computers +If you've met me in the past decade, you probably know that I am +extremely passionate about computers. Let me first explain why. + +On the most basic level computers are little (or big) machines that +can be programmed to do things, or /compute/ if we're being +technical.[fn:1] + +They host and provide access to the Internet, which is a pretty big +thing, but they do little things too like unlock your car door and +tell your microwave to beep at you. They solve problems. Big or small. + +They're also /everywhere/ - which can be scary to think about, but +ultimately helps propel us into the future. + +There's something pretty cool about that - when you look at the +essence of computation. There are endless quantities of these machines +which follow the same basic rules and can be used to solve /real/ +problems. + +** The Programmer +Now, let us consider the /programmer/. They have power. /real/ +power. They understand the language of computers, can whisper to them +in various dialects. It can be intimidating to witness until you +realize how often the programmer says the wrong thing - a bug. + +In reality, the programmer has a symbiotic relationship with +computers. Good programmers understand this relationship well. + +#+begin_annecdote +One day after I got my first job at a software company, I remember +being on an all-hands meeting due to a client service outage. We had +some management, our lead devs, product team, and one curious looking +man who happened to be our lead IT consultant who had just joined. He +was sitting up on a hotel bed, shirtless, vaping an e-cig, typing +away in what I can only imagine was a shell prompt. + +After several minutes he took a swig from a bottle of Coke and said +"Node 6 is sick." then a few seconds later our services were +restored. For the next hour on the call he explained what happened and +why, but that particular phrase always stuck with me. He didn't say +Node 6 was down, or had an expired cert - his diagnosis was that /it/ +was /sick/. +#+end_annecdote + +The more you work closely with computers, the more you start to think +of them this way. You don't start screaming when the computer does the +wrong thing, you figure out what's wrong and learn from it. With +experience, you start to understand the different behaviors of the +machines you work with. I like to call this /Machine Empathy/. + +** Programs +I already mentioned bugs - I write plenty of those, but usually I try +to write /programs/. Programs to me are like poetry. I like to think +they are for the computer too. + +Just like computers, /computer programs/ come in different shapes and +sizes but in basic terms they are sets of instructions used to control +a computer. + +You can write programs to do anything - when I first started, my +programs made music. The program was a means to an end. Over time, I +started to see the program as something much more. I saw it as the +music itself. + +[fn:1] ... perform computations + + +* On Infra +Something that is missing from many organizations big or large, is an +effective way to store and access information, even about their own +org. + +It can be difficult problem to solve - usually there's the official +one, say Microsoft Sharepoint and then the list of unofficial sources +which becomes tribal corporate hacker knowledge. Maybe the unofficial +ones are more current, or are annotated nicely, but their very +existence breaks the system. There's no longer a single source of +truth. + +My priority in this department is writing services which process and +store information from a variety of sources in a distributed knowledge +graph. The graph can later be queried to access information on-demand. + +My idea of infrastructure is in fact to build my own Cloud. Needless +to say I don't have an O365 subscription, and wherever possible I'll +be relying on hardware I have physical access to. I'm not opposed to +cloud services at large but based on principle I like to think we +shouldn't be built on them. diff -r 000000000000 -r 87b04952fb18 20231223.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231223.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,3 @@ +* https://cal-coop.gitlab.io/utena/utena-specification/main.pdf +from the author of cl-decentralise2. draft specification of a +/Maximalist/ Computing System. diff -r 000000000000 -r 87b04952fb18 20231224.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231224.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,4 @@ +* public datasets +https://github.com/awesomedata/awesome-public-datasets +https://docs.openml.org/Datasets/ +https://wiki.pathmind.com/open-datasets diff -r 000000000000 -r 87b04952fb18 20231228.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20231228.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,40 @@ +* useful internals +#+begin_src lisp + sb-sys:*runtime-dlhandle* + sb-fasl:+fasl-file-version+ + sb-fasl:+backend-fasl-file-implementation+ + sb-debug:print-backtrace + sb-debug:map-backtrace + sb-pretty:pprint-dispatch-table + sb-lockless: + sb-ext:simd-pack + sb-walker:define-walker-template + sb-walker:macroexpand-all + sb-walker:walk-form + sb-kernel:empty-type + sb-kernel:*eval-calls* + sb-kernel:*gc-pin-code-pages* + sb-kernel:*restart-clusters* + sb-kernel:*save-lisp-clobbered-globals* + sb-kernel:*top-level-form-p* + sb-kernel:*universal-fun-type* + sb-kernel:*universal-type* + sb-kernel:*wild-type* + sb-kernel:+simd-pack-element-types+ + (sb-vm:memory-usage) + (sb-vm:boxed-context-register) + (sb-vm:c-find-heap->arena) + (sb-vm:copy-number-to-heap) + (sb-vm:dump-arena-objects) + (sb-vm:fixnumize) + (sb-vm:rewind-arena) + (sb-vm:show-heap->arena) + (sb-vm:with/without-arena) + (sb-cltl2:{augment-environment,compiler-let,define-declaration,parse-macro}) + (sb-cltl2:{declaration-information, variable-information, function-information}) + sb-di: + sb-assem: + sb-md5: + sb-regalloc: + sb-disassem: +#+end_src diff -r 000000000000 -r 87b04952fb18 20240103.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240103.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,27 @@ +* [[https://github.com/sigmf/SigMF][SigMF]] +#+begin_quote +Sharing sets of recorded signal data is an important part of science +and engineering. It enables multiple parties to collaborate, is often +a necessary part of reproducing scientific results (a requirement of +scientific rigor), and enables sharing data with those who do not have +direct access to the equipment required to capture it. + +Unfortunately, these datasets have historically not been very +portable, and there is not an agreed upon method of sharing metadata +descriptions of the recorded data itself. This is the problem that +SigMF solves. + +By providing a standard way to describe data recordings, SigMF +facilitates the sharing of data, prevents the "bitrot" of datasets +wherein details of the capture are lost over time, and makes it +possible for different tools to operate on the same dataset, thus +enabling data portability between tools and workflows. +#+end_quote + +the-spec: https://github.com/sigmf/SigMF/blob/sigmf-v1.x/sigmf-spec.md +* [[https://www.libvolk.org/][LibVOLK]] +Vector-Optimized Library of Kernels (simd) +* [[https://docs.kernel.org/fb/framebuffer.html][/dev/fb*]] +framebuffers, used by fbgrab/fbcat program +* [[https://docs.kernel.org/block/ublk.html][ublk]] +https://github.com/ming1/ubdsrv diff -r 000000000000 -r 87b04952fb18 20240104.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240104.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,6 @@ +goals: +make problems smaller. + +sections: +why lisp? +- doesn't need mentioning more and more diff -r 000000000000 -r 87b04952fb18 20240120.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240120.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,36 @@ +* TODO taobench demo +:LOGBOOK: +- State "TODO" from [2024-01-21 Sun 00:32] +:END: +https://github.com/audreyccheng/taobench - shouldn't have missed this :) +obviously we need to implement this using core -- in demo/bench/tao? +* TODO clap completion for nushell +:LOGBOOK: +- State "TODO" from [2024-01-20 Sat 23:23] +:END: +https://github.com/clap-rs/clap/tree/master/clap_complete_nushell +* Dataframe scripting +https://studioterabyte.nl/en/blog/polars-vs-pandas +nushell supports DFs, polars underneath? +https://www.nushell.sh/book/cheat_sheet.html + +#+begin_src nushell + +#+end_src +* Cloud Squatting +** Google +- [[https://cloud.google.com/free/docs/free-cloud-features][Free Cloud Features]] + + 90-day $300 credits + + e2-micro - free hours worth 1 instance/month + + +** Amazon +- AWS Free Tier +** Akamai +- Linode Free Trial +** Oracle +- [[https://www.oracle.com/cloud/free/?intcmp=ohp052322ocift][OCI Free Tier]] + + always free: 2 x oracle autonomous DB + + 2 x AMD Compute VMs + + up to 4 x ARM Ampere A1 with 3k/cpu/hr and 18k/gb/h per month + + block/object/archive storage + + 30-day $300 credits diff -r 000000000000 -r 87b04952fb18 20240129.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240129.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,67 @@ +* NOTE trash as block device +:LOGBOOK: +- State "NOTE" from [2024-01-29 Mon 20:53] +- State "NOTE" from [2024-01-29 Mon 20:53] +:END: +in nushell there is option for rm command to always use 'trash' - +AFAIK the current approach is via a service (trashd). + +An interesting experiment would be to designate a block device as +'trash' - may be possible to remove reliance on a service + +may be an opportunity for ublk driver to shine - instead of /dev/null +piping we need a driver for streaming a file to /dev/trash +* NOTE compute power +:LOGBOOK: +- State "NOTE" from [2024-01-29 Mon 16:28] +:END: +- mostly x86_64 machines - currently 2 AWS EC2 instances, some podman containers, and our home beowulf server: +- beowulf: + - Zor + - mid-size tower enclosed (Linux/Windows) + - CPU + - Intel Core i7-6700K + - 4 @ 4.0 + - GPU + - NVIDIA GeForce GTX 1060 + - 6GB + - Storage + - Samsung SSD 850: 232.9GB + - Samsung SSD 850: 465.76GB + - ST2000DM001-1ER1: 1.82TB + - WDC WD80EAZZ-00B: 7.28TB + - PSSD T7 Shield: 3.64TB + - My Passport 0820: 1.36TB + - RAM + - 16GB (2*8) [64GB max] + - DDR4 + - Jekyll + - MacBook Pro 2019 (MacOS/Darwin) + - CPU + - Intel + - 8 @ + - RAM + - 32G DDR4 + - Hyde + - Thinkpad + - CPU + - Intel + - 4 @ + - RAM + - 24G DDR3 + - Boris + - Pinephone Pro + - CPU + - 64-bit 6-core 4x ARM Cortex A53 + 2x ARM Cortex A72 + - GPU + - Mali T860MP4 + - RAM + - 4GB LPDDR4 + - pi + - Raspberry Pi 4 Model B + - CPU + - Cortex-A72 (ARM v8) 64-bit SoC + - 4 @ 1.8GHz + - RAM + - 8 GB + - DDR4 4200 diff -r 000000000000 -r 87b04952fb18 20240210.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240210.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,13 @@ +* BigBenches +#+name: 1trc-nu +#+begin_src nushell + let ms = '1trc/measurements-0.parquet' + dfr open $ms + | dfr group-by station + | dfr agg [ + (dfr col measure | dfr min | dfr as "min") + (dfr col measure | dfr max | dfr as "max") + (dfr col measure | dfr sum | dfr as "sum") + (dfr col measure | dfr count | dfr as "count") + ] +#+end_src diff -r 000000000000 -r 87b04952fb18 20240218.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240218.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,75 @@ +* NOTE WL vs X +:LOGBOOK: +- State "NOTE" from [2024-02-18 Sun 11:55] +:END: +In the past few months there has been drama regarding Wayland vs X. It +seems to be on everyone's minds after Artem's freakout issue and the +follow up YT vids/comments. + +I admit that it made me reconsider the fitness of WL as a whole - +there was a github gist that made some scathing arguments against it. + +It's an odd debate though. I think there are many misunderstandings. + +So first off, if we look at the homepage +https://wayland.freedesktop.org/, Wayland claims it is a replacement +for X11. It now has /manifest destiny/, which in my opinion is a great +shame. + +X-pros seem to agree that Wayland has /manifest destiny/ - like if you +are building softwares that look remotely like a window system, it's a +successor to X. That's the model of doing things and there's no way +around it. + +The disagreement starts with how this destiny - of an X2 - should be +fulfilled. X-pros want a fork of X, but it's too late for +that. WL-pros want X to run on top of Wayland compositor: +https://wayland.freedesktop.org/xserver.html. + +Xwayland is a problem for me. From the project description: 'if we're +migrating away from X, it makes sense to have a good backwards +compatibility story.' Full disclosure: I have never done significant +work on Xwayland, so perhaps my opinion is unwarranted. But I have no +intention of attempting to maintain a computer system that uses +Wayland and X clients at the same time. + +To me, X is ol' reliable. Every distro has first-class X support, and +it runs on most systems with very little user intervention. Where it +doesn't, there is 20+ years of dev history and battle-tested +workarounds for you to find your solution in. + +Wayland is the new kid on the block, born just in 2008. It's a fresh +start to one of the most difficult challenges in software - window +systems. A re-write would be pointless though, and so the real +value-add is in design. Wayland is designed as a protocol and +collection of libraries which are implemented in your own +compositor. Coming from Lisp - with ANSI Common Lisp and SRFIs, this +feels right even if the implementation is something very different +(compositor vs compiler). + +With X, it is assumed to be much harder to write an equivalent +'compositor'. Here's the thing though - with a significantly complex X +client implementation, it is /impossible/ to replicate in WL. This is +really the crux of Artemi's argument in his issue. He asked for a 1:1 +equivalent X/WL comparison when no such thing exists, and in my +opinion it is a waste of time. + +The WL core team is fully aware of this dichotomy, but also that this +is in no way a problem or weakness in either system. It means they're +different systems, goddammit. + +If it was up to me, Xwayland wouldn't exist. I understand why it does, +and that it does make things easier for developers who need to support +both, and users who have multiple apps with multiple windowing +requirements. It's a bandaid though, and one that is particularly +dangerous because it re-enforces the idea that Wayland is just X2 and +that they're fully compatible. + +What interests me in the Wayland world right now is the idea of a +small, modular, full-stack Wayland compositor API. There are several +'kiosk' based compositors for single applications (cage), but these +aren't complete solutions. It is possible to get much closer to the +metal, and that's where I want to be so that I can build my own APIs +on top - I don't want to live on top of X, and I certainly don't want +to live on top of X on top of WL. I want a /pure/ solution that hides +as little as possible, exposing the interesting bits. diff -r 000000000000 -r 87b04952fb18 20240301.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240301.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,6 @@ +* TODO collect more data +:LOGBOOK: +- State "TODO" from [2024-03-01 Fri 15:27] +:END: +https://www.csie.ntu.edu.tw/~cjlin/libsvmtools/datasets/ +weather - music - etc diff -r 000000000000 -r 87b04952fb18 20240302.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240302.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,117 @@ +* NOTE On blocks and devices +:LOGBOOK: +- State "NOTE" from [2024-03-02 Sat 21:30] +:END: +[[https://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/dev.html][/dev]] +In Linux, everything is a file. + +/dev/ contains special device files - usually block or character +device. + +major, minor = category, device +0, 5 + +mknod - create special device files + +[[https://www.redhat.com/en/blog/linux-block-devices-hints-debugging-and-new-developments][redhat hints]] + +#+begin_src shell + dd if=/dev/zero of=myfile bs=1M count=32 + losetup --show -f myfile + ls -al /dev/loop0 + losetup -d /dev/loop0 #teardown +#+end_src + +#+begin_src shell + echo "sup dude" > /dev/loop0 + dd if=/dev/loop0 -bs=1 + dd if=/dev/nvme0 of=/dev/null progress=true + #pacman -S hdparm + hdparm -T /dev/nvme0 +#+end_src + +#+begin_src shell +modprobe scsi_debug add_host=5 max_luns=10 num_tgts=2 dev_size_mb=16 +#+end_src + +sparsefiles: create with C, dd, or truncate + +#+begin_src shell :results output +truncate --help +#+end_src + +#+RESULTS: +#+begin_example +Usage: truncate OPTION... FILE... +Shrink or extend the size of each FILE to the specified size + +A FILE argument that does not exist is created. + +If a FILE is larger than the specified size, the extra data is lost. +If a FILE is shorter, it is extended and the sparse extended part (hole) +reads as zero bytes. + +Mandatory arguments to long options are mandatory for short options too. + -c, --no-create do not create any files + -o, --io-blocks treat SIZE as number of IO blocks instead of bytes + -r, --reference=RFILE base size on RFILE + -s, --size=SIZE set or adjust the file size by SIZE bytes + --help display this help and exit + --version output version information and exit + +The SIZE argument is an integer and optional unit (example: 10K is 10*1024). +Units are K,M,G,T,P,E,Z,Y,R,Q (powers of 1024) or KB,MB,... (powers of 1000). +Binary prefixes can be used, too: KiB=K, MiB=M, and so on. + +SIZE may also be prefixed by one of the following modifying characters: +'+' extend by, '-' reduce by, '<' at most, '>' at least, +'/' round down to multiple of, '%' round up to multiple of. + +GNU coreutils online help: +Full documentation +or available locally via: info '(coreutils) truncate invocation' +#+end_example + +test mkfs.btrfs on 10T dummy block device +#+begin_src shell + dd if=/dev/zero of=/tmp/bb1 bs=1 count=1 seek=10T + du -sh /tmp/bb1 + losetup --show -f /tmp/bb1 + mkfs.btrfs /dev/loop0 +#+end_src + +diagnostics +#+begin_src shell + iostat # pacman -S sysstat + blktrace # paru -S blktrace + iotop # pacman -S iotop +#+end_src + +bcc/ trace: Who/which process is executing specific functions against +block devices? + +bcc/biosnoop: Which process is accessing the block device, how many +bytes are accessed, which latency for answering the requests? + +at the kernel level besides BPF we got kmods and DKMS, + +compression/de-duplication can be done via VDO kernel mod + +https://en.wikipedia.org/wiki/Dynamic_Kernel_Module_Support + +* NOTE save-lisp-and-respawn +:LOGBOOK: +- State "NOTE" from [2024-03-02 Sat 22:57] +:END: +#+begin_src lisp + sb-ext:*save-hooks* +#+end_src + +* NOTE syslog for log +:LOGBOOK: +- State "NOTE" from [2024-03-03 Sun 16:35] +:END: +sb-posix: +- openlog syslog closelog +- levels: emerg alert crit err warning notice info debug +- setlogmask diff -r 000000000000 -r 87b04952fb18 20240313.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240313.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,6 @@ +* RESEARCH [[https://github.com/guicho271828/sbcl-wiki/wiki/][sbcl-wiki]] +:LOGBOOK: +- State "RESEARCH" from [2024-03-13 Wed 21:49] +:END: +** IR1 +** IR2 diff -r 000000000000 -r 87b04952fb18 20240317.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240317.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,49 @@ +* NOTE DB Benchmarking +:LOGBOOK: +- State "NOTE" from [2024-02-04 Sun 20:40] +:END: +[[https://github.com/facebook/rocksdb/wiki/Benchmarking-tools][RocksDB benchmarking tools]] + +* NOTE packy design +:PROPERTIES: +:ID: 76ae24f5-46e8-4b91-8991-41245383d337 +:END: +:LOGBOOK: +- State "NOTE" from [2024-01-25 Thu 22:39] +:END: +- API root: https://packy.compiler.company +- source packs: https://vc.compiler.company/packy +** Lib +*** Types +**** Pack +Primary data type of the library - typically represents a compressed +archive, metadata, and ops. +**** Bundle +Collection data type, usually contains a set of packs with metadata. +**** PackyEndpoint +Represents a Packy instance bound to a UDP socket +**** PackyEndpointConfig +Global endpoint configuration object +**** PackyClientConfig +Configuration for outgoing packy connections on an endpoint +**** PackyServerConfig +Configuration for incoming packy connection son an endpoint +**** PackyConnection +Packy connection object +*** Traits +**** PackyClient +***** query +***** install +***** update +***** login +***** logout +***** pull +***** push +**** PackyServer +***** start_packy_server +***** stop_packy_server +***** start_packy_registry +**** PackyRegistry +***** register_pack +***** register_user +***** register_bundle diff -r 000000000000 -r 87b04952fb18 20240325.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240325.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,8 @@ +* TBD investigate alieneval for phash opps +:LOGBOOK: +- State "TBD" from [2024-03-25 Mon 18:56] +:END: +* TBD +:LOGBOOK: +- State "TBD" from [2024-03-25 Mon 18:57] +:END: diff -r 000000000000 -r 87b04952fb18 20240419.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240419.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,86 @@ +#+title: demo-old-readme +* How it works +The backend services are written in Rust and controlled by a simple +messaging protocol. Services provide common runtime capabilities known +as the /service protocol/ but are specialized on a unique /service +type/ which may in turn register their own /custom protocols/ (via +core). + +Services are capable of dispatching data directly to clients, or +storing data in the /database/ (sqlite, postgres, mysql). + +The frontend clients are pre-dominantly written in Common Lisp and +come in many shapes and sizes. There is a cli-client, web-client +(CLOG), docker-client (archlinux, stumpwm, McCLIM), and native-client +which also compiles to WASM (slint-rs). + +* Guide +** Build +- *install dependencies* + #+begin_src bash + ./tools/deps.sh + #+end_src +- *make executables* \\ + Simply run =make build=. Read the ~makefile~ and change the options + as needed. +- MODE :: Mode (debug, release) +- LISP :: Lisp (sbcl, cmucl, ccl) +- CFG :: Config (default.cfg) +** Run +#+begin_src shell + ./demo -i +#+end_src +** Config +Configs can be specified in JSON, TOML, RON, or of course SEXP. See +=default.cfg= for an example. +** Play +The high-level user interface is presented as a multi-modal GUI +application which adapts to the specific application /instances/ +below. +*** Weather +This backend retrieves weather data using the NWS API. +*** Stocks +The 'Stocks' backend features a stock ticker with real-time analysis +capabilities. +*** Bench +This is a benchmark backend for testing the capabilities of our +demo. It spins up some mock services and allows fine-grained control +of input/throughput. +* tasks +** TODO DSLs +- consider tree-sitter parsing layout, use as a guide for developing a + single syntax which expands to Rust or C. +- with-rs +- with-c +- with-rs/c +- with-cargo +- compile-rs/c +*** TODO rs-macroexpand +- rs-gen-file +- rs-defmacro +- rs-macros +- rs-macroexpand +- rs-macroexpand-1 +*** TODO c-macroexpand +- c-gen-file h/c +- c-defmacro +- c-macros +- c-macroexpand +- c-macroexpand-1 +*** TODO slint-macroexpand +- slint-gen-file +- slint-defmacro +- slint-macros +- slint-macroexpand +- slint-macroexpand-1 +*** TODO html (using who) +** TODO web templates +create a basic static page in CL which will be used to host Slint UIs +and other WASM doo-dads in a browser. +** TODO CLI +using clingon, decide on generic options and write it up +** TODO docs +work on doc generation -- Rust and CL should be accounted for. +** TODO tests +We have none! need to make it more comfy - set up testing in all Rust +crates and for the lisp systems. diff -r 000000000000 -r 87b04952fb18 20240425.org --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/20240425.org Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,1 @@ +* https://docs.gitlab.com/ee/administration/backup_restore/migrate_to_new_server.html diff -r 000000000000 -r 87b04952fb18 refs.bib --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/refs.bib Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,169 @@ +@article{btrfs, +author = {Rodeh, Ohad and Bacik, Josef and Mason, Chris}, +year = {2013}, +month = {08}, +pages = {}, +title = {BTRFS: The linux B-tree filesystem}, +volume = {9}, +journal = {ACM Transactions on Storage (TOS)}, +doi = {10.1145/2501620.2501623} +} +@INPROCEEDINGS{zfs, + author={Rodeh, O. and Teperman, A.}, + booktitle={20th IEEE/11th NASA Goddard Conference on Mass Storage Systems and Technologies, 2003. (MSST 2003). Proceedings.}, + title={zFS - a scalable distributed file system using object disks}, + year={2003}, + volume={}, + number={}, + pages={207-218}, + doi={10.1109/MASS.2003.1194858}} + +@inproceedings{tmpfs, + title={tmpfs: A Virtual Memory File System}, + author={Peter Snyder}, + year={1990}, + url={https://api.semanticscholar.org/CorpusID:54156693} +} + +@Article{nvme-ssd-ux, +AUTHOR = {Kim, Seongmin and Kim, Kyusik and Shin, Heeyoung and Kim, Taeseok}, +TITLE = {Practical Enhancement of User Experience in NVMe SSDs}, +JOURNAL = {Applied Sciences}, +VOLUME = {10}, +YEAR = {2020}, +NUMBER = {14}, +ARTICLE-NUMBER = {4765}, +URL = {https://www.mdpi.com/2076-3417/10/14/4765}, +ISSN = {2076-3417}, +DOI = {10.3390/app10144765} +} + +@inproceedings{ext4, +author = {Djordjevic, Borislav and Timcenko, Valentina}, +title = {Ext4 File System Performance Analysis in Linux Environment}, +year = {2011}, +isbn = {9781618040282}, +publisher = {World Scientific and Engineering Academy and Society (WSEAS)}, +address = {Stevens Point, Wisconsin, USA}, +booktitle = {Proceedings of the 11th WSEAS International Conference on Applied Informatics and Communications, and Proceedings of the 4th WSEAS International Conference on Biomedical Electronics and Biomedical Informatics, and Proceedings of the International Conference on Computational Engineering in Systems Applications}, +pages = {288–293}, +numpages = {6}, +keywords = {Linux, journaling, ext4/ext3/ext2, filesystems, inodes, disk performances, file block allocation}, +location = {Florence, Italy}, +series = {AIASABEBI'11} +} + +@Article{hd-failure-ml, +AUTHOR = {Zhang, Mingyu and Ge, Wenqiang and Tang, Ruichun and Liu, Peishun}, +TITLE = {Hard Disk Failure Prediction Based on Blending Ensemble Learning}, +JOURNAL = {Applied Sciences}, +VOLUME = {13}, +YEAR = {2023}, +NUMBER = {5}, +ARTICLE-NUMBER = {3288}, +URL = {https://www.mdpi.com/2076-3417/13/5/3288}, +ISSN = {2076-3417}, +DOI = {10.3390/app13053288} +} + +@inproceedings{smart-ssd-qp, +author = {Do, Jaeyoung and Kee, Yang-Suk and Patel, Jignesh M. and Park, Chanik and Park, Kwanghyun and DeWitt, David J.}, +title = {Query Processing on Smart SSDs: Opportunities and Challenges}, +year = {2013}, +isbn = {9781450320375}, +publisher = {Association for Computing Machinery}, +address = {New York, NY, USA}, +url = {https://doi.org/10.1145/2463676.2465295}, +doi = {10.1145/2463676.2465295}, +booktitle = {Proceedings of the 2013 ACM SIGMOD International Conference on Management of Data}, +pages = {1221–1230}, +numpages = {10}, +keywords = {smart ssd}, +location = {New York, New York, USA}, +series = {SIGMOD '13} +} + +@inproceedings{ssd-perf-opt, +author = {Zuck, Aviad and G\"{u}hring, Philipp and Zhang, Tao and Porter, Donald E. and Tsafrir, Dan}, +title = {Why and How to Increase SSD Performance Transparency}, +year = {2019}, +isbn = {9781450367271}, +publisher = {Association for Computing Machinery}, +address = {New York, NY, USA}, +url = {https://doi.org/10.1145/3317550.3321430}, +doi = {10.1145/3317550.3321430}, +booktitle = {Proceedings of the Workshop on Hot Topics in Operating Systems}, +pages = {192–200}, +numpages = {9}, +location = {Bertinoro, Italy}, +series = {HotOS '19} +} + +@article{flash-openssd-systems, +author = {Kwak, Jaewook and Lee, Sangjin and Park, Kibin and Jeong, Jinwoo and Song, Yong Ho}, +title = {Cosmos+ OpenSSD: Rapid Prototype for Flash Storage Systems}, +year = {2020}, +issue_date = {August 2020}, +publisher = {Association for Computing Machinery}, +address = {New York, NY, USA}, +volume = {16}, +number = {3}, +issn = {1553-3077}, +url = {https://doi.org/10.1145/3385073}, +doi = {10.1145/3385073}, +journal = {ACM Trans. Storage}, +month = {jul}, +articleno = {15}, +numpages = {35}, +keywords = {storage system, solid state drive (SSD), flash translation layer (FTL), Flash memory} +} + +@INPROCEEDINGS{emmc-mobile-io, + author={Zhou, Deng and Pan, Wen and Wang, Wei and Xie, Tao}, + booktitle={2015 IEEE International Symposium on Workload Characterization}, + title={I/O Characteristics of Smartphone Applications and Their Implications for eMMC Design}, + year={2015}, + volume={}, + number={}, + pages={12-21}, + doi={10.1109/IISWC.2015.8}} + +@inproceedings{xfs-scalability, + author = {Adam Sweeney and + Doug Doucette and + Wei Hu and + Curtis Anderson and + Mike Nishimoto and + Geoff Peck}, + title = {Scalability in the {XFS} File System}, + booktitle = {Proceedings of the {USENIX} Annual Technical Conference, San Diego, + California, USA, January 22-26, 1996}, + pages = {1--14}, + publisher = {{USENIX} Association}, + year = {1996}, + url = {http://www.usenix.org/publications/library/proceedings/sd96/sweeney.html}, + timestamp = {Wed, 04 Jul 2018 13:06:34 +0200}, + biburl = {https://dblp.org/rec/conf/usenix/Sweeney96.bib}, + bibsource = {dblp computer science bibliography, https://dblp.org} +} + +@inproceedings{xfs, + title={xFS: A wide area mass storage file system}, + author={Wang, Randolph Y and Anderson, Thomas E}, + booktitle={Proceedings of IEEE 4th Workshop on Workstation Operating Systems. WWOS-III}, + pages={71--78}, + year={1993}, + organization={IEEE} +} + +@inproceedings {zns-usenix, +author = {Matias Bj{\o}rling and Abutalib Aghayev and Hans Holmberg and Aravind Ramesh and Damien Le Moal and Gregory R. Ganger and George Amvrosiadis}, +title = {{ZNS}: Avoiding the Block Interface Tax for Flash-based {SSDs}}, +booktitle = {2021 USENIX Annual Technical Conference (USENIX ATC 21)}, +year = {2021}, +isbn = {978-1-939133-23-6}, +pages = {689--703}, +url = {https://www.usenix.org/conference/atc21/presentation/bjorling}, +publisher = {USENIX Association}, +month = jul, +} \ No newline at end of file diff -r 000000000000 -r 87b04952fb18 vocab --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/vocab Sun Apr 28 19:51:45 2024 -0400 @@ -0,0 +1,19 @@ +;;; docs/vocab --- project glossary -*- mode:outline;outline-regexp:"[-]+" -*- +- wrt : With Respect To +- nyi : Not Yet Implemented +- rt : Regression Testing +- vm : Virtual Machine +- asm : Assembly +- comp : Compiler +- eval : Evaluate +- alloc : Allocate +- ret : Return +- tco : Tail-call Optimization +- reg : Register +- sbcl : Steel Bank Common Lisp +- rs : Rust (the language) +- el : Emacs Lisp +- cl : Common Lisp +- pcl : Practical Common Lisp +- taomop : The Art of the Meta Object Protocol +- lol : Let Over Lambda