2 ms·

> Let's talk about RAM usage: Not using available RAM is a failure not a reason to be proud... That is rather disingenuous. People aren't complaining about usi

> Let's talk about RAM usage: Not using available RAM is a failure not a reason to be proud... That is rather disingenuous. People aren't complaining about using RAM at all, they are complaining about using it inefficiently compared to other options. Your statement makes it sound like using more RAM is in itself a source of pride. Many of your other points are perfectly valid, but they are overshadowed a bit by that rather silly one.

The_rationalist 7y ago
>Many of your other points are perfectly valid, but they are overshadowed a bit by that rather silly one Thank you. >they are complaining about using it inefficiently compared to other options I cannot deny nor confirm that, where is the evidence? For an equivalent UX?
- dspillett 7y ago
  > where is the evidence Evidence of people stating that Electron apps use RAM inefficiently compared to how they believe "more native" implementations would? All over the place. Of people giving specific examples? No time to search one out right now but I've seen many discussions where similar tools written in different frameworks show Node+Chrome+YourCode to use much more memory than the others, sometimes with a less responsive feeling UX, while providing a very similar feature set, so that evidence should be easy to find. Do you have any evidence of your opposing theory? Applications with the same feature set where an Electron based version has similar (or, indeed, lower) memory requirements for similarly performant operation / UX, or a situation where an Electron based tool manages to provide more functionality with the same memory requirements?