From e34078ae09c540d356dc8c376b1acb4a005f8caa Mon Sep 17 00:00:00 2001 From: Leo Vivier Date: Fri, 3 Dec 2021 22:12:53 +0100 Subject: Add pad stuff --- 2021/talks/build.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to '2021/talks') diff --git a/2021/talks/build.md b/2021/talks/build.md index 7ec0da46..9b34f6fd 100644 --- a/2021/talks/build.md +++ b/2021/talks/build.md @@ -30,6 +30,19 @@ For more details about CEDAR: # Discussion +Pad: + +- Q1: Which level of compatibility with GNU Emacs do you want to achieve? + - A: I want to achieve 100% compatibility (when possible) +- Q2: Are you then planning to reimplment all Emacs C primitives? + - A:No, the underlayer would be different +- Q3: Do you plan on doing something to ease interaction between redundant "components" in both Elisp and Common Lisp (like CLOS and EIEIO)? How about semantic differences between both? + - A: (Probably answered by voice.) +- Q4: Have you used Nyxt, which is Emacs-like and written in Common Lisp? If so, what did you think about it? + - A: I think it's a great project and I would like to use it as a my main Browse (with the firefox extension layer) +- Q5: "Emacs is a great operating system, just lacking a good editor." How do you feel about the push to use Emacs as a full computing interface, and do you think Cedar could thrive in some of the fully common lisp system ideas that might catch on (like Robert Strandh's proposed CLOSOS)? + - A: I think CEDAR can achieve more integration with the OS (the same as the CL implementations) but I think the goal of been a good Emacs is good enought + 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. -- cgit v1.2.3