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