|
|
|
|
|
|
by jolux
3869 days ago
|
|
|
Oh, I open it up about once a week. It's not that much slower than, say, Sublime Text, without any plugins installed. However, I like to load up my text editors with IDE-like affordances. I also wanted to experiment with a bunch of Facebook languages so I thought I'd try Nuclide, which basically made Atom unusable that last time I tested it. It's a shame that it doesn't work better, because it's truly a great idea. I have some faith that the performance will improve but there is a limit and I'm almost certain that that limit is below that of editors that render natively. Now, if they started supporting a statically typed JS like TypeScript or if they did something like restrict the plugin architecture to a simpler DSL and the theming language to be a smaller subset of HTML, that might improve things, but it would also no longer "just work" for web developers wanting to write plugins for it. Edit: Also if WebAssembly becomes a widespread thing it would help performance greatly. |
|
|
I found the same. I just tried nuclide again, which I do once a month or so, and it basically rendered Atom useless.
> I have some faith that the performance will improve but there is a limit
I used to argue the same thing, because it is built on the DOM, but after talking to a few of the Atom developers and a guy from Google at a conference I have new hope. The google guy said in a talk that Google was adding an API that allows javascript to go around the DOM. You will be able to render text into an existing DIV directly without triggering the DOM. This was specifically to allow things like atom to display and scroll text fast.
So there are clever people working to fix speed problems. I personally am not seeing speed problems even with 30 or 40 plugins. I think the breaking point was 1.0.