this post was submitted on 30 Oct 2024
15 points (94.1% liked)

VS Code

803 readers
1 users here now

founded 1 year ago
MODERATORS
Ategon
Lodra
15
Visual Studio Code version 1.95 is now available (code.visualstudio.com)
submitted 3 weeks ago by [email protected] to c/vscode
6 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] notnotmike 7 points 3 weeks ago (3 children)

Damn they went hard on Copilot on this release

[–] FizzyOrange 5 points 3 weeks ago (1 children)

They've been doing that for about the last 6 releases. I wish they'd fix some of the long-standing annoying bugs like the fact that you can't respect .gitignore and search in a subdirectory at the same time. Or the fact that you can't stage a submodule unless you also have that submodule open.

Or how about a less annoying way to configure Run/Debug than launch.json?

Still, can't complain. It's mostly free and still very good overall. I'll definitely be watching Zed... but maybe not too closely until it supports opening large files.

[–] [email protected] 1 points 3 weeks ago (1 children)

Got a link to the ticket about some modules? I think that must have been inconsistent behavior I've been observing when attempting to stage them from my super project.

[–] nebeker 2 points 3 weeks ago

An open source-ish corporate product is valuable in so much as it’s a vehicle for a paid service, right?

[–] spartanatreyu 1 points 3 weeks ago* (last edited 3 weeks ago)

I wonder if the slowdown in non-ai features this release was influenced in some way by their migration away from AMD modules to ES modules.

Putting myself in their shoes and taking codemods into account, I wouldn't want to make a big feature and have to worry about AMD/ES module concerns. Why do that when instead I could get a bunch of checking and smaller (but non headline) tasks out of the way and get back onto the larger features in 1-2 months after the ES modules are proven to work and I don't have to worry about rolling back changes.

Either that, or sometimes by statistical eventuality we end up with changes (which all take a different time to be completed) just not being released within a small period of time.