3 :ID: 2d40eec1-62f4-4f3d-9be7-110400808e06 5 In heptapod we have a root group named
=comp=, containg a variety of
6 subgroups. Some of these groups should be public, while others are
7 internal to comp members exclusively. Within each subgroup, we should
8 have the root group members automatically granted privileged access to
9 projects. This is relevant for the
=startup= subgroup in particular,
10 where each project is potentially maintained by multiple non-root
13 We also need to consider how we will manage subrepos across the
14 organization. It is about time we start integrating HG bundles and
15 potentially mirrors. For our core VC pipeline we should have no
16 reliance on Git, but this may be difficult. It depends on the behavior
19 Bookmarks/tags should be used for milestones in the root group and are
20 infrequent. They are more frequent in projects with a regular release
24 :ID: 0a52be58-990a-47da-ba5a-a7da7192361c 26 I started poking around in the webapp space again so that I can launch
27 a landing page for NAS-T quickly. The Rust situation has improved
28 somewhat on the frontend side, and the axum backend stack is nice.
30 This might seem like a lot of Rust and not a lot of Lisp, which it is,
31 but there's still room for Lisp wherever we need it. It mostly plays a
32 role in the backend, servicing the database and responding to requests
33 from the Rust edges. All of the important tests for the web APIs are
34 also written in Lisp. We will almost certainly use Lisp for all static
35 processing and HTML generation at compile-time.
37 This I believe, is the appropriate way to integrate Lisp into a
38 cutting-edge web-app. You get the good parts of Lisp where you need
39 them (interactive debugging, dynamic language, REPL) and avoid the bad
40 parts (OOB optimization, RPS performance) in areas where the customer
41 would be impacted. In this domain, Lisp takes the form of a glue
42 rather than the bricks and mortar it sometimes appears to us as.
