5 ms·

Is Atom not snappy for you? I've used both and I honestly can't spot the difference on Linux; both are enough snappy for me. I know Atom lags with huge files s

by spoiler 10y ago

Is Atom not snappy for you? I've used both and I honestly can't spot the difference on Linux; both are enough snappy for me. I know Atom lags with huge files sometimes, or when I place a lot of multiple cursors and then edit something, but I haven't tried either with VSCode.

overcast 10y ago
Atom is pretty horrendous on both Mac, and Windows, at least from the last time I used it. Which admittedly was months ago. I really, really tried to give it a shot. But it takes forever to start up, and is just overall sluggish on simple stuff. Try VSCode, you'll never use Atom again. It feels pretty damn close to Sublime in responsiveness.
rb808 10y ago
Try opening a 1GB log file.
- atomi 10y ago
  But why?
  - rpeden 10y ago
    Perhaps because it's a use case that many people use a text editor for. For those people, opening such a file makes for a good test to compare the performance of Atom and VSCode...and Vim, and Emacs, and lots of others. For writing code, I find Atom a bit slower to start up than Code, but generally nice and usable afterward. That's on an 8 core, 32GB of RAM system, though, so Atom could very well be more sluggish for others.
    - ygra 10y ago
      But a text editor to open a file you won't ever edit is maybe also not the best idea. A pure text viewer can use different data structures that don't have to anticipate edits to the text and likely be faster. Or, on the other hand, a text editor trying to optimise the use case where people open large files without editing them (or only editing tiny portions of it), will likely grow a lot more complex.
nobleach 10y ago
Irony here is, I just opened a 290k file in vim... and... well, let's just say it was about 30 seconds before I could do anything. So I thought, "let me open this in Atom". Almost immediately it appeared, AND I could scroll through it! (with vim-mode obviously)
- Redoubts 10y ago
  Eh, when this happens to me I just hit ^C, since it's likely trying to apply syntax to the whole thing. At least I can do something in the editor immediately after.

by spoiler 10y ago

overcast 10y ago

Atom is pretty horrendous on both Mac, and Windows, at least from the last time I used it. Which admittedly was months ago. I really, really tried to give it a shot. But it takes forever to start up, and is just overall sluggish on simple stuff. Try VSCode, you'll never use Atom again. It feels pretty damn close to Sublime in responsiveness.

rb808 10y ago

Try opening a 1GB log file.

atomi 10y ago
But why?
- rpeden 10y ago
  Perhaps because it's a use case that many people use a text editor for. For those people, opening such a file makes for a good test to compare the performance of Atom and VSCode...and Vim, and Emacs, and lots of others. For writing code, I find Atom a bit slower to start up than Code, but generally nice and usable afterward. That's on an 8 core, 32GB of RAM system, though, so Atom could very well be more sluggish for others.
  - ygra 10y ago
    But a text editor to open a file you won't ever edit is maybe also not the best idea. A pure text viewer can use different data structures that don't have to anticipate edits to the text and likely be faster. Or, on the other hand, a text editor trying to optimise the use case where people open large files without editing them (or only editing tiny portions of it), will likely grow a lot more complex.

nobleach 10y ago

Irony here is, I just opened a 290k file in vim... and... well, let's just say it was about 30 seconds before I could do anything. So I thought, "let me open this in Atom". Almost immediately it appeared, AND I could scroll through it! (with vim-mode obviously)

Redoubts 10y ago
Eh, when this happens to me I just hit ^C, since it's likely trying to apply syntax to the whole thing. At least I can do something in the editor immediately after.