about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorDarren Bane <darren.bane@gmail.com>2020-10-22 19:21:29 +0100
committerDarren Bane <darren.bane@gmail.com>2020-10-22 19:21:29 +0100
commitf2a165df9877bc25f4358c245e6dbc7ee375042b (patch)
treed12f5e944086f537404f11e74c29354df321475e
parent290b6a9de3f2877dca7f6e623fae435b373d24ef (diff)
downloadlsp-f2a165df9877bc25f4358c245e6dbc7ee375042b.tar.gz
Threading is hard
-rw-r--r--doc/breaking_rules.md5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/breaking_rules.md b/doc/breaking_rules.md
index 29c8267..94c7141 100644
--- a/doc/breaking_rules.md
+++ b/doc/breaking_rules.md
@@ -74,6 +74,8 @@ The following technology is recommended:
 
 For simple multi-user,
 use the IRCv3 bots (nickserv, chanserv) and IRCCloud or similar.
+But avoid multi-threading at this stage,
+event-driven should do the job.
 
 The following is probably the most work that makes sense
 without earning money.
@@ -138,7 +140,8 @@ First, ensure that the surrounding infrastructure is in place:
 Then, the following code & documentation improvements should be made:
 
 * Document the system more exhaustively
-* Can use more of quicklisp, e.g. the trivial-\* libraries.
+* Can use more of quicklisp, e.g. the trivial-\* libraries
+* Can multi-thread to take advantage of all cores
 * Port to platform.sh?
 
 Since we have a working prototype,