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

141–150 of 185 posts

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

#141

Post by tsimionescu »

worksonmine wrote: post #116
tsimionescu wrote: post #94

Earlier quoted context omitted.

> 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 bre…

I have inline debugging with gdb in neovim. +b/B: add/remove breakpoint +n/N: step/over ... and so on. To start it just run :termdebug. If you change the debugger to rr you can even replay. It's a shame the language support is poor, but I'm sure they'll add DAP support eventually.

This is exactly what I meant by an integrated debugger. I probably should have used the term IDE less, as that brings to mind Visual Studio or Eclipse and such - but I just meant any integrated editor+debugger, whether neovim, Emacs, or whatever else.

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

#142

Post by zhisme »

monegator wrote: post #66
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…

> Great there are other true open-source tools to be used zed, nvim without going into the actual qualities of the editor, they simply lack extension support, for now. In the embedded space, many manufacturers have switched - or are switching - to a suite of VSCode plugins and gradually discontinued the previous tools. Which is great on one hand: they don't have to keep supporting heavily modified IDEs from 10 or 20…

That's fair point.

Did you try other IDEs? For example from Jetbrains? I'm not using IDEs but actually don't know others besides VSCode/Cursor and Jetbrains

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

#143

Post by rrgok »

torben-friis wrote: post #122
Lapel2742 wrote: post #70

Earlier quoted context omitted.

>Sometimes that means having a side panel. I do not even need that. Modal editing is enough to keep me away from all the VI clones. I hate it with a passion. I have a fully customized Emacs that I use for anything Lispy and it's great for that purpose but everything else is just "ok". I try to use Zed but since it is a commercial offering it is just a matter of time until it gets entshitified too. Vscode is/was reall…

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 supposed to make small movements when I'm in insert mode, with the arrow keys? Like move cursor to the left by 3 chars. Do I enter normal mode, press l 3 times. Or delete the whole word and rewrite it?

Third. Why some movements are symbols? Like, line ending is $. Beginning of line is 0. so much so for home row movements.

Fourth. Could never remember if f or t includes the char I'm looking for.

Fifth. How cumbersome is to press ESC on the top left corner every damn time. Yes, there exists Ctrl+[. But still. So much so - again - homerow movement.

Not directly related to modal editing.

Sixth. I could not make copy/paste work reliably in remote a linux server from a Windows machine via SSH. Hell, I could not make it work with WSL2.

Sevent. Debuggers sucks. There is no comparison to JetBrains Debugger GUI. Not even VSCode come close to it.

Sorry for the rant.

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

#144

Post by reactordev »

dmicah wrote: post #139
beAbU wrote: post #127

Earlier quoted context omitted.

I think they fixed that to some degree. I have an old win10 PC that now has a persistent "upgrade to W11" banner that informs me my PC is below spec, so I can't upgrade. Fine by me!

Eventually Microsoft will stop providing security updates to their old OS, compelling users to upgrade if they want to stay on Windows

Which is fine. No one expects them to support everything forever.

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

#145

Post by reactordev »

square_usual wrote: post #133
reactordev wrote: post #117

Earlier quoted context omitted.

No, no they can’t. Again, it’s a part of the agreement. It’s included and bundled with ANY service you order, like it or not.

So enterprises are just accepting paying twice as much as they used to for no value? The "c'mon man" should be directed at you!

No it’s just baked in. Not opt in. Just baked in.

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

#146

Post by srfrog »

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.

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

#148

Post by beezlewax »

clever-leap wrote: post #48
alias_neo wrote: post #32

Earlier quoted context omitted.

This piece of news follows that of Copilot being added in an "update" to LG TVs with no option to disable or opt out. https://news.ycombinator.com/item?id=46268844

Simple, do not purchase LG TV.

I did this without researching enough and it its the worst ui experience going

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

#149

Post by mindcrash »

reactordev wrote: post #144
dmicah wrote: post #139

Earlier quoted context omitted.

Eventually Microsoft will stop providing security updates to their old OS, compelling users to upgrade if they want to stay on Windows

Which is fine. No one expects them to support everything forever.

A 2025 Linux kernel with all recent features is able to boot on a system from 2006.

Likewise the Windows 11 (which is just a rebranded Windows 10, just look at the full build number which should start with 10.x) kernel could boot systems from ~2017 onwards. Maybe with some kernel features disabled which most (if not all) Windows 10 users would not miss anyway, but it could still boot without any issues. Those running a Rufus-patched Windows 11 are living proof of this.

This never was a technical issue, or one which could cost them money, but a cold blooded business decision which generated thousands upon thousands of kilos of e-waste.

And for what?

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

#150

Post by torben-friis »

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…

I think if you google ADM-3A terminal keyboard you'll see half your issues explained :)

There's a ton of historical baggage there. Thankfully, a bit of it can be resolved by setting esc and/or ctrl in caps lock.

Post reply on HN