3 ms·
Nah dude this line of thinking got us here. We need to reach back to what the OG's in computing thought about. Small size, fast performance. Limit ourselves. I
by sergiotapia 8y ago
Nah dude this line of thinking got us here. We need to reach back to what the OG's in computing thought about. Small size, fast performance. Limit ourselves.
I read about this dude who purposely writes software on a shitheap laptop just so that "if it's fast here, it's fast on modern mobile phones."
Even my app written in Elixir and uses 160MB of RAM after letting it run for a week; I've been thinking: "Maybe I could bring it lower to what nzbget uses (around 59MB)". I've been exploring Nim for that.
We need a return to small-footprint as a feature.
- arendtio 8y agoHehe, kinda funny when an application comes with more security vulnerabilities than it has lines of code for its own logic ;-) EDIT: edited to make it less ambiguous
- monetus 8y agoSorry, is this a comment on elixer or Nim?
- arendtio 8y agoNeither. It is about having a color picker (probably just a few lines of code) bundled with quite a set of dependencies and complex chromium runtime environment which does not get updated regularly. Therefore they keep their vulnerabilities even after they are known and fixed in later versions of the dependencies. With small footprint applications, you are less likely to have such problems.
- monetus 8y agoCan't argue with you there, I tend to use tcl/tk for something this small.
- sergiotapia 8y agoMy app does very little and is meant to be self-hosted for your own use. Or are you talking about Elixir or Nim as a language? Edit: Oh I get it you actually meant: "Hehe, kinda funny when your application written for Electron comes with more security vulnerabilities than it has lines of code for its own logic ;-)"