I love the concept of Atom and have a lot invested in its success. That being said, I switched back to Sublime because of the responsiveness, and here's why: Programming (for me) is a craft. When I'm in the flow of coding, there's a conversation between me and my program, mediated through the editor (and my REPL). Even a subtle typing lag is enough to subtly disrupt that flow state – the speed of thought and text no…
I've had the same feeling about the startup speed issue, but with javascript / typescript, I've found that Visual Studio Code occupies the middle in startup performance, and I've found the "intellisense" information to take a load off the mental difficulty of work and memory. So now I use Sublime to make quick edits, but for anything longer, I use Visual Studio Code.
Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
121–130 of 176 posts
Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
#122The new features and updates are great, but the one thing holding me back from using it is the fact it is extremely slow and laden with performance issues. Anyone who has ever attempted to open a file with a lot of lines of code will attest to the fact that Atom has issues. Ironically, Microsoft's open source Visual Studio Code editor is based in part of some aspects of Atom and it has exceptional performance and is…
I simply don't understand the appeal of the thing. To a person, everyone who raves about it says, essentially "just like Sublime Text, but in Javascript!" , and yeah, that seems right. Just like Sublime Text, but in Javascript...and plagued with the performance problems you'd expect from Sublime Text, written in JavaScript. There's not really a killer feature that makes me want to switch from the editor I use already…
Build 3103: February 2016
Build 3080/3083: March 2015
Build 3065: August 2014
Build 3059: December 2013
Atom:
1.6: March 2016
1.5: February 2016
1.4: January 2016
1.3: December 2015
User experience-wise, I don't find a large difference between the two editors. Some things are better in ST3, some are better in Atom, but these are very minor things and they're more about my personal preferences rather than the operation of either editor.
The fact that Atom is actively developed however, is a major boon in my eyes. I am confident that whatever bug pops up in Atom will be seen to within a reasonable timeframe. I have no such confidence regarding bugs and issues in ST3.
Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
#123I really wish there was a way to use Atom in client/server mode. I'd like to leave a headless session running on my home Linux server and be able to attach to it from work. Right now, I use SSHFS to mount the remote directory so I can edit locally, but it leaves a lot to be desired. Considering that Atom is all just Node and Chromium under the hood, it's surprising that there's no way to run at is as a server.
Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
#124Yet another broken release for half of the world.
Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
#125I love the concept of Atom and have a lot invested in its success. That being said, I switched back to Sublime because of the responsiveness, and here's why: Programming (for me) is a craft. When I'm in the flow of coding, there's a conversation between me and my program, mediated through the editor (and my REPL). Even a subtle typing lag is enough to subtly disrupt that flow state – the speed of thought and text no…
Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
#126I love the concept of Atom and have a lot invested in its success. That being said, I switched back to Sublime because of the responsiveness, and here's why: Programming (for me) is a craft. When I'm in the flow of coding, there's a conversation between me and my program, mediated through the editor (and my REPL). Even a subtle typing lag is enough to subtly disrupt that flow state – the speed of thought and text no…
There is a massive gap in the market for a native speed open-source SublimeText clone.
Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
#127I love the concept of Atom and have a lot invested in its success. That being said, I switched back to Sublime because of the responsiveness, and here's why: Programming (for me) is a craft. When I'm in the flow of coding, there's a conversation between me and my program, mediated through the editor (and my REPL). Even a subtle typing lag is enough to subtly disrupt that flow state – the speed of thought and text no…
Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
#128Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
#129Earlier quoted context omitted.
I simply don't understand the appeal of the thing. To a person, everyone who raves about it says, essentially "just like Sublime Text, but in Javascript!" , and yeah, that seems right. Just like Sublime Text, but in Javascript...and plagued with the performance problems you'd expect from Sublime Text, written in JavaScript. There's not really a killer feature that makes me want to switch from the editor I use already…
Sublime Text 3: Build 3103: February 2016 Build 3080/3083: March 2015 Build 3065: August 2014 Build 3059: December 2013 Atom: 1.6: March 2016 1.5: February 2016 1.4: January 2016 1.3: December 2015 User experience-wise, I don't find a large difference between the two editors. Some things are better in ST3, some are better in Atom, but these are very minor things and they're more about my personal preferences rather t…
> Sublime Text 3:
>
> Build 3103: February 2016
I'm just as annoyed as anyone else about the rate of development on Sublime Text, but please, at least state the whole truth.Build 3109
Release Date: 18 March 2016
Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API
#130I love the concept of Atom and have a lot invested in its success. That being said, I switched back to Sublime because of the responsiveness, and here's why: Programming (for me) is a craft. When I'm in the flow of coding, there's a conversation between me and my program, mediated through the editor (and my REPL). Even a subtle typing lag is enough to subtly disrupt that flow state – the speed of thought and text no…
Agreed, and the sluggish problem can't be solved because the Atom team chose a developer stack which benefited them, and not one which benefited the actual users of the software. There is a massive gap in the market for a native speed open-source SublimeText clone.
And the your first statement seems to imply some kind of obligation where there is none. Open source is a public service not a public obligation.