<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" 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/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>It’s good for you.</title>
	
	<link>http://marvintam.com</link>
	<description />
	<lastBuildDate>Tue, 09 Mar 2010 17:45:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/marvintam" /><feedburner:info uri="marvintam" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Is this why IE6 doesn’t support PNG24?</title>
		<link>http://feedproxy.google.com/~r/marvintam/~3/XMP3q_sPSuQ/</link>
		<comments>http://marvintam.com/2010/03/is-this-why-ie6-doesnt-support-png24/#comments</comments>
		<pubDate>Tue, 09 Mar 2010 01:44:30 +0000</pubDate>
		<dc:creator>Marvin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://marvintam.com/?p=471</guid>
		<description><![CDATA[So Mosaic&#8217;s source code has just been released on GitHub, and a sharp eye at Reddit has already spotted this gem (keep in mind that IE is originally derived from Mosaic).
Assuming that IE was actually derived from this code base, may I present the reason we had to work around PNG24 for almost a decade:

/* [...]]]></description>
			<content:encoded><![CDATA[<p>So <a href="http://en.wikipedia.org/wiki/Mosaic_(web_browser)">Mosaic</a>&#8217;s source code has just been released <a href="http://github.com/alandipert/ncsa-mosaic">on GitHub</a>, and a sharp eye <a href="http://www.reddit.com/r/programming/comments/barki/mosaic_browser_source_code_now_in_github/c0ltm90">at Reddit</a> has already spotted <a href="http://github.com/alandipert/ncsa-mosaic/blob/master/src/readPNG.c#L200">this gem</a> (keep in mind that IE is originally derived from Mosaic).</p>
<p>Assuming that IE was actually derived from this code base, may I present the reason we had to work around PNG24 for almost a decade:</p>

<div class="wp_syntax"><div class="code"><pre class="c" style="font-family:monospace;"><span style="color: #808080; font-style: italic;">/* its #if'ed out for now cause I don't have anything to
   test it with */</span></pre></div></div>

<img src="http://feeds.feedburner.com/~r/marvintam/~4/XMP3q_sPSuQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://marvintam.com/2010/03/is-this-why-ie6-doesnt-support-png24/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://marvintam.com/2010/03/is-this-why-ie6-doesnt-support-png24/</feedburner:origLink></item>
		<item>
		<title>HTML5: &lt;!DOCTYPE html&gt;</title>
		<link>http://feedproxy.google.com/~r/marvintam/~3/nX1ZIiejhQU/</link>
		<comments>http://marvintam.com/2010/03/html5-doctype-html/#comments</comments>
		<pubDate>Mon, 08 Mar 2010 04:51:28 +0000</pubDate>
		<dc:creator>Marvin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[html5]]></category>

		<guid isPermaLink="false">http://marvintam.com/?p=465</guid>
		<description><![CDATA[All the cool kids have started using the new HTML5 doctype:

&#60;!DOCTYPE html&#62;

It triggers standards mode even in shitty browsers, so we can dump its verbose predecessor and start blazing a path of HTML5 glory.
]]></description>
			<content:encoded><![CDATA[<p>All the cool kids have started using the new HTML5 doctype:</p>

<div class="wp_syntax"><div class="code"><pre class="html" style="font-family:monospace;">&lt;!DOCTYPE html&gt;</pre></div></div>

<p>It triggers standards mode even in shitty browsers, so we can dump its verbose predecessor and start blazing a path of HTML5 glory.</p>
<img src="http://feeds.feedburner.com/~r/marvintam/~4/nX1ZIiejhQU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://marvintam.com/2010/03/html5-doctype-html/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://marvintam.com/2010/03/html5-doctype-html/</feedburner:origLink></item>
		<item>
		<title>HTML5: &lt;meta charset="UTF-8"&gt;</title>
		<link>http://feedproxy.google.com/~r/marvintam/~3/PMXeE1BpWNQ/</link>
		<comments>http://marvintam.com/2010/03/html5-meta-charset-utf-8/#comments</comments>
		<pubDate>Fri, 05 Mar 2010 22:48:15 +0000</pubDate>
		<dc:creator>Marvin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[html5]]></category>

		<guid isPermaLink="false">http://marvintam.com/?p=454</guid>
		<description><![CDATA[The old way:

&#60;meta http-equiv=&#34;Content-Type&#34; content=&#34;text/html; charset=UTF-8&#34;&#62;

The HTML5 way, which works on all browsers:

&#60;meta charset=&#34;UTF-8&#34;&#62;

Even though the charset can and should already be set in the HTTP response header, the meta tag is still relevant when the document is offline.
]]></description>
			<content:encoded><![CDATA[<p>The old way:</p>

<div class="wp_syntax"><div class="code"><pre class="html" style="font-family:monospace;">&lt;meta http-equiv=&quot;Content-Type&quot; content=&quot;text/html; charset=UTF-8&quot;&gt;</pre></div></div>

<p>The HTML5 way, which <a href="http://www.w3.org/International/tests/results/results-html5-charset">works on all browsers</a>:</p>

<div class="wp_syntax"><div class="code"><pre class="html" style="font-family:monospace;">&lt;meta charset=&quot;UTF-8&quot;&gt;</pre></div></div>

<p>Even though the charset can and should already be set in the HTTP response header, the meta tag is still relevant when the document is offline.</p>
<img src="http://feeds.feedburner.com/~r/marvintam/~4/PMXeE1BpWNQ" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://marvintam.com/2010/03/html5-meta-charset-utf-8/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://marvintam.com/2010/03/html5-meta-charset-utf-8/</feedburner:origLink></item>
		<item>
		<title>Naming conventions should follow the language</title>
		<link>http://feedproxy.google.com/~r/marvintam/~3/qx84OabD8sE/</link>
		<comments>http://marvintam.com/2010/03/naming-conventions-should-follow-the-language/#comments</comments>
		<pubDate>Wed, 03 Mar 2010 18:33:02 +0000</pubDate>
		<dc:creator>Marvin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://marvintam.com/2010/03/naming-conventions-should-conform-to-the-language/</guid>
		<description><![CDATA[For example, id, class and attribute names should be in lowercase-with-dashes in HTML/CSS; JavaScript names should be in camelCase (better defined here); and anything in URLs (including file names) should be in lowercase not only because of conventions, but for cross-platform compatibility as well.
Please, avoid crazy shit like ab_someName and keep things consistent!
]]></description>
			<content:encoded><![CDATA[<p>For example, id, class and attribute names should be in <code>lowercase-with-dashes</code> in HTML/CSS; JavaScript names should be in <code>camelCase</code> (better defined <a href="http://javascript.crockford.com/code.html">here</a>); and anything in URLs (including file names) should be in lowercase not only because of conventions, but for cross-platform compatibility as well.</p>
<p>Please, avoid crazy shit like ab_someName and keep things consistent!</p>
<img src="http://feeds.feedburner.com/~r/marvintam/~4/qx84OabD8sE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://marvintam.com/2010/03/naming-conventions-should-follow-the-language/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://marvintam.com/2010/03/naming-conventions-should-follow-the-language/</feedburner:origLink></item>
		<item>
		<title>F.lux: better lighting for your screen</title>
		<link>http://feedproxy.google.com/~r/marvintam/~3/DfhLgD4dxhc/</link>
		<comments>http://marvintam.com/2010/02/f-lux-better-lighting-for-your-screen/#comments</comments>
		<pubDate>Fri, 26 Feb 2010 06:31:21 +0000</pubDate>
		<dc:creator>Marvin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://marvintam.com/?p=412</guid>
		<description><![CDATA[F.lux adjusts the color temperature of your screen to match your lighting and time of the day.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.stereopsis.com/flux/">F.lux</a> adjusts the color temperature of your screen to match your lighting and time of the day.</p>
<img src="http://feeds.feedburner.com/~r/marvintam/~4/DfhLgD4dxhc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://marvintam.com/2010/02/f-lux-better-lighting-for-your-screen/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://marvintam.com/2010/02/f-lux-better-lighting-for-your-screen/</feedburner:origLink></item>
		<item>
		<title>Optimize only when you have a reason to.</title>
		<link>http://feedproxy.google.com/~r/marvintam/~3/lxYnp6qyi_c/</link>
		<comments>http://marvintam.com/2010/02/optimize-only-when-you-have-a-reason-to/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 17:58:56 +0000</pubDate>
		<dc:creator>Marvin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://marvintam.com/?p=413</guid>
		<description><![CDATA[Measuring Javascript Parse and Load
While studies like this are fascinating to observe and to learn from, be very careful — unless you&#8217;re doing something like distributing JS libraries, these optimizations probably do not apply to you.
Keep in mind that the parse-and-load test runs 1000 iterations; in the first table, the actual average parse time is [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://carlos.bueno.org/2010/02/measuring-javascript-parse-and-load.html">Measuring Javascript Parse and Load</a></p>
<p>While studies like this are fascinating to observe and to learn from, be very careful — unless you&#8217;re doing something like distributing JS libraries, these optimizations probably do not apply to you.</p>
<p>Keep in mind that the parse-and-load test runs 1000 iterations; in the first table, the actual average parse time is really only 0.125ms at worst and 0.003ms at best. Compare that to the average HTTP request — you might see sub-30ms responses just for a HTTP 304 on a good day, but 1000ms+ responses are not unheard of on unprimed caches (even more with DNS lookups). To put this into perspective, a snappy HTTP request at 30ms is more than <strong>200 times</strong> slower than the slowest parse time of 0.125ms.</p>
<p>In other words, the net improvement you might gain from such parse-and-load optimizations is insignificant compared to the improvement from removing just <em>one</em> HTTP request.</p>
<p>So before you go adding more lines of code to accomplish yet another new trick, profile your code to see where the actual bottlenecks are. Otherwise, this smells like a lot like <a href="http://en.wikipedia.org/wiki/Program_optimization#When_to_optimize">premature optimization</a>.</p>
<img src="http://feeds.feedburner.com/~r/marvintam/~4/lxYnp6qyi_c" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://marvintam.com/2010/02/optimize-only-when-you-have-a-reason-to/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://marvintam.com/2010/02/optimize-only-when-you-have-a-reason-to/</feedburner:origLink></item>
		<item>
		<title>Always check your permissions!</title>
		<link>http://feedproxy.google.com/~r/marvintam/~3/cDrDILsdbOM/</link>
		<comments>http://marvintam.com/2010/02/always-check-your-permissions/#comments</comments>
		<pubDate>Wed, 17 Feb 2010 18:52:36 +0000</pubDate>
		<dc:creator>Marvin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://marvintam.com/?p=399</guid>
		<description><![CDATA[Note to self — Apache (stock on Leopard, which runs as _www) cannot read the preset directories in my home directory (like Desktop, Documents, Downloads, Library etc) because these directories only allow owner access by default (drwx------). 
So that is why PHP won&#8217;t include files on my desktop. D’oh.
]]></description>
			<content:encoded><![CDATA[<p>Note to self — Apache (stock on Leopard, which runs as <code>_www</code>) cannot read the preset directories in my home directory (like <code>Desktop</code>, <code>Documents</code>, <code>Downloads</code>, <code>Library</code> etc) because these directories only allow owner access by default (<code>drwx------</code>). </p>
<p>So <em>that</em> is why PHP won&#8217;t include files on my desktop. D’oh.</p>
<img src="http://feeds.feedburner.com/~r/marvintam/~4/cDrDILsdbOM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://marvintam.com/2010/02/always-check-your-permissions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://marvintam.com/2010/02/always-check-your-permissions/</feedburner:origLink></item>
		<item>
		<title>Origin of the wheel group</title>
		<link>http://feedproxy.google.com/~r/marvintam/~3/iGEiQYSxJV0/</link>
		<comments>http://marvintam.com/2010/02/origin-of-the-wheel-group/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 18:29:56 +0000</pubDate>
		<dc:creator>Marvin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://marvintam.com/?p=400</guid>
		<description><![CDATA[Ever wonder how the wheel group in /etc/group came to be?

“The guy who wrote the group functionality was both a buddhist and a Journey fan.  He was listening to &#8220;Wheel in the Sky&#8221; while trying to figure out a way to give more people administrative rights without giving too much access. In a fit [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://lists.freebsd.org/pipermail/freebsd-chat/2003-December/001724.html">Ever wonder how the <code>wheel</code> group in <code>/etc/group</code> came to be?</a></p>
<blockquote><p>
“The guy who wrote the group functionality was both a buddhist and a Journey fan.  He was listening to &#8220;Wheel in the Sky&#8221; while trying to figure out a way to give more people administrative rights without giving too much access. In a fit of enlightment, he came up with a special group for administrators.  Since they were the ones who kept things turning, it only seemed appropriate that &#8220;wheel&#8221; be immortalized in the /etc/group file.”
</p></blockquote>
<img src="http://feeds.feedburner.com/~r/marvintam/~4/iGEiQYSxJV0" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://marvintam.com/2010/02/origin-of-the-wheel-group/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://marvintam.com/2010/02/origin-of-the-wheel-group/</feedburner:origLink></item>
		<item>
		<title>Google begins IE6’s death march</title>
		<link>http://feedproxy.google.com/~r/marvintam/~3/fle8Jn8AEBo/</link>
		<comments>http://marvintam.com/2010/01/google-begins-ie6s-death-march/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 23:25:17 +0000</pubDate>
		<dc:creator>Marvin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://marvintam.com/?p=388</guid>
		<description><![CDATA[Modern browsers for modern applications

“We’re also going to begin phasing out our support, starting with Google Docs and Google Sites. As a result you may find that from March 1 key functionality within these products &#8212; as well as new Docs and Sites features &#8212; won’t work properly in older browsers.”

]]></description>
			<content:encoded><![CDATA[<p><a href="http://googleenterprise.blogspot.com/2010/01/modern-browsers-for-modern-applications.html">Modern browsers for modern applications</a></p>
<blockquote><p>
“We’re also going to begin phasing out our support, starting with Google Docs and Google Sites. As a result you may find that from March 1 key functionality within these products &#8212; as well as new Docs and Sites features &#8212; won’t work properly in older browsers.”
</p></blockquote>
<img src="http://feeds.feedburner.com/~r/marvintam/~4/fle8Jn8AEBo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://marvintam.com/2010/01/google-begins-ie6s-death-march/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://marvintam.com/2010/01/google-begins-ie6s-death-march/</feedburner:origLink></item>
		<item>
		<title>In light of iPad’s unveiling…</title>
		<link>http://feedproxy.google.com/~r/marvintam/~3/TEq59OOm1kE/</link>
		<comments>http://marvintam.com/2010/01/in-light-of-ipads-unveiling/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 20:32:29 +0000</pubDate>
		<dc:creator>Marvin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://marvintam.com/?p=383</guid>
		<description><![CDATA[A couple of choice quotes I found on &#8220;A message to the Internets regarding the iPad&#8221;:
“You can&#8217;t just ask customers what they want and then try to give that to them. By the time you get it built, they&#8217;ll want something new.”
— Steve Jobs
Subsequently spotted in the comments:
“If I had asked people what they wanted, [...]]]></description>
			<content:encoded><![CDATA[<p>A couple of choice quotes I found on <a href="http://cruftbox.com/blog/archives/001592.html">&#8220;A message to the Internets regarding the iPad&#8221;</a>:</p>
<blockquote><p>“You can&#8217;t just ask customers what they want and then try to give that to them. By the time you get it built, they&#8217;ll want something new.”<br />
<cite>— Steve Jobs</cite></p></blockquote>
<p>Subsequently spotted in the comments:</p>
<blockquote><p>“If I had asked people what they wanted, they would have said faster horses.”<br />
<cite>— Henry Ford</cite></p></blockquote>
<img src="http://feeds.feedburner.com/~r/marvintam/~4/TEq59OOm1kE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://marvintam.com/2010/01/in-light-of-ipads-unveiling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://marvintam.com/2010/01/in-light-of-ipads-unveiling/</feedburner:origLink></item>
	</channel>
</rss><!-- Dynamic page generated in 1.236 seconds. --><!-- Cached page generated by WP-Super-Cache on 2010-03-09 12:50:35 --><!-- Compression = gzip -->
