2 ** use branches for separate levels of expansion 3 - or perhaps some other VC feature.. although I don't want any
4 parallel to time, as if expansions occur in sequence. Thus things
5 like tags don't feel quite right.
7 for libraries, always prefer
[[https://common-lisp-libraries.readthedocs.io/][defacto libs]] 8 ** [[https://github.com/screenshotbot/screenshotbot-oss][screenshotbot-oss]] 9 - monolithic repo, includes third-party dependencies
10 - full quicklisp source
12 - addresses many of my concerns about running CL in prod
13 - the repo is too heavy for my liking though
14 - I do like the idea of having many systems though
17 **** [[https://github.com/fukamachi/mito][mito]] 18 ORM, sqlite, postgres, mysql support
19 **** [[https://github.com/fukamachi/cl-dbi][cl-dbi]] 20 database independent interface
21 **** [[https://github.com/fukamachi/sxql][sxql]] 24 **** [[https://github.com/launchbadge/sqlx][sqlx]] 25 - supports rustls, tokio
26 - we should write the service queries using a common-lisp DSL!
28 sqlx = { version = "0.7", features = [ "runtime-tokio", "tls-rustls", "any", "chrono" ] }
32 **** [[https://github.com/sharplispers/log4cl/][log4cl]] 35 **** [[https://crates.io/crates/tracing][tracing]] 36 **** [[https://crates.io/crates/tokio-console][tokio-console]] - monitoring tool 37 works with tracing using the
[[https://crates.io/crates/console-subscriber][console-subscriber]] crate
39 [[https://mcclim.common-lisp.dev/][mcclim]] 40 [[https://slint-ui.com/][slint-ui]] 41 [[https://github.com/rabbibotton/clog][clog]]