Live data from Hacker News

Emacs and Vim in the Age of AI

batsov.com

61–70 of 155 posts

Re: Emacs and Vim in the Age of AI

#61
post #56
post #43

Earlier quoted context omitted.

please see the HN FAQ, this is NOT acceptable for this site.

[flagged]

I often get the impulse to call people stupid fucking morons on this site, because despite how intelligent people supposedly are, they really are complete fucking morons. It will, however, get you flagged and banned.

Re: Emacs and Vim in the Age of AI

#62
I put off adopting popular agents for most of 2025 primarily because there was no agent-agnostic path to first-class Emacs integration. That changed with ACP (https://agentclientprotocol.com), thus I started working on agent-shell.

I'm happy with how the integration is shaping up, enabling me to have my cake and eat it too (Emacs + AI agents).

I wrote an agent-shell post recently with the latest changes https://xenodium.com/agent-shell-0-47-1-updates

Re: Emacs and Vim in the Age of AI

#64
post #35

Earlier quoted context omitted.

This is not my experience at all, the AI agents are many many many times faster than what I can do. What anyone can do. It's crazy how quick I can create stuff these days.

AI can generate code much much faster. But do you never need a specific change (e.g. bugfix), that even describing in English is slower than just doing it? Especially in vim where editor movements are fast.

I'd argue you should be working towards no longer having to do these because agentic systems in place will do it in your stead.

All you need to do now, is sign off the code and adjust the agent so it would do these as you would.

Re: Emacs and Vim in the Age of AI

#65
post #16

I'm not convinced that terminal orientedness of AI tooling itself will last. My hypothesis is that it was chosen by developers of the current generation building for developers of the current generation. I hypothesize that there is a future where command lines and terminals don't matter, and hence I feel the focus will shift to, as the author points out, to planning, reviewing and ideation tools none of which demands…

I'm somewhat agreeing with it. CLI tools won't go away, since lines of text as an exchange format between tools is extremely powerful, especially with text based LLMs. However using an interactive TUI application to prompt agents will probably be less relevant in the future. E.g. if I want to build a web frontend, why wouldn't I just prompt and interact directly on the side I'm building?

Re: Emacs and Vim in the Age of AI

#66
post #35

Earlier quoted context omitted.

This is not my experience at all, the AI agents are many many many times faster than what I can do. What anyone can do. It's crazy how quick I can create stuff these days.

AI can generate code much much faster. But do you never need a specific change (e.g. bugfix), that even describing in English is slower than just doing it? Especially in vim where editor movements are fast.

possibly there's cases where maybe you want to change some text or something, but I don't think its faster in vim given you likely don't have that file open, and by the time you get to the file, and location, you could have fixed it with your agent, not only that, you could have generated the test case and then fixed in your agent

Re: Emacs and Vim in the Age of AI

#67
For me, AI increased my NeoVim usage. Claude Code and Codex made me go full cli. I run several sessions in multiple tabs in WezTerm, using Tmux, Tmuxinator, and excellent tui based file manager named Yazi in left pane, opening files in NeoVim, running Claude Code in right split. With this setup I work on several projects in parallel. Use lazygit as git client. Everything in cli, super fast.

Initially I went with Cursor, but the terminal setup feels way faster, more natural.

Re: Emacs and Vim in the Age of AI

#69
post #35

Earlier quoted context omitted.

This is not my experience at all, the AI agents are many many many times faster than what I can do. What anyone can do. It's crazy how quick I can create stuff these days.

AI can generate code much much faster. But do you never need a specific change (e.g. bugfix), that even describing in English is slower than just doing it? Especially in vim where editor movements are fast.

Anybody using cursor or antigravity ?

I tried them a bit and often they can infer immense amount of ideas from the immediate source context and suggest paragraph patches semantically close to what I had in mind from just one word.

Saying this as a vi/emacs user who liked to automate via macros, snippets, dynamic overlay inserts and what not.. I still enjoy being sharp on a keyboard and navigating source / branches swiftly but LLM can match and go beyond it seems. (not promoting them, feel free to stay in good old vi command sequences if that's fun for you)

Re: Emacs and Vim in the Age of AI

#70
post #16

I'm not convinced that terminal orientedness of AI tooling itself will last. My hypothesis is that it was chosen by developers of the current generation building for developers of the current generation. I hypothesize that there is a future where command lines and terminals don't matter, and hence I feel the focus will shift to, as the author points out, to planning, reviewing and ideation tools none of which demands…

I think AI tooling has actually reminded us how useful the terminal really is. running claude code, running formatters and linters and test suites, managing incremental work with git etc. Are all vital in the modern way we write code. I don't see how you can put a glossy UI on top of that and maintain any fine-grained control. Since we're already giving up a LOT of control by having agents write our code, we need to retain some control and certainty over the quality control and review process of the outputs.
Post reply on HN