Live data from Hacker News

Introducing Block Decorations

blog.atom.io

31–38 of 38 posts

Re: Introducing Block Decorations

#31
post #6

Earlier quoted context omitted.

I've recently started using more, but I still have to turn to sublime fairly often due to speed (dealing with larger projects, bigger data files, more complex regex searching). That being said, the performance has been getting steadily better, enough to the point I can do most of my coding in it without noticing a problem. I'd suggest giving it another go and see how it does for you! It's quite a joy to hack on.

Can you give an example of 'more complex regex searching'? I thought the JS regex engine would be at par with whatever sublime uses.

I don't have issues in terms of expressiveness, but in terms of performance. Complex/expensive regexs that run quite quickly in sublime take a long time on atom, especially on large documents.

Perhaps this is an abuse of the tool, but I find its convenient to do these sorts of things in a text editor where I can watch my regexs highlight it's selections in real time.

Re: Introducing Block Decorations

#32

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…

What are people doing with their text editor that they need blazing speed?

I admit the answer that immediately comes to mind is: "uh, editing text?" But to be more serious --

My own coding projects rarely have files with more than 300-400 lines, but the coding projects I'm working on aren't always my own, and my own projects involving text files aren't always coding. If I have reason to load a 3000-line source code file, I don't expect my editor to choke. (I've done this on occasion.) If I have reason to load a 603K, 7300-paragraph Markdown file, I don't expect my editor to choke on that, either. (For somewhat obscure reasons, I'm doing that weekly, and yes, I'm making edits as I go.)

In (very!) limited testing just now with both those cases, Atom 1.4 seemed to do just fine, for the record.

Re: Introducing Block Decorations

#33

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 tried installing it recently and adding on the facebook react extention, and whilst installing it completely broke. Restarting made it end up in the same install cycle as before. Atom fixes what is broken in Sublime, but has it's own issues that are currently far worse.

Facebook have their own "ide" - Nuclide. Many of their plugins break Atom when used standalone.

Re: Introducing Block Decorations

#34

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 wish Atom would prevent me from opening such files, as an option. I sometimes accidentally open large minified files and have to wait.

Re: Introducing Block Decorations

#35

Earlier quoted context omitted.

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…

Your codebase is very modular and wonderful but for other projects, large files (100kb+) are not uncommon. For those projects, "clean up your code before using my product" is not an acceptable answer.

This seems like a tragedy of the commons: those projects only exist in the state they're in because some products exist which allow you to work with them despite their flaws. Whereas, if nothing worked with 100kb+ source files, the projects would change.

Re: Introducing Block Decorations

#36

Earlier quoted context omitted.

I tried installing it recently and adding on the facebook react extention, and whilst installing it completely broke. Restarting made it end up in the same install cycle as before. Atom fixes what is broken in Sublime, but has it's own issues that are currently far worse.

Facebook have their own "ide" - Nuclide. Many of their plugins break Atom when used standalone.

To make that clearer: Nuclide is to Ubuntu as Atom is to Debian. You can use Debian packages on Ubuntu, but Ubuntu packages are really unlikely to work on Debian.

Re: Introducing Block Decorations

#37

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…

Opening log files? Having a generic text editing component that can scale to showing 75k logs makes it easy to build great visual tooling on top of that.

Re: Introducing Block Decorations

#38
post #13

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.

I just downloaded the latest minified production release of ember.js and it took Atom less than a second to open it on my Machine (2014 rMBP).

Opening it up and trying to edit it/move around are two different things. Try to scroll to the end of it. You'll break Atom either the line will just randomly stop or you'll freeze your Atom.
Post reply on HN