Buried at the bottom of the article is a link to this github issue that explains VS Code’s policy, which is apparently to make beta-quality APIs available to one or two extensions first to get feedback, then make it publicly available later. The extension author gets access to the API early but accepts that it’s non-final and subject to changes or breakages. This appears to be what happened with InlineCompletionProvider which is one of the APIs Codeium complains about.
Sure, it’s very convenient for Microsoft to give early access to another Microsoft product but it’s not the worst policy ever to get feedback before everyone in the world starts developing against API and it becomes harder to fix design problems.
I wonder if Codeium has requested their extension to be selected for this status.
I wouldn’t touch AI tooling with a ten-foot pole. Sooner or later, someone’s gonna get sued for copyright infringement because they plagiarized someone else’s code via Copilot, and I don’t wanna be that someone.
At least the way I use AI tooling, it would be very difficult to accidentally plagiarize code outside of boilerplate I guess. The way tools like GitHub Copilot are really useful is when using your existing code as “reference”, so if you use it to write a simple method, it’s only going to be restructuring your existing code.
In other words, Copilot is basically just meant to be used as really smart copy-paste.
I think the title is a bit misleading… vscode was made as a light weight script text editor, and it wasn’t even used that much internally at microsoft when it first came out. most people were using something like notepad++ / sublime for config file edits and stuff… it wasn’t until like 2018/2019 that it started to see wide usage internally. Most of this was due to C# being the language of choice, and the fat visual studio had a lot better integration for C# and azure development… though as teams started to use other languages, and the C# dev tools improved, you saw gradual shifts to people using vscode (mostly due to its much faster startup times)
the funny thing is, the vscode team released their github integrations internally to dogfood before the acquisition of github was announced, and due to regulatory stuff, the team behind the project wasn’t even aware of the acquisition until it went public.
While it makes sense that msft integrated co-pilot into vscode due to its popularity, its a far stretch to assume that it was planned out in some long road map. It was most likely a small team that implemented it, and it gained traction, then fell onto a roadmap for vscode (though, thats a guess, i havent worked at msft for quite a few years). I say this due to the workplace interoperability and the anecdotal things i saw while there (like the github bit above)
Why did Microsoft make VSCode? Well who knows, you can theorycraft about EEE all you want, and some of that may be true. The hard fact though is that VS Code replaced Atom with the sheer power of being way fucking better in every way and frankly good riddance. I am extremely glad to have a tool as good as VS Code at my disposal nowadays, something we didn’t have 5 years ago.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@beehaw.org
All things programming and coding related. Subcommunity of Technology.
Buried at the bottom of the article is a link to this github issue that explains VS Code’s policy, which is apparently to make beta-quality APIs available to one or two extensions first to get feedback, then make it publicly available later. The extension author gets access to the API early but accepts that it’s non-final and subject to changes or breakages. This appears to be what happened with InlineCompletionProvider which is one of the APIs Codeium complains about.
Sure, it’s very convenient for Microsoft to give early access to another Microsoft product but it’s not the worst policy ever to get feedback before everyone in the world starts developing against API and it becomes harder to fix design problems.
I wonder if Codeium has requested their extension to be selected for this status.
I wouldn’t touch AI tooling with a ten-foot pole. Sooner or later, someone’s gonna get sued for copyright infringement because they plagiarized someone else’s code via Copilot, and I don’t wanna be that someone.
At least the way I use AI tooling, it would be very difficult to accidentally plagiarize code outside of boilerplate I guess. The way tools like GitHub Copilot are really useful is when using your existing code as “reference”, so if you use it to write a simple method, it’s only going to be restructuring your existing code.
In other words, Copilot is basically just meant to be used as really smart copy-paste.
I think the title is a bit misleading… vscode was made as a light weight script text editor, and it wasn’t even used that much internally at microsoft when it first came out. most people were using something like notepad++ / sublime for config file edits and stuff… it wasn’t until like 2018/2019 that it started to see wide usage internally. Most of this was due to C# being the language of choice, and the fat visual studio had a lot better integration for C# and azure development… though as teams started to use other languages, and the C# dev tools improved, you saw gradual shifts to people using vscode (mostly due to its much faster startup times)
the funny thing is, the vscode team released their github integrations internally to dogfood before the acquisition of github was announced, and due to regulatory stuff, the team behind the project wasn’t even aware of the acquisition until it went public.
While it makes sense that msft integrated co-pilot into vscode due to its popularity, its a far stretch to assume that it was planned out in some long road map. It was most likely a small team that implemented it, and it gained traction, then fell onto a roadmap for vscode (though, thats a guess, i havent worked at msft for quite a few years). I say this due to the workplace interoperability and the anecdotal things i saw while there (like the github bit above)
Yeah what the hell is this title.
Why did Microsoft make VSCode? Well who knows, you can theorycraft about EEE all you want, and some of that may be true. The hard fact though is that VS Code replaced Atom with the sheer power of being way fucking better in every way and frankly good riddance. I am extremely glad to have a tool as good as VS Code at my disposal nowadays, something we didn’t have 5 years ago.