3 ms·
Opening a 1GB JSON file and scrolling, editing, and keeping syntax highlighting correct is something that even native text editors struggle with.
by newaccount74 3y ago
Opening a 1GB JSON file and scrolling, editing, and keeping syntax highlighting correct is something that even native text editors struggle with.
- Alifatisk 3y agoSublime have opened way larger files with no issues for me
- eyelidlessness 3y agoI’ll second this. And to emphasize, so it’s not just a useless “+1 comment”: I never cared for Sublime as an editor, despite some effort to appreciate it when it was at its popularity peak. But it instantly became, and remained, my go to editor for working with huge files.
- arghwhat 3y agoNative code does not replace efficient algorithms. V8 can also JIT JS to something that runs fast, although the extra layers of abstraction between web code and platform interfaces do not help, and V8 can only do so much.
- Pannoniae 3y agoNotepad++ is a champ at doing that, as long as it has line breaks. (It chokes with massive single-line files like any other editor)
- zo1 3y agoLove Notepad++ to bits, but it chokes on just 20MB of nicely-formatted XML if you have syntax highlighting on. Disable that (if you can figure out how), and you're golden.
- datavirtue 3y agoI had to buy UltraEdit which is capable of handling 10GB files (the size in my case). Nothing else that I tried would work. Of course, this was ten years ago. I havent had to work with very large text files since then. It was able to perform search and replace at an acceptable and responsive pace, nearly instant.
- al_borland 3y agoWith a native editor, like Sublime, it may take a while to become functional, but it will eventually do what I want. With VS Code, loading in a big file usually crashes it. Thankfully I don’t have to deal with this as much as I used to.