From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Spencer Boucher Newsgroups: gmane.emacs.devel Subject: Re: First draft of the Emacs website Date: Tue, 08 Dec 2015 10:21:25 -0500 Message-ID: References: <87io4lem98.fsf@petton.fr> <56604A9C.7080508@gmail.com> <20151208130529.GA28682@HAL9000> <1c367763-4ba1-4c65-80d1-be1b365c3b35@default> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=-=-=" X-Trace: ger.gmane.org 1449590461 10288 80.91.229.3 (8 Dec 2015 16:01:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 8 Dec 2015 16:01:01 +0000 (UTC) Cc: Valentijn , John Yates , Emacs developers To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 08 17:00:55 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1a6KhC-0002Gi-Pe for ged-emacs-devel@m.gmane.org; Tue, 08 Dec 2015 17:00:55 +0100 Original-Received: from localhost ([::1]:60494 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a6KhC-0002gS-7K for ged-emacs-devel@m.gmane.org; Tue, 08 Dec 2015 11:00:54 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42015) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a6K57-0000AE-Kx for emacs-devel@gnu.org; Tue, 08 Dec 2015 10:21:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a6K54-0001oO-DF for emacs-devel@gnu.org; Tue, 08 Dec 2015 10:21:33 -0500 Original-Received: from smtp.developermail.io ([88.198.18.23]:49912) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a6K54-0001oA-0e for emacs-devel@gnu.org; Tue, 08 Dec 2015 10:21:30 -0500 Original-Received: by smtp.developermail.io Authentication-Results: smtp.developermail.io; dmarc=none header.from=spencerboucher.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spencerboucher.com; s=2015; t=1449588088; bh=TRd20DqfST/vCX7i0CUSh58auEL46MtsS8iWOXjMB+M=; h=References:From:To:Cc:Subject:In-reply-to:Date:From; b=Fg36weS9qEoCngDD4eClHVop0fDU+w68Rj1VFIzH1nsJDbTmkLC8+OqmQYhaH5rVe aXxX+vny+qZipAfLCDi2dgWkzAyHyEm607981j7Q8dPpcGUJC+9neMxR0/wxe/qWPV hUQS2yhimiLxCN/TIHbw8K8IQuLTZh/AkLNwDNa0= In-reply-to: <1c367763-4ba1-4c65-80d1-be1b365c3b35@default> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 88.198.18.23 X-Mailman-Approved-At: Tue, 08 Dec 2015 11:00:29 -0500 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:195980 Archived-At: --=-=-= Content-Type: text/plain --=-=-= Content-Type: multipart/alternative; boundary="==-=-=" --==-=-= Content-Type: text/plain; format=flowed > At the end of the day, we do need to refer to the language by its > name, I think, but we could stress that it is a "Python-like" > language, to connect with what people might be more familiar with. Calling elisp "python-like" might be a bit of a stretch :) > Concentrate on its features rather than its name: Why someone > should want to know that it is part of Emacs, even at the outset. > What it brings to Emacs and its users. Exactly. The fact that elisp is not Python is a GOOD thing. Even though I love Python and use it in my work (it was also my first real programming language), I wouldn't WANT it to be the language behind my editor. We should emphasize the things about lisp that make it the best choice for powering an editor (macros, homoiconicity, etc.). --==-=-= Content-Type: multipart/related; boundary="===-=-=" --===-=-= Content-Type: text/html

> At the end of the day, we do need to refer to the language by its
> name, I think, but we could stress that it is a "Python-like"
> language, to connect with what people might be more familiar with.

Calling elisp "python-like" might be a bit of a stretch :)

> Concentrate on its features rather than its name: Why someone
> should want to know that it is part of Emacs, even at the outset.
> What it brings to Emacs and its users.

Exactly. The fact that elisp is not Python is a GOOD thing. Even though I love Python and use it in my work (it was also my first real programming language), I wouldn't WANT it to be the language behind my editor. We should emphasize the things about lisp that make it the best choice for powering an editor (macros, homoiconicity, etc.).

--===-=-=-- --==-=-=-- --=-=-= Content-Type: multipart/related; boundary="====-=-=" --====-=-= Content-Type: text/html

<#multipart type=alternative><#part type=text/plain>

> At the end of the day, we do need to refer to the language by its
> name, I think, but we could stress that it is a "Python-like"
> language, to connect with what people might be more familiar with.

Calling elisp "python-like" might be a bit of a stretch :)

> Concentrate on its features rather than its name: Why someone
> should want to know that it is part of Emacs, even at the outset.
> What it brings to Emacs and its users.

Exactly. The fact that elisp is not Python is a GOOD thing. Even though I love Python and use it in my work (it was also my first real programming language), I wouldn't WANT it to be the language behind my editor. We should emphasize the things about lisp that make it the best choice for powering an editor (macros, homoiconicity, etc.).
<#multipart type=related><#part type=text/html><p>
&gt; At the end of the day, we do need to refer to the language by its<br />
&gt; name, I think, but we could stress that it is a "Python-like"<br />
&gt; language, to connect with what people might be more familiar with.<br />
</p>

<p>
Calling elisp "python-like" might be a bit of a stretch :)<br />
</p>

<p>
&gt; Concentrate on its features rather than its name: Why someone<br />
&gt; should want to know that it is part of Emacs, even at the outset.<br />
&gt; What it brings to Emacs and its users.<br />
</p>

<p>
Exactly. The fact that elisp is not Python is a GOOD thing. Even though I love Python and use it in my work (it was also my first real programming language), I wouldn't WANT it to be the language behind my editor. We should emphasize the things about lisp that make it the best choice for powering an editor (macros, homoiconicity, etc.).<br />
</p>
<#/multipart>
<#/multipart>

--====-=-=-- --=-=-=--