3 ms·

I’m old school vim person, so don’t have much clue. Is atom still relevant or is vscode taking over everything?

edoceo 8y ago
Our shop has 4 devs, one on VSCode, unlikely to convert, three on Atom. I was the last covert to Atom here - after 15+ years on jEdit.
- d3sandoval 8y ago
  For a second there, I thought I finally found the other person on the internet who was a jEdit zealot. But then I realized it's the same person I've known for years ;) What makes you stick to Atom? I switched to VSCode due to Atom's terrible performance when opening huge files.
  - edoceo 8y ago
    :) I don't open huge files, finally found a good SFTP plugin, php-debug hooks with xdebug. Really it took me many months of tweaking to get Atom to be a daily driver - I don't want to do it again soon
    - aynawn 8y ago
      I used Atom for a couple years and raved about it's features and package management but when it came to using it as an IDE, it fell short for one reason. It doesn't have a configurable way to debug across all languages. For example, try debugging python vs node. Python works well but node doesn't afaik. OTOH vscode does have a way to do this using a `launch.json` file which is flexible enough to add custom debugging profiles for a single project and it can be stored directly in version control. I tried the editor out because of this one feature alone in order to debug node and haven't looked back.
pjmlp 8y ago
VSCode is the only Electron app that I care to have on my computer, mostly due to TypeScript and Rust. Interesting how Microsoft manages to do in TypeScript stuff that Github not even with C++ managed to (according to the interwebs), regarding performance. Now that they are also part of Microsoft, maybe they could share some information among them.
- quaunaut 8y ago
  At the same time, on a giant project, I'm finding VSCode's performance starts to fall apart completely where Atom performs the exact same as before. For example- it's not uncommon for Vim mode in VSCode to just stop functioning for 5-10 seconds on large projects while other addons continue operating. I keep switching back and forth, primarily because VSCode's performance wins are so deceptive- it will feel amazing and look cool on some things, then in completely unexpected places just absolutely shit the bed. So I hop back and forth, and have even started working on building my own plugins for VSCode to do the things no one's added to it yet that Atom has addons for.
  - jgalt212 8y ago
    Got To Symbol is basically non-working in non-trivial sized Python projects and doesn't seem to have anything to do with whether or not ctags is installed. https://code.visualstudio.com/docs/editor/editingevolved#_go-to-symbol https://code.visualstudio.com/docs/editor/editingevolved#_go...
superdaniel 8y ago
For merges and other finicky git actions I’ve been increasingly turning to Atom instead of the commandline. I like how it auto-formats my commit messages to line wrap and how it makes highlighting merge conflicts easy. For everything else these days I use VSCode.

Our shop has 4 devs, one on VSCode, unlikely to convert, three on Atom. I was the last covert to Atom here - after 15+ years on jEdit.

d3sandoval 8y ago
For a second there, I thought I finally found the other person on the internet who was a jEdit zealot. But then I realized it's the same person I've known for years ;) What makes you stick to Atom? I switched to VSCode due to Atom's terrible performance when opening huge files.
- edoceo 8y ago
  :) I don't open huge files, finally found a good SFTP plugin, php-debug hooks with xdebug. Really it took me many months of tweaking to get Atom to be a daily driver - I don't want to do it again soon
  - aynawn 8y ago
    I used Atom for a couple years and raved about it's features and package management but when it came to using it as an IDE, it fell short for one reason. It doesn't have a configurable way to debug across all languages. For example, try debugging python vs node. Python works well but node doesn't afaik. OTOH vscode does have a way to do this using a `launch.json` file which is flexible enough to add custom debugging profiles for a single project and it can be stored directly in version control. I tried the editor out because of this one feature alone in order to debug node and haven't looked back.

pjmlp 8y ago

VSCode is the only Electron app that I care to have on my computer, mostly due to TypeScript and Rust. Interesting how Microsoft manages to do in TypeScript stuff that Github not even with C++ managed to (according to the interwebs), regarding performance. Now that they are also part of Microsoft, maybe they could share some information among them.

quaunaut 8y ago
At the same time, on a giant project, I'm finding VSCode's performance starts to fall apart completely where Atom performs the exact same as before. For example- it's not uncommon for Vim mode in VSCode to just stop functioning for 5-10 seconds on large projects while other addons continue operating. I keep switching back and forth, primarily because VSCode's performance wins are so deceptive- it will feel amazing and look cool on some things, then in completely unexpected places just absolutely shit the bed. So I hop back and forth, and have even started working on building my own plugins for VSCode to do the things no one's added to it yet that Atom has addons for.
- jgalt212 8y ago
  Got To Symbol is basically non-working in non-trivial sized Python projects and doesn't seem to have anything to do with whether or not ctags is installed. https://code.visualstudio.com/docs/editor/editingevolved#_go-to-symbol https://code.visualstudio.com/docs/editor/editingevolved#_go...

superdaniel 8y ago

For merges and other finicky git actions I’ve been increasingly turning to Atom instead of the commandline. I like how it auto-formats my commit messages to line wrap and how it makes highlighting merge conflicts easy. For everything else these days I use VSCode.