<story><title>Small Memory Software: Patterns for systems with limited memory</title><url>http://www.smallmemory.com/book.html</url></story><parent_chain></parent_chain><comment><author>userbinator</author><text>The one thing that I was strongly expecting but didn&amp;#x27;t seem to find any mention of when I was quickly paging through is the idea of using simpler, constant-space algorithms (e.g. streaming style, keeping only what&amp;#x27;s needed in memory) and in general &lt;i&gt;reducing the amount of code and data&lt;/i&gt;.&lt;p&gt;Likewise, the use of C++ and Java in a book about &amp;quot;limited memory&amp;quot; is a bit unusual.&lt;p&gt;Then again, I&amp;#x27;m &lt;i&gt;really&lt;/i&gt; not keen on the whole &amp;quot;patterns&amp;quot; thing, because from experience I&amp;#x27;ve found it tends to replace careful thought with dogmatic application of rules that might not be relevant at all to the situation at hand.</text></comment>
<story><title>Small Memory Software: Patterns for systems with limited memory</title><url>http://www.smallmemory.com/book.html</url></story><parent_chain></parent_chain><comment><author>fiatjaf</author><text>At least this serves to remind people they must think about memory, at least sometimes. The rule today seems to be to use as much memory as possible, load gigantic frameworks or use super-heavy languages for the most simple of tasks. I only notice because my computer do not have all the memory a normal modern computer has.</text></comment>