News for hackers. Stuff that matters.
Re:A RAM Edition of Dirty Coding Tricks by Bartweiss on Sunday December 17, 2017 @06:09PM (#15948197)
I always think about Windows Vista when I hear "unlimited memory". Somebody looked at expanding memory and processing, and decided "let's have an animated 3D background for the OS, that'll be good". Memory is always going to be pushed to its limits unless devs and users alike go out of their way to keep it intact.
Re:A RAM Edition of Dirty Coding Tricks by jooke on Monday December 18, 2017 @08:13AM (#15951362)
What's the point of having more memory if not for new features?
Re:A RAM Edition of Dirty Coding Tricks by Bartweiss on Monday December 18, 2017 @10:54AM (#15952440)
In general, nothing.

For example, Chrome eats pretty much all free memory keeping tabs loaded, but surrenders it gracefully when needed. That's a great use of memory.

But for an OS, and specifically for a feature that doesn't devolve unless the user goes and manually changes it, it's obnoxious. The OS is inherently a support layer for the things the user opens by choice; I'd argue any expansion of its resource footprint ought to have a clear justification.

Re:A RAM Edition of Dirty Coding Tricks by lostgame on Monday December 18, 2017 @09:03AM (#15951620)
In an Operating System, that ‘more memory’ could be used for applications instead of bloat.
Re:A RAM Edition of Dirty Coding Tricks by hoosieree on Monday December 18, 2017 @07:32PM (#15956791)
Sorry, I don't trust myself or you to exercise restraint. The ONLY thing that keeps memory usage in check is physics.