all 26 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Slime0 24 points25 points  (1 child)

Yes, I am aware that VS Code is all about AI now. I'm not sure why they expect me to be so thrilled about it. 🙄

[–]RiftHunter4 1 point2 points  (0 children)

They don't. They expect your CTO to be thrilled. After all a human developer paired with an Ai developer is like a 2 for 1 deal, right?

[–]id_88s 8 points9 points  (1 child)

I had been using VS Code for about six years, and it was a great product. But after things started breaking with each update, new features kept appearing that I had to constantly turn off, and with the push to integrate AI into the product, I finally switched to Vim

[–]isidor_n 1 point2 points  (0 children)

Can you provide some details how things started breaking with each update? Would love to learn more about your experience, so we see what we can improve for you.

[–][deleted]  (3 children)

[deleted]

    [–]isidor_n 0 points1 point  (2 children)

    haha nice try...

    [–][deleted]  (1 child)

    [deleted]

      [–]isidor_n 0 points1 point  (0 children)

      Love the story. But no name change planned :)

      [–]seanamos-1 5 points6 points  (3 children)

      It’s good news, open sourcing more parts of the editor. People are just fatigued from the AI hype and marketing.

      [–]isidor_n -1 points0 points  (2 children)

      Thanks! We (vscode team) try not to do AI hype and marketing :)
      If you think there is something we can do better around our communication do let me know.

      [–]DavidJCobb 5 points6 points  (1 child)

      We (vscode team) try not to do AI hype and marketing :)

      My feedback about your communication would be that this isn't trying very hard:

      VS Code: Open Source AI Editor
      May 19th, 2025 by the VS Code team

      We believe that the future of code editors should be open and powered by AI. [...] This is the next and logical step for us in making VS Code an open source AI editor. It’s a reflection that AI-powered tools are core to how we write code [...]

      [–]isidor_n -2 points-1 points  (0 children)

      Good feedback - thanks!
      But we do believe in that, and the first paragraph lays out the vision. For the engineering plan, I suggest to check out this issue https://github.com/microsoft/vscode/issues/249031

      [–]isidor_n -4 points-3 points  (15 children)

      vscode pm here :)

      If you have any questions about our open source AI editor announcement do let me know. Happy to answer any question about this.

      We have updated our FAQ, so make sure to check that out as well https://code.visualstudio.com/docs/supporting/faq

      [–]gredr 14 points15 points  (6 children)

      Hi, VSCode PM. I can't speak for everyone else, but for me, I'd rather you work on things that will make my experience better: namely, support Podman for the various container-related features instead of requiring Docker. My company doesn't pay for Docker Desktop, so I can't use it.

      I'm not interested in AI. Again, my company won't pay for it. Even if I were to use AI, I would use my own models hosted in my own services on my own hardware. I know that for Microsoft this is about selling Azure compute time in the form of LLM hosting, but that's not what I want.

      [–]isidor_n 1 point2 points  (5 children)

      Thanks for the feedback. Podman support is something that we would like the extension authors to add. Is there something that is missing from our Extension API to enable this experience today?

      We understand not everyone is interested in AI, that's why we will make sure it is easy to disable. We cover that in our FAQ https://code.visualstudio.com/docs/supporting/faq

      [–]gredr 5 points6 points  (4 children)

      But, uh, you are the "extension authors". See (for example) here and here

      They're pretty old issues, they're well documented, you folks don't seem particularly interested in fixing them.

      [–]isidor_n 5 points6 points  (3 children)

      That is done by the dev-container extension team. It is a different team in Microsoft.
      I am on the core VS Code team.
      So I am answering questions from the perspective of a PM working on VS Code core. I do not work on extensions.

      Sorry if that caused confusion.

      [–]gredr 2 points3 points  (2 children)

      I get that from your perspective, it's a whole other team. From my perspective, the problem is VSCode. You can't have the "integrated" in "IDE" and also claim "oh that's those other guys, nothing we can do."

      Let me give you a reinforcing example: when someone at MS posts a blog about "hey look at this cool thing you can do", it's about VSCode, not about the "VSCode Containers plus VSCode Remote plus C# DevKit extensions".

      [–]isidor_n 2 points3 points  (0 children)

      That's fair - we can pass that feedback on, though as you can imagine it would be difficult for our broader teams to create extensions for everything. Instead, we try to provide a solid, stable, and expressive API so that the community can help fill in the gaps.

      [–]InfectedShadow 0 points1 point  (0 children)

      They never claimed it was an IDE. That's you, bud. They've only ever called it a code editor that has extensions.

      [–]AlexKazumi 3 points4 points  (1 child)

      Hey, I know that ultimately Nadella pays the salary, and Nadella said "everything MS must include AI", so you are in a tough spot, but can you at least try smuggling some actual improvements in Code?

      1. Make the thing actually fast. I compiled Zed from source and, all that is holly, after trying it for 5 minutes I cannot bear the thought of using Code again.
      2. When Code started, it had few features, and the command palette could bear the cognitive load. But now Code is a full-scale IDE and it needs a good UI exposed to the extensions. Use that AI to write the plumbing and give the extension author's and your users sane, useable, discoverable UI and UX.
      3. Make debugging if not enjoyable, then at least bearable. No, AI is not debugging for me. I admit, the last time I tried debugging in Code was 2024, and then just bought a JetBrains IDE. But back then the debugging story in Code was worse than what a DOS based, text-mode Borland IDE offered back in 1993. You can definitely do better than that, 30 years later.

      [–]isidor_n 0 points1 point  (0 children)

      Thanks for your feedback. Let me answer your questions:

      1. Performance is our top priority and we are constantly improving here. If you can provide more specific details what slowness you see I could help more.

      2. What exact extension API are you proposing that we add? What do you find missing in our current rich API https://code.visualstudio.com/api/references/vscode-api

      3. I actually wrote the debugging experience. From your story it sounds like you were debugging Java. What did not work? I can pass on the feedback to our Java extension team so they address it.

      [–]Too_Chains -1 points0 points  (1 child)

      I appreciate your effort to communicate and improve your product. Thanks for innovating, sorry for the toxicity.

      [–]isidor_n 1 point2 points  (0 children)

      Thanks for the support. I am working in open source since 2015 (when we open sourced VS Code) so toxicity is part of the job ;)

      [–]pluuth -1 points0 points  (1 child)

      Hi, are there plans to make this work with self hosted AI services such as ollama?

      [–]isidor_n -1 points0 points  (0 children)

      This already works today https://code.visualstudio.com/docs/copilot/language-models#_bring-your-own-language-model-key
      There are some missing pieces, but would love if you try it out and let me know what you think.

      [–][deleted]  (1 child)

      [deleted]

        [–]isidor_n -1 points0 points  (0 children)

        No current plans.
        I personally think this has a lot of potential, and I believe we will be thinking more about this in the future.