Visual Studio Code VS Vim

For IDE-heavy teams, BYOK (bring your own key) can be interesting, no matter whether you live in WebStorm or VS Code. On the JetBrains side, the JetBrains AI plans and Junie BYOK docs allow it, and most VS Code AI extensions offer the same idea: keep the IDE, connect provider keys, pay the provider.

One can (maybe, probably) disable copilot completely in vscode: chat.disableAIFeatures

https://github.com/microsoft/vscode/issues/309947

I am considering pinning whatever the earliest version in which this setting was introduced. I can't think of a single feature VSCode has implemented in the last three years that I couldn't go without. The binary for 121 is like 50% larger than 120.

Option 1: Raw editing in IDE. You open the .md file in VS Code or whatever you use. Syntax highlighting shows you the structure. Maybe you toggle a preview pane. This works for quick edits but becomes painful for anything involving tables, diagrams, or complex formatting.

The Google Cloud Shell- available on every Google Cloud project — comes with a built-in code editor that allows you to browse file directories, view and edit files, with continued access to the Cloud Shell. The Cloud Shell Editor is available by default with every Cloud Shell instance, and is based on Code OSS.

You'll need Python 3.8+ and pip for the quickstart, with venv recommended for isolation. Install the requests library for HTTP calls. VS Code with the Python extension works well as an editor, though PyCharm or Sublime Text work equally well. You'll also need a free Foxit developer account.

Now here's the key point: Antigravity 2.0 is a huge departure from 1.0 in the sense that it is functionally no longer based on Microsoft's VS Code. That means a huge majority of all the personalizations from 1.0 will not carry over to 2.0.

There's a one-line pull request open against microsoft/vscode. It changes the default value of a setting called git.addAICoAuthor from "off" to "all". The PR is titled, with no embellishment, "Enabling ai co author by default." It was opened on April 15, 2026 by cwebster-99, a member of the VS Code team. By the time the HN thread on the PR hit 1,239 points and 646 comments in early May, the practical effect was already shipping: every commit you make in VS Code, regardless of whether you wrote the code yourself or had Copilot write it, gets a Co-authored-by: Copilot trailer in the commit message.

I'm not a fan of him, but I'm still glad he picked up this.

Just take a gander on the recent issues listed here, and how completely unavoidable they are: https://github.com/vim/vim/security

I hoped the people that wanted neovim features would've stuck to neovim instead of pushing vim to accelerate, but it seems like free LLM tokens made it a bit too tempting.

I'm not the GP, but I do remember why I rejected Kitty when I tried several terminal emulators last years: it broke quite a few of my workflows.

For instance, in vim the F3 key was broken[^1]. It was very surprising and weird, and a portable workaround required some arcane vim configuration.

Another important pain point was that the font rendering was different in Kitty to any other app, and very dependent on the screen DPI. IIRC, for a DPI around 100, I had to switch to "legacy rendering" because the default rendering was barely readable.

I also remember issues with SSH. And Kitty crashed at least once. And I wasn't a fan of Kitty's mix of C and Python. After a week or two of usage, my Kitty config file was big, with an extra hundred lines of Python for the tabbar. Despite some nice features (like the shortcut to put the output of the last command into a file), I got uneasy with all this mess. I tried Ghostty, which was as good as Kitty with much less oddities.

[^1]: https://github.com/vim/vim/issues/13328

The relevant release commit is, https://github.com/vim/vim/commit/e7e21018fc0b60c153c8e668f6... (at time of writing, two hours ago).

It seems they didn't publish the tag yet though.

Finally we are in a point where we will start drawing thing to the screen. First we will give it a Vim feel by drawing some tildes (~) at the left of the screen of every line that come after the end of the file being edited

Bram died 2 years ago (already(!!!), time flies!), so it's not so recently...

Also the community does an incredible job and it's quite active with further development and improvements, especially in improving the Vim9 script engine among many things they work on.

If you don't believe me, just see for yourself https://github.com/vim/vim/commits/master/

https://github.com/vim/vim/issues/3608#issuecomment-84907404...

Official site of VIM VIM git repo Here you can download Or refer some YouTube videos