changelog shortlog graph tags branches changeset file revisions annotate raw help

Mercurial > org > notes / 20230730.org

revision 15: 45ac54093c09
parent 14: a04ca5a66178
child 16: a63dfd1affed
     1.1--- a/20230730.org	Tue Aug 27 21:35:44 2024 -0400
     1.2+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.3@@ -1,42 +0,0 @@
     1.4-* VC infrastructure
     1.5-:PROPERTIES:
     1.6-:ID:       2d40eec1-62f4-4f3d-9be7-110400808e06
     1.7-:END:
     1.8-In heptapod we have a root group named =comp=, containg a variety of
     1.9-subgroups. Some of these groups should be public, while others are
    1.10-internal to comp members exclusively. Within each subgroup, we should
    1.11-have the root group members automatically granted privileged access to
    1.12-projects. This is relevant for the =startup= subgroup in particular,
    1.13-where each project is potentially maintained by multiple non-root
    1.14-contributors.
    1.15-
    1.16-We also need to consider how we will manage subrepos across the
    1.17-organization. It is about time we start integrating HG bundles and
    1.18-potentially mirrors. For our core VC pipeline we should have no
    1.19-reliance on Git, but this may be difficult. It depends on the behavior
    1.20-of HG bundles.
    1.21-
    1.22-Bookmarks/tags should be used for milestones in the root group and are
    1.23-infrequent. They are more frequent in projects with a regular release
    1.24-life-cycle.
    1.25-* Approaching Webapps
    1.26-:PROPERTIES:
    1.27-:ID:       0a52be58-990a-47da-ba5a-a7da7192361c
    1.28-:END:
    1.29-I started poking around in the webapp space again so that I can launch
    1.30-a landing page for NAS-T quickly. The Rust situation has improved
    1.31-somewhat on the frontend side, and the axum backend stack is nice.
    1.32-
    1.33-This might seem like a lot of Rust and not a lot of Lisp, which it is,
    1.34-but there's still room for Lisp wherever we need it. It mostly plays a
    1.35-role in the backend, servicing the database and responding to requests
    1.36-from the Rust edges. All of the important tests for the web APIs are
    1.37-also written in Lisp. We will almost certainly use Lisp for all static
    1.38-processing and HTML generation at compile-time.
    1.39-
    1.40-This I believe, is the appropriate way to integrate Lisp into a
    1.41-cutting-edge web-app. You get the good parts of Lisp where you need
    1.42-them (interactive debugging, dynamic language, REPL) and avoid the bad
    1.43-parts (OOB optimization, RPS performance) in areas where the customer
    1.44-would be impacted. In this domain, Lisp takes the form of a glue
    1.45-rather than the bricks and mortar it sometimes appears to us as.