3 ms·

It should not take an i7 processor to run a text editor. I mean no disrespect, but either something is very wrong with your computer, or something is very wrong

• OriginalPenguin 10y ago
  For years and years it took a very powerful computer to get decent performance out of Emacs. Emacs only seems speedy now because computers have finally caught up. Either Atom will get faster, or it will add so much value it's okay being slow. And then computers will eventually catch up, just like they did with Emacs.
  • vonklaus 10y ago
    I said this elsewhere but vscode's strategy won me over atom's. Vscode was faster and more stable with much less features which they gradually added over time. Atom had all the features, more lag, and has been trying to polish them since. Texteditors must be fast and predictable. Tab support for vscode was it for me. Also, their ide must add overhead and yet still much faster than atom
• ipedrazas 10y ago
  In this case, you can blame the software without any doubt
• mikeokner 10y ago
  It's the original Electron[1] app. It's just a JavaScript web application running in a re-branded Chrome window, which is why it uses an absurd amount of computing power compared to a normal text editor (or most other native applications). [1] http://electron.atom.io/ http://electron.atom.io/
  • duaneb 10y ago
    Do they at least render natively, or do they rely on Blink + (I'm assuming) some crazy JS text rendering & syntax coloring to get it usable?
    • mintplant 10y ago
      The latter.