3 ms·
Slightly OT: Why aren't AI coding assistants implemented as plugins (like through an LSP), rather than being a standalone AI-first editor (like Cursor)? I migh
by tiffanyh 1y ago
Slightly OT: Why aren't AI coding assistants implemented as plugins (like through an LSP), rather than being a standalone AI-first editor (like Cursor)?
I might be missing the obvious, and I get no standard exists, but why aren't AI coding assistants just plugins?
- behnamoh 1y agoBecause it would be easier to get funded that way. VCs prefer a product rather than a plugin.
- jptlnk 1y agoI don't think it's obvious but in my own experiments with this it's things like permissions that can get a little hairy. It's all doable and IMO preferable to have an agent-as-daemon. aider is kind of like this.
- chuckadams 1y agoDo you mean for Zed in particular? Because there are lots of AI agent plugins for VSC and Jetbrains IDEs both. I’m currently using one now, namely Augment. And AFAIK, copilot is still a plugin.
- nsonha 1y agoIf you actually look it up you'll see more of them that are plugins than full editors. I don't actually know their thinking but I know that for the VSCode ones (fork or extension), I tend to have at least 2 AIs at any point in time and compare them in my daily work. Probably when this field matures, lock-in will be more common, and you need control of the entire editor for that.