<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Actually, this IS your father&#8217;s text editor</title>
	<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/</link>
	<description>on programming, usability, and design; by Patrick Dubroy</description>
	<pubDate>Mon, 05 Jan 2009 23:49:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Peter Crouch</title>
		<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-17707</link>
		<pubDate>Thu, 04 Sep 2008 20:46:17 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-17707</guid>
					<description>&lt;p&gt;Personally I prefer this plain and simple old school text editor:
http://home.online.no/~westerma/WestEdit/&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Personally I prefer this plain and simple old school text editor:<br />
http://home.online.no/~westerma/WestEdit/</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Patrick</title>
		<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-17105</link>
		<pubDate>Mon, 25 Aug 2008 23:24:44 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-17105</guid>
					<description>&lt;p&gt;@Danielle: Nope, haven't heard of Fortress before, but I'll check it out. Based on your description, sounds a bit like Knuth's literate programming.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Danielle: Nope, haven&#8217;t heard of Fortress before, but I&#8217;ll check it out. Based on your description, sounds a bit like Knuth&#8217;s literate programming.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Danielle Fong</title>
		<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-17104</link>
		<pubDate>Mon, 25 Aug 2008 22:55:58 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-17104</guid>
					<description>&lt;p&gt;Have you looked at Fortress? It has much more interesting typesetting; like coding in Latex, but... better.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Have you looked at Fortress? It has much more interesting typesetting; like coding in Latex, but&#8230; better.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Miller Peterson</title>
		<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-17033</link>
		<pubDate>Sun, 24 Aug 2008 20:41:51 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-17033</guid>
					<description>&lt;p&gt;I know what you mean about the home / end commands on macs. I used to use the home/end keys in the same way, but had to give it up since I switched to mac. Command-left / command-right are like home/end for macs, but it's not the same. &lt;/p&gt;

&lt;p&gt;Having recently started using Eclipse for Java development after being strictly plain text-editor, I'm still getting used to all the sweet features it has - just being able to navigate method declarations and rename variables automatically is blowing my mind.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I know what you mean about the home / end commands on macs. I used to use the home/end keys in the same way, but had to give it up since I switched to mac. Command-left / command-right are like home/end for macs, but it&#8217;s not the same. </p>
<p>Having recently started using Eclipse for Java development after being strictly plain text-editor, I&#8217;m still getting used to all the sweet features it has - just being able to navigate method declarations and rename variables automatically is blowing my mind.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Nate Hollingsworth</title>
		<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-15592</link>
		<pubDate>Sat, 02 Aug 2008 12:07:43 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-15592</guid>
					<description>&lt;p&gt;I use Visual Studio for my code (my work is all C#). Its really nice, but still lacks many features or the feature is there just very ackward to use (for example Go To Definition).&lt;/p&gt;

&lt;p&gt;I really like your idea of turning coding text editors into hypertext. When tracking down a bug or trying to figure out why the code is so stupid, I spend a lot of time following the code path.  Like you say it would be really nice to be able to see a visual code path somehow.&lt;/p&gt;

&lt;p&gt;I think we need to get away from thinking of code as lines in a file. In the OO world we deal with objects and methods (mostly). So, we should be working with those primitives directly.&lt;/p&gt;

&lt;p&gt;I completely agree that the coding environment really hasn't changed alot in the last 30 years.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I use Visual Studio for my code (my work is all C#). Its really nice, but still lacks many features or the feature is there just very ackward to use (for example Go To Definition).</p>
<p>I really like your idea of turning coding text editors into hypertext. When tracking down a bug or trying to figure out why the code is so stupid, I spend a lot of time following the code path.  Like you say it would be really nice to be able to see a visual code path somehow.</p>
<p>I think we need to get away from thinking of code as lines in a file. In the OO world we deal with objects and methods (mostly). So, we should be working with those primitives directly.</p>
<p>I completely agree that the coding environment really hasn&#8217;t changed alot in the last 30 years.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Patrick</title>
		<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-14044</link>
		<pubDate>Fri, 11 Jul 2008 13:06:07 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-14044</guid>
					<description>&lt;p&gt;@Boris: No, TextMate doesn't do smooth scrolling. You know, it's not something I've ever really thought about, but it would be a nice touch.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Boris: No, TextMate doesn&#8217;t do smooth scrolling. You know, it&#8217;s not something I&#8217;ve ever really thought about, but it would be a nice touch.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Boris Bokowski</title>
		<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-14039</link>
		<pubDate>Fri, 11 Jul 2008 09:17:17 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-14039</guid>
					<description>&lt;p&gt;I am still waiting for smooth scrolling in text editors, like it was implemented by Cygnus Ed (Amiga, ca. 1990), or nowadays on the iPhone. Both implementations are based on a model that make the sroll movement appear like that of physical objects, which is much easier on the eyes and brain compared to what all other text-displaying apps do.  (Does TextMate do smooth scrolling?)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I am still waiting for smooth scrolling in text editors, like it was implemented by Cygnus Ed (Amiga, ca. 1990), or nowadays on the iPhone. Both implementations are based on a model that make the sroll movement appear like that of physical objects, which is much easier on the eyes and brain compared to what all other text-displaying apps do.  (Does TextMate do smooth scrolling?)</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Patrick</title>
		<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-14007</link>
		<pubDate>Thu, 10 Jul 2008 17:29:10 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-14007</guid>
					<description>&lt;p&gt;@David Mathers: Really? Can you give me some details about the vim plugins that can do this kind of thing?&lt;/p&gt;

&lt;p&gt;@Jeremy Handcock: Interesting, I've never seen that kind of code visualization before, but not surprised that someone else has thought of it. I guess for profiling, the reason it's probably never caught on is that (a) most people never profile their code, and (b) finding the name of the top 5 or 10 hottest methods is usually good enough. Heat maps wouldn't be cool, but aren't necessarily that much more useful.&lt;/p&gt;

&lt;p&gt;On the other hand, I could imagine code path indicators in a debugger to be &lt;em&gt;really&lt;/em&gt; useful. Imagine you pull up your debugger to investigate a crash, and it shows the code path most recently taken through the method. Kind of a lightweight version of the rewindable debugger.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@David Mathers: Really? Can you give me some details about the vim plugins that can do this kind of thing?</p>
<p>@Jeremy Handcock: Interesting, I&#8217;ve never seen that kind of code visualization before, but not surprised that someone else has thought of it. I guess for profiling, the reason it&#8217;s probably never caught on is that (a) most people never profile their code, and (b) finding the name of the top 5 or 10 hottest methods is usually good enough. Heat maps wouldn&#8217;t be cool, but aren&#8217;t necessarily that much more useful.</p>
<p>On the other hand, I could imagine code path indicators in a debugger to be <em>really</em> useful. Imagine you pull up your debugger to investigate a crash, and it shows the code path most recently taken through the method. Kind of a lightweight version of the rewindable debugger.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jeremy Handcock</title>
		<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-13984</link>
		<pubDate>Thu, 10 Jul 2008 02:58:11 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-13984</guid>
					<description>&lt;p&gt;Great post, Patrick.  This seems like a ripe area of research opportunities!&lt;/p&gt;

&lt;p&gt;Me, I use Eclipse for Java and vi for everything else.  This is mostly because they are the standard tools and I've never bothered to see if anything better is out there.  Maybe I'll give TextMate a try.&lt;/p&gt;

&lt;p&gt;It's not quite yet dead, but code visualization (ie. heat maps for profiled code) has never really caught on in a big way.  I'm not sure why that is.&lt;/p&gt;

&lt;p&gt;Your thoughts on supporting exploratory programming in an editor are really interesting.  I'd like to see this in my editor for sure.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Great post, Patrick.  This seems like a ripe area of research opportunities!</p>
<p>Me, I use Eclipse for Java and vi for everything else.  This is mostly because they are the standard tools and I&#8217;ve never bothered to see if anything better is out there.  Maybe I&#8217;ll give TextMate a try.</p>
<p>It&#8217;s not quite yet dead, but code visualization (ie. heat maps for profiled code) has never really caught on in a big way.  I&#8217;m not sure why that is.</p>
<p>Your thoughts on supporting exploratory programming in an editor are really interesting.  I&#8217;d like to see this in my editor for sure.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: David Mathers</title>
		<link>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-13983</link>
		<pubDate>Thu, 10 Jul 2008 00:55:46 +0000</pubDate>
		<guid>http://dubroy.com/blog/2008/07/09/actually-this-is-your-fathers-text-editor/#comment-13983</guid>
					<description>&lt;p&gt;Vim can already do much/most of what you ask for. The barrier is that to enable those features you have to learn about vim configuration and plugins, which can be daunting. What vim really needs is an easy and convenient way to manage the functionality that is already available.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Vim can already do much/most of what you ask for. The barrier is that to enable those features you have to learn about vim configuration and plugins, which can be daunting. What vim really needs is an easy and convenient way to manage the functionality that is already available.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
