updatesHEADmaster

1 files changed, 156 insertions, 101 deletions

diff --git a/2025/captions/emacsconf-2025-schemacs--one-year-progress-update-schemacs-formerly-gypsum--ramin-honary--answers.vtt b/2025/captions/emacsconf-2025-schemacs--one-year-progress-update-schemacs-formerly-gypsum--ramin-honary--answers.vtt
index 738e9779..0ec71aed 100644
--- a/2025/captions/emacsconf-2025-schemacs--one-year-progress-update-schemacs-formerly-gypsum--ramin-honary--answers.vtt
+++ b/2025/captions/emacsconf-2025-schemacs--one-year-progress-update-schemacs-formerly-gypsum--ramin-honary--answers.vtt
@@ -1,7 +1,12 @@
 WEBVTT
 
-00:00:00.000 --> 00:00:03.839
-[oops, forgot to start] object protocol has a scheme implementation.
+NOTE Q: I think that Kiczalez et al.'s metaobject protocol has a scheme implementation, does this mean schemacs will be metaobject-changeable in practice?
+
+00:00:00.000 --> 00:00:01.091
+[oops, forgot to start] [Corwin]: ... object protocol
+
+00:00:01.092 --> 00:00:03.839
+has a scheme implementation.
 
 00:00:03.840 --> 00:00:07.159
 Does this mean schemacs will be
@@ -10,7 +15,7 @@ Does this mean schemacs will be
 meta object changeable in practice?
 
 00:00:11.080 --> 00:00:16.599
-So I don't actually need the meta object protocol so far.
+[Ramin]: So I don't actually need the meta object protocol so far.
 
 00:00:16.600 --> 00:00:19.279
 In the reference implementation for Guile,
@@ -81,11 +86,16 @@ And that's all the more I've needed so far.
 00:01:26.200 --> 00:01:33.399
 So, yeah. Oh, yeah, please, next question. Sure.
 
+NOTE Q: How will the GUI display code be r7rs compliant afaik there is no dlopen in r7rs?
+
 00:01:33.400 --> 00:01:39.599
-So how will the GUI display code be R7RS compliant?
+[Corwin]: So how will the GUI display code be R7RS compliant?
 
-00:01:39.600 --> 00:01:45.079
-As far as I know, there's no DL open in R7RS. That's right.
+00:01:39.600 --> 00:01:44.486
+As far as I know, there's no DL open in R7RS.
+
+00:01:44.487 --> 00:01:45.079
+[Ramin]: That's right.
 
 00:01:45.080 --> 00:01:48.879
 Yeah, R7RS small is extremely small
@@ -142,7 +152,7 @@ support the Schemacs GUI protocol?
 So I've kind of written my own protocol,
 
 00:02:34.200 --> 00:02:36.679
-and it's entirely R7 RSML compliant.
+and it's entirely R7RS small compliant.
 
 00:02:36.680 --> 00:02:38.239
 It's all done with record,
@@ -150,8 +160,10 @@ It's all done with record,
 00:02:38.240 --> 00:02:43.039
 what are they called, record types.
 
+NOTE Q: Do you think some of schemacs could be extracted into SRFIs since you have made it portable between scheme implementations?
+
 00:02:43.040 --> 00:02:46.519
-Do you think some of the Schemacs
+[Corwin]: Do you think some of the Schemacs
 
 00:02:46.520 --> 00:02:50.679
 could be extracted into SFRIs since you've made it portable
@@ -160,7 +172,7 @@ could be extracted into SFRIs since you've made it portable
 between scheme implementations?
 
 00:02:52.880 --> 00:02:55.279
-Yes, I would definitely like to do that.
+[Ramin]: Yes, I would definitely like to do that.
 
 00:02:55.280 --> 00:02:59.239
 Probably first thing I'll do is start splitting up
@@ -169,7 +181,7 @@ Probably first thing I'll do is start splitting up
 and publishing independent libraries
 
 00:03:01.680 --> 00:03:04.319
-on the Aku package manager.
+on the Akku package manager.
 
 00:03:04.320 --> 00:03:07.639
 This is a kind of a package manager ecosystem for Scheme,
@@ -198,11 +210,13 @@ I don't think that exists yet in Scheme,
 00:03:29.840 --> 00:03:34.319
 so I thought that might make a good SRFI.
 
+NOTE Q: Is there a recommended scheme implementation or does it try to be as portable as possible?
+
 00:03:34.320 --> 00:03:36.719
-Is there a recommended Scheme implementation?
+[Corwin]: Is there a recommended Scheme implementation?
 
 00:03:36.720 --> 00:03:44.559
-Guile is the reference implementation.
+[Ramin]: Guile is the reference implementation.
 
 00:03:44.560 --> 00:03:47.279
 It's the only one that works with GUI,
@@ -222,8 +236,10 @@ and I've had trouble with some of the scheme compilers.
 00:04:00.040 --> 00:04:04.839
 But yeah, I would recommend Guile.
 
+NOTE Q: How would Schemacs deal with Emacs' (re)display architecture? Would it be having its own display architecture? If so, how can it be compatible with things like overlays, images, etc.? From what I know, Emacs is extremely idiosyncratic here.
+
 00:04:04.840 --> 00:04:07.719
-But how would schemacs deal with
+[Corwin]: But how would schemacs deal with
 
 00:04:07.720 --> 00:04:10.039
 Emacs's re-display architecture
@@ -238,7 +254,7 @@ And if so, how will you handle
 things like overlays and images?
 
 00:04:18.480 --> 00:04:25.239
-Yeah, definitely. That's to be determined.
+[Ramin]: Yeah, definitely. That's to be determined.
 
 00:04:25.240 --> 00:04:31.279
 So basically, the scheme way of doing things
@@ -288,8 +304,10 @@ specifically to support Emacs Lisp.
 00:05:22.040 --> 00:05:28.559
 I don't know yet. I haven't got that far.
 
+NOTE Q: You were saying that you'd like to get "most" of the one thousand three hundred and something Emacs packages done. Is there a technical blocker to doing them all? Or just a problem of getting enough people in to help and start writing scheme?
+
 00:05:28.560 --> 00:05:30.079
-You were saying that you would like
+[Corwin]: You were saying that you would like
 
 00:05:30.080 --> 00:05:33.479
 to get the most out of the 1300
@@ -304,7 +322,7 @@ Are there technical blockers to doing them all
 or just a problem of getting enough people to jump into it?
 
 00:05:44.040 --> 00:05:48.639
-Yeah, it's just a matter of implementing enough
+[Ramin]: Yeah, it's just a matter of implementing enough
 
 00:05:48.640 --> 00:05:50.839
 of the Emacs built-in functions.
@@ -316,7 +334,7 @@ Right now, there's kind of a big bug.
 I mentioned this also in the presentation.
 
 00:05:59.360 --> 00:06:02.599
-The stacks trace that you saw during my presentation,
+The stacktrace that you saw during my presentation,
 
 00:06:02.600 --> 00:06:05.799
 that is the biggest bug right now
@@ -373,10 +391,10 @@ But I imagine, I have no idea, no way of knowing,
 but I imagine we don't need 100% of them
 
 00:06:56.460 --> 00:06:58.167
-in order to run most of Elpa.
+in order to run most of ELPA.
 
 00:06:58.168 --> 00:07:05.084
-We probably can get some of the important large Elpa packages
+We probably can get some of the important large ELPA packages
 
 00:07:05.085 --> 00:07:12.719
 like Magit and Org mode with just enough of the Emacs Lisp
@@ -394,19 +412,21 @@ So yeah, I'll try to get this bug fixed right away.
 That way we can all start working on it together, hopefully.
 
 00:07:24.980 --> 00:07:27.126
-Highly relatable answer there.
+[Corwin]: Highly relatable answer there.
 
 00:07:27.127 --> 00:07:31.959
 We'll burn that bridge when we're on it or something.
 
+NOTE Q: What are you thoughts on Chicken Scheme? Would it be a good fit?
+
 00:07:31.960 --> 00:07:34.559
-What are your thoughts on chicken scheme?
+[Corwin]: What are your thoughts on Chicken Scheme?
 
 00:07:34.560 --> 00:07:37.199
 Will that be a good fit? Do you think?
 
 00:07:37.200 --> 00:07:41.039
-I think it will be, um, I, I did show
+[Ramin]: I think it will be, um, I, I did show
 
 00:07:41.040 --> 00:07:44.959
 trying to run chicken scheme in my, um, presentation
@@ -424,7 +444,7 @@ Um, it's probably something to do with the, uh, pattern matcher.
 Um, I'm using the pattern matcher,
 
 00:07:58.920 --> 00:08:00.599
-uh, written by Alex shin,
+uh, written by Alex Shinn,
 
 00:08:00.600 --> 00:08:02.599
 which seems to be the most portable.
@@ -439,7 +459,7 @@ But not all scheme compilers implement, what is it called?
 The macro, I can't remember what it's called.
 
 00:08:19.560 --> 00:08:24.199
-There's the macro expansion system for R7 RS small.
+There's the macro expansion system for R7RS small.
 
 00:08:24.200 --> 00:08:27.199
 All of these scheme implementations
@@ -471,11 +491,13 @@ if somebody can help me get it to work on chicken team,
 00:08:52.440 --> 00:08:56.599
 I'd really appreciate it.
 
+NOTE Q: Can this emacs lisp implementation be used by Guile's emacs lisp "mode"?
+
 00:08:56.600 --> 00:09:01.799
-Can this implementation be used by Guile's Emacs Lisp mode?
+[Corwin]: Can this implementation be used by Guile's Emacs Lisp mode?
 
 00:09:01.800 --> 00:09:08.199
-Guile's Emacs list mode. Okay. Yeah, good question.
+[Ramin]: Guile's Emacs Lisp mode. Okay. Yeah, good question.
 
 00:09:08.200 --> 00:09:10.919
 I did mention this last year in my presentation.
@@ -535,10 +557,10 @@ it's necessarily going to be not reliant
 on anything that's inside of the Guile library,
 
 00:10:19.120 --> 00:10:21.479
-including the Emacs LISP interpreter that's there.
+including the Emacs Lisp interpreter that's there.
 
 00:10:21.480 --> 00:10:24.959
-Maybe I could replace the Emacs LISP interpreter in Guile
+Maybe I could replace the Emacs Lisp interpreter in Guile
 
 00:10:24.960 --> 00:10:29.599
 if Andy Wingo would be interested. All right.
@@ -558,8 +580,10 @@ quickly try to make my text a little bigger
 00:10:40.680 --> 00:10:42.799
 so I can read a question that came here.
 
+NOTE Q: I wonder if we could do some sort of programmatic analysis on popular Emacs packages to see what list of functions they tend to depend upon, follow function calls down to the lowest level
+
 00:10:42.800 --> 00:10:48.479
-I wonder if we can do some sort of pragmatic analysis
+[Corwin]: I wonder if we can do some sort of pragmatic analysis
 
 00:10:48.480 --> 00:10:49.959
 on popular Emacs packages
@@ -571,19 +595,22 @@ to see what list of functions they tend to depend on
 while a function calls down to the lower level.
 
 00:10:54.800 --> 00:10:57.209
-Yeah, that would be good.
+[Ramin]: Yeah, that would be good.
 
-00:10:57.210 --> 00:11:02.251
-Somebody please do that for me. Awesome.
+00:10:57.210 --> 00:10:59.382
+Somebody please do that for me.
 
-00:11:02.252 --> 00:11:05.439
-Somebody's raising their hand. Divya.
+00:10:59.383 --> 00:11:05.439
+[Corwin]: Awesome. Somebody's raising their hand. Divya.
 
 00:11:05.440 --> 00:11:08.799
-Let's see. Yeah, can you hear me?
+[Divya]: Let's see. Yeah, can you hear me?
+
+00:11:08.800 --> 00:11:11.734
+[Corwin]: Yes, we can. Yeah, go ahead.
 
-00:11:08.800 --> 00:11:12.359
-Yes, I can. Yeah, go ahead. Hello, thank you.
+00:11:11.735 --> 00:11:12.359
+[Divya]: Hello, thank you.
 
 00:11:12.360 --> 00:11:14.079
 Yeah, this is really awesome.
@@ -612,17 +639,19 @@ Because I know a lot of people do not consider Racket
 00:11:32.960 --> 00:11:36.639
 as a sort of scheme thing, because it grew out of it.
 
+NOTE Q: Do you think there is an opportunity to use Racket?
+
 00:11:36.640 --> 00:11:39.519
-Do you think you'll take something from Racket?
+[Divya]: Do you think you'll take something from Racket?
 
-00:11:39.520 --> 00:11:42.119
+00:11:39.520 --> 00:11:40.424
 Because I think Racket has
 
-00:11:42.120 --> 00:11:44.519
+00:11:40.425 --> 00:11:42.090
 a lot of good ideas that can be used.
 
-00:11:44.520 --> 00:11:48.439
-Yeah, I briefly looked at Racket's GUI library,
+00:11:42.091 --> 00:11:48.439
+[Ramin]: Yeah, I briefly looked at Racket's GUI library,
 
 00:11:48.440 --> 00:11:51.879
 but it's very, very heavily dependent
@@ -640,40 +669,40 @@ is extremely complex for Racket,
 and I don't think it's possible to port it to any other scheme,
 
 00:12:02.160 --> 00:12:07.679
-as far as I know. But Racket is based on SheaScheme.
+as far as I know. But Racket is based on Chez Scheme.
 
 00:12:07.680 --> 00:12:14.479
-And I am making an effort to port my code to Shea's scheme.
+And I am making an effort to port my code to Chez's Scheme.
 
 00:12:14.480 --> 00:12:18.639
 I mentioned this earlier,
 
 00:12:18.640 --> 00:12:22.159
-but there's the Gwen Weinholdt Aku system,
+but there's the Gwen Weinholdt Akku system,
 
 00:12:22.160 --> 00:12:25.439
 which allows you to translate R7RS to R6RS.
 
 00:12:25.440 --> 00:12:28.519
-And since Shea is an R6RS compiler,
+And since Chez is an R6RS compiler,
 
 00:12:28.520 --> 00:12:33.919
 I did at one point get the Emacs Lisp interpreter
 
 00:12:33.920 --> 00:12:34.919
-to compile for Shea,
+to compile for Chez,
 
 00:12:34.920 --> 00:12:38.239
-although I think There's been a change
+although I think there's been a change
 
 00:12:38.240 --> 00:12:40.479
-either to Aku or somewhere in my own code base.
+either to Akku or somewhere in my own code base.
 
 00:12:40.480 --> 00:12:42.879
 It doesn't build anymore, and I'm not sure why.
 
 00:12:42.880 --> 00:12:47.039
-But I would also very much like to run this on Che.
+But I would also very much like to run this on Chez.
 
 00:12:47.040 --> 00:12:54.679
 And I guess in that sense, we'll be able to work on Racket as well.
@@ -697,40 +726,45 @@ But that would be something interesting.
 Yes, I would like to try that.
 
 00:13:12.920 --> 00:13:13.919
-Yeah, it'll be interesting.
+[Divya]: Yeah, it'll be interesting.
 
 00:13:13.920 --> 00:13:15.839
-I do have some experience with chairs.
+I do have some experience with Chez.
 
 00:13:15.840 --> 00:13:17.479
 So, uh, if I can find some time,
 
-00:13:17.480 --> 00:13:21.239
-I'll, I'll, I'll certainly like to, I would appreciate.
+00:13:17.480 --> 00:13:20.006
+I'll, I'll, I'll certainly like to,
+
+00:13:20.007 --> 00:13:21.239
+[Ramin]: I would very much appreciate.
 
 00:13:21.240 --> 00:13:24.039
 Yes. Yeah. Go ahead. Yeah.
 
+NOTE Q: Shouldn't it be enough to just implement the builtin functions? Most of the commands are written in Emacs Lisp, right?
+
 00:13:24.040 --> 00:13:26.079
-Another question I have is, like,
+[Divya]: Another question I have is, like,
 
 00:13:26.080 --> 00:13:29.199
 what exactly is sort of, like, the, the approach is that
 
 00:13:29.200 --> 00:13:31.479
-you'll 1st want to do the interpreter
+you'll first want to do the interpreter
 
 00:13:31.480 --> 00:13:33.799
-and then have enough list functions.
+and then have enough Elisp functions,
 
 00:13:33.800 --> 00:13:36.479
-Uh, getting the max list functions
+ getting the GNU Emacs Lisp functions
 
 00:13:36.480 --> 00:13:38.119
-interpreted or interpretable.
+interpreted or interpretable,
 
 00:13:38.120 --> 00:13:40.999
-And then go for GUI or do you want
+and then go for GUI, or do you want
 
 00:13:41.000 --> 00:13:42.759
 to sort of like go hand in hand
@@ -742,10 +776,10 @@ is like we have the interpreter working on
 and we have also the GUI
 
 00:13:46.960 --> 00:13:53.199
-and we sort of use one for the other.
+and we sort of use one for the other?
 
 00:13:53.200 --> 00:13:56.479
-Yeah, I consider the two tasks to be parallel.
+[Ramin]: Yeah, I consider the two tasks to be parallel.
 
 00:13:56.480 --> 00:13:59.639
 So I'm actually doing the GUI separately.
@@ -802,10 +836,10 @@ In Schemacs, using the Emacs programming language,
 I think that's something that we should worried about
 
 00:14:59.320 --> 00:15:03.399
-after we have enough of the Emacs list implemented.
+after we have enough of the Emacs Lisp implemented.
 
 00:15:03.400 --> 00:15:04.919
-Yeah, that makes sense.
+[Divya]: Yeah, that makes sense.
 
 00:15:04.920 --> 00:15:06.679
 There are sort of, I'm a bit worried.
@@ -829,7 +863,7 @@ And essentially one of the issues that I'm up against
 is that Emacs's display system
 
 00:15:20.360 --> 00:15:25.439
-is sort of very let's say, not flexible.
+is sort of very... let's say, not flexible.
 
 00:15:25.440 --> 00:15:31.839
 When trying to analyze where this inflexibility comes from,
@@ -838,7 +872,7 @@ When trying to analyze where this inflexibility comes from,
 I don't think it's just the display architecture.
 
 00:15:35.760 --> 00:15:38.319
-I think parts of eLISP itself
+I think parts of Elisp itself
 
 00:15:38.320 --> 00:15:43.599
 are connected to the display architecture.
@@ -856,13 +890,13 @@ how the re-display architecture works.
 So I think you'll have to sort of figure out
 
 00:15:57.200 --> 00:16:00.679
-what exactly you can salvage from ELISP
+what exactly you can salvage from Elisp
 
 00:16:00.680 --> 00:16:05.199
 without taking the display architecture baggage.
 
 00:16:05.200 --> 00:16:08.001
-That's right. I do anticipate
+[Ramin]: That's right. I do anticipate
 
 00:16:08.002 --> 00:16:09.876
 that's going to be fairly challenging.
@@ -886,28 +920,31 @@ that will somehow translate down
 to the React-like protocol that I've written.
 
 00:16:30.040 --> 00:16:32.719
-But yeah, I don't I haven't that's nice.
+But yeah, I don't... I haven't... That's nice.
 
-00:16:32.720 --> 00:16:36.319
-No, this is this is very exciting. Yeah. Oh Yes, it is.
+00:16:32.720 --> 00:16:35.256
+[Divya]: No, this is this is very exciting. Yeah.
+
+00:16:35.257 --> 00:16:36.319
+[Ramin]: Oh, yes, it is.
 
 00:16:36.320 --> 00:16:39.559
-Yeah, I'm glad so like a lot of people have told me
+Yeah, I'm glad. A lot of people have told me
 
 00:16:39.560 --> 00:16:41.679
-that they really Are excited to see this project
+that they really are excited to see this project,
 
 00:16:41.680 --> 00:16:42.719
 and this really helps me
 
 00:16:42.720 --> 00:16:46.399
-You know keep focused on this project
+keep focused on this project,
 
 00:16:46.400 --> 00:16:48.319
 because a lot of people are very interested.
 
 00:16:48.320 --> 00:16:50.359
-So It's so I'd like to move on
+[Corwin]: I'd like to move on
 
 00:16:50.360 --> 00:16:52.159
 to a couple of questions from the past.
@@ -916,16 +953,18 @@ to a couple of questions from the past.
 We're starting to build up a good backlog.
 
 00:16:54.480 --> 00:16:59.719
-Thank you for that. Yeah Next question from the pad I have.
+Thank you for that, Divya. Next question from the pad I have.
+
+NOTE Q: Tell us more about this show-stopping bug! How to squash it? Can people help?
 
 00:16:59.720 --> 00:17:02.239
-Can you tell us more about the show stopping bug?
+[Corwin]: Can you tell us more about the show stopping bug?
 
 00:17:02.240 --> 00:17:04.159
 How to squash it? How can people help?
 
 00:17:04.160 --> 00:17:08.799
-OK, well, that one, unfortunately, I think,
+[Ramin]: OK, well, that one, unfortunately, I think,
 
 00:17:08.800 --> 00:17:11.679
 unless you're really a scheme genius
@@ -1059,20 +1098,22 @@ You never know with bugs.
 00:19:17.240 --> 00:19:21.759
 They're always a little bit tricky. Okay, next question.
 
+NOTE Q: Are there performance concerns with implementing certain C primitives in pure scheme?
+
 00:19:21.760 --> 00:19:23.119
-Are there performance concerns
+[Corwin]: Are there performance concerns
 
 00:19:23.120 --> 00:19:28.479
-with implementing certain C primitives in PeerScheme?
+with implementing certain C primitives in pure Scheme?
 
 00:19:28.480 --> 00:19:32.879
-So who is it? The famous computer scientist that said
+[Ramin]: So who is it? The famous computer scientist that said
 
 00:19:32.880 --> 00:19:35.879
 premature optimization is the root of all evil.
 
 00:19:35.880 --> 00:19:39.799
-I think it was the guy who invented the A star algorithm.
+I think it was the guy who invented the A* algorithm.
 
 00:19:39.800 --> 00:19:42.719
 His name escapes me at the minute.
@@ -1084,7 +1125,7 @@ But yeah, I'm not concerned about performance yet,
 although most of the scheme compilers that I have seen,
 
 00:19:52.120 --> 00:19:56.999
-especially Shea and Gambit
+especially Chez and Gambit
 
 00:19:57.000 --> 00:20:02.039
 have extremely good performance characteristics.
@@ -1120,7 +1161,7 @@ maybe for a Wayland implementation or something.
 But I don't know. It's not a concern for me, performance.
 
 00:20:29.080 --> 00:20:32.079
-Okay, there are a few more questions. I do want to mention
+[Corwin]: Okay, there are a few more questions. I do want to mention
 
 00:20:32.080 --> 00:20:33.839
 that the stream has cut away at this point,
@@ -1141,7 +1182,7 @@ So, I appreciate all the enthusiastic questions
 and you're kind of tanking through them all.
 
 00:20:47.800 --> 00:20:52.799
-Me too. I love how many questions I'm getting.
+[Ramin]: Me too. I love how many questions I'm getting.
 
 00:20:52.800 --> 00:20:54.039
 This is very encouraging
@@ -1161,8 +1202,13 @@ I think you should be receiving.
 00:21:01.440 --> 00:21:04.159
 This is a fantastic project. Thank you so much.
 
-00:21:04.160 --> 00:21:08.439
-I'll just say so myself. If the project is successful,
+00:21:04.160 --> 00:21:07.051
+I'll just say so myself.
+
+NOTE Q:  If this project is successful, are you worried about a possible split in the community between Schemacs and GNU Emacs users?
+
+00:21:07.052 --> 00:21:08.439
+[Corwin]: If the project is successful,
 
 00:21:08.440 --> 00:21:11.479
 are you worried about a possible split in the community
@@ -1171,7 +1217,7 @@ are you worried about a possible split in the community
 between Schemacs and GNU Emacs?
 
 00:21:15.600 --> 00:21:18.959
-Oh, I have thought about that.
+[Ramin]: Oh, I have thought about that.
 
 00:21:18.960 --> 00:21:24.039
 And I really don't know what's going to happen.
@@ -1272,11 +1318,16 @@ Oh, Cairo, like Cairo.
 00:23:01.040 --> 00:23:07.599
 Oh, Cairo, yeah. Absolutely. I spelled that poorly.
 
+NOTE Q: The dream of never even needing to change to the web browser - would schemacs bring us closer to that?
+
 00:23:07.600 --> 00:23:12.519
-The dream of never needing to change to the web browser.
+[Corwin]: The dream of never needing to change to the web browser.
 
-00:23:12.520 --> 00:23:18.376
-Would schemacs bring us closer to that? I hope so.
+00:23:12.520 --> 00:23:17.818
+Would schemacs bring us closer to that?
+
+00:23:17.819 --> 00:23:18.376
+[Ramin]: I hope so.
 
 00:23:18.377 --> 00:23:21.709
 That's also a dream of mine.
@@ -1294,7 +1345,7 @@ is so that I could, you know,
 we could write apps like, you know,
 
 00:23:34.880 --> 00:23:38.759
-they have a mastodon client written in Emacs Lisp.
+they have a Mastodon client written in Emacs Lisp.
 
 00:23:38.760 --> 00:23:42.199
 that would be so nice to have this, you know,
@@ -1338,11 +1389,13 @@ And so I hope that that's where we end up in a couple of years.
 00:24:20.080 --> 00:24:29.999
 The sooner the better. Anything, just double checking.
 
+NOTE Q: Anything specific other than minimalism that made you choose Scheme over Common Lisp?
+
 00:24:30.000 --> 00:24:33.319
 Anything specific other than minimalism
 
 00:24:33.320 --> 00:24:35.799
-that made you choose Scheme over Commonwealth?
+that made you choose Scheme over Common Lisp?
 
 00:24:35.800 --> 00:24:40.199
 Oh, yeah, it's kind of a philosophical question.
@@ -1354,7 +1407,7 @@ So a couple of things. First of all, it was a conversation
 I had with William Byrd,
 
 00:24:47.400 --> 00:24:50.519
-and he's a guy who makes the Mini Conran framework for Scheme.
+and he's a guy who makes the miniKanren framework for Scheme.
 
 00:24:50.520 --> 00:24:52.879
 It was his PhD thesis.
@@ -1447,7 +1500,7 @@ a fraction of what it can do.
 That's why I've chosen scheme.
 
 00:26:22.400 --> 00:26:24.719
-Divya, I see you've got a bunch more comments.
+[Corwin]: Divya, I see you've got a bunch more comments.
 
 00:26:24.720 --> 00:26:26.679
 I think we're just about close to our time here,
@@ -1459,7 +1512,7 @@ but if you wanted to jump back in,
 I'm sorry, I had to cut you off a little before.
 
 00:26:30.520 --> 00:26:33.959
-No, it's fine. No, it's fine.
+[Divya]: No, it's fine. No, it's fine.
 
 00:26:33.960 --> 00:26:36.599
 I think I agree with most of what he said.
@@ -1467,11 +1520,13 @@ I think I agree with most of what he said.
 00:26:36.600 --> 00:26:40.679
 So, yeah, thank you so much.
 
+NOTE Closing thoughts
+
 00:26:40.680 --> 00:26:45.159
-Um, closing thoughts, Ramin.
+[Corwin]: Um, closing thoughts, Ramin.
 
 00:26:45.160 --> 00:26:51.639
-Yeah, I guess everybody, please, if you're interested,
+[Ramin]: Yeah, I guess everybody, please, if you're interested,
 
 00:26:51.640 --> 00:26:56.719
 keep watching my Mastodon and keep watching my Codeberg.
@@ -1504,7 +1559,7 @@ and I think we're pretty close
 to getting something that we can all use together.
 
 00:27:29.120 --> 00:27:31.719
-Thank you once again for your amazing talk,
+[Corwin]: Thank you once again for your amazing talk,
 
 00:27:31.720 --> 00:27:34.039
 for your exceptional work,
@@ -1516,7 +1571,7 @@ and for jumping in, doing the live Q&A,
 rolling with us here as we have yet another
 
 00:27:40.040 --> 00:27:42.079
-We'll See How It Goes conference.
+"we'll see how it goes" conference.
 
 00:27:42.080 --> 00:27:44.279
 It's been just amazing so far,
@@ -1525,7 +1580,7 @@ It's been just amazing so far,
 and this talk is no small part of that. Thank you.
 
 00:27:46.840 --> 00:27:50.279
-Oh, thank you so much. Yeah. OK, cool.
+[Ramin]: Oh, thank you so much. Yeah. OK, cool.
 
 00:27:50.280 --> 00:27:51.834
 And thanks for all the questions, everyone.