From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tom Newsgroups: gmane.emacs.devel Subject: Re: Emacs Lisp's future (was: Guile emacs thread (again)) Date: Wed, 17 Sep 2014 11:01:13 +0000 (UTC) Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1410951744 19343 80.91.229.3 (17 Sep 2014 11:02:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 17 Sep 2014 11:02:24 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 17 13:02:17 2014 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 1XUD03-0006bk-Lv for ged-emacs-devel@m.gmane.org; Wed, 17 Sep 2014 13:02:15 +0200 Original-Received: from localhost ([::1]:44019 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUD03-00012o-AH for ged-emacs-devel@m.gmane.org; Wed, 17 Sep 2014 07:02:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56167) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUCze-0000sv-Ip for emacs-devel@gnu.org; Wed, 17 Sep 2014 07:01:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XUCzX-0000d7-20 for emacs-devel@gnu.org; Wed, 17 Sep 2014 07:01:50 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:55579) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XUCzW-0000an-SK for emacs-devel@gnu.org; Wed, 17 Sep 2014 07:01:42 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XUCzM-0006My-37 for emacs-devel@gnu.org; Wed, 17 Sep 2014 13:01:32 +0200 Original-Received: from 94-21-223-246.pool.digikabel.hu ([94.21.223.246]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 17 Sep 2014 13:01:32 +0200 Original-Received: from adatgyujto by 94-21-223-246.pool.digikabel.hu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 17 Sep 2014 13:01:32 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 18 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 94.21.223.246 (Mozilla/5.0 (Windows NT 6.1; rv:32.0) Gecko/20100101 Firefox/32.0) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:174409 Archived-At: Lally Singh gmail.com> writes: > > So if this a runtime system issue, what about elisp on LLVM?  Let the LLVM project handle the backend and performance issues, and emacs can maintain one language frontend.  There are plenty of people working on that, so emacs can ride that for almost free. In the long run this would be the most practical solution. Choosing a well supported and widely used VM which gets tons of developer attention, so the VM development would be taken care of, and Elisp could be implemented as a frontend. This approach has the advantage of supporting the existing Elisp code base and it would also make it possible to use other languages to extend emacs, because widdely used VMs have frontend implementations for many modern languages (Python, etc.)