Live data from Hacker News

Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API

blog.atom.io

121–130 of 176 posts

Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API

#121
post #54

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's startup speed was heavily improved in 1.5 for me. I keep checking back every so often to see if it improves and they're steadily working on it. I think by the time 1.7 hits it'll be about on par with VSCode.

Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API

#122
post #61

The 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…

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 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

#123

I 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.

it's shocking to see how poor all of these editors are at remote editing after using emacs+tramp. all of the tools i use locally (magit, projectile, etc) just work when editing remote files on emacs.

Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API

#125
post #54

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…

Yes Sublime is more responsive, but for me it's just a minor annoyance. The benefits of a community over a one man project who has a tendency to disappear are more than evident IMO.

Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API

#126
post #54

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…

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.

Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API

#127
post #54

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 just did some benchmarking and discovered switching the Windows theme to Classic reduced the lag with 30-40ms!!!

Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API

#128
While I agree with most people that Atom is kind of unresponsive, don't you think that we have talked about it enough? Stop acting like you are the first person to notice. Since its first release that is the major complaint point. They either can't or don't want to do anything about it. Deal with it.

Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API

#129
post #61

Earlier 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

https://www.sublimetext.com/3dev

Re: Atom 1.6 Released with Pending Pane Items, Async Git and Top and Bottom Bar API

#130
post #54

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…

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.

I don't know that the stack is the problem. Visual Studio Code seems quite fast.

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.

Post reply on HN