21–30 of 38 posts
I find Atom very interesting, but the performance always drives me away from using it. Have recent versions improved? Anyone using it full time?
It's still kind of bad. Just try opening up a minified JS (or any kind of large file) file and watch your Atom become unresponsive for 5 minutes.
Earlier quoted context omitted.
It's still kind of bad. Just try opening up a minified JS (or any kind of large file) file and watch your Atom become unresponsive for 5 minutes.
Sure but that's not a common use-case and won't affect people who want to use Atom as a day-to-day code editor.
I find Atom very interesting, but the performance always drives me away from using it. Have recent versions improved? Anyone using it full time?
I find Atom very interesting, but the performance always drives me away from using it. Have recent versions improved? Anyone using it full time?
I find Atom very interesting, but the performance always drives me away from using it. Have recent versions improved? Anyone using it full time?
Earlier quoted context omitted.
I've never done it, but id assume the effort to do a rewrite would be tremendous.
Not really, it would be tedious, but idiomatic coffeescript can be converted to idiomatic javascript basically on a line-for-line basis. Also the compiler really does produce readable code (though unmistakeably computer-generated), so the process might even be sped by reducing it to just tidying up compiler output. It's a task that could easily be spread across any number of human translators, too. The main limiting…
I find Atom very interesting, but the performance always drives me away from using it. Have recent versions improved? Anyone using it full time?
I've been using Atom full time for about a year and a half now. I've never noticed performance issues though, so I've always been curious about where these complaints come from. I just ran a find over the project I've been working on full time, and the largest file, by a long shot, is 8kb, and a little under 100 lines. That's just an autogenerated enum of the HTTP status codes though, so it isn't indicative of real c…
I find Atom very interesting, but the performance always drives me away from using it. Have recent versions improved? Anyone using it full time?
I've been using Atom full-time for about a year, after switching from Sublime. I'm happy with it as an editor, and like the momentum behind the plugins ecosystem. Performance has been completely adequate, and I've seen none of the issues that always seem to crop up whenever Atom is mentioned on HN. There may be a platform difference - I use it on OSX, but friends of mine on Linux have been less satisfied. I do still…
I've noticed that the editor, with my load of plugins, comes up relatively quick on OSX (~4 seconds from launching, equally as long to open a new window), and roughly twice as slow on Windows (~8 seconds from click, ~3 seconds to open a window)
But, when I'm using it, I'm basically living in the app, so the startup time is really a moot point IMO.
Earlier quoted context omitted.
Not really, it would be tedious, but idiomatic coffeescript can be converted to idiomatic javascript basically on a line-for-line basis. Also the compiler really does produce readable code (though unmistakeably computer-generated), so the process might even be sped by reducing it to just tidying up compiler output. It's a task that could easily be spread across any number of human translators, too. The main limiting…
Along those lines, it would be wonderful if someone would write a coffeescript implementation that output clean, idiomatic ES6 rather than ES5!