3 ms·
On my GNU / Debian testing 64-bit, with 10 tabs opened it consumed 31 MiB of RAM and my CPU pushed itself to reach 0.75% at its busiest processing during typing
by stephen82 6y ago
On my GNU / Debian testing 64-bit, with 10 tabs opened it consumed 31 MiB of RAM and my CPU pushed itself to reach 0.75% at its busiest processing during typing.
To me this is simply mind-blowing.
- alcover 6y agoNot as mind-blowing as SublimeText leaking 3 solid GB of RAM after a few days on my Debian..
- vijaybritto 6y agoIts always the extensions. Not sublime itself. That has been my experience so far
- barrkel 6y agoWe used to be able to open 10 files at a time on 4MB systems back in the 90s. (They weren't big files, of course, but still. Standards have slipped.)
- stephen82 6y agoYes, those were the days...every once in a while, I visit https://kolibrios.org/en/screen https://kolibrios.org/en/screen to get nostalgic. Indeed standards have slipped or better say have been sacrificed at the altar of "quantity over quality". For a simple "Hello, World!" string message, nowadays you need how many MBs of RAM. Madness, complete madness!
- anthk 6y agoWut, I opened 12 files in 9MB back in the day on a 32MB device as nothing.
- cormacrelf 6y agoRight now, I'm editing all the files in a 3kLOC project in neovim, doing completion with an LSP host, in 14.8MB. Keep it going for a few days and you might rack up 40MB. People can keep creating lightweight editors all they like, but you really need to bring more to the table than that when vim already exists.