<?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: version control: writers vs programmers</title>
	<atom:link href="http://nonstandarddeviation.com/2006/07/25/version-control-writers-vs-programmers/feed/" rel="self" type="application/rss+xml" />
	<link>http://nonstandarddeviation.com/2006/07/25/version-control-writers-vs-programmers/</link>
	<description>they distracted us, so now we're distracting you</description>
	<lastBuildDate>Thu, 22 Oct 2009 12:51:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andy Dent</title>
		<link>http://nonstandarddeviation.com/2006/07/25/version-control-writers-vs-programmers/#comment-76</link>
		<dc:creator>Andy Dent</dc:creator>
		<pubDate>Wed, 24 Jan 2007 20:46:23 +0000</pubDate>
		<guid isPermaLink="false">http://nonstandarddeviation.com/2006/07/25/version-control-writers-vs-programmers/#comment-76</guid>
		<description>&lt;p&gt;I found the GroupEdit proposal very interesting, particularly as I work in a scientific organisation with colleagues who are involved in international standards refinement (XML-schemas such as GML and GeoSciML).&lt;/p&gt;

&lt;p&gt;Beyond a certain level of complexity, Word&#039;s change tracking and markup becomes unwieldy, as well as the instability you mention. I have my own horror memory of being stupid enough to try pasting about 20 Visio diagrams into an architecture document in Word.&lt;/p&gt;

&lt;p&gt;I&#039;m not convinced about your argument that the natural object of interest is different for writers and programmers and I don&#039;t actually believe that the line-orientation of Subversion is particularly good. We have gone a long way backwards compared to the method-oriented editors of Smalltalk and the classic ObjectMaster environment for C++ et al, about which I blogged nostalgically last year.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.artima.com/forums/flat.jsp?forum=106&amp;thread=158259&quot; rel=&quot;nofollow&quot;&gt;http://www.artima.com/forums/flat.jsp?forum=106&amp;thread=158259&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I think that there is a larger &quot;text chunk&quot; which seems relevant to the GroupEdit discussion and would be analogous to methods in an OO language. If anything, the GroupEdit proposal highlights how silly it is that most of our tools are still line-oriented.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I found the GroupEdit proposal very interesting, particularly as I work in a scientific organisation with colleagues who are involved in international standards refinement (XML-schemas such as GML and GeoSciML).</p>

<p>Beyond a certain level of complexity, Word&#8217;s change tracking and markup becomes unwieldy, as well as the instability you mention. I have my own horror memory of being stupid enough to try pasting about 20 Visio diagrams into an architecture document in Word.</p>

<p>I&#8217;m not convinced about your argument that the natural object of interest is different for writers and programmers and I don&#8217;t actually believe that the line-orientation of Subversion is particularly good. We have gone a long way backwards compared to the method-oriented editors of Smalltalk and the classic ObjectMaster environment for C++ et al, about which I blogged nostalgically last year.</p>

<p><a href="http://www.artima.com/forums/flat.jsp?forum=106&#038;thread=158259" rel="nofollow">http://www.artima.com/forums/flat.jsp?forum=106&#038;thread=158259</a></p>

<p>I think that there is a larger &#8220;text chunk&#8221; which seems relevant to the GroupEdit discussion and would be analogous to methods in an OO language. If anything, the GroupEdit proposal highlights how silly it is that most of our tools are still line-oriented.</p>]]></content:encoded>
	</item>
</channel>
</rss>
