That's odd. I am replying here, although there are a number of atom-is-slow comments throughout the thread. I don't find it to be slow with normal-sized sourcefiles. By "normal", I mean less than, say 5kb of text per file. Big files I do avoid in atom, but they tend to be rare in my codebases.
I don't use a ton of plugins, just tag matchers, minimal, and linters. I do all my build tooling (gulp for js/web dev, mavensmate for salesforce, etc) outside of atom, so maybe that helps.
Of course, the only real benefit I feel over sublimetext is in plugins. Linter support in atom is (IMO) better than ST. For actual code editing, they're all similar enough once you learn key bindings and whatnot.
I will say: being proficient in vi means I can work on ARM devices (Chromebooks with crouton), because neither ST nor atom work on arm. Yet, from the atom perspective, or ever from the ST one, which is the other reason I like the atom project. Loftier, FOSS goals.
>I don't find it to be slow with normal-sized sourcefiles. By "normal", I mean less than, say 5kb of text per file.
5 thousand bytes is pretty small. It is 122 lines of text if we use the average bytes per line of some code I have lying around (Emacs Lisp, exactly one byte per character, lines limited to 80 characters). For comparison, the average lines per file in the code I have lying around is 233.
I don't use a ton of plugins, just tag matchers, minimal, and linters. I do all my build tooling (gulp for js/web dev, mavensmate for salesforce, etc) outside of atom, so maybe that helps.
Of course, the only real benefit I feel over sublimetext is in plugins. Linter support in atom is (IMO) better than ST. For actual code editing, they're all similar enough once you learn key bindings and whatnot.
I will say: being proficient in vi means I can work on ARM devices (Chromebooks with crouton), because neither ST nor atom work on arm. Yet, from the atom perspective, or ever from the ST one, which is the other reason I like the atom project. Loftier, FOSS goals.