I'm mostly reminded of Brackets, https://github.com/adobe/brackets, which I moved away from as a general-purpose text editor, but still seems solid for specifically doing frontend development.
Everyone focuses on Atom as a general-purpose editor, and its performance isn't so great in that regard, but if it focused on a specific area, it would be something I might consider using again. It feels easier to have editors for different things, than manually enabling different sets of plugins, for different projects.
Max Brunsfeld gave a talk about Tree-Sitter at FOSDEM 2018. You can check it out here.
I like Atom exactly for what it is. Simple at its core, very customizable, fast enough for regular use and under active development. Maybe other editors can do the same or more, but I don't really care.
However broad the policy shows people various things with different products, it basically doesn't say much of anything about vs code, and starts discussing enterprise environments are situations in which you need to talk to your enterprise admin about privacy stuff, yada yada.
Going back to the vs code page, it says they use telemetry and crash dump reporting. It does say that users can follow a link for info about turning off crash reporting.
I am not sure what the exact definition of telemetry is, and if it varies from company to company. After seeing that MSoft was sucking in every keystroke typed on a windows machine, and having a terrible experience with UN-removable one-drive with an office 201X install, I've lost faith in what Msoft has become, and trust them less than free products from google.
Maybe there is some way to run vscode in a VM that is 100% blocked from the internet and that would prevent it from sending tons of data?
Maybe I am missing something this early and no coffee yet.
Wouldn't these user settings be enough?
Depends on the console and on what you're used to. If you can maximize it in full screen and especially if the diffs are colored like git's, then it's a very pleasant experience.
What I like about Atom is that it's not an IDE. It's an editor. If you want it to be an IDE, then you can add language specific plugins that turn it into an IDE. Even the integrated git/github plugin is useless to me because we're using fossil. In contrast, VS Code comes packed with features for Js/Ts which make it an IDE rather than an editor.
There's a definite performance cost for this customizability, but I'm willing to pay for it.
Going beyond a tutorial, what could be really cool is a GUI where someone can paste in a code snippet of a language they want to colorize, then manually go through tokens classifying them as literals/keywords/whatever. Making a proper grammar for an entire language just to get some basic colorization gets old fast.
One thing I like very much in Atom, and I miss in VSCode, is the ability to amend a commit: you check "Amend", your commit is displayed, you do your changes, you click "Commit", done.
I think I've never noticed it was blocking. Great work.