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

161–170 of 185 posts

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

#161

Post by duskdozer »

falcor84 wrote: post #112
mindcrash wrote: post #90

Earlier quoted context omitted.

"Just" some Copilot integration (in the form of chat or smart suggestions) is just the start. The next major Windows 11 update coming in 2026 will have full agentic AI with full control over your (your?) PC. And it will hard require a pretty recent processor with Neural Processor Unit to make it work (so a lot more e-waste is coming). I fear for the future.

> And it will hard require a pretty recent processor with Neural Processor Unit to make it work Am I right to understand that as people don't upgrade their hardware, they're safe from that, right? Sounds like a plus to me.

Lots of people are now upgrading hardware because of the end of standard Windows 10 updates

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

#162

Post by tonyedgecombe »

bpavuk wrote: post #118
tonyedgecombe wrote: post #101

Earlier quoted context omitted.

I'm already not buying Samsung devices, I'll run out of choices soon.

why not just use a big ol' monitor with a smart TV box and plain Android TV? or, even better, build a HTPC with Plasma Bigscreen or Bazzite?

Because that would be a crap solution.

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

#163

Post by theshrike79 »

srfrog wrote: post #146

Use Zed. VS Code is dead. I've been using Zed for about a month and I'm very happy with performance the features. It guides you to setup only what you need, that was a problem with VSCode that would collect random plugins through time. I work regularly with Go, React, TypeScript, and I don't miss VSCode.

90% of the reason I use VSCode is the extensions. Zed doesn't have the ecosystem.

For VSCode I can get the official extension by the actual company doing $thing. With Zed I need to trust Random Person's extension that it doesn't have spyware or keyloggers in it.

"but but the company could!" yes, but they have a reputation to protect, releasing an official extension that leaks data is Very Bad. Random Person (if that's their real name) doesn't care, or does. I have no way of telling.

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

#164

Post by skydhash »

torben-friis wrote: post #151
skydhash wrote: post #129

Earlier quoted context omitted.

> This workability indeed might require temporally replicating old habits while I learn the new ones, which lazyvim does I'm not judging your for it, but to me that sounds like learning the violin by plucking the strings like a guitar. You're increasing the learning period by following old habits which may even be harmful. I think it's better to just use the new editor sparingly, learning what you need, then switch f…

>that sounds like learning the violin by plucking the strings like a guitar. I'd compare it more to learning photography without going for manual aperture and developing analog film straight away. You'll have a better experience if you learn stuff like framing with an automated camera that frees you to shoot a hundred pictures daily and focus on a certain skill. I am increasing the learning period, that much is true.…

IMO, it’s still the wwrong approach. Vim and Emacs are just editors. Very much like Notepad. You don’t have to learn the extra stuff.

Once you are comfortable with basic notepad-like usage, you can then learn more advanced features. But emacs and vim are different from VSCode because those advanced things are supposed to be tweaked to personal preferences, not be handed down from high. When you start with something like Lazyvim, you’re missing on everything that makes vim, vim. You just have a walmart version of VSCode.

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

#166

Post by duskdozer »

torben-friis wrote: post #111
giamma wrote: post #89

Earlier quoted context omitted.

How about switching from VS Code to VS Codium? Same experience without the microsoft telemetry. I suppose Copilot won't be included due to licensing constraints.

How does the extension model work with MS? I did a similar move to chromium and eventually had to move to firefox when they pulled the plug on ad blockers.

There's https://open-vsx.org/. I've seen in the repo people talk about tweaking workarounds to use the proprietary MS stuff.

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

#167

Post by duskdozer »

zhisme wrote: post #23

Great there are other true open-source tools to be used zed, nvim. I also noticed that copilot nowadays is forcing you to upgrade to their with following text: "You've reached your monthly code completion limit. Upgrade your plan to Copilot Pro (30-day Free Trial) or wait until 2025-12-19 for your limit to reset to continue coding with GitHub Copilot" Was using it actually like smarter auto-completion. But paying for…

Is zed not just another option trying to build a userbase before clamping down? How is it different than the way VSCode is open-source?

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

#168

Post by skydhash »

rrgok wrote: post #143
torben-friis wrote: post #122

Earlier quoted context omitted.

Honest question, what is it that you hate about modal editing?

I tried Helix and Kakoune too. They all have the same problems. First. It adds friction. Every damn time I need to write, I forget to enter insert mode. You have no idea how many times I ended up with a strange buffer. Hopefully there is undo. But it gets boring fast. I need to write as soon I enter the editor. I don't need to move the cursor to read the text that visible on the current page. Second, how the hell I'm…

The rant is fine. I'll just provide some explanation.

First: Vim comes from vi, which is a visual mode for ex, which is a supercharged version of ed, which is (the standard editor) a line editor. With ed, you don't really write, you issue commands that does things to the file. Think of the file as a long roll of paper and the program as an assistant. So a command could be "replace your on line 14 with you're" or "delete line 34 to 45". Ex added more commands, Vi made it interactive, and Vim added even more features (syntax highlighting, scripting, location list,...). But still the same mode of interaction remains. The cursor is what you control. It's not just an indicator where the next character will appear or be deleted. It's the starting point of more powerful interactions.

Second. You're not supposed to move the cursor that much in insert mode. For 3 characters to the left, I just backspace and rewrite. For more, I go to normal mode and use F, f, T, or t which will land me to the character I want. Then I can use something like x (delete character) or r (replace character) without having to enter insert mode. There's a lot of movement beside hjkl, and I rarely uses h or l for things that further away than two characters.

Third. There's not a lot of key on the keyboard. $ is end of line in most regex dialect, ^ is beginning of line which would be actually the first character, but most people would assume it's the first non-whitespace character, so that's how they went. In C, curly braces mark blocks of code, so it's a small leap to use it for blocks of text, aka paragraphs.

Fourth. My mnemonics are f (find) and t (to). The latter does not include the character.

Firth. A lot of people remaps the caps lock to either Ctrl or ESC.

Sixth. They're different computers so there's no shared clipboard. Sharing information between the clipboard can be done using escape sequences, but I've never bother to. I just maximize the current buffer so I can use the terminal selection. And if I wanted more than a screen (dmesg), I'd pipe the command to a file and then download that file with sftp.

Seventh. Jetbrains only have debuggers for a handful of programming languages while `printf` is universal. And there's no law forbidding installing an IDE alongside your editor.

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

#169

Post by tzs »

alias_neo wrote: post #160
BearOso wrote: post #135

Earlier quoted context omitted.

> Front loading That's the problem. Front-loading washers have generally been a terrible invention. Unbalancing and mold are among the widespread problems. The actually reliable washers are still top-load.

I've always wondered, since we only have front-load washers here in the UK, is there some sort of advantage to it, aside from space, which seems to be the obvious one, does gravity help with battering the clothes around when the drum spins slowly enough they can fall from the top of the drum?

Front loaders are gentler on clothes, use a lot less water, use a lot less energy, and spin faster in the spin cycle so there is less work for your dryer if you use one.

Top loaders are easier to load and unload, cheaper, and slightly easier to maintain.

With front loaders you should wipe the gasket after use because water left in its folds can promote mold and odors. With both you should leave the door open when not in use so air can circulate in the drum. With a front loader the open door can get in the way and is easier to accidentally close.

Front loaders are easier to stack.

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

#170

Post by alias_neo »

tzs wrote: post #169
alias_neo wrote: post #160

Earlier quoted context omitted.

I've always wondered, since we only have front-load washers here in the UK, is there some sort of advantage to it, aside from space, which seems to be the obvious one, does gravity help with battering the clothes around when the drum spins slowly enough they can fall from the top of the drum?

Front loaders are gentler on clothes, use a lot less water, use a lot less energy, and spin faster in the spin cycle so there is less work for your dryer if you use one. Top loaders are easier to load and unload, cheaper, and slightly easier to maintain. With front loaders you should wipe the gasket after use because water left in its folds can promote mold and odors. With both you should leave the door open when not…

Interesting, thanks, I had no idea about much of this, I was aware of the door/mould thing, and stacking, though it's not something I've ever seen done here in the UK personally.

As a "typical" British household, we don't use a dryer, don't even own one in fact, we just hang our clothes to dry, which always struck me as ironic for such a humid, cold country, with smaller (than the US) homes and thus less space to hang stuff to dry.

Post reply on HN