Microsoft gives a product for free. It is free to add whatever features it wants in it. No?
(and that's why I use emacs...)
Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
51–60 of 227 posts
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#52Earlier quoted context omitted.
fork vscode, do whatever you want. merge back when ready.
Won't really help ya. As outlined at https://ghuntley.com/fracture/ as soon as you compile "VSCode" (MIT) the ecosystem fractures in a bad way (tm) including no-license to run majority of MSFT extensions (Language LSPs, Copilot, Remote Development). If you are a vendor producing a MIT fork then one needs to iterate the graph and convince 3rd party extension authors to _not use the MSFT extensions_ as dependencies _an…
If MS didn't owned VS code. What would they be doing?
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#53Everyone is reading this as intentional anti-competitive practices. While that may be true, isn't another reasonable explanation that the Copilot development team is moving as fast as they can and these sorts of workarounds are being forced through in the name of team velocity? It takes a lot more time/energy to push public APIs and it's probably a very different team than the team developing the copilot extension. S…
Not malicious, but still selfish. It's important to remember that the copilot extensions are an extremely effective way of monetizing VScode. So it seems more like they're kind of compromising on their API usage rules in order to get to market quicker. But allowing themselves to use the APIs before anyone else is in a way anti-competitive, because the only way one could compete would be to use the unfinished APIs. Bu…
Check my comment elsewhere (it's now bobbing up and down). Some things just take time, no need to assume malicious intent.
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#54Everyone is reading this as intentional anti-competitive practices. While that may be true, isn't another reasonable explanation that the Copilot development team is moving as fast as they can and these sorts of workarounds are being forced through in the name of team velocity? It takes a lot more time/energy to push public APIs and it's probably a very different team than the team developing the copilot extension. S…
Seems like the only sensible comment in this thread so far. Here's what I imagine it's like working on the Copilot team: > Mgmt: "We need this feature, and we need in 2 weeks." > Devs: "That feature is not technically possible." > Mgmt: "Well, figure out a way to make it possible. That's _your_ problem."
[dead]
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#55Earlier quoted context omitted.
Are other extensions like Codeium[0] allowed to publish under the same rules? I'm not saying your comment is incorrect, but unless Copilot competitors can get the same treatment, it seems extremely unfair and anti-competitive. [0]: https://marketplace.visualstudio.com/items?itemName=Codeium....
[flagged]
Eh not quite. Famously, you can fork VSCode, but you can't use the VSCode Extension Marketplace if you do, which loses a lot of the network effect benefits of the VSCode ecosystem. (As far as I know Cursor is flat out violating Microsoft's terms of service with respect to the extension marketplace).
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#56Earlier quoted context omitted.
[flagged]
> VSCode is provided fully free as in beer and freedom No, VSCode is a proprietary text editor/IDE from Microsoft. Code-OSS is provided fully free as in beer and freedom, and is currently what resides at https://github.com/microsoft/vscode . Why would Microsoft not want other AI agent extensions to get the same benefits, which would benefit all AI agent users? Edit: I have removed the portion of the comment which dis…
Does throwaway account negates the arguments though?
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#57Lloks like Microsoft is going back to it's old ways. I am not surprised tbh.
I mean, Microsoft has been very clear about their business model of VSCode -- similar to Chromium, the base product is free and you can do whatever you want (and indeed there are lots of products reusing the core of VSCode), but extension marketplace/remote/GitHub Copilot are proprietary. It sounds like a fair deal to me -- Microsoft can't just do open source without expecting to get something in return. Now, coming…
This. LSP is a great example of something that also takes a while to flesh out because the problem space spans a lot (syntax, autocomplete, etc.)
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#58There are just certain technologies my brain says "fuck, no" to. GNOME. The Great Banality Laser (whose official name was once Twitter). Visual Studio Code. The fullness of time usually proves my brain's initial impressions right, as it seems to be doing now with Visual Studio Code. I can still remember the monthly paroxysm of bliss that radiated throughout Hackernews, regular as clockwork, timed with Microsoft's mon…
Sent from my iPhone
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#59I honestly don't see the issue here (Full disclosure: I work for Microsoft, but in professional services, not in product - and nevertheless fully expect to be downvoted to oblivion). If these aren't finished, that most likely means that they still haven't stabilized enough to go through the full support and release pipeline--that usually means documenting them, publishing a couple of reference development samples, do…
Yep, downvoted to oblivion alright. Took all of five minutes, and doesn't reflect at all well on radical HN folk's ability to empathize with people working hard to ship actual product.
Re: Microsoft is introducing hidden APIs to VS Code only enabled for Copilot?
#60Everyone is reading this as intentional anti-competitive practices. While that may be true, isn't another reasonable explanation that the Copilot development team is moving as fast as they can and these sorts of workarounds are being forced through in the name of team velocity? It takes a lot more time/energy to push public APIs and it's probably a very different team than the team developing the copilot extension. S…
Seems like the only sensible comment in this thread so far. Here's what I imagine it's like working on the Copilot team: > Mgmt: "We need this feature, and we need in 2 weeks." > Devs: "That feature is not technically possible." > Mgmt: "Well, figure out a way to make it possible. That's _your_ problem."
Sounds like when Slack started taking marketshare from Skype for Business and they pushed out Teams as fast as possible.