<?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: Is the 80 character line limit still relevant?</title>
	<atom:link href="http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/feed/" rel="self" type="application/rss+xml" />
	<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/</link>
	<description>The adventures of a young kiwi software developer in London</description>
	<lastBuildDate>Tue, 31 Jan 2012 19:56:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Bats</title>
		<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/comment-page-1/#comment-17130</link>
		<dc:creator>Bats</dc:creator>
		<pubDate>Fri, 24 Sep 2010 00:46:49 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=77#comment-17130</guid>
		<description>The 80 character limit is derived way back when they began punch cards ` 1890&#039;s. Based on the size of the current dollar bill, you could only get 80 characters across. Like most things it is a carry over that serves no further purpose, but carries on &quot; just because this is the way it has always been done. This was done right up to the  1970&#039;s, by IBM.
Bats....</description>
		<content:encoded><![CDATA[<p>The 80 character limit is derived way back when they began punch cards ` 1890&#8242;s. Based on the size of the current dollar bill, you could only get 80 characters across. Like most things it is a carry over that serves no further purpose, but carries on &#8221; just because this is the way it has always been done. This was done right up to the  1970&#8242;s, by IBM.<br />
Bats&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Toponce</title>
		<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/comment-page-1/#comment-4330</link>
		<dc:creator>Aaron Toponce</dc:creator>
		<pubDate>Fri, 08 May 2009 03:07:07 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=77#comment-4330</guid>
		<description>There isn&#039;t a hard fast rule that can be applied to all scenarios. The fact
of the matter is, you code the way you code; you write the way you write.
If you prefer 80, then great. If you prefer 120, great. If you prefer
unlimited, great. In terms of yourself, do what you want. In terms of
working with others, it&#039;s probably best to communicate a standard among
everyone, and stick with it. In terms of dealing with others online, it&#039;s
probably &quot;best practice&quot; to keep email wrapping at 72 characters, and code
at 80, just like you should bottom-post when replying to email threads, and
compose your email in plain text, not HTML. Netiquette is rarely taught,
and hardly understood.</description>
		<content:encoded><![CDATA[<p>There isn&#8217;t a hard fast rule that can be applied to all scenarios. The fact<br />
of the matter is, you code the way you code; you write the way you write.<br />
If you prefer 80, then great. If you prefer 120, great. If you prefer<br />
unlimited, great. In terms of yourself, do what you want. In terms of<br />
working with others, it&#8217;s probably best to communicate a standard among<br />
everyone, and stick with it. In terms of dealing with others online, it&#8217;s<br />
probably &#8220;best practice&#8221; to keep email wrapping at 72 characters, and code<br />
at 80, just like you should bottom-post when replying to email threads, and<br />
compose your email in plain text, not HTML. Netiquette is rarely taught,<br />
and hardly understood.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micah Elliott</title>
		<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/comment-page-1/#comment-94</link>
		<dc:creator>Micah Elliott</dc:creator>
		<pubDate>Fri, 13 Jun 2008 04:27:17 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=77#comment-94</guid>
		<description>80 characters is an important limit for many reasons.  Actually, I stick to 72 for most everything, including all coding in any language and in email (2 chars for each &gt;-reply).

 * Many debuggers add 8 chars with line numbers
 * Some printers expect 80 chars not exceeded
 * Formatting tools (lint, perltidy, etc) will generate warnings)
 * Most programmers you&#039;ll share code with will have their textwidth set to 72 or 80.  When they see your code extending to 120 chars they&#039;ll yell at you.
 * ESR says so

There are actually some more reasons that I can&#039;t name off the top of my head, but the most important factor beyond these historic limits is *vertical code density*.  Most lines will be much shorter than 80.  So if you keep all other lines within that (short), you will have better uniformity and compactness.  I.e., the greater the line-length variety, the lower the density.  Then with a good wide, high-res monitor you&#039;ll be staring at four terminals worth of code at a time.  500 lines on one of my screens.  Multiply that by nine virtual desktops (and add a second monitor), and you&#039;re looking at a lot of code!</description>
		<content:encoded><![CDATA[<p>80 characters is an important limit for many reasons.  Actually, I stick to 72 for most everything, including all coding in any language and in email (2 chars for each &gt;-reply).</p>
<p> * Many debuggers add 8 chars with line numbers<br />
 * Some printers expect 80 chars not exceeded<br />
 * Formatting tools (lint, perltidy, etc) will generate warnings)<br />
 * Most programmers you&#8217;ll share code with will have their textwidth set to 72 or 80.  When they see your code extending to 120 chars they&#8217;ll yell at you.<br />
 * ESR says so</p>
<p>There are actually some more reasons that I can&#8217;t name off the top of my head, but the most important factor beyond these historic limits is *vertical code density*.  Most lines will be much shorter than 80.  So if you keep all other lines within that (short), you will have better uniformity and compactness.  I.e., the greater the line-length variety, the lower the density.  Then with a good wide, high-res monitor you&#8217;ll be staring at four terminals worth of code at a time.  500 lines on one of my screens.  Multiply that by nine virtual desktops (and add a second monitor), and you&#8217;re looking at a lot of code!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Varaneckas</title>
		<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/comment-page-1/#comment-93</link>
		<dc:creator>Tomas Varaneckas</dc:creator>
		<pubDate>Thu, 12 Jun 2008 05:05:42 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=77#comment-93</guid>
		<description>I totally disagree that limit of 80 characters is no longer relevant. For example, if you are a Java developer and use tools like Eclipse along with laptop or not too big desktop display (1280px width), you won&#039;t get much more than 80 chars in code window because of additional panels (Project Navigator, Outline). Even if you have a huge 30&quot; Apple cinema display but you still work in a team where someone uses 13&quot; MacBook, it&#039;s disrespectful to have line length limits like 120 characters.</description>
		<content:encoded><![CDATA[<p>I totally disagree that limit of 80 characters is no longer relevant. For example, if you are a Java developer and use tools like Eclipse along with laptop or not too big desktop display (1280px width), you won&#8217;t get much more than 80 chars in code window because of additional panels (Project Navigator, Outline). Even if you have a huge 30&#8243; Apple cinema display but you still work in a team where someone uses 13&#8243; MacBook, it&#8217;s disrespectful to have line length limits like 120 characters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/comment-page-1/#comment-92</link>
		<dc:creator>James</dc:creator>
		<pubDate>Wed, 11 Jun 2008 22:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=77#comment-92</guid>
		<description>I&#039;ve seen java import statements that have exceeded 80 characters. I personally prefer something larger, so there isn&#039;t any strange wrapping.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen java import statements that have exceeded 80 characters. I personally prefer something larger, so there isn&#8217;t any strange wrapping.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/comment-page-1/#comment-91</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 11 Jun 2008 18:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=77#comment-91</guid>
		<description>...err, I mean &quot;teletype&quot;, not &quot;monitor&quot;.

What good would the teletype be if it couldn&#039;t print out any
of the world&#039;s existing code?

-Matt</description>
		<content:encoded><![CDATA[<p>&#8230;err, I mean &#8220;teletype&#8221;, not &#8220;monitor&#8221;.</p>
<p>What good would the teletype be if it couldn&#8217;t print out any<br />
of the world&#8217;s existing code?</p>
<p>-Matt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/comment-page-1/#comment-90</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 11 Jun 2008 18:11:32 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=77#comment-90</guid>
		<description>DClayton,

Of course they cared about displaying a transcribed punch card. 
What good would their fancy new &quot;monitor&quot; be if you couldn&#039;t display
any of the world&#039;s existing code on it?

As for divisible by 8 and 10, why do you think IBM chose that length
for the punch cards? (of course I&#039;m not at all sure what was the byte
size on the machines the punch cards were designed for.)</description>
		<content:encoded><![CDATA[<p>DClayton,</p>
<p>Of course they cared about displaying a transcribed punch card.<br />
What good would their fancy new &#8220;monitor&#8221; be if you couldn&#8217;t display<br />
any of the world&#8217;s existing code on it?</p>
<p>As for divisible by 8 and 10, why do you think IBM chose that length<br />
for the punch cards? (of course I&#8217;m not at all sure what was the byte<br />
size on the machines the punch cards were designed for.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: diegoeche</title>
		<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/comment-page-1/#comment-88</link>
		<dc:creator>diegoeche</dc:creator>
		<pubDate>Tue, 10 Jun 2008 06:25:39 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=77#comment-88</guid>
		<description>I usually work on a 85 char basis. In some strange situations I break the rule. For me is just a matter of aesthetics, but also is easier to put the breakpoints.

Also. when i use VS or emacs I really like a big font (15, 16) so the limit also increases the readability of the code.</description>
		<content:encoded><![CDATA[<p>I usually work on a 85 char basis. In some strange situations I break the rule. For me is just a matter of aesthetics, but also is easier to put the breakpoints.</p>
<p>Also. when i use VS or emacs I really like a big font (15, 16) so the limit also increases the readability of the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dclayton</title>
		<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/comment-page-1/#comment-87</link>
		<dc:creator>dclayton</dc:creator>
		<pubDate>Mon, 09 Jun 2008 22:55:03 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=77#comment-87</guid>
		<description>The 80 character line limit has nothing to do with punch cards.  They are just two instances of the number &quot;80&quot; that have nothing to do with each other.  Seriously, do you really believe that the inventors of the first TTY monitors cared at all about how a transcribed punch card would look on a monitor?  More likely, 80-wide was arrived at due to being evenly divisible by 8 (to facilitate memory mapped character displays) and 10 (to facilitate simple math lookups of the memory mapped display.)</description>
		<content:encoded><![CDATA[<p>The 80 character line limit has nothing to do with punch cards.  They are just two instances of the number &#8220;80&#8243; that have nothing to do with each other.  Seriously, do you really believe that the inventors of the first TTY monitors cared at all about how a transcribed punch card would look on a monitor?  More likely, 80-wide was arrived at due to being evenly divisible by 8 (to facilitate memory mapped character displays) and 10 (to facilitate simple math lookups of the memory mapped display.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Michaux</title>
		<link>http://richarddingwall.name/2008/05/31/is-the-80-character-line-limit-still-relevant/comment-page-1/#comment-84</link>
		<dc:creator>Peter Michaux</dc:creator>
		<pubDate>Mon, 09 Jun 2008 15:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://richarddingwall.name/?p=77#comment-84</guid>
		<description>For usenet posts it is best to use a 72 character limit as it may be wrapped after that. A 70 character limit ensures that at least one reply can be written without wrapping the code.</description>
		<content:encoded><![CDATA[<p>For usenet posts it is best to use a 72 character limit as it may be wrapped after that. A 70 character limit ensures that at least one reply can be written without wrapping the code.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

