taoeffect · February 20, 2026 22:31 · Oct 22, 2025 · Oct 22, 2025 · Oct 22, 2025 · Oct 21, 2025
diff --git a/Great Editor.md b/Great Editor.md
@@ -64,7 +64,7 @@ Rust and Zig are disqualified for bad syntax. Zed's greatness comes in spite of
 
 For extending the editor, use a simple programming langauge that is powerful. Use something like [Janet](https://janet-lang.org/). Maybe Scheme.
 
-Lisps are a fantastic choice. Some will say to use Lua, but Lua isn't 0-based indexed, and its syntax is a bit verbose, although it's simple (do you really need to write out `end` instead of `)` or `}`?).
+Lisps are a fantastic choice. Some will say to use Lua, but Lua isn't 0-based indexed, and its syntax is a bit verbose, although it's simple (do we really need to write out `end` instead of `)` or `}`?).
 
 You don't need syntax. You need design!
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -64,7 +64,7 @@ Rust and Zig are disqualified for bad syntax. Zed's greatness comes in spite of
 
 For extending the editor, use a simple programming langauge that is powerful. Use something like [Janet](https://janet-lang.org/). Maybe Scheme.
 
-Lisps are a fantastic choice. Some will say to use Lua, but Lua isn't 0-based indexed, and its syntax is a bit verbose, although it's simple.
+Lisps are a fantastic choice. Some will say to use Lua, but Lua isn't 0-based indexed, and its syntax is a bit verbose, although it's simple (do you really need to write out `end` instead of `)` or `}`?).
 
 You don't need syntax. You need design!
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -64,7 +64,7 @@ Rust and Zig are disqualified for bad syntax. Zed's greatness comes in spite of
 
 For extending the editor, use a simple programming langauge that is powerful. Use something like [Janet](https://janet-lang.org/). Maybe Scheme.
 
-Lisps are a fantastic choice. Some will say to use Lua, but Lua isn't 0-based indexed, and it still has [too much syntax](https://www.taoeffect.com/blog/2010/01/how-newlisp-took-my-breath-and-syntax-away/).
+Lisps are a fantastic choice. Some will say to use Lua, but Lua isn't 0-based indexed, and its syntax is a bit verbose, although it's simple.
 
 You don't need syntax. You need design!
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -56,7 +56,7 @@ Everything should "just work" on every system and with the absolute minimum inte
 
 ## Write It In A Fast Memory-safe Language
 
-Choose either Go, [V](https://vlang.io/) (V is like Go [but better](https://vlang.io/compare)), or Guile Scheme.
+Choose either Go, [V](https://vlang.io/) (V is like Go [but better](https://vlang.io/compare)), or Scheme.
 
 Rust and Zig are disqualified for bad syntax. Zed's greatness comes in spite of its choice of Rust, not because of it (although Rust certainly has its upsides when compared to something like C++).
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -56,7 +56,7 @@ Everything should "just work" on every system and with the absolute minimum inte
 
 ## Write It In A Fast Memory-safe Language
 
-Choose either Go, [V](https://vlang.io/) (V is like Go [but better](https://vlang.io/compare)), or Julia. Maybe Guile Scheme.
+Choose either Go, [V](https://vlang.io/) (V is like Go [but better](https://vlang.io/compare)), or Guile Scheme.
 
 Rust and Zig are disqualified for bad syntax. Zed's greatness comes in spite of its choice of Rust, not because of it (although Rust certainly has its upsides when compared to something like C++).
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -56,7 +56,7 @@ Everything should "just work" on every system and with the absolute minimum inte
 
 ## Write It In A Fast Memory-safe Language
 
-Choose either Go, [V](https://vlang.io/), or Julia. Maybe Guile Scheme.
+Choose either Go, [V](https://vlang.io/) (V is like Go [but better](https://vlang.io/compare)), or Julia. Maybe Guile Scheme.
 
 Rust and Zig are disqualified for bad syntax. Zed's greatness comes in spite of its choice of Rust, not because of it (although Rust certainly has its upsides when compared to something like C++).
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -68,6 +68,8 @@ Lisps are a fantastic choice. Some will say to use Lua, but Lua isn't 0-based in
 
 You don't need syntax. You need design!
 
+You could also stick with the language the editor itself is written in.
+
 And if you really want something else, choose JavaScript. Whatever. 🙄 (But use Deno!)
 
 ## Simple Preferences

diff --git a/Great Editor.md b/Great Editor.md
@@ -56,7 +56,7 @@ Everything should "just work" on every system and with the absolute minimum inte
 
 ## Write It In A Fast Memory-safe Language
 
-Choose either Go, V, or Julia. Maybe Guile Scheme.
+Choose either Go, [V](https://vlang.io/), or Julia. Maybe Guile Scheme.
 
 Rust and Zig are disqualified for bad syntax. Zed's greatness comes in spite of its choice of Rust, not because of it (although Rust certainly has its upsides when compared to something like C++).
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -40,7 +40,7 @@ And sometimes these things just kind of step on each other's toes. So if you wan
 
 ## Create An Extensible Editor
 
-[Micro](https://micro-editor.github.io/) is a great example of a decent starting point for a modern terminal editor.
+[Micro](https://micro-editor.github.io/) is a great example of a decent starting point for a modern terminal editor. Its copy/paste and mouse integration are excellent.
 
 However it is too primitive, and its extensibility is too limited.
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -104,7 +104,7 @@ Everyone's got opinions, but some people's opinions are just wrong.
 
 Why is Zed succeeding? Because it's got opinions, and they're the right ones (comparatively speaking).
 
-This is the sort of wisdom you only get with experience, so learn from the experience of others. I've over two decades of writing software in various languages using various editors. These aren't just "opinions", they're battle scars.
+This is the sort of wisdom you only get with experience, so learn from the experience of others. I've over two decades of experience writing software in various languages using various editors. These aren't just "opinions", they're battle scars.
 
 ## Good Luck!
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -104,7 +104,7 @@ Everyone's got opinions, but some people's opinions are just wrong.
 
 Why is Zed succeeding? Because it's got opinions, and they're the right ones (comparatively speaking).
 
-This is the sort of wisdom you only get with experience, so learn from the experience of others.
+This is the sort of wisdom you only get with experience, so learn from the experience of others. I've over two decades of writing software in various languages using various editors. These aren't just "opinions", they're battle scars.
 
 ## Good Luck!
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -58,7 +58,7 @@ Everything should "just work" on every system and with the absolute minimum inte
 
 Choose either Go, V, or Julia. Maybe Guile Scheme.
 
-Rust and Zig are disqualified for bad syntax.
+Rust and Zig are disqualified for bad syntax. Zed's greatness comes in spite of its choice of Rust, not because of it (although Rust certainly has its upsides when compared to something like C++).
 
 ## Use A Decent Scripting Language
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -94,7 +94,7 @@ AI agents are incredible. Make it easy for them to interact with the editor.
 
 ## Have A Menu (Bar)
 
-How do users discover the editor's features? How to they learn the default keyboard shortcuts?
+How do users discover the editor's features? How do they learn the default keyboard shortcuts?
 
 ...A menu! I'll leave it up to you to decide whether it should be a menubar or a popup menu.
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -92,11 +92,11 @@ Your machine shouldn't be compromised just because you decided to try out a new
 
 AI agents are incredible. Make it easy for them to interact with the editor.
 
-## Have A Menu Bar
+## Have A Menu (Bar)
 
 How do users discover the editor's features? How to they learn the default keyboard shortcuts?
 
-...A menubar!
+...A menu! I'll leave it up to you to decide whether it should be a menubar or a popup menu.
 
 ## Be Opinionated, But Have the Right Opinions
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -92,6 +92,12 @@ Your machine shouldn't be compromised just because you decided to try out a new
 
 AI agents are incredible. Make it easy for them to interact with the editor.
 
+## Have A Menu Bar
+
+How do users discover the editor's features? How to they learn the default keyboard shortcuts?
+
+...A menubar!
+
 ## Be Opinionated, But Have the Right Opinions
 
 Everyone's got opinions, but some people's opinions are just wrong.

diff --git a/Great Editor.md b/Great Editor.md
@@ -28,7 +28,7 @@ I want a source code editor, not the tools to build a slightly crappy source cod
 
 ## What To Do Instead
 
-The problem with Emacs is that although it is "extremely powerful" thanks to the ability for anyone to exend it as they please, this is NOT an OK design for building a great editor.
+The problem with Emacs is that although it is "extremely powerful" thanks to the ability for anyone to extend it as they please, this is NOT an OK design for building a great editor.
 
 Even if you use "emacs starter kits", you'll quickly discover that they're a PITA, and this PITA comes from the fact that Emacs has no hard and steadfast rules for how to extend it. It gives everyone the ability to do whatever they want, however they want, and this quickly turns into a furball mess of a nightmare.
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -68,7 +68,7 @@ Lisps are a fantastic choice. Some will say to use Lua, but Lua isn't 0-based in
 
 You don't need syntax. You need design!
 
-And if you really want something else, choose JavaScript. Whatever. 🙄
+And if you really want something else, choose JavaScript. Whatever. 🙄 (But use Deno!)
 
 ## Simple Preferences
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -56,7 +56,7 @@ Everything should "just work" on every system and with the absolute minimum inte
 
 ## Write It In A Fast Memory-safe Language
 
-Choose either Go, V, or Julia.
+Choose either Go, V, or Julia. Maybe Guile Scheme.
 
 Rust and Zig are disqualified for bad syntax.
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -36,7 +36,7 @@ We need strict rules for doing everything.
 
 It's absurd that if I want to set the indentation level to 2 spaces in Emacs, I have to think about potentially 50 different "modes" and "variables" to do that. There isn't a *single* variable to adjust. There's an uncountable and unknowable number of variables, because each package does its own thing and uses its own stuff.
 
-And sometimes these things just kind of step on each other's toes. So if you want to use Package A with Package B, sometime they just don't work well together, because nobody is following any hard rules for how to create their packages, it's all just a random mishmash of elisp, a garbage Lisp btw that is bascially Common Lisp, another crappy Lisp (which still puts it head and shoulders above most other languages).
+And sometimes these things just kind of step on each other's toes. So if you want to use Package A with Package B, sometimes they just don't work well together, because nobody is following any hard rules for how to create their packages, it's all just a random mishmash of elisp, a garbage Lisp btw that is bascially Common Lisp, another crappy Lisp (which still puts it head and shoulders above most other languages).
 
 ## Create An Extensible Editor
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -56,7 +56,9 @@ Everything should "just work" on every system and with the absolute minimum inte
 
 ## Write It In A Fast Memory-safe Language
 
-Choose either Go, V, Julia, Rust or Zig.
+Choose either Go, V, or Julia.
+
+Rust and Zig are disqualified for bad syntax.
 
 ## Use A Decent Scripting Language
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -56,7 +56,7 @@ Everything should "just work" on every system and with the absolute minimum inte
 
 ## Write It In A Fast Memory-safe Language
 
-Choose either Go, V, Rust or Zig.
+Choose either Go, V, Julia, Rust or Zig.
 
 ## Use A Decent Scripting Language
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -54,6 +54,10 @@ Allow the plugins to work together, but make sure there are clear rules about ho
 
 Everything should "just work" on every system and with the absolute minimum intervention from the user.
 
+## Write It In A Fast Memory-safe Language
+
+Choose either Go, V, Rust or Zig.
+
 ## Use A Decent Scripting Language
 
 For extending the editor, use a simple programming langauge that is powerful. Use something like [Janet](https://janet-lang.org/). Maybe Scheme.

diff --git a/Great Editor.md b/Great Editor.md
@@ -84,7 +84,7 @@ Your machine shouldn't be compromised just because you decided to try out a new
 
 ## Integrate With AI
 
-AI agents are incredible. Make easy for them to interact with the editor.
+AI agents are incredible. Make it easy for them to interact with the editor.
 
 ## Be Opinionated, But Have the Right Opinions
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -82,6 +82,10 @@ If there's a bug with a plugin or the editor itself, make this information easil
 
 Your machine shouldn't be compromised just because you decided to try out a new theme or a new table editing plugin.
 
+## Integrate With AI
+
+AI agents are incredible. Make easy for them to interact with the editor.
+
 ## Be Opinionated, But Have the Right Opinions
 
 Everyone's got opinions, but some people's opinions are just wrong.

diff --git a/Great Editor.md b/Great Editor.md
@@ -74,6 +74,14 @@ Enforce this format for both the editor's settings and plugin settings.
 
 NOBODY SHOULD BE FORCED TO USE A PROGRAMMING LANGUAGE TO CONFIGURE THEIR EDITOR!
 
+## Make It Easy To Diagnose Problems
+
+If there's a bug with a plugin or the editor itself, make this information easily accessible to both users and AI tools.
+
+## Sandbox Your Plugins
+
+Your machine shouldn't be compromised just because you decided to try out a new theme or a new table editing plugin.
+
 ## Be Opinionated, But Have the Right Opinions
 
 Everyone's got opinions, but some people's opinions are just wrong.

diff --git a/Great Editor.md b/Great Editor.md
@@ -72,6 +72,8 @@ Zed's choice of JSON here is excellent. JSONC would be even better. TOML is also
 
 Enforce this format for both the editor's settings and plugin settings.
 
+NOBODY SHOULD BE FORCED TO USE A PROGRAMMING LANGUAGE TO CONFIGURE THEIR EDITOR!
+
 ## Be Opinionated, But Have the Right Opinions
 
 Everyone's got opinions, but some people's opinions are just wrong.

diff --git a/Great Editor.md b/Great Editor.md
@@ -46,7 +46,7 @@ However it is too primitive, and its extensibility is too limited.
 
 We need something like Emacs, but a well designed Emacs. Basically Zed for the terminal.
 
-The reason why Zed is so amazing is because it does everything, and it does almost everything correctly. We's well designed. It's extensible. And it's not a cluttered difficult-to-use mess.
+The reason why Zed is so amazing is because it does everything, and it does almost everything correctly. It's well designed. It's extensible. And it's not a cluttered difficult-to-use mess.
 
 So create a powerful plugin system, where plugins and the editor can seamlessly interoperate together, and can powerfully extend the editor, but *without* each plugin having to re-invent the wheel for whatever settings its needs. Every plugin should work smoothly with every other plugin, and each should use as many settings from the editor itself as opposed to providing its own little world of configuration. Whatever configuration the plugins do offer need to be truly unique to their use-case.
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -42,7 +42,7 @@ And sometimes these things just kind of step on each other's toes. So if you wan
 
 [Micro](https://micro-editor.github.io/) is a great example of a decent starting point for a modern terminal editor.
 
-However it is too primitive, and what its extensibility is too limited.
+However it is too primitive, and its extensibility is too limited.
 
 We need something like Emacs, but a well designed Emacs. Basically Zed for the terminal.
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -18,7 +18,7 @@ Don't think I'm going to spare Emacs either.
 
 It might've been the best thing around back in the day, but by today's standards, that award goes to [Zed](https://zed.dev/).
 
-And editor should "just work", and Emacs doesn't.
+An editor should "just work", and Emacs doesn't.
 
 Using emacs is like getting a house that consists of a foundation, and several piles of wood and boxes of nails and tools.
 

diff --git a/Great Editor.md b/Great Editor.md
@@ -0,0 +1,85 @@
+# How To Build A Great Terminal Editor That Is Better Than Emacs and VIM
+
+Everyone has their opinion. This is mine.
+
+First, building an editor that is better than VIM is quite easy: avoid VIM and modal-based editing.
+
+## Why Modal Editing Is Wrong
+
+Perhaps I'm an alien, or perhaps VIM users are aliens, but there is no reason for modal-based editing.
+
+Modal-based editing is unnatural. If I want to do something, I shouldn't have to first think about what "mode" I'm in. That's dumb and slows users down for no reason.
+
+Every modern editor uses keyboard shortcuts, just like Emacs pioneered back in the day, and that's how all terminal editors should be (as long as their user-interface is a keyboard).
+
+## Why Emacs Sucks
+
+Don't think I'm going to spare Emacs either.
+
+It might've been the best thing around back in the day, but by today's standards, that award goes to [Zed](https://zed.dev/).
+
+And editor should "just work", and Emacs doesn't.
+
+Using emacs is like getting a house that consists of a foundation, and several piles of wood and boxes of nails and tools.
+
+That's Emacs.
+
+I want a source code editor, not the tools to build a slightly crappy source code editor.
+
+## What To Do Instead
+
+The problem with Emacs is that although it is "extremely powerful" thanks to the ability for anyone to exend it as they please, this is NOT an OK design for building a great editor.
+
+Even if you use "emacs starter kits", you'll quickly discover that they're a PITA, and this PITA comes from the fact that Emacs has no hard and steadfast rules for how to extend it. It gives everyone the ability to do whatever they want, however they want, and this quickly turns into a furball mess of a nightmare.
+
+We need strict rules for doing everything.
+
+It's absurd that if I want to set the indentation level to 2 spaces in Emacs, I have to think about potentially 50 different "modes" and "variables" to do that. There isn't a *single* variable to adjust. There's an uncountable and unknowable number of variables, because each package does its own thing and uses its own stuff.
+
+And sometimes these things just kind of step on each other's toes. So if you want to use Package A with Package B, sometime they just don't work well together, because nobody is following any hard rules for how to create their packages, it's all just a random mishmash of elisp, a garbage Lisp btw that is bascially Common Lisp, another crappy Lisp (which still puts it head and shoulders above most other languages).
+
+## Create An Extensible Editor
+
+[Micro](https://micro-editor.github.io/) is a great example of a decent starting point for a modern terminal editor.
+
+However it is too primitive, and what its extensibility is too limited.
+
+We need something like Emacs, but a well designed Emacs. Basically Zed for the terminal.
+
+The reason why Zed is so amazing is because it does everything, and it does almost everything correctly. We's well designed. It's extensible. And it's not a cluttered difficult-to-use mess.
+
+So create a powerful plugin system, where plugins and the editor can seamlessly interoperate together, and can powerfully extend the editor, but *without* each plugin having to re-invent the wheel for whatever settings its needs. Every plugin should work smoothly with every other plugin, and each should use as many settings from the editor itself as opposed to providing its own little world of configuration. Whatever configuration the plugins do offer need to be truly unique to their use-case.
+
+Allow the plugins to work together, but make sure there are clear rules about how this is done.
+
+Everything should "just work" on every system and with the absolute minimum intervention from the user.
+
+## Use A Decent Scripting Language
+
+For extending the editor, use a simple programming langauge that is powerful. Use something like [Janet](https://janet-lang.org/). Maybe Scheme.
+
+Lisps are a fantastic choice. Some will say to use Lua, but Lua isn't 0-based indexed, and it still has [too much syntax](https://www.taoeffect.com/blog/2010/01/how-newlisp-took-my-breath-and-syntax-away/).
+
+You don't need syntax. You need design!
+
+And if you really want something else, choose JavaScript. Whatever. 🙄
+
+## Simple Preferences
+
+Use a common storage format for storing your user's preferences.
+
+Zed's choice of JSON here is excellent. JSONC would be even better. TOML is also great.
+
+Enforce this format for both the editor's settings and plugin settings.
+
+## Be Opinionated, But Have the Right Opinions
+
+Everyone's got opinions, but some people's opinions are just wrong.
+
+Why is Zed succeeding? Because it's got opinions, and they're the right ones (comparatively speaking).
+
+This is the sort of wisdom you only get with experience, so learn from the experience of others.
+
+## Good Luck!
+
+Let me know when you get it done. I've been looking everywhere for a decent terminal editor and I can't find one.
No results found