惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

云风的 BLOG
云风的 BLOG
M
MIT News - Artificial intelligence
Recent Announcements
Recent Announcements
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Stack Overflow Blog
Stack Overflow Blog
J
Java Code Geeks
Microsoft Azure Blog
Microsoft Azure Blog
罗磊的独立博客
博客园 - 【当耐特】
H
Help Net Security
腾讯CDC
大猫的无限游戏
大猫的无限游戏
GbyAI
GbyAI
Last Week in AI
Last Week in AI
Jina AI
Jina AI
博客园 - 聂微东
Blog — PlanetScale
Blog — PlanetScale
A
About on SuperTechFans
Apple Machine Learning Research
Apple Machine Learning Research
P
Proofpoint News Feed
Y
Y Combinator Blog
C
Check Point Blog
博客园 - 司徒正美
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Finally learned how to close Neovim. Still can't leave
Slee Woo · 2026-05-01 · via DEV Community

There's a famous joke: I've been using Vim for years because I don't know how to close it.

Now I finally learned how to close it.

But still can't leave.


A brief museum of editors I loved

Before Neovim there were others. There are always others.

Zend Studio, for the veterans who remember. The IDE that came with a PHP license and a sense of seriousness. It knew what a project was before "project" meant a folder with a package.json.

Eclipse, the cathedral next door - workspaces, perspectives, a plugin for every problem and three more for every solution. If you were coding in the 2000s, Eclipse wasn't your editor; it was your operating system.

RubyMine, when Ruby was the future and autocomplete that actually understood your models felt like a small miracle. JetBrains in general - heavy, opinionated, smarter than you, willing to tell you so.

Sublime. The editor that taught a generation of us that startup time is a feature. Command-P was a religious experience in 2013.

Then the Electron wave. Atom first, then VS Code. Suddenly your editor was a browser, your browser was an editor, and somehow we all just accepted that 400MB of RAM was fine for typing.

I used all of them. I liked all of them. I was, briefly, each of those people.

Wonder how things would've gone if Zed had been around in 2015.


The plugins, sharpened over years

Here's what nobody tells you about a decade in one editor: you don't accumulate plugins, you accumulate positions. A plugin isn't a feature you installed, it's a decision you made about how you want to work, frozen into a line of config.

Every keymap is a small vote you cast against your past self.

Every leader-key combination is a sentence you taught your hands to speak.

Ten years of that and the editor stops being software. It becomes a dialect.

People quote that line - perfection is achieved not when there is nothing more to add, but when there is nothing left to take away. And the older I get, the more I think the real version is even quieter: an ideal tool is one where there is nothing left to drop. Everything that's still there earned its way back, after you tried to remove it and missed it.

My Neovim config is like that now. Not because I designed it. Because time did.


Five attempts

I tried to switch to Zed about five times in the last year.

Zed is genuinely great. Fast in the way Sublime was fast, but with the modern stack underneath. And the v1 release, with the agents finally something you can switch off and ignore - that removed the last excuse I had.

Every time I opened it, wanted the switch to work.

Every time, after a few hours, I was back in Neovim. Not because Zed did anything wrong. Because my hands kept reaching for things that weren't there in the same shape, and the small constant friction of that translation just... wore me down.

One attempt is curiosity. Five is something else. Five means some part of me keeps pulling me back, and I can't quite negotiate with it.


Vim-mode is not Vim

Yes, Zed has a vim mode. Yes, it's technically excellent. The keybindings work. The motions are there. On paper it's a perfect bridge.

Emotionally it's a different room.

It's the difference between speaking a language and being translated into it. The surface matches. The underneath doesn't. You can feel the seam, even when you can't point at it.


The part I can't transfer

Here's the sad part - and I don't even know if "sad" is the right word, I still can't quite name this feeling.

None of this transfers.

Ten years of muscle memory, ten years of config decisions, ten years of "oh I fixed that annoyance in 2019 and forgot it was ever annoying" - there's no export button for that. You can't git clone a decade of embodiment into a new editor.

And that's what it is, really. The editor isn't an application I use anymore, it's a prism I think through. Switching isn't learning a new tool, it's relearning the angle at which my thoughts come out.

It's not age. I don't think it's age. A kid who's been deep in one editor for three years has the same thing in miniature. It's just what happens when a tool stops being external.


So

I still use Neovim.

Zed is on my machine. I open it sometimes. I'll probably try again - a sixth attempt, a seventh.

Both editors are great. That part I'm sure of. The rest of it, the why-can't-I-just-switch part, I'm still sitting with.

If you've felt this about any tool - an editor, a shell, a keyboard layout, a language you can't quite leave - I'd love to hear it. I suspect this isn't really a Neovim post. I suspect it's a post about how the things we use long enough start using us back.

And not sure that's really a problem.