IRC notes from day 2

1 files changed, 19 insertions, 4 deletions

diff --git a/2021/talks/build.md b/2021/talks/build.md
index dcea8624..7ec0da46 100644
--- a/2021/talks/build.md
+++ b/2021/talks/build.md
@@ -28,10 +28,25 @@ and the challenges.
 
 For more details about CEDAR: <https://gitlab.com/sasanidas/cedar>
 
--   40 minutes:
-    A dive into the Emacs/Lisp machines history, what makes GNU Emacs
-    an Emacs and how you can build an Emacs.
-
+# Discussion
+
+IRC nick: akrl
+
+- I think the performance stuff is mostly orthogonal to elisp.  ex. very large files or files with really long lines grind horribly.
+- agreed, it's typically the massive amount of code that needs to interact with eachother that causes the slowdown but Emacs Lisp itself seems fairly performant.
+- there is a WIP CL implementation written called SICL :) 
+  - akrl: yes but is bootstrapped from SBCL, so... :)
+- I know of three or four other attempts to write CL Emacsen. All long dead...
+- fundamentally there are not very many CL developers: there are probably many more elisp developers by now. C (and C++, and Java, and heck probably F# and Rust) have way more developers, so will always be more likely to gain enough momentum to not just die
+- the fashionable languages have lots of users but tend to fade away, CL is undead for ages... I would help in a CL implementation
+- I think everyone should write their own editor at some point.  It's a very good learning experience.
+  - Alan Kay says a similar thing about writing your own operating system
+  - With Emacs you get both! :-)
+- I would love to see '#_' reader macro in Elisp for comments. core.async port and maybe, immutable collection (but that one is too much to ask)
+- isn't that what Xi-editor tried to build on?
+  - it's definitely what xray tried to build on
+- akrl: I'm extremely skeptical on the feasibility of reaching 100% compatibility :) (with an approachable effort)
+  
 
 [[!inline pages="internal(2021/captions/build)" raw="yes"]]