Hacker News new | ask | show | jobs
by dust42 212 days ago
Still it would be a lot wiser if all the forkers would do one 'AI-enabled' fork together that exposes all the extras that copilot gets. The barrier for testing would be much lower and all the extension makers would also jump onto the train. Likely MS would finally give in and make all the extras available for everyone. But all the fragmentation only helps MS.
2 comments
ewoodrich 212 days ago
What exactly are the "extras" that Copilot gets?

I've had a Github Copilot subscription from work for 1yr+ and switch between the official Copilot and Roo/Kilo Code from time to time. The official Copilot extension has improved a lot in the last 3-6 months but I can't recall ever seeing Copilot do something that Roo/Kilo can't do, or am I missing something obvious?

link
lozenge 212 days ago
The Copilot extension uses proposed APIs, meaning it's on an allowlist bundled with VS Code. Roo likely enables these early. The API can stay proposed for years before Microsoft opens it up to third party users.
link
meowface 212 days ago
They're all going to have quite divergent opinions on how to structure the fork and various other design decisions that would inevitably lead to forks of the fork again.

I think forking VS Code is probably the most sensible strategy and I think that will remain the case for many years. Really, I don't think it's changing until AI agents get so ridiculously good that you can vibe code an entire full-featured polished editor in one or a few sessions with an LLM. Then we'll be seeing lots of de novo editors.

link