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.
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.
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.
Damn they went hard on Copilot on this release
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.
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.
https://github.com/microsoft/vscode/issues/205125
Also I found this duplicate: https://github.com/microsoft/vscode/issues/211508
There’s probably more…
An open source-ish corporate product is valuable in so much as it’s a vehicle for a paid service, right?
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.