3 ms·
interesting article and one i resonate with personally. But one things sticks out: the author complains about his text editor taking enormous sums of memory. I
by dijit 4y ago
interesting article and one i resonate with personally.
But one things sticks out: the author complains about his text editor taking enormous sums of memory. I sympathise, truly, but obviously this text editor is doing something more than just displaying text that necessitates the ram consumption.
Maybe things are leaking like crazy, but the author isn't using the built-in MacOS text editor, so I wonder what internal costs we attribute to useful tools.
I usually get more bent out of shape about software that I'm forced to run, like Teams, Slack and the progressively heavy Web. (with chrome as a de-facto requirement).
For text editing, there's trade-offs but at least they're yours to make. You can go very far with nvim (and neovide) with almost no memory consumption, but you wont get the nice UI elements.
- fuzzygroup 4y ago> I sympathise, truly, but obviously this text editor is doing something more than just displaying text that necessitates the ram consumption. All I do is edit text. My editor isn't an IDE. It doesn't run tests, etc. It is just an editor. I have no idea why it does what it does but it does it. And I get what you are saying about nvim / neovide but it feels reasonable to me that __45__ years into the WIMP interface (assuming 1977 as a point when Xerox Parc had things running well) that we should be able to: * Have a nice UI * That edits text without crashing I completely agree on tools you are forced to use. Truth.