4 ms·
I haven’t read the docs lately but when I was hacking on Atom years ago, the plugin model was TOO freeform, and with plugins all running on the main thread, it
by ZitchDog 4y ago
I haven’t read the docs lately but when I was hacking on Atom years ago, the plugin model was TOO freeform, and with plugins all running on the main thread, it was easy for a plugin to kill performance and slow down the editor. The vscode model strikes a better tradeoff between extensibility and performance. Extensions have less power but my editing experience is never ruined by a rogue extension.
- neurobashing 4y agoOne of the last things I remember about Atom was that by the time they’d figured out all the stuff they needed to fix, VSCode had come in and stolen all the eyeballs, so to speak. So they have a good roadmap, they just need to do the implementation.