Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

On the flipside, I recently had to make some changes to a ~1.5GB XML file, like in the middle of the file. I had a sudden flashback to the Atom editor, which developers considered a 1MB XML file as "large", and hence it totally chocked on a 100MB one I tried once, crashing out after eating 8+GB of RAM.

To my mild surprise, it opened in a few seconds, and while all the fancy checking stuff got disabled, basic syntax highlighting still worked so element tags were colorized. Finding and changing the offending element was not much different from normal. I checked memory usage, expecting it to be astronomical, but it was quite within reason (~3 GB IIRC).

I admit I did not expect it to go that well.



You didn't mention which editor you were able to edit the large XML in. Just confirming, it was VSCode? Because that'd be amazing!


Yes, VSCode as of half a year ago.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: