5 ms·
For the last several months I've been in a perpetual state of switching back and forth between Atom and VS Code. So far, I find myself continually frustrated.
by quaunaut 8y ago
For the last several months I've been in a perpetual state of switching back and forth between Atom and VS Code. So far, I find myself continually frustrated.
Undoubtedly, Atom is slow to start up in a new folder. But in exchange for that initial speed, I get:
* Universally better keybinds. From better split editor(even using the newest VS Code Insiders, which has new split editing binds/tools), to better Vim integration(having to spam j or k to go up/down lines), Atom keybinds(whether official or from the community) seem to just work intelligently.
* Teletype in VS Code is just rough.(CAVEAT: I've not used Atom's, so it may be just as bad.) From it breaking many keybinds for as long as you have your experience shared(using vim `o` to newline and indent is genuinely a 50/50 as to whether it works, and there's a lot more where that came from), to difficulty for the sharer to track the people they've shared with, to the inbuilt console just failing to let one of my sharees to run my tests.
* The number and usefulness of addons in the VS Code community seems to be just consistently a step below. ElixirLS[1] is official on VS Code, yet breaks fairly often- yet never does on Atom, despite it being merely a test! There's no alternative for Advanced Open File[2]. I understand this is an ecosystem problem and that I can contribute to fixing it, but with it being so frequent I often get frustrated.
Furthermore, I really want to know the future of these two projects, plus atom/xray[3]. Because if Atom can get VSCode's speed, I don't see a point to Atom. Alternatively, if VSCode could just get better along the edges, that would similarly be a huge improvement. Both are so fantastic and so close to my ideal(at this point, I have more language issues than editor issues), so both being under the same roof I don't see as inherently negative- but investing in either also seems foolhardy.
------------------
1. https://github.com/JakeBecker/elixir-ls https://github.com/JakeBecker/elixir-ls
2. https://atom.io/packages/advanced-open-file https://atom.io/packages/advanced-open-file
3. https://github.com/atom/xray https://github.com/atom/xray
- symlinkk 8y agoTo answer your first complaint, Atom keybinds are available for VSCode: https://github.com/Microsoft/vscode-atom-keybindings https://github.com/Microsoft/vscode-atom-keybindings
- jamesgeck0 8y ago> to better Vim integration(having to spam j or k to go up/down lines) What movement command are you trying to use that isn't working? All the basic up/down movement commands should be supported. https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md
- softwaregirl 8y agoI think he means that you have to spam j/k instead of just holding it down. ie. if you hold j you expect the cursor to keep moving up, with vs code it will just move up a single line.
- chillee 8y agoThat shouldn't be an issue. Check the README. This is a common issue people run into on Macs.