At least they've fixed the tabs.

@vanillama I've been using Zed as my daily driver for a few years now. Instantly reverted back to it, as it's just so much less noisy. Though they've recently introduced a new key binding that opens a AI threaded side panel right next to the "Format Code" binding. Which is incredibly annoying... Just need to find how to kill that 😂

So how does this work? Is this a mastodon post or a lemmy post or both? Can this be seen in mastodon as a "toot" and at lemmy as a post?

And for the post itself, what code editor have you been using?

I use Zed personally, it's also annoying with the AI nonsense, but just like vscode it has a button to just disable all of it, and it's very snappy even on my slower machines, especially compared to vscode

VSCodium exists and is way less Microsoft infused. https://vscodium.com/

@vscode Lol straight in with a request to use #CoPilot via a massive pop-up. #vscode #ai #code #programming

Great, another slopped out update with no actual features for programming.

But hey, at least we increased the tech debt!

Was anyone else annoyed that they don’t say which models they tested with? It’s all so secretive. Or did I miss that info somewhere?

All but one of the changes is AI related.

Notably, they have enabled AI autopilot by default, where it can take certain actions on its own without your approval, and the setting is intended to be managed at the organizational level instead of by your own user settings.

Oh look, another slop filled release.

And since they've been hacked by a vsc extension, have they committed to fixing their broken extension permission model?

No, they just delayed extension updates by two hours.

So now they'll just be hacked two hours later...

Face meet palm

I think based on the context of their replies they just live exclusively in Linux and have never noticed the Mac look, or the more likely explanation that it's subtle sarcasm (humor). Both outcomes are great in my opinion lol.

it makes me sad that vscode extension api is so specific and constrained that this has to be done as a change to the editor code itself

At the same company that immediately backtracked on a an image of a guy wearing a green hat in an installer? Probably.

Real happenings, Zero Bullshit

There was also the santa hat debacle

NOTE: I have zero fucks to give about ether of those specific issues, I’m just pointing out Microsoft's spine for these things has the consistency of overcooked linguini

If you want that kind of features to be adopted, it's best to the maintainer's input before writing any code.

It's likely for them to want some features on top of what you did (I can think about styling for instance, in which case the name "rainbow" might not be super appropriate?)

(I didn't read the code, maybe you thought about that already)

Thank you for the kind words :D

I did not recognize it from macOS

Are you saying it's not from macOS - or at least was not part of the macOS you've actually seen? This thing is many years old, so it wouldn't be a very recent thing.

I don't use or see macOS, though, so my [historical] impression could be wrong (which is why I used subjective/uncertain terminology).

Or by 'suggesting' did you mean you were joking?

I love you. This answer (while I was playing around suggesting I did not recognize it from macOS) is totally how a wonderful human being would respond. Helpful, kind, assuming the best.

You are truly the person this world needs.

I'm pretty sure that's originally a macOS thing. Then some design tools adopted it (probably because designers are in the macOS world). I took this from the screenshot in the linked pull request. No idea what they use, but I assumed macOS. Dunno if any Gnome or KDE themes adopt it.

What gnome or kde theme is that from?

If the top left window actions can be one color each, then the bottom can too!

VScodium AFAIK only builds straight from the repo.

So I am not sure if that is possible or not.

I use it though and it is such a relief to be away from microsofts dirty eyes while still using their products.

(Unfortunately, I am using the dart and flutter plugins, so Google still gets the privilege of spying on me, if anyone knows similar plugins without the google crap, do tell me in pm. I disable analytics, but no way this does anything.)

Not going to lie, pretty good for readability. If they don't merge it maybe give VSCodium a go.

They published a release without release notes.

The release notes came later.

Why not find a way to automate this,

Why not find a way to automate every single change that the vscode team makes that may break something?

Or why not let users do whatever?

Ultimately, users can do whatever.

But when they need help, they come to me.

I have a recommended list of settings for things that should already be defaults, to guide them away from footguns, and to prevent themselves from needing my help in the first place. But I also sometimes need to go around with a critical (usually temporary) list of changes for when a vscode update truly borks something up.

My concern was potentially needing to go around the office once a month for those critical fixes to once a week.

This is why I suggested multiple release channels. Have a weekly release for developers who are okay with the trade-off of more frequently broken setups for newer features faster, and have a monthly release for developers who want more stable environments.

It'd be a lot easier for me to run the weekly channel to be kept abreast of any changes, and I can support other coworkers on a monthly cycle.

We want actual features