Google's Antigravity IDE Sparks Forking Debate(visualstudiomagazine.com)
visualstudiomagazine.com
Google's Antigravity IDE Sparks Forking Debate
https://visualstudiomagazine.com/articles/2025/11/21/googles-antigravity-ide-sparks-forking-debate.aspx
4 comments
Source discussion being covered: https://news.ycombinator.com/item?id=45967814
Isnt the express purpose of open source "take the source code and do whatever-the-fuck-you want, including forking?" (providing it is the right license).
What was the expectation when MS was open sourcing vscode? That people wont fork the code?
What was the expectation when MS was open sourcing vscode? That people wont fork the code?
I'll start with my bias as someone building a VS Code extension that I can see why folks forked initially, but don't see the need.
There's so much you can do as an extension and the Microsoft team behind it seems to be rational and listening to the extension community about their needs.
I do think Microsoft needs to find a way to host a conversation that discusses why folks must fork and how they can provide APIs to make the tools more configurable.
One big problem for extension programmers in the world with AI chatbots, is the extension is sandboxed and there isn't cross extension communications or a message bus. If there was that standard and a way to send messages, then my extension could push to a AI chat bot. This is a UX shortcoming I'm seeing.
There are also limitations in the ability to overlay UI/UX on top of the editors, e.g. to add comments or annotations that are persistent.
That said, these aren't reasons to fork in my view. I think you a get a good enough experience.
Anywho, I'm new to the eco-system so maybe I'm an optimistic idiot, happy to be wrong.
There's so much you can do as an extension and the Microsoft team behind it seems to be rational and listening to the extension community about their needs.
I do think Microsoft needs to find a way to host a conversation that discusses why folks must fork and how they can provide APIs to make the tools more configurable.
One big problem for extension programmers in the world with AI chatbots, is the extension is sandboxed and there isn't cross extension communications or a message bus. If there was that standard and a way to send messages, then my extension could push to a AI chat bot. This is a UX shortcoming I'm seeing.
There are also limitations in the ability to overlay UI/UX on top of the editors, e.g. to add comments or annotations that are persistent.
That said, these aren't reasons to fork in my view. I think you a get a good enough experience.
Anywho, I'm new to the eco-system so maybe I'm an optimistic idiot, happy to be wrong.