summaryrefslogtreecommitdiffstats
path: root/2024/talks/gypsum.md
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--2024/talks/gypsum.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/2024/talks/gypsum.md b/2024/talks/gypsum.md
index c566357c..3ee7c4cd 100644
--- a/2024/talks/gypsum.md
+++ b/2024/talks/gypsum.md
@@ -456,7 +456,8 @@ You may also like another talk by this speaker:
- guile-elisp is part of guile's compiler system (elisp -> tree-il -> cps -> bytecode), unless another scheme sets out to be guile-compatible in that respect it won't be portable at all
- To be fair, I've been screwing around with chicken, guile, and racket. I haven't found any 2 scheme implementations to be compatible, even within SRFI implementations
- Just the basic syntax and semantics, nothing else
- - yeah, scheme's lack of portable libraries in practice motivated me to suggest something that's sure to piss everyone off; Javascript
+ - yeah, scheme's lack of portable libraries in practice motivated me to suggest something that's sure to piss everyone off: Javascript
+- YouTube comment: Cool, great, amazing. Extremely ambitious. A clone like this project might be significant harder than for example Lem, which does not care about backward compatibility with Emacs. A clone also is somewhat harder to create a unique selling point for. Especially if Guile-Emacs is also going to be a thing now. Just my 2 cents up to discussions. Anyway I am excited and will follow it:)
[[!inline pages="internal(2024/info/gypsum-after)" raw="yes"]]