and i should probably say: i haven't optimised duin at all lol. there's a lot of code i'm sure could be done better, but there's probably even more improvements that i don't know

so idk maybe duin will be one of those editors that can open big files just fine? would be awesome if true

i tried some other editors out too!

micro uses a lot more memory but less cpu, which is probably better? not sure

and vim... idk how they fucking do it but vim only uses 19mb ram and 2.5% cpu. somehow

(not as much as firefox though)

did you try opening the 400.000+ line file in firefox? :)

another stress test i recommend is opening a file with one or more very long lines, such as an executable binary file. win10 notepad.exe's word wrapping suffers a lot in such files, especially when the window (i guess that's equivalent to your terminal's viewport) is resized causing all word wrap points to be recalculated.

i tried opening the duin executable inside of duin, but it didn't seem to bad - the memory goes up to like 65M and cpu to 40%
might be because duin doesn't actually wrap words yet though lol (the rendering really really sucks)

as for firefox, it's badddd lol
it goes to 40% cpu usage when i scroll through the file, and the memory usage gets even higher than usual >~<