编程与软件工程yehudakatz.com
所有劝我用 Vim 的人都错了
Everyone Who Tried to Convince Me to Use Vim Was Wrong
2010 — 2019，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
这是 Yehuda Katz 2010 年的一篇博客文章，他反驳那些劝他转用 Vim 的人，并质疑是否存在一种不会在头几周显著降低生产力的切换方式。文章引发了关于 Vim 陡峭学习曲线和模态编辑本质的长期讨论。
为什么经久不衰：它精准触及了“短期生产力 vs 长期收益”和模态编辑这一 Vim 入门核心痛点，所以十多年来每次讨论编辑器选择时都会被翻出来。
HN 评论精选
Vim 难学的核心是模态编辑，而非普通新编辑器的学习曲线。
我认为 Katz 没做出的关键区分是：切换到 Vim 并不是“你在学一个新编辑器，当然会有学习曲线”的问题。正如有人指出的，TextMate 也是新编辑器，但你第一次用并不会停滞。Vim 与 TextMate 是根本不同种类的编辑器。不是不同程序，而是它可能是你第一个模态编辑器。在我看来，学 Vim 最难的第一步主要就是理解模态编辑。无论你是想禁用方向键、强迫自己离开插入模式来培养好习惯，还是只想凑合着用、能用到多少 Vim 特性就用多少，全看读者自己。这类似于你想一直盖住键帽用 Dvorak 即使还不会盲打，还是慢慢来。但那个坎——质性不同的体验——就是应用的模态性。
crux查看英文原文
I think the key distinction that Katz is failing to make is this: switching to Vim is not a matter of 'You’re learning a new EDITOR for God’s sakes. Of COURSE there’s going to be a learning curve.' As pointed out, Textmate is a new editor and you don't come to a standstill when you use it for the first time. But Vim is a fundamentally different KIND of editor than Textmate. It's not that it's a different program. It's that it's probably the first modal editor you've ever used. As far as I'm concerned, the whole bulk of the first and hardest step in learning Vim is just wrapping your head around editing modally. Whether you want to disable your arrow keys and obsessively leave Insert mode, in order to cultivate good habits, or you just want to muddle through and implement Vimisms where you can is wholly up to the reader. It's analogous to whether you want to cover your keycaps and use dvorak all the time even when you can't touch type, or just ease into it. But the hump, the bit that's a qualitatively different experience, is the modality of the application.
反驳作者：学习 Vim 需要先牺牲短期生产力，才能到达更高水平。
作者提出挑战：有没有一种切换方式不会在头几周显著降低我的生产力？这个论点的问题在于，它清楚地展示了为什么很多人会卡在局部最优，尽管周围有高得多的山峰，只需要先下坡再上坡。这需要流汗。
zikzikzik查看英文原文
"The last few times someone tried to get me to switch to vim, I issued them a simple challenge. Can you tell me a way to switch that will not significantly reduce my productivity for the first few weeks." The problem with this argument is that it clearly shows why so many people get stuck in local maximums, even though there are much higher peaks around, one just has to walk downhill first and then uphill again. It takes sweat.
质疑 Vim 能否胜任完整开发工作，痛点在于调试、导航和工具链而非编辑。
对我来说，过去尝试 Vim 时，痛点从来不是编辑本身。而是我需要可视化单步调试、加断点和监视点，以及在大型文件层级（包括许多导入文件、HTML 模板、配置文件）中直观导航，执行临时数据库查询，上传文件到服务器等等，还有跳转到类和函数定义、智能自动补全、弹出参数、捕捉变量名拼写错误等能力。我和那些说“真正的选择只有 Vim 和 Emacs”的程序员之间有根本脱节。我完全愿意考虑是我做错了，但我想知道有没有什么能说服我：在模态编辑器里待在主行上，可以完成程序员和维护者的整个工作，而不只是编辑和输入单个或少数文件中的文本。
WilliamLP查看英文原文
For me, having tried to use Vim in the past, the pain point is never the editing itself. It's the fact that I need visual step-through debugging, adding breakpoints and watch points, and intuitive navigation through a large file hierarchy including lots of imported files, HTML templates, config files, performing ad hoc database investigation queries, uploading files to a server, and whatever else, along with ability to jump to classes and function definitions and intelligent auto-complete and popping up parameters and catching my variable name typos and so forth. There's a fundamental disconnect between me and the programmers who say "the only real choices are Vim and Emacs", and I'm fully willing to consider that I'm doing it all wrong, but I wonder if there's anything out there that could convince me that living on the home row in a modal editor can work me through the entire job of being a programmer and maintainer, as opposed to editing and entering text in a single or very few files.
推荐用 vimtutor 半小时入门，性价比高。
以下内容在 HN 上重复过很多次，但对 Vim 新手或 HN 新读者仍值得再说一遍。1. 打开终端。2. 输入 vimtutor。3. 花半小时。4. 恭喜！你现在能在 Vim 里生存了，虽然远不是大师，但生产力大概能达到普通无插件文本编辑器的 80% 到 90%。我认为这 30 分钟花得很值。
melvinroest查看英文原文
The following has been repeated quite a lot on HN, but for people who are new to vim or new to reading HN it bears repeating. 1. Go to your terminal. 2. Type in vimtutor. 3. Spend half an hour. 4. Congratulations! You are now able to survive in vim, while you're by no means a master yet, you're probably around 80 to 90% as productive in vim as with a general text-editor without plugins. IMO it's 30 minutes well spent.
历次讨论
同类还值得读
开源应用架构
The Architecture of Open Source Applications
《开源软件架构》（AOSA）是一本在线免费书，邀请知名开源项目的作者亲自剖析其内部设计，涵盖 SQLAlchemy、LLVM、Audacity、Apache、Bash 等系统。
编程与软件工程上首页 9 次 · 2011–2024aosabook.org编辑精选编程语言简史：简短、不完整且多半错误
A Brief, Incomplete, and Mostly Wrong History of Programming Languages
一篇以戏谑、故意不准确的方式回顾编程语言史的博客文章，用夸张轶事和讽刺定义串起 Lisp、C、C++、Java、JavaScript、PHP 等语言。
编程与软件工程上首页 8 次 · 2009–2021james-iry.blogspot.comSQLite 是如何测试的
How SQLite is tested
SQLite 官方文档页，系统介绍 SQLite 的测试体系：多种测试方法（TCL 测试、模糊测试、回归测试、静态分析等）和海量测试用例，展示了这个小型开源项目如何靠极致测试获得…
编程与软件工程上首页 8 次 · 2009–2025sqlite.org编辑精选高级编程语言（2009）
Advanced programming languages (2009)
Matt Might 的经典文章，按用途推荐“高级编程语言”：如果追求就业就选主流语言，如果追求表达力、学术研究或创业，则推荐 Haskell、OCaml、Scala 等函数式语…
编程与软件工程上首页 8 次 · 2009–2022matt.might.net我的 Forth 与栈机器经历
Yosefk - My history with Forth & stack machines
作者以亲身经历回顾了使用 Forth 语言和栈式机器的历程：既赞叹其简洁优雅、代码量小、可自举的优点，也坦率指出栈操作在实际编程中的痛苦，以及 Forth 社区文化中的问题。
编程与软件工程上首页 8 次 · 2010–2024yosefk.com编辑精选