Can we talk about how much copilot sucks in vscode? I have to use for work, buggy as hell for the premier product of a trillion dollar company.
I use Claude Code in Zed via ACP and have issues all the time. It pushes me towards using the CLI, but I don’t want to do things that way because it’s a vibe coding workflow. I want to be in the drivers seat, see what the agent has done and be able apply or reject hunks.
Why is Claude an Electron app?
31–40 of 483 posts
Re: Why is Claude an Electron app?
#32Can we talk about how much copilot sucks in vscode? I have to use for work, buggy as hell for the premier product of a trillion dollar company.
Re: Why is Claude an Electron app?
#33Re: Why is Claude an Electron app?
#34I can see it in my team. We've all been using Claude a lot for the last 6 months. It's hard to measure the impact, but I can tell our systems are as buggy as ever. AI isn't a silver bullet.
Re: Why is Claude an Electron app?
#35Re: Why is Claude an Electron app?
#36Re: Why is Claude an Electron app?
#37Re: Why is Claude an Electron app?
#38> For now, Electron still makes sense A few years ago maybe. Tauri makes better sense for this use case today - like Electron but with system webviews, so at least doesn't bloat your system with extra copies of Chrome. And strongly encourages Rust for the application core over JS/Node.
Re: Why is Claude an Electron app?
#39I've been building a native macOS AI client in Swift — it's 15MB, provider-agnostic, and open source: https://github.com/dinoki-ai/osaurus
Committing to one platform well beats a mediocre Electron wrapper on all three.
Re: Why is Claude an Electron app?
#40It's a nodejs app, and there is no reason to have a problem with that. Nodejs can wait for inference as fast as any native app can.