> So to answer your question: they would be forking Atom (which I think would’ve won otherwise).
Atom was far slower than VS Code, despite both of them being built on Electron. I wouldn't have used Atom, but I use VS Code.
It is entirely possible that some other closed-source editor with a superior package/extension system would have won, or the "war" would have been postponed until Rust was ready enough for Zed to come along.
> I use Github Copilot because it's what my job provides to me. But 95% of my usage is via OpenCode (which is officially supported [0]), not copilot-cli or their IDE plugins.
Does the bug where premium requests get consumed for spinning up subagents still exist?
I've stuck to Visual Studio Code's GitHub Copilot integration because of this, because I'm on a tight budget and didn't fancy burning through my premium requests.
But I'm also not sure what qualifies as a bug here, given Microsoft's weird billing model. If you get charged for subagents, you'll burn through your premium requests in no time. If you don't get charged for subagents, you can get nearly unlimited usage of premium mode by using a go-between agent with a cheap/free model.
Currently I'm doing the latter, although I have to assume Microsoft will crack down on it at some point.
> The first time I thought "oh man, they've lost the thread" was Notifications. On iOS, Notifications make sense — you've got apps buried in folders three screens deep, so a unified system for surfacing what's happening is genuinely useful. On macOS, this design makes absolutely no sense at all. You can see your applications. They're right there. In the Dock. Which is also right there.
I've been a Mac user since 2005. I don't know when notifications were added to macOS, but I did finally find a use for notifications with agentic IDEs. (I remember wondering why I have never ever received notifications for anything on macOS, and I somehow have them turned off by default.)
It's pretty nice to give a prompt, then be able to do something else until my attention is needed again.
If it's a simple, extremely long prompt that should be copied and pasted without customisation, wouldn't it make more sense to build it as a set of skills?
Atom was far slower than VS Code, despite both of them being built on Electron. I wouldn't have used Atom, but I use VS Code.
It is entirely possible that some other closed-source editor with a superior package/extension system would have won, or the "war" would have been postponed until Rust was ready enough for Zed to come along.
reply