<?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: Making Github&#8217;s Code Readable</title>
	<atom:link href="http://codeulate.com/2009/11/making-githubs-code-readable/feed/" rel="self" type="application/rss+xml" />
	<link>http://codeulate.com/2009/11/making-githubs-code-readable/</link>
	<description></description>
	<lastBuildDate>Sun, 05 Sep 2010 18:31:40 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Max</title>
		<link>http://codeulate.com/2009/11/making-githubs-code-readable/comment-page-1/#comment-3444</link>
		<dc:creator>Max</dc:creator>
		<pubDate>Mon, 01 Feb 2010 02:42:15 +0000</pubDate>
		<guid isPermaLink="false">http://codeulate.com/?p=46#comment-3444</guid>
		<description>The reason for selecting courier, I believe, is that it is a well known, commonly used, and widely supported fixed pitch font. I personally love fixed pitch for coding, because it causes my text to line up well, so if I am calling the same method on a list of parameters, as often is the case when writing to configuration or log files, I have the parameters in columns, and can use my text editor&#039;s column mode to edit them simultaneously. I also find it more readable, as code must be interpreted by my mind and deciphered, I often find myself looking for a specific part of the line; &lt;i&gt;my eyes are in column mode&lt;/i&gt;. I agree that the example you showed was badly formatted, but I think the font size was the issue, not the type, and I feel that you could have solved the problem locally with a script like &lt;a href=&quot;//lab.arc90.com/experiments/readability/css/readability-print.css&#039;;_readability_print_css.media=&#039;print&#039;;_readability_print_css.type=&#039;text/css&#039;;document.getElementsByTagName(&#039;head&#039;)[0].appendChild(_readability_print_css);})();&quot; rel=&quot;nofollow&quot;&gt;&quot;readability&quot;&lt;/a&gt; or such. 

I do not post this to bitch - I liked the rest of the post. I just happen to have courier&#039;s back on this matter.</description>
		<content:encoded><![CDATA[<p>The reason for selecting courier, I believe, is that it is a well known, commonly used, and widely supported fixed pitch font. I personally love fixed pitch for coding, because it causes my text to line up well, so if I am calling the same method on a list of parameters, as often is the case when writing to configuration or log files, I have the parameters in columns, and can use my text editor&#8217;s column mode to edit them simultaneously. I also find it more readable, as code must be interpreted by my mind and deciphered, I often find myself looking for a specific part of the line; <i>my eyes are in column mode</i>. I agree that the example you showed was badly formatted, but I think the font size was the issue, not the type, and I feel that you could have solved the problem locally with a script like <a href="//lab.arc90.com/experiments/readability/css/readability-print.css';_readability_print_css.media='print';_readability_print_css.type='text/css';document.getElementsByTagName('head')[0].appendChild(_readability_print_css);})();" rel="nofollow">&#8220;readability&#8221;</a> or such. </p>
<p>I do not post this to bitch &#8211; I liked the rest of the post. I just happen to have courier&#8217;s back on this matter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Croak</title>
		<link>http://codeulate.com/2009/11/making-githubs-code-readable/comment-page-1/#comment-3416</link>
		<dc:creator>Dan Croak</dc:creator>
		<pubDate>Fri, 27 Nov 2009 18:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://codeulate.com/?p=46#comment-3416</guid>
		<description>Also, we started to write an iPhone Gorillas app as a goof: flick the touchscreen to send the banana through the air on a TV screen. The two players have their own iPhones used as controllers.</description>
		<content:encoded><![CDATA[<p>Also, we started to write an iPhone Gorillas app as a goof: flick the touchscreen to send the banana through the air on a TV screen. The two players have their own iPhones used as controllers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Croak</title>
		<link>http://codeulate.com/2009/11/making-githubs-code-readable/comment-page-1/#comment-3415</link>
		<dc:creator>Dan Croak</dc:creator>
		<pubDate>Fri, 27 Nov 2009 18:14:39 +0000</pubDate>
		<guid isPermaLink="false">http://codeulate.com/?p=46#comment-3415</guid>
		<description>&quot;If you&#039;re on Windows or OS X, you probably don’t either.&quot;

To all those &quot;blame Windows&quot; commenters, I believe the author is not on Windows. I&#039;ll take a wild guess and say Ubuntu.

I&#039;d second the Userstyle idea.

Github&#039;s code looks pretty good on my Mac OS X, I think because of their super-duper anti-aliasing?</description>
		<content:encoded><![CDATA[<p>&#8220;If you&#8217;re on Windows or OS X, you probably don’t either.&#8221;</p>
<p>To all those &#8220;blame Windows&#8221; commenters, I believe the author is not on Windows. I&#8217;ll take a wild guess and say Ubuntu.</p>
<p>I&#8217;d second the Userstyle idea.</p>
<p>Github&#8217;s code looks pretty good on my Mac OS X, I think because of their super-duper anti-aliasing?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans</title>
		<link>http://codeulate.com/2009/11/making-githubs-code-readable/comment-page-1/#comment-3396</link>
		<dc:creator>Hans</dc:creator>
		<pubDate>Mon, 02 Nov 2009 07:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://codeulate.com/?p=46#comment-3396</guid>
		<description>C&#039;mon, if you want your code to look good don&#039;t use Windows. But if you insist, your problem is font rendering so you colud try GDI++, take a look at this &lt;a href=&quot;http://vladg.com/2009/03/make-windows-fonts-look-as-smooth-as-mac-os-x-fonts/&quot; rel=&quot;nofollow&quot;&gt;http://vladg.com/2009/03/make-windows-fonts-look-as-smooth-as-mac-os-x-fonts/&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>C&#8217;mon, if you want your code to look good don&#8217;t use Windows. But if you insist, your problem is font rendering so you colud try GDI++, take a look at this <a href="http://vladg.com/2009/03/make-windows-fonts-look-as-smooth-as-mac-os-x-fonts/" rel="nofollow">http://vladg.com/2009/03/make-windows-fonts-look-as-smooth-as-mac-os-x-fonts/</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://codeulate.com/2009/11/making-githubs-code-readable/comment-page-1/#comment-3395</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Mon, 02 Nov 2009 03:57:02 +0000</pubDate>
		<guid isPermaLink="false">http://codeulate.com/?p=46#comment-3395</guid>
		<description>Fonts always look ugly on Windows. It looks fine on mac (Courier), and would look fine on Linux (Bitstream Vera is a pretty standard font). Font rendering is also better on those OSs</description>
		<content:encoded><![CDATA[<p>Fonts always look ugly on Windows. It looks fine on mac (Courier), and would look fine on Linux (Bitstream Vera is a pretty standard font). Font rendering is also better on those OSs</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gene t</title>
		<link>http://codeulate.com/2009/11/making-githubs-code-readable/comment-page-1/#comment-3393</link>
		<dc:creator>gene t</dc:creator>
		<pubDate>Sun, 01 Nov 2009 18:10:13 +0000</pubDate>
		<guid isPermaLink="false">http://codeulate.com/?p=46#comment-3393</guid>
		<description>I&#039;ve made suggestions, they respond pretty quickly, within an hour (i.e. , they don&#039;t implement your suggest in an hour, they indicate they&#039;ll work on it, ).  One was that they do some kind of primitive code folding based on line indentations;

http://github.com/contact</description>
		<content:encoded><![CDATA[<p>I&#8217;ve made suggestions, they respond pretty quickly, within an hour (i.e. , they don&#8217;t implement your suggest in an hour, they indicate they&#8217;ll work on it, ).  One was that they do some kind of primitive code folding based on line indentations;</p>
<p><a href="http://github.com/contact" rel="nofollow">http://github.com/contact</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivetti Underwood</title>
		<link>http://codeulate.com/2009/11/making-githubs-code-readable/comment-page-1/#comment-3392</link>
		<dc:creator>Olivetti Underwood</dc:creator>
		<pubDate>Sun, 01 Nov 2009 16:30:54 +0000</pubDate>
		<guid isPermaLink="false">http://codeulate.com/?p=46#comment-3392</guid>
		<description>Not to mention the general butt-ugliness of blogs in general. Wake up, web!! This is 2009, not 1985. People have high resolution screens and don&#039;t need to read &quot;light gray on white&quot; type in 4 point helvetica. Pretty much anything is more readable. Any more &quot;90% gray&quot; and I&#039;m going to program firefox to substitute fonts and colors mercilessly.</description>
		<content:encoded><![CDATA[<p>Not to mention the general butt-ugliness of blogs in general. Wake up, web!! This is 2009, not 1985. People have high resolution screens and don&#8217;t need to read &#8220;light gray on white&#8221; type in 4 point helvetica. Pretty much anything is more readable. Any more &#8220;90% gray&#8221; and I&#8217;m going to program firefox to substitute fonts and colors mercilessly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: masklinn</title>
		<link>http://codeulate.com/2009/11/making-githubs-code-readable/comment-page-1/#comment-3391</link>
		<dc:creator>masklinn</dc:creator>
		<pubDate>Sun, 01 Nov 2009 16:09:24 +0000</pubDate>
		<guid isPermaLink="false">http://codeulate.com/?p=46#comment-3391</guid>
		<description>FWIW in OSX, courier (the default monospace font for both Safari and Camino) &lt;a href=&quot;http://imgur.com/L62Sa&quot; rel=&quot;nofollow&quot;&gt;looks pretty good I think&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>FWIW in OSX, courier (the default monospace font for both Safari and Camino) <a href="http://imgur.com/L62Sa" rel="nofollow">looks pretty good I think</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mcrittenden</title>
		<link>http://codeulate.com/2009/11/making-githubs-code-readable/comment-page-1/#comment-3390</link>
		<dc:creator>mcrittenden</dc:creator>
		<pubDate>Sun, 01 Nov 2009 16:08:25 +0000</pubDate>
		<guid isPermaLink="false">http://codeulate.com/?p=46#comment-3390</guid>
		<description>Or just set up a userstyle to make it use whatever typeface you want it to.</description>
		<content:encoded><![CDATA[<p>Or just set up a userstyle to make it use whatever typeface you want it to.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dude</title>
		<link>http://codeulate.com/2009/11/making-githubs-code-readable/comment-page-1/#comment-3389</link>
		<dc:creator>dude</dc:creator>
		<pubDate>Sun, 01 Nov 2009 16:03:24 +0000</pubDate>
		<guid isPermaLink="false">http://codeulate.com/?p=46#comment-3389</guid>
		<description>First of all, you&#039;re a programmer and you don&#039;t have bitstream vera sans? Second, looks like you&#039;re on windows so you&#039;re used to having everything look like shit... Why would github cater to people with such low standards to begin with?</description>
		<content:encoded><![CDATA[<p>First of all, you&#8217;re a programmer and you don&#8217;t have bitstream vera sans? Second, looks like you&#8217;re on windows so you&#8217;re used to having everything look like shit&#8230; Why would github cater to people with such low standards to begin with?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
