[SwellJoe]

I tried it, liked that it was faster than Atom at the time (though the gap has shrunk, as I understand it), but couldn't deal with it having an "only one open project" model. That was a deal-breaker for me. All of my stuff is broken out into many small projects, and I'm trying to go further in that direction rather than toward more monolithic codebases.

That one factor was a deal-breaker and I went back to Atom (though I still use vim just as often as Atom, since I don't have every project open in Atom at any given time, and sometimes I just need to edit one file really quick and check it in).

VSCode is very good. But, as long as it's got a one-project model, I can't do anything with it.

[marksomnian]

That's changed in the latest insider build - you can now have multiple projects open

[SwellJoe]

Cool. I'll give it another go when I have some time to play. But honestly, most of the stuff I didn't like about Atom is resolved lately. It's fast enough, small enough (for my 16GB laptop), and reliable. And, has a gazillion features, most of which I never use.

[SOLAR_FIELDS]

Does it still choke up on any file that is either larger than 20,000 lines or has a single line that's longer than 20,000 or so characters?

I used to use Atom a lot but being that I regularly am pulling and investigating large files that was a deal breaker.

[SwellJoe]

I've never used it for anything quite that large. I have three windows open on my first virtual desktop: Editor, terminal, and browser. When I want to poke around in log files or other really long files, I'm using grep, tail, awk, and Perl (and vim), in the terminal.

The biggest file I regularly work with in the editor is 10,631 lines long (I just checked, and it's longer than I thought). Atom works fine with it, including syntax highlighting, and cutting/pasting/typing/etc.

Actually...out of curiosity, I just opened up a ~110,000 line file (a log I had laying around). It seems to work fine. It took a little longer to open than it would in vim (which is effectively instant), but not as long as I would have expected. It was well under a second, and within my comfort zone for opening files. Switching tabs seems maybe a little more sluggish with it loaded, but not uncomfortably so.

I think I have to accept Atom into the category of editors that can work with pretty large files. I can't imagine having a source file any longer than that 10,000 line file I work with regularly (and I would never make a file that large, but historic codebases sometimes have weird things in them), but it seems like it'll work even if someone did.

[SOLAR_FIELDS]

I think it is less the line count that I have problems with lately than line length. It's quite a specific use case, but I work with geographic data and occasionally deal with absolutely enormous wkb's that can be in the hundreds of thousands of characters. Couple that with writing in Hadoop typically going to one line per JSON representation and now I am regularly opening files to review that consist of a single line of text that might have upwards of 80,000 characters on average. Even beautified it still is problematic. VS code seems to be able to do it reasonably so the software stack cannot be blamed.

[ppbutt]

What do you use now?

[SOLAR_FIELDS]

VS Code mostly and if it's a big one even VS code cannot handle I will use Vim. See the sibling comment for my somewhat pointed use case.