<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: The power of a 500 MHz Pentium III system with 128 MB of RAM.</title>
	<atom:link href="http://pinderkent.blogsavy.com/archives/69/feed" rel="self" type="application/rss+xml" />
	<link>http://pinderkent.blogsavy.com/archives/69</link>
	<description>Just another Blogsavy.com weblog</description>
	<pubDate>Thu, 28 Aug 2008 03:01:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: adam</title>
		<link>http://pinderkent.blogsavy.com/archives/69#comment-99</link>
		<dc:creator>adam</dc:creator>
		<pubDate>Fri, 12 Oct 2007 01:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/80#comment-99</guid>
		<description>AVG Free

http://free.grisoft.com</description>
		<content:encoded><![CDATA[<p>AVG Free</p>
<p><a href="http://free.grisoft.com" rel="nofollow">http://free.grisoft.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chui Tey</title>
		<link>http://pinderkent.blogsavy.com/archives/69#comment-98</link>
		<dc:creator>Chui Tey</dc:creator>
		<pubDate>Mon, 23 Jul 2007 05:58:14 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/80#comment-98</guid>
		<description>Actually McAfee AV chews up about 300 Mb on my machine. Anyone can recommend better alternatives?</description>
		<content:encoded><![CDATA[<p>Actually McAfee AV chews up about 300 Mb on my machine. Anyone can recommend better alternatives?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jivlain</title>
		<link>http://pinderkent.blogsavy.com/archives/69#comment-97</link>
		<dc:creator>Jivlain</dc:creator>
		<pubDate>Mon, 23 Jul 2007 01:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/80#comment-97</guid>
		<description>Software expands to fill the hardware that contains it. If everyone's got shiny 3GHz dual-core processors, 2Gb of memory and a 300Gb hard drive it's only natural that we'll all run software that, for no good reason, actually needs all that.</description>
		<content:encoded><![CDATA[<p>Software expands to fill the hardware that contains it. If everyone&#8217;s got shiny 3GHz dual-core processors, 2Gb of memory and a 300Gb hard drive it&#8217;s only natural that we&#8217;ll all run software that, for no good reason, actually needs all that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://pinderkent.blogsavy.com/archives/69#comment-96</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sun, 22 Jul 2007 23:55:09 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/80#comment-96</guid>
		<description>With just Xorg, emacs, and opera the memory is pretty much consumed. For emacs I don't know that memory consumption was much of a design criteria however I see on Ubuntu its using about 10mb-13mb, which isn't that bad.</description>
		<content:encoded><![CDATA[<p>With just Xorg, emacs, and opera the memory is pretty much consumed. For emacs I don&#8217;t know that memory consumption was much of a design criteria however I see on Ubuntu its using about 10mb-13mb, which isn&#8217;t that bad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MemoryWhore</title>
		<link>http://pinderkent.blogsavy.com/archives/69#comment-95</link>
		<dc:creator>MemoryWhore</dc:creator>
		<pubDate>Sun, 22 Jul 2007 17:16:16 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/80#comment-95</guid>
		<description>And yes, I too am nostalgic for the days of I hacked QBASIC on a 486. But I'd rather retire from the IT world than go back to that. I'm gleefully looking forward to when I have terabytes of memory at my disposal.</description>
		<content:encoded><![CDATA[<p>And yes, I too am nostalgic for the days of I hacked QBASIC on a 486. But I&#8217;d rather retire from the IT world than go back to that. I&#8217;m gleefully looking forward to when I have terabytes of memory at my disposal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MemoryWhore</title>
		<link>http://pinderkent.blogsavy.com/archives/69#comment-94</link>
		<dc:creator>MemoryWhore</dc:creator>
		<pubDate>Sun, 22 Jul 2007 16:54:10 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/80#comment-94</guid>
		<description>Well, my original comment was vaporized when your little
blog shat out some sort of PHP/DB connectivity error. For
some reason I'm rewriting the comment:

If you're working with images, it is perfectly imaginable
and common to use several hundred MB of memory. A few medium
(or even one large image) combined with undo histories can
easily eat up several hundred or even well over a gig of
memory. When I set my image editor to only use 128 MB, I am
quite annoyed by the lack of undo history, and I only edit
relatively small images at a maximum of 3kx2k pixels one at
a time.

There are many other "legitimate" uses of gross amounts of
memory. However, I do admit that these uses for the common
PC user to be few and far between.

On the other hand, I will argue the typical "illegitimate"
uses of memory are in fact quite legitimate when you take in
to account the extreme difficulty it would take to optimize
the memory footprint of modern software as much as is
practically possible. Given how cheap memory is, the market
for such software is very small. This is rather fortunate in
my opinion, because although I find an occasional
optimization hack to be challenging and fun, I would find it
very tiresome and tedious to do such optimizations again and
again out of necessity.

Do I think it's worth having an extra 60 MB of RAM (at about
$1 / 16 MB) for all of Firefox's bloated features (including
for example quicker backwards navigation)? Absolutely.</description>
		<content:encoded><![CDATA[<p>Well, my original comment was vaporized when your little<br />
blog shat out some sort of PHP/DB connectivity error. For<br />
some reason I&#8217;m rewriting the comment:</p>
<p>If you&#8217;re working with images, it is perfectly imaginable<br />
and common to use several hundred MB of memory. A few medium<br />
(or even one large image) combined with undo histories can<br />
easily eat up several hundred or even well over a gig of<br />
memory. When I set my image editor to only use 128 MB, I am<br />
quite annoyed by the lack of undo history, and I only edit<br />
relatively small images at a maximum of 3kx2k pixels one at<br />
a time.</p>
<p>There are many other &#8220;legitimate&#8221; uses of gross amounts of<br />
memory. However, I do admit that these uses for the common<br />
PC user to be few and far between.</p>
<p>On the other hand, I will argue the typical &#8220;illegitimate&#8221;<br />
uses of memory are in fact quite legitimate when you take in<br />
to account the extreme difficulty it would take to optimize<br />
the memory footprint of modern software as much as is<br />
practically possible. Given how cheap memory is, the market<br />
for such software is very small. This is rather fortunate in<br />
my opinion, because although I find an occasional<br />
optimization hack to be challenging and fun, I would find it<br />
very tiresome and tedious to do such optimizations again and<br />
again out of necessity.</p>
<p>Do I think it&#8217;s worth having an extra 60 MB of RAM (at about<br />
$1 / 16 MB) for all of Firefox&#8217;s bloated features (including<br />
for example quicker backwards navigation)? Absolutely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RobM</title>
		<link>http://pinderkent.blogsavy.com/archives/69#comment-93</link>
		<dc:creator>RobM</dc:creator>
		<pubDate>Sun, 22 Jul 2007 11:08:39 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/80#comment-93</guid>
		<description>I presume you've all seen this?

http://www.joelonsoftware.com/articles/fog0000000020.html

I realise he's the spawn of the devil because he once took Microsoft's shilling, but I still think he makes a good point.</description>
		<content:encoded><![CDATA[<p>I presume you&#8217;ve all seen this?</p>
<p><a href="http://www.joelonsoftware.com/articles/fog0000000020.html" rel="nofollow">http://www.joelonsoftware.com/articles/fog0000000020.html</a></p>
<p>I realise he&#8217;s the spawn of the devil because he once took Microsoft&#8217;s shilling, but I still think he makes a good point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dynamic</title>
		<link>http://pinderkent.blogsavy.com/archives/69#comment-92</link>
		<dc:creator>Dynamic</dc:creator>
		<pubDate>Sun, 22 Jul 2007 09:52:15 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/80#comment-92</guid>
		<description>That would be oh so nice, static, if XP were equivalent to Ubuntu.

XP is a joke.</description>
		<content:encoded><![CDATA[<p>That would be oh so nice, static, if XP were equivalent to Ubuntu.</p>
<p>XP is a joke.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bitter Old Man</title>
		<link>http://pinderkent.blogsavy.com/archives/69#comment-91</link>
		<dc:creator>Bitter Old Man</dc:creator>
		<pubDate>Sun, 22 Jul 2007 04:38:42 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/80#comment-91</guid>
		<description>1 Meg of RAM! And we liked it! We LOVED it!</description>
		<content:encoded><![CDATA[<p>1 Meg of RAM! And we liked it! We LOVED it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://pinderkent.blogsavy.com/archives/69#comment-90</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sun, 22 Jul 2007 04:08:59 +0000</pubDate>
		<guid isPermaLink="false">http://pinderkent.blogsavy.com/archives/80#comment-90</guid>
		<description>First, the memory available on systems a decade or more old has no bearing on the modern concept of "minimal".  I can't recall the last time I was on a system with less than 512, and even that is rare.

However, as an embedded developer, we don't use Linux on our embedded systems specifically because Linux hogs way too much memory for a resource-limited, real-time environment like a network switch.  So, at least for us embedded folks, there still are places today where you can find memory-limited systems where the original poster's argument is in fact laughable.</description>
		<content:encoded><![CDATA[<p>First, the memory available on systems a decade or more old has no bearing on the modern concept of &#8220;minimal&#8221;.  I can&#8217;t recall the last time I was on a system with less than 512, and even that is rare.</p>
<p>However, as an embedded developer, we don&#8217;t use Linux on our embedded systems specifically because Linux hogs way too much memory for a resource-limited, real-time environment like a network switch.  So, at least for us embedded folks, there still are places today where you can find memory-limited systems where the original poster&#8217;s argument is in fact laughable.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
