1.1--- a/.hgsub	Fri Oct 20 20:21:26 2023 -0400
     1.2+++ b/.hgsub	Tue Oct 24 22:23:37 2023 -0400
     1.3@@ -1,5 +1,2 @@
     1.4 blog=https://lab.rwest.io/comp/blog
     1.5-docs=https://lab.rwest.io/comp/docs
     1.6-notes=ssh://git@lab.rwest.io/comp/notes
     1.7-pitch=ssh://git@lab.rwest.io/comp/pitch
     1.8-roadmap=ssh://git@lab.rwest.io/comp/roadmap
     1.9\ No newline at end of file
    1.10+docs=https://lab.rwest.io/comp/docs
    1.11\ No newline at end of file

     2.1--- a/.hgsubstate	Fri Oct 20 20:21:26 2023 -0400
     2.2+++ b/.hgsubstate	Tue Oct 24 22:23:37 2023 -0400
     2.3@@ -1,5 +1,2 @@
     2.4-0000000000000000000000000000000000000000 blog
     2.5-0000000000000000000000000000000000000000 docs
     2.6-92ed9071dbc374962d1aad574c73a48de6ab40b5 notes
     2.7-66df5a8b13ca8988eb959de3dbca2a2fe411e0a8 pitch
     2.8-5a40ce874037097279aac0023f0212f39ac02ad4 roadmap
     2.9+281364f7d1106b16f12d1ca1b2ee16901fe6ecae blog
    2.10+b154f8be21c8c89c2c04ecf6b4230842b15115b1 docs

     3.1--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     3.2+++ b/ideas.org	Tue Oct 24 22:23:37 2023 -0400
     3.3@@ -0,0 +1,86 @@
     3.4+#+TITLE: ideas
     3.5+#+TODO: TODO WIP RFC | DONE
     3.6+This is a running list of ideas. Most of these are tools, libraries,
     3.7+projects, etc but anything is fair game.
     3.8+
     3.9+* TODO shed
    3.10+:PROPERTIES:
    3.11+:ID:       fc9a94e1-91c5-4915-90b8-73218fa3b8bc
    3.12+:END:
    3.13+:LOGBOOK:
    3.14+- State "TODO"       from              [2023-04-07 Fri 23:24]
    3.15+:END:
    3.16+rlib
    3.17+> ulib
    3.18+> ulib
    3.19+> ulib
    3.20+> ulib
    3.21+
    3.22+** TODO sh* tools
    3.23+:PROPERTIES:
    3.24+:ID:       c0613a13-7ccb-4af9-b47e-e14a41c782c2
    3.25+:END:
    3.26+:LOGBOOK:
    3.27+- State "TODO"       from "TODO"       [2023-04-07 Fri 23:22]
    3.28+:END:
    3.29+shc,shx,etc
    3.30+* WIP packy
    3.31+:LOGBOOK:
    3.32+- State "TODO"       from              [2023-04-07 Fri 23:33]
    3.33+:END:
    3.34+** WIP rust
    3.35+** WIP common-lisp
    3.36+** WIP emacs-lisp
    3.37+** python
    3.38+** julia
    3.39+** C
    3.40+** C++
    3.41+* TODO tenex
    3.42+:LOGBOOK:
    3.43+- State "TODO"       from              [2023-04-07 Fri 23:52]
    3.44+:END:
    3.45+* TODO mpk
    3.46+:LOGBOOK:
    3.47+- State "TODO"       from              [2023-04-07 Fri 23:52]
    3.48+:END:
    3.49+* TODO cfg
    3.50+:LOGBOOK:
    3.51+- State "TODO"       from              [2023-04-07 Fri 23:34]
    3.52+:END:
    3.53+* TODO obj
    3.54+:LOGBOOK:
    3.55+- State "TODO"       from              [2023-04-07 Fri 23:51]
    3.56+:END:
    3.57+split out from rlib to separate package
    3.58+- a purely OOP class library
    3.59+* TODO lab
    3.60+:LOGBOOK:
    3.61+- State "TODO"       from              [2023-04-07 Fri 23:34]
    3.62+:END:
    3.63+* TODO source categories
    3.64+- need a way of extracting metadata from a repo
    3.65+- need ability to search and query libs/packages
    3.66+- separate modules based on where they belong in our stack?
    3.67+  - app
    3.68+  - lib
    3.69+  - script?
    3.70+  - dist
    3.71+    - software distros
    3.72+* TODO generic query language
    3.73+from obj protocol?
    3.74+sql compatibility?
    3.75+
    3.76+/check out kdb/
    3.77+* TODO bbdb
    3.78+:LOGBOOK:
    3.79+- Note taken on [2023-10-24 Tue 22:16] \\
    3.80+  graph database, build on rocksdb
    3.81+:END:
    3.82+insidious Big Brother database.
    3.83+- an application built with obj
    3.84+- sql
    3.85+
    3.86+* TODO NAS-TV                                                         :nas:t:
    3.87+- media streaming
    3.88+- gstreamer backend
    3.89+- audio/video

     5.1--- a/readme.org	Fri Oct 20 20:21:26 2023 -0400
     5.2+++ b/readme.org	Tue Oct 24 22:23:37 2023 -0400
     5.3@@ -0,0 +1,11 @@
     5.4+#+TITLE: comp/org
     5.5+
     5.6+* blog
     5.7+
     5.8+* docs
     5.9+
    5.10+* notes
    5.11+
    5.12+* pitch
    5.13+
    5.14+* roadmap

     7.1--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     7.2+++ b/scratch/20230730.org	Tue Oct 24 22:23:37 2023 -0400
     7.3@@ -0,0 +1,36 @@
     7.4+* VC infrastructure
     7.5+In heptapod we have a root group named =comp=, containg a variety of
     7.6+subgroups. Some of these groups should be public, while others are
     7.7+internal to comp members exclusively. Within each subgroup, we should
     7.8+have the root group members automatically granted privileged access to
     7.9+projects. This is relevant for the =startup= subgroup in particular,
    7.10+where each project is potentially maintained by multiple non-root
    7.11+contributors.
    7.12+
    7.13+We also need to consider how we will manage subrepos across the
    7.14+organization. It is about time we start integrating HG bundles and
    7.15+potentially mirrors. For our core VC pipeline we should have no
    7.16+reliance on Git, but this may be difficult. It depends on the behavior
    7.17+of HG bundles.
    7.18+
    7.19+Bookmarks/tags should be used for milestones in the root group and are
    7.20+infrequent. They are more frequent in projects with a regular release
    7.21+life-cycle.
    7.22+* Approaching Webapps
    7.23+I started poking around in the webapp space again so that I can launch
    7.24+a landing page for NAS-T quickly. The Rust situation has improved
    7.25+somewhat on the frontend side, and the axum backend stack is nice.
    7.26+
    7.27+This might seem like a lot of Rust and not a lot of Lisp, which it is,
    7.28+but there's still room for Lisp wherever we need it. It mostly plays a
    7.29+role in the backend, servicing the database and responding to requests
    7.30+from the Rust edges. All of the important tests for the web APIs are
    7.31+also written in Lisp. We will almost certainly use Lisp for all static
    7.32+processing and HTML generation at compile-time.
    7.33+
    7.34+This I believe, is the appropriate way to integrate Lisp into a
    7.35+cutting-edge web-app. You get the good parts of Lisp where you need
    7.36+them (interactive debugging, dynamic language, REPL) and avoid the bad
    7.37+parts (OOB optimization, RPS performance) in areas where the customer
    7.38+would be impacted. In this domain, Lisp takes the form of a glue
    7.39+rather than the bricks and mortar it sometimes appears to us as.

     8.1--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     8.2+++ b/scratch/20231024.org	Tue Oct 24 22:23:37 2023 -0400
     8.3@@ -0,0 +1,59 @@
     8.4+* virt
     8.5+** QEMU
     8.6+** KVM
     8.7+** Hyper-V
     8.8+** Firecracker
     8.9+** Docker
    8.10+** Vagrant
    8.11+** LXC
    8.12+** LXD
    8.13+** containerd
    8.14+** systemd-nspawn
    8.15+** VirtualBox
    8.16+
    8.17+* Concatenative
    8.18+** Factor                                                           :factor:
    8.19+- [2023-07-04 Tue]
    8.20+  Factor is a cool concatenative lang but unfortunately the C interface
    8.21+  (vm/master.h) no longer exists on the master branch.
    8.22+** Joy                                                                 :joy:
    8.23+
    8.24+*** https://hypercubed.github.io/joy/html/j02maf.html
    8.25+
    8.26+*** [[https://builds.openlogicproject.org/content/incompleteness/arithmetization-syntax/arithmetization-syntax.pdf][arithmetization of syntax]]
    8.27+* Lisp                                                                 :lisp:
    8.28+These notes pertain to Lisp. More specifically, ANSI Common Lisp in
    8.29+most places.
    8.30+
    8.31+- https://github.com/lispnik/iup/ - doesn't support MacOS yet, looks
    8.32+  cool though
    8.33+  - what we really need is wasm compiler.. TBD
    8.34+* Rust
    8.35+** Serde
    8.36+- [2023-07-05 Wed] \\
    8.37+  important part of the Rust ecosystem, another dtolnay
    8.38+  contribution. If you want to program a /data/ format in the Rust
    8.39+  ecosystem, this is how you do it.
    8.40+
    8.41+  The way it works is that you define some special structs, a
    8.42+  Serializer and a Deserializer which implement the Serialize and
    8.43+  Deserialize traits provided by serde, respectively.
    8.44+
    8.45+  You can use these structs to provide your public API. The
    8.46+  conventional choice is public top-level functions like from-str
    8.47+  and to-string. That's it, your serialization library can now read and
    8.48+  write your data format as Rust data types.
    8.49+
    8.50+  [[https://serde.rs/enum-representations.html][enum-representations]]
    8.51+  - the default behavior is an externally tagged representation (verbose)
    8.52+
    8.53+  The docs use strings as core IO when implementing a custom format,
    8.54+  but the convention is to implement for T where T is bound by std::io
    8.55+  Read or Write trait. Then you can provide a more robust public API
    8.56+  (from_bytes, from_writer, etc).
    8.57+* C
    8.58+* CPP
    8.59+* Nu
    8.60+[[https://www.nushell.sh/][~]]
    8.61+[[https://www.nushell.sh/cookbook/][cookbook]]
    8.62+[[https://github.com/nushell/nu_scripts][nu_scripts]]