Visual Studio Code VS Atom

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.

> All of the code is OOP-based, and they mount DOM nodes the old-school way (which is what React was supposed to solve..)

I don't know about VS Code, but I remember Atom was refactored to use manual DOM updates because the performance penalty of using React wasn't worth it.[1] By the way, isn't OOP by far the most popular paradigm for building desktop UIs? I imagine VS Code is a difficult codebase to work with that has a lot of intricate code (as is usually the case with large software projects), but that's a strange piece of criticism :-)

1. https://github.com/atom/atom/pull/5624

Atom used to recommend this: https://github.com/atom/atom/blob/master/CONTRIBUTING.md#git...

For JavaScript, HTML, and CSS, Visual Studio Code is the best solution because it already runs on the Electron framework. So, try VSCode. Don't worry; your device won't be harmed. If its performance was unbearable, you can always put it aside. You can also try Atom. It is outdated, but it could be answer to your need.

you can still get atom from it github page: https://github.com/atom/atom/releases/tag/v1.60.0

I'm surprised that nobody here mentioned Atom [1]. IIUC, Atom was designed to be hackable like Emacs.

A successor to Atom is Pulsar [2].

[1] https://github.com/atom/atom

[2] https://pulsar-edit.dev/

atom (RIP buddy! Free) Atom is a hackable text editor for the 21st century, built on Electron, and based on everything we love about our favourite editors. We designed it to be deeply customizable, but still approachable using the default configuration

Hey everyone, I'm developing an open source text editor called Valence. I'm just getting started with its development and the next and main thing I need to implement is the editor itself. Now I know there are many different code editors like CodeMirror, Ace.js and Monaco but I want to start from scratch and build something like Atom had done. Currently I created a contenteditable div and also added a custom cursor. BTW I'm using React, TailwindCSS and TypeScript. Here is the component

These versions of Atom will stop working on February 2 [2023]. To keep using Atom, users will need to download a previous Atom version.