5 ms·

A 2 MB file limit makes Atom just impossible for me to use.

by mproud 12y ago

seanp2k2 12y ago
Curious: what type of things would you want to edit over 2MiB? I think it's probably more a function of "having such a huge DOM would be a bad UX anyway" vs just some arbitrary limit.
- xienze 12y ago
  Log files.
  - adrusi 12y ago
    I'm curious, do you really need a text editor for log files? It seems like the wrong tool, after all, you're not editing your logs. I have never found a case where `cat example.log | grep Error | less` is insufficient. Granted, I think a good editor should be able to handle files of any size, but if atom sacrifices that for the ability to let an extension display anything it wants inline with the text, it doesn't seem like a catastrophic loss.
    - nilkn 12y ago
      Moreover, if you really need a text editor for a log file, you can just launch vim or something for that task. I've never really understood why people get in this mindset of "X is my editor, and I will only use X." I guess, though, this is harder to do if you insist on a completely GUI-based interface.
      - snotrockets 12y ago
        > I've never really understood why people get in this mindset of "X is my editor, and I will only use X." If you use certain software a lot, you'd find it behaviour and shortcuts ingrained into your subconscious mind. Like driving: an experienced driver doesn't consciously think of how to control the car, she just does. This is what makes Emacs or vi users so efficient: they had years to get the operation of those editors ingrained into their brains. Which takes quite an effort, that is not worth repeating with another editor (unless yours is broken).
        nilkn 12y ago
        There's no reason to downvote me because you have a different opinion. I thought this place was supposed to be better for discussion but evidently not. I'm a vim user who can easily use something else if it's better for a certain purpose. I guess not everybody feels the same way and some are even offended by the suggestion.
        reitanqild 12y ago
        The offense is not about not agreeing with you it seems but about the way you present it. (Disclaimer: not a downvoter, just an observer. )
        deleted 12y ago
        [deleted]
    - xienze 12y ago
      > I'm curious, do you really need a text editor for log files? Well, it doesn't always boil down to "grep for one specific thing." Usually you find one thing, then you have to locate the next couple instances of it (I use vim, so I'm used to just doing nnnnnnnn... to keep finding the next occurrence). Or perhaps you grep for one specific thing, find out something is related, need to search for some other thing, etc. Maybe you need a little bit of context around the thing you grepped for. Text editors work pretty well for combing through log files...
    - hollerith 12y ago
      I use grep every day, but never from a terminal emulator or from an interactive Unix shell. (I use Emacs's grep mode.) And almost never without visiting (opening in the editor) at least one of the files being grepped.
corford 12y ago
I regularly work with 70MB-150MB csv files that need editing in a few places before being imported to the db.
hollerith 12y ago
I just opened a 131-meg file in TextMate 2 to see what would happen. It was very slow, but perfectly possible. In particular, loading the file into TextMate took about 15 sec. Searching for a string (using ^S) took 2 or 3 sec per occurrence (i.e., per tap of the S key with the control key held down). Inserting took 2 or 3 seconds per character. Scrolling was probably just as snappy as it is in a small file. In particular, by dragging in the scroll bar a person can smoothly scroll past many megs of text per second. In GNU Emacs, loading took about 4 sec, after which scrolling, searching, moving to the top or bottom, and inserting (even near the end of the file) were instantaneous.

A 2 MB file limit makes Atom just impossible for me to use.

by mproud 12y ago

A 2 MB file limit makes Atom just impossible for me to use.

Curious: what type of things would you want to edit over 2MiB? I think it's probably more a function of "having such a huge DOM would be a bad UX anyway" vs just some arbitrary limit.

xienze 12y ago
Log files.
- adrusi 12y ago
  I'm curious, do you really need a text editor for log files? It seems like the wrong tool, after all, you're not editing your logs. I have never found a case where `cat example.log | grep Error | less` is insufficient. Granted, I think a good editor should be able to handle files of any size, but if atom sacrifices that for the ability to let an extension display anything it wants inline with the text, it doesn't seem like a catastrophic loss.
  - nilkn 12y ago
    Moreover, if you really need a text editor for a log file, you can just launch vim or something for that task. I've never really understood why people get in this mindset of "X is my editor, and I will only use X." I guess, though, this is harder to do if you insist on a completely GUI-based interface.
    - snotrockets 12y ago
      > I've never really understood why people get in this mindset of "X is my editor, and I will only use X." If you use certain software a lot, you'd find it behaviour and shortcuts ingrained into your subconscious mind. Like driving: an experienced driver doesn't consciously think of how to control the car, she just does. This is what makes Emacs or vi users so efficient: they had years to get the operation of those editors ingrained into their brains. Which takes quite an effort, that is not worth repeating with another editor (unless yours is broken).
      - nilkn 12y ago
        There's no reason to downvote me because you have a different opinion. I thought this place was supposed to be better for discussion but evidently not. I'm a vim user who can easily use something else if it's better for a certain purpose. I guess not everybody feels the same way and some are even offended by the suggestion.
        reitanqild 12y ago
        The offense is not about not agreeing with you it seems but about the way you present it. (Disclaimer: not a downvoter, just an observer. )
        deleted 12y ago
        [deleted]
  - xienze 12y ago
    > I'm curious, do you really need a text editor for log files? Well, it doesn't always boil down to "grep for one specific thing." Usually you find one thing, then you have to locate the next couple instances of it (I use vim, so I'm used to just doing nnnnnnnn... to keep finding the next occurrence). Or perhaps you grep for one specific thing, find out something is related, need to search for some other thing, etc. Maybe you need a little bit of context around the thing you grepped for. Text editors work pretty well for combing through log files...
  - hollerith 12y ago
    I use grep every day, but never from a terminal emulator or from an interactive Unix shell. (I use Emacs's grep mode.) And almost never without visiting (opening in the editor) at least one of the files being grepped.

corford 12y ago

I regularly work with 70MB-150MB csv files that need editing in a few places before being imported to the db.

hollerith 12y ago

I just opened a 131-meg file in TextMate 2 to see what would happen. It was very slow, but perfectly possible. In particular, loading the file into TextMate took about 15 sec. Searching for a string (using ^S) took 2 or 3 sec per occurrence (i.e., per tap of the S key with the control key held down). Inserting took 2 or 3 seconds per character. Scrolling was probably just as snappy as it is in a small file. In particular, by dragging in the scroll bar a person can smoothly scroll past many megs of text per second. In GNU Emacs, loading took about 4 sec, after which scrolling, searching, moving to the top or bottom, and inserting (even near the end of the file) were instantaneous.