<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Packaging images in your code</title>
	<atom:link href="http://almaer.com/blog/packaging-images-in-your-code/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/packaging-images-in-your-code</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Sat, 08 Sep 2012 07:06:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Vik</title>
		<link>http://almaer.com/blog/packaging-images-in-your-code/comment-page-1#comment-28953</link>
		<dc:creator>Vik</dc:creator>
		<pubDate>Tue, 08 Nov 2005 17:38:15 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/packaging-images-in-your-code#comment-28953</guid>
		<description>This reminds me of those old x86 Assembler &quot;intros&quot; put out by the pirate groups.  The whole thing would be packaged in one tiny EXE or COM file, with the GIF image completely inlined.  The purpose was to make it easy to transport the intro across the wire so more people would see it -- having external GIFs, or a zipped EXE plug GIF would certainly reduce viewership.

I don&#039;t see how those ideas translate to webapps. I mean they&#039;re supposed to be centrally hosted. Plus, wouldn&#039;t it be more beneficial to allow people to change the PNG if they wanted... easily?

I certainly don&#039;t think this calls for a generalization of JSP vs PHP programmers, because I&#039;ve seen some pretty whacky things being done with JSP as well.  What I do see is that a JSP person would be more likely to do this hack in an external class (with some &quot;framework&quot;) because that&#039;s the prevailing mindset.
</description>
		<content:encoded><![CDATA[<p>This reminds me of those old x86 Assembler &#8220;intros&#8221; put out by the pirate groups.  The whole thing would be packaged in one tiny EXE or COM file, with the GIF image completely inlined.  The purpose was to make it easy to transport the intro across the wire so more people would see it &#8212; having external GIFs, or a zipped EXE plug GIF would certainly reduce viewership.</p>
<p>I don&#8217;t see how those ideas translate to webapps. I mean they&#8217;re supposed to be centrally hosted. Plus, wouldn&#8217;t it be more beneficial to allow people to change the PNG if they wanted&#8230; easily?</p>
<p>I certainly don&#8217;t think this calls for a generalization of JSP vs PHP programmers, because I&#8217;ve seen some pretty whacky things being done with JSP as well.  What I do see is that a JSP person would be more likely to do this hack in an external class (with some &#8220;framework&#8221;) because that&#8217;s the prevailing mindset.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee</title>
		<link>http://almaer.com/blog/packaging-images-in-your-code/comment-page-1#comment-28952</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Fri, 04 Nov 2005 17:46:19 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/packaging-images-in-your-code#comment-28952</guid>
		<description>Dion - I think you&#039;ve touched on one of the core differences between PHP and Java developers. PHP developers will do what seems cool, whereas Java developers (generally) do what works, regardless of its &quot;cool&quot; factor.

Or maybe its just that I perceive Java developers to be more pragmatic? I don&#039;t know... I&#039;ve done both camps, and now reside in the Java camp - I&#039;ve seen the error of my ways, and try to educate those that haven&#039;t yet seen the light, but sometimes its difficult...
</description>
		<content:encoded><![CDATA[<p>Dion &#8211; I think you&#8217;ve touched on one of the core differences between PHP and Java developers. PHP developers will do what seems cool, whereas Java developers (generally) do what works, regardless of its &#8220;cool&#8221; factor.</p>
<p>Or maybe its just that I perceive Java developers to be more pragmatic? I don&#8217;t know&#8230; I&#8217;ve done both camps, and now reside in the Java camp &#8211; I&#8217;ve seen the error of my ways, and try to educate those that haven&#8217;t yet seen the light, but sometimes its difficult&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dion</title>
		<link>http://almaer.com/blog/packaging-images-in-your-code/comment-page-1#comment-28951</link>
		<dc:creator>Dion</dc:creator>
		<pubDate>Tue, 01 Nov 2005 18:11:36 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/packaging-images-in-your-code#comment-28951</guid>
		<description>Lee -

I know :)  I thought that someone with a ukonline account would get the sarcasm of the thing ;)

Dion
</description>
		<content:encoded><![CDATA[<p>Lee -</p>
<p>I know :)  I thought that someone with a ukonline account would get the sarcasm of the thing ;)</p>
<p>Dion</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee</title>
		<link>http://almaer.com/blog/packaging-images-in-your-code/comment-page-1#comment-28950</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Tue, 01 Nov 2005 16:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/packaging-images-in-your-code#comment-28950</guid>
		<description>on what weird ass planet is that clever? ever heard of maintainability?

besides, its a CPU/RAM hit to access your script and chuck out the code for the image. If you simply put it in the equivalent of your htdocs dir its a lot less burden. Guess you aren&#039;t envisioning your app ever being successful, but then again with techniques like that, I can understand why ;)
</description>
		<content:encoded><![CDATA[<p>on what weird ass planet is that clever? ever heard of maintainability?</p>
<p>besides, its a CPU/RAM hit to access your script and chuck out the code for the image. If you simply put it in the equivalent of your htdocs dir its a lot less burden. Guess you aren&#8217;t envisioning your app ever being successful, but then again with techniques like that, I can understand why ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pramod Biligiri</title>
		<link>http://almaer.com/blog/packaging-images-in-your-code/comment-page-1#comment-28949</link>
		<dc:creator>Pramod Biligiri</dc:creator>
		<pubDate>Tue, 01 Nov 2005 11:43:15 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/packaging-images-in-your-code#comment-28949</guid>
		<description>I think base64 encoding of images is popular on the web. I&#039;ve seen some Javascript code and Greasemonkey scripts use this to store images.
</description>
		<content:encoded><![CDATA[<p>I think base64 encoding of images is popular on the web. I&#8217;ve seen some Javascript code and Greasemonkey scripts use this to store images.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliot Anderson</title>
		<link>http://almaer.com/blog/packaging-images-in-your-code/comment-page-1#comment-28948</link>
		<dc:creator>Elliot Anderson</dc:creator>
		<pubDate>Tue, 01 Nov 2005 07:45:52 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog2/packaging-images-in-your-code#comment-28948</guid>
		<description>Been there, done that :P

I got the idea from a little script I found once by CeleronDude that did something similar. Most of the time I would just use an absolute link to the images off my server but if the app needs to run on its own then I would package it into the script.
</description>
		<content:encoded><![CDATA[<p>Been there, done that :P</p>
<p>I got the idea from a little script I found once by CeleronDude that did something similar. Most of the time I would just use an absolute link to the images off my server but if the app needs to run on its own then I would package it into the script.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
