3 ms·
RAM wasn't the problem, that's the whole point.
by kodablah 8y ago
RAM wasn't the problem, that's the whole point.
- freehunter 8y agoYou're right, but that's missing the point. The problem is inefficient code using too much RAM. Instead of fixing the process, the user took out some RAM hoping the code would magically become more efficient when it needed to run with less RAM. Instead the program ran even slower, and the user was somehow surprised by this outcome. Either the user can continue to blame the program and remove even more RAM, or the user can fix the process that was using too much RAM to begin with. In some very misguided cases, the user might even remove RAM and increase CPU power, leading to even more wasted resources and no improvement in program speed. Far too often the solution is to continue removing RAM in the hopes that the inefficient process magically fixes itself. It rarely does.