<?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: Emacs.NET?</title>
	<atom:link href="http://pthree.org/2008/01/01/emacsnet/feed/" rel="self" type="application/rss+xml" />
	<link>http://pthree.org/2008/01/01/emacsnet/</link>
	<description>Linux.  GNU.  Freedom.</description>
	<pubDate>Sat, 30 Aug 2008 05:27:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-hemorrhage</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John M. Anderson</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87812</link>
		<dc:creator>John M. Anderson</dc:creator>
		<pubDate>Thu, 03 Jan 2008 21:47:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87812</guid>
		<description>There is a good post on regonline about this too: 
http://www.regdeveloper.co.uk/2008/01/03/emacs_dot_net/</description>
		<content:encoded><![CDATA[<p>There is a good post on regonline about this too:<br />
<a href="http://www.regdeveloper.co.uk/2008/01/03/emacs_dot_net/" rel="nofollow">http://www.regdeveloper.co.uk/2008/01/03/emacs_dot_net/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87762</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Thu, 03 Jan 2008 03:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87762</guid>
		<description>@levi- Now I understand.  I never realized Emacs was such a bloated program.  No wonder I like Vim.  It's a text-editor only, and does its job well.</description>
		<content:encoded><![CDATA[<p>@levi- Now I understand.  I never realized Emacs was such a bloated program.  No wonder I like Vim.  It&#8217;s a text-editor only, and does its job well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadim P.</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87751</link>
		<dc:creator>Vadim P.</dc:creator>
		<pubDate>Thu, 03 Jan 2008 01:08:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87751</guid>
		<description>They'll patent it, and add 1 to their list of patents!

(see sudo)</description>
		<content:encoded><![CDATA[<p>They&#8217;ll patent it, and add 1 to their list of patents!</p>
<p>(see sudo)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87741</link>
		<dc:creator>Phil</dc:creator>
		<pubDate>Wed, 02 Jan 2008 20:07:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87741</guid>
		<description>I'm with Levi here; it makes no sense for them to build off the GNU Emacs codebase. If you look back at the history, the word Emacs does not even describe a single program. It started as a set of TECO macros, and then it was implemented in MockLisp. Not until GNU Emacs was written (1985?) was it even implemented in what we now know as elisp.

It's pretty clear whatever they are building will follow the framework of Emacs in which you have a core functionality based around a certain task (editing) and a language that allows extensions to work seamlessly. Similarly Mozilla could be called the Emacs of web browsing since it provides a core (Gecko rendering and the XUL toolkit) and a language that allows it to be extended in ways that are very different from the original Mozilla. (See Songbird, for example.)

Of course, Elisp is really the most interesting part of GNU Emacs, and while it's a bit backwards compared to Common Lisp or Scheme, it's miles ahead of C#, which is probably what this will be based on. So I expect this to be a step in the right direction for them, but ultimately of little interest to anyone who's not OS-challenged.</description>
		<content:encoded><![CDATA[<p>I&#8217;m with Levi here; it makes no sense for them to build off the GNU Emacs codebase. If you look back at the history, the word Emacs does not even describe a single program. It started as a set of TECO macros, and then it was implemented in MockLisp. Not until GNU Emacs was written (1985?) was it even implemented in what we now know as elisp.</p>
<p>It&#8217;s pretty clear whatever they are building will follow the framework of Emacs in which you have a core functionality based around a certain task (editing) and a language that allows extensions to work seamlessly. Similarly Mozilla could be called the Emacs of web browsing since it provides a core (Gecko rendering and the XUL toolkit) and a language that allows it to be extended in ways that are very different from the original Mozilla. (See Songbird, for example.)</p>
<p>Of course, Elisp is really the most interesting part of GNU Emacs, and while it&#8217;s a bit backwards compared to Common Lisp or Scheme, it&#8217;s miles ahead of C#, which is probably what this will be based on. So I expect this to be a step in the right direction for them, but ultimately of little interest to anyone who&#8217;s not OS-challenged.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Microsoft after &#8220;Emacs&#8221; &#8212; Emacs.NET &#171; Venkatesh&#8217;s scribblings</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87739</link>
		<dc:creator>Microsoft after &#8220;Emacs&#8221; &#8212; Emacs.NET &#171; Venkatesh&#8217;s scribblings</dc:creator>
		<pubDate>Wed, 02 Jan 2008 18:15:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87739</guid>
		<description>[...] January 2, 2008 &#183; No Comments  As seen here, and the links that are referred to, Microsoft is apparently after the One True Program &#8212; [...]</description>
		<content:encoded><![CDATA[<p>[...] January 2, 2008 &middot; No Comments  As seen here, and the links that are referred to, Microsoft is apparently after the One True Program &#8212; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Levi</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87734</link>
		<dc:creator>Levi</dc:creator>
		<pubDate>Wed, 02 Jan 2008 17:05:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87734</guid>
		<description>Of course they're NOT going to use the emacs codebase.  

For one, it's a GPL codebase.  This reason should be self-explanatory.

For another, it's mostly in elisp, the primary virtue of which is that emacs is written in it.  It's a rather backwards lisp dialect that I don't think anyone would choose to use if there wasn't so much code already written for emacs in it.  Microsoft has exactly NO reason to start using elisp.

Finally, emacs is a rather unique KIND of program.  While vi's codebase (as an example) very explicitly describes a certain kind of editor, emacs is basically a programming runtime environment with a bunch of editor primitives built-in, and a bunch of supporting elisp code that defines the sort of editor that emacs is, as well as a zillion other things.

So, Microsoft already has a language runtime that they're supporting, and trying to push further.  Their goal is to create an emacs-like system, by which they mean a minimal set of editing/GUI primitives that will support the creation of an emacs-like editor on top of it.  Presumably they'll use a saner language than elisp, and have it tie into other Microsoft technologies that they're pushing.

The result will be 100% incompatible with the emacs codebase, but will be emacs-like in spirit.  Thus, it may roughly be described as 'emacs.net'.</description>
		<content:encoded><![CDATA[<p>Of course they&#8217;re NOT going to use the emacs codebase.  </p>
<p>For one, it&#8217;s a GPL codebase.  This reason should be self-explanatory.</p>
<p>For another, it&#8217;s mostly in elisp, the primary virtue of which is that emacs is written in it.  It&#8217;s a rather backwards lisp dialect that I don&#8217;t think anyone would choose to use if there wasn&#8217;t so much code already written for emacs in it.  Microsoft has exactly NO reason to start using elisp.</p>
<p>Finally, emacs is a rather unique KIND of program.  While vi&#8217;s codebase (as an example) very explicitly describes a certain kind of editor, emacs is basically a programming runtime environment with a bunch of editor primitives built-in, and a bunch of supporting elisp code that defines the sort of editor that emacs is, as well as a zillion other things.</p>
<p>So, Microsoft already has a language runtime that they&#8217;re supporting, and trying to push further.  Their goal is to create an emacs-like system, by which they mean a minimal set of editing/GUI primitives that will support the creation of an emacs-like editor on top of it.  Presumably they&#8217;ll use a saner language than elisp, and have it tie into other Microsoft technologies that they&#8217;re pushing.</p>
<p>The result will be 100% incompatible with the emacs codebase, but will be emacs-like in spirit.  Thus, it may roughly be described as &#8216;emacs.net&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87708</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Wed, 02 Jan 2008 11:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87708</guid>
		<description>Well of course they'll be using the emacs codebase.  Why would we "describe" a a project "Emacs.NET" if it were not using the Emacs codebase or libraries?  That makes no sense to me.  What else would they be using?  The Firefox libraries?  I fail to see how they would "describe" a project after Emacs if they weren't using it.  The only thing I see called into question is the final product.  And of course it's already been ported to Windows.  I don't think the goal of the project is to re-port it, but to build on top of it, making some superior tool.</description>
		<content:encoded><![CDATA[<p>Well of course they&#8217;ll be using the emacs codebase.  Why would we &#8220;describe&#8221; a a project &#8220;Emacs.NET&#8221; if it were not using the Emacs codebase or libraries?  That makes no sense to me.  What else would they be using?  The Firefox libraries?  I fail to see how they would &#8220;describe&#8221; a project after Emacs if they weren&#8217;t using it.  The only thing I see called into question is the final product.  And of course it&#8217;s already been ported to Windows.  I don&#8217;t think the goal of the project is to re-port it, but to build on top of it, making some superior tool.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sontek</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87687</link>
		<dc:creator>sontek</dc:creator>
		<pubDate>Wed, 02 Jan 2008 05:56:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87687</guid>
		<description>Emacs.NET is not the name, it was the description. 

quote from his blog: "We are looking for developers/testers to build a tool that I will roughly describe as "Emacs.Net"."</description>
		<content:encoded><![CDATA[<p>Emacs.NET is not the name, it was the description. </p>
<p>quote from his blog: &#8220;We are looking for developers/testers to build a tool that I will roughly describe as &#8220;Emacs.Net&#8221;.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Levi</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87686</link>
		<dc:creator>Levi</dc:creator>
		<pubDate>Wed, 02 Jan 2008 05:03:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87686</guid>
		<description>I still fail to understand why you believe that there will be any code borrowed from emacs.  If you look at Doug Purdy's blog, he doesn't say the project is named Emacs.Net, he says that he could "roughly describe" it as Emacs.Net.

Emacs already exists on Windows.  There would be no point in redoing it.  They're going to create something that is analogous to emacs, but not the same.</description>
		<content:encoded><![CDATA[<p>I still fail to understand why you believe that there will be any code borrowed from emacs.  If you look at Doug Purdy&#8217;s blog, he doesn&#8217;t say the project is named Emacs.Net, he says that he could &#8220;roughly describe&#8221; it as Emacs.Net.</p>
<p>Emacs already exists on Windows.  There would be no point in redoing it.  They&#8217;re going to create something that is analogous to emacs, but not the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87675</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Wed, 02 Jan 2008 02:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87675</guid>
		<description>@Levi- Of course none of the speculation mentions any of that.  The point being, they're going to use the Emacs codebase one way or another, and as they do best, do what's best for them.  I would hope that due to the nature of open source software, especially the code they'll be using, they would help the project.  But that's going against history, isn't it?

@sontek-  "They haven't said they are going to base anything off of emacs."  Then why the "Emacs.NET" name?  Surely they are, we just don't know what the final product is going to be, be it a text editor, IDE, platform or new language.</description>
		<content:encoded><![CDATA[<p>@Levi- Of course none of the speculation mentions any of that.  The point being, they&#8217;re going to use the Emacs codebase one way or another, and as they do best, do what&#8217;s best for them.  I would hope that due to the nature of open source software, especially the code they&#8217;ll be using, they would help the project.  But that&#8217;s going against history, isn&#8217;t it?</p>
<p>@sontek-  &#8220;They haven&#8217;t said they are going to base anything off of emacs.&#8221;  Then why the &#8220;Emacs.NET&#8221; name?  Surely they are, we just don&#8217;t know what the final product is going to be, be it a text editor, IDE, platform or new language.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sontek</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87642</link>
		<dc:creator>sontek</dc:creator>
		<pubDate>Tue, 01 Jan 2008 20:45:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87642</guid>
		<description>They haven't said they are going to base anything off of emacs. They are basically going to make an editor that hardcore hackers would like (those who are against using Visual Studio). Thats what I got from it anyways, but its all speculation until they announce something more concrete.</description>
		<content:encoded><![CDATA[<p>They haven&#8217;t said they are going to base anything off of emacs. They are basically going to make an editor that hardcore hackers would like (those who are against using Visual Studio). Thats what I got from it anyways, but its all speculation until they announce something more concrete.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Levi</title>
		<link>http://pthree.org/2008/01/01/emacsnet/#comment-87623</link>
		<dc:creator>Levi</dc:creator>
		<pubDate>Tue, 01 Jan 2008 18:05:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.pthree.org/2008/01/01/emacsnet/#comment-87623</guid>
		<description>What in the world makes you think that they're going to actually build on emacs anything that could be 'contributed back'?  None of the speculation at either of the blogs you linked to even goes that far.

My guess is that it will be a vaguely emacs-like sort of programmable editor framework, probably using some language that already exists in .net.</description>
		<content:encoded><![CDATA[<p>What in the world makes you think that they&#8217;re going to actually build on emacs anything that could be &#8216;contributed back&#8217;?  None of the speculation at either of the blogs you linked to even goes that far.</p>
<p>My guess is that it will be a vaguely emacs-like sort of programmable editor framework, probably using some language that already exists in .net.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
