Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

VS Code deactivates IntelliCode in favor of the paid Copilot

heise.de

Post reply on HN
Print view View original

91–100 of 185 posts

Re: VS Code deactivates IntelliCode in favor of the paid Copilot

#91

Post by DecoPerson »

djfobbz wrote: post #75

VS Code feels like nothing but bloat. Sublime Text is still my go-to, as I'm not very well-versed in Neovim yet. I'm also really digging the new C/Lua-based Lite XL - https://lite-xl.com . One of my New Year's resolutions is to learn Neovim properly.

Try Zed. Open-source (GPL+Apache), reliable, fast, not bloated at all, decently configurable, amazing remote-host support, Vim mode, AI stuff totally optional, extensions/lang-servers available for many languages, and... well overall I find it very neat and polished!

(I'm not associated with Zed, just a happy user looking to share the goodness.)

Re: VS Code deactivates IntelliCode in favor of the paid Copilot

#92

Post by nerdsniper »

SPICLK2 wrote: post #61

I refuse to use VS Code on principle. It has captured a staggering percentage of software development, across many software disciplines. Somehow ARM/Keil has been persuaded to go all-in on VS Code and will deprecate their "legacy" IDE, which will cause trouble for any hold-out embedded firmware developers.

I believe their legacy IDE was a fork of Eclipse.

Re: VS Code deactivates IntelliCode in favor of the paid Copilot

#93

Post by tashoecraft »

reactordev wrote: post #69
PedroBatista wrote: post #13

Microsoft doing Microsoft things, even with all those fresh coats of "open source" paint they bathe themselves in the last decade they really can't change their DNA. Expect the amount of f*ckery to increase as the AI realities set in but the number has to go up either way. It reminds me of the good old days of Visual Studio + .NET + SQL Server where they played these games too.

This made me laugh a bit as I remembered people saying “Oh we have Nadella now, things have changed”. Have they? Have they really? Windows Recall. VS Code forcing Copilot. Windows forcing Copilot. Office forcing Copilot. Azure forcing Copilot. GitHub forcing Copilot. Outlook forcing Copilot. Edge forcing Copilot. You folks are insane.

I've heard Github makes more money from copilot than everything else combined. You can think what you want about the strategy, but it's hard to ignore that.

Re: VS Code deactivates IntelliCode in favor of the paid Copilot

#94

Post by tsimionescu »

torben-friis wrote: post #88
somenameforme wrote: post #51

Earlier quoted context omitted.

I think some of the big features of VSCode are the extensions and, equivalently, the nice debug support. I just started using VSCode about a week ago thanks to moving to a project that uses scons as its primary supported build tool, and I've learned to hate scons and love VSCode over that time. The completely manual tasks/launch/etc stuff is kind of weird at first, but then becomes amazing and far more convenient, af…

I can't help you much, as currently I happen to use ruby at work and native debugging is enough - you can drop into an interactive console at a breaking point adding a single line, with no tooling. Here's the chapter on debugging in the book I mentioned if you want to take a look: https://lazyvim-ambitious-devs.phillips.codes/course/chapter...

> I happen to use ruby at work and native debugging is enough - you can drop into an interactive console at a breaking point adding a single line, with no tooling.

If you've only ever used this type of debugging, you should really try out a real IDE debugger once. The difference in productivity when you can use your IDE to navigate to, say, the usages of a function and then just press a keyboard shortcut to put a breakpoint on the line with that usage is immense.

Compare this to the native debug support: you have to leave the interactive debugger, move to your editor, find usages, note down the file name and line number, then go back to your interactive debugger and type a manual break command (break my_file.rb:2517 or something). All of that context switching and remembering is replaced by a single keyboard shortcut in Emacs, VS Code, or any other integrated debugger. And no, adding manual breakpoints in your source code is not simpler - what I'm describing works interactively while your code is already running, whereas a breakpoint statement requires you to restart the whole process.

Re: VS Code deactivates IntelliCode in favor of the paid Copilot

#95

Post by mbirth »

reactordev wrote: post #69
PedroBatista wrote: post #13

Microsoft doing Microsoft things, even with all those fresh coats of "open source" paint they bathe themselves in the last decade they really can't change their DNA. Expect the amount of f*ckery to increase as the AI realities set in but the number has to go up either way. It reminds me of the good old days of Visual Studio + .NET + SQL Server where they played these games too.

This made me laugh a bit as I remembered people saying “Oh we have Nadella now, things have changed”. Have they? Have they really? Windows Recall. VS Code forcing Copilot. Windows forcing Copilot. Office forcing Copilot. Azure forcing Copilot. GitHub forcing Copilot. Outlook forcing Copilot. Edge forcing Copilot. You folks are insane.

You forgot that even poor old notepad.exe also got the Copilot treatment.

Re: VS Code deactivates IntelliCode in favor of the paid Copilot

#96

Post by __jonas »

NGRhodes wrote: post #50
__jonas wrote: post #41

Earlier quoted context omitted.

I didn’t think it was even possible to install proprietary microsoft extensions in VSCodium, how is that related to the version of the editor and how would it affect VSCodium?

It is not possible to install proprietary Microsoft extensions using the official VSCodium builds without additional, non-default configuration.

Right. Then the removal of this IntelliCode extension from MS should have no effect on VSCodium users.

I thought originally it may have been an OSS extension, but it actually seems to have been a proprietary project licensed under the Microsoft Software License, similar to Copilot and such.

Re: VS Code deactivates IntelliCode in favor of the paid Copilot

#97

Post by freedomben »

torben-friis wrote: post #65
skydhash wrote: post #46

Earlier quoted context omitted.

> I had tried many times to switch to vim/emacs and the initial barrier to get a workable system always kept me from pushing forward What’s that initial barrier? Both Vim and emacs has great documentation that includes a tutorial, a guide, and a reference. What people often defines as workable system is replicating their old editors instead of learning the current one. Like adding a file tree on the side

>What people often defines as workable system is replicating their old editors instead of learning the current one. Like adding a file tree on the side Well, kinda. I define a workable system as a system I, personally, can work with straight away, with a minimum loss of productivity. It is not at all meant as a judgement on how good plain vim/emacs are. This workability indeed might require temporally replicating old…

Yeah, for most of us in the real world, we can't afford to be way underproductive for a week while we learn and set up our new editor from scratch. Learning vim is one of the greatest gifts I think I gave myself, and I'm extremely glad I did it, but it was not easy. A more gradual curve or even a crutch is completely fine in my opinion. I've seen plenty of people get started with vim just by putting them key bindings in their IDE and getting used to the motions, and then gradually moving over. The main key is to iterate, and not stagnate

Re: VS Code deactivates IntelliCode in favor of the paid Copilot

#98

Post by runjake »

reactordev wrote: post #69
PedroBatista wrote: post #13

Microsoft doing Microsoft things, even with all those fresh coats of "open source" paint they bathe themselves in the last decade they really can't change their DNA. Expect the amount of f*ckery to increase as the AI realities set in but the number has to go up either way. It reminds me of the good old days of Visual Studio + .NET + SQL Server where they played these games too.

This made me laugh a bit as I remembered people saying “Oh we have Nadella now, things have changed”. Have they? Have they really? Windows Recall. VS Code forcing Copilot. Windows forcing Copilot. Office forcing Copilot. Azure forcing Copilot. GitHub forcing Copilot. Outlook forcing Copilot. Edge forcing Copilot. You folks are insane.

I’m not sure why people are surprised. If you watch Nadella interviews, he tells you what he thinks and where he wants to take the company.

He touts AI, services, agentic copilot, and all the other stuff customers are railing against.

Some Windows manager got crucified on X recently for an enthusiastic tweet about turning Windows into an agentic OS. People called for this persons firing. But, this was straight out of Nadella’s playbook.

Re: VS Code deactivates IntelliCode in favor of the paid Copilot

#99

Post by kgwxd »

CharlieDigital wrote: post #44
kgwxd wrote: post #19

Copilot is what finally pushed me to use vim seriously. There's not a single thing I miss from VS Code, or Visual Studio, and I'm not even using neovim. Also dropped .NET, which I've used professionally since Framework 1.0, in favor of Go. Don't miss anything from there either.

> Don't miss anything from there either Not even EF Core? C# pattern matching and switch expressions? Linq? I find these very hard not to miss when working in other langs. C# is a fantastic programming language nowadays.

EF Core!? Holy cow, no. Stopped using that years ago. Linq is nice, but I don't really miss it.

Re: VS Code deactivates IntelliCode in favor of the paid Copilot

#100

Post by torben-friis »

railka wrote: post #18
torben-friis wrote: post #11

If anyone is considering moving editors, I was recently in the same boat and I can’t recommend enough lazyvim + the ebook “lazyvim for ambitious developers”. This gets you a fully featured vscode-like baseline (navigation, language integration, integrated terminal, the whole thing). I had tried many times to switch to vim/emacs and the initial barrier to get a workable system always kept me from pushing forward. With…

I think many people don't know or underestimate Zed. Native, fast, with extensions, with Vim mode support.

The reason I didn't explore Zed is their for profit model.

There might be awesome people and work behind it now, but I've already been burned enough times by rug pulls and shittyfication. I don't want to be planning another move 5 years from now.

Post reply on HN