From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Michael Reilly Newsgroups: gmane.emacs.devel Subject: Re: Emacs in a Chrome Tab? (related to NaCl Support for Emacs discussion) Date: Mon, 9 Jan 2012 16:56:49 -0500 Message-ID: References: <87boqc1t51.fsf@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=e89a8f83a931b9384804b61f7911 X-Trace: dough.gmane.org 1326146218 20301 80.91.229.12 (9 Jan 2012 21:56:58 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 9 Jan 2012 21:56:58 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 09 22:56:55 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RkND4-0005ZY-NP for ged-emacs-devel@m.gmane.org; Mon, 09 Jan 2012 22:56:54 +0100 Original-Received: from localhost ([::1]:58835 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkND4-0004Gy-9Y for ged-emacs-devel@m.gmane.org; Mon, 09 Jan 2012 16:56:54 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:43874) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkND1-0004GV-Ls for emacs-devel@gnu.org; Mon, 09 Jan 2012 16:56:52 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RkND0-0002sR-9p for emacs-devel@gnu.org; Mon, 09 Jan 2012 16:56:51 -0500 Original-Received: from mail-tul01m020-f169.google.com ([209.85.214.169]:47375) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RkND0-0002sB-4N for emacs-devel@gnu.org; Mon, 09 Jan 2012 16:56:50 -0500 Original-Received: by obcwo8 with SMTP id wo8so5583182obc.0 for ; Mon, 09 Jan 2012 13:56:49 -0800 (PST) Original-Received: by 10.182.162.70 with SMTP id xy6mr16578843obb.53.1326146209265; Mon, 09 Jan 2012 13:56:49 -0800 (PST) Original-Received: by 10.182.147.37 with HTTP; Mon, 9 Jan 2012 13:56:49 -0800 (PST) In-Reply-To: <87boqc1t51.fsf@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.214.169 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:147530 Archived-At: --e89a8f83a931b9384804b61f7911 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Jan 9, 2012 at 4:08 PM, Antoine Levitt wrote: Isn't that an issue to be tackled by the window managers? Why would it > be emacs-specific? I'm not sure I see the point anyway. > Window Managers? Maybe you missed my point. A little history: for years engineers from coast to coast (me on the East and Steve Yegge on the West) have primarily used two tools every day: Emacs and (some) Browser (Chrome for Steve and I). Steve once asked the pointed question: Wouldn't it be great if Emacs could browse (taking for granted that Emacs w3 doesn't count as a real browser) or a Browser could do what Emacs does? I answered the question with a definite Yes and posited that Emacs will never provide a real WWW browsing experience, at least not in our lifetime and not in Gnu Emacs' current implementation. So clearly that leaves Emacs to run inside the Browser. But this was clearly not a priority with the Brpwser developers so the two wonderful tools have lived apart lo these many years. With the advent of NativeClient, there is now a more likely path to realizing Emacs functionality inside a browser tab but that path could be filled with all kinds of roadside bombs that will make it impossible to get there from here. To me this means targeting Gnu Emacs to build on a "NativeClient" platform and thus producing a set of bits that will be found in an App Store like the Chrome Web Store. Another relevant piece of history: I tried using a ChromeBook device last year. Other than the fact that they were under powered and I could not run Emacs on them, it is a great model --- no machine maintenance, cheap, easy access to apps (lots of freely available software) and a very simple interface. Emacs in a tab would make a ChromeBook much more attractive. And Emacs in a tab would be able to leverage browser APIs to a much higher degree than we see in Emacs out of a tab. Now it might be the case that you don't see the point in a ChromeBook device or Chrome OS software model. If so you can take comfort in the fact that that probably puts you in a 90% category. But then, on the other hand, didn't IE own 90% of the browser market a short while ago? :-) -pmr --e89a8f83a931b9384804b61f7911 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Mon, Jan 9, 2012 at 4:08 PM, Antoine Levitt <= span dir=3D"ltr"><antoine.le= vitt@gmail.com> wrote:

Isn't that an issue to be tackled by the window managers? Why would it<= br> be emacs-specific? I'm not sure I see the point anyway.

Window Managers? =A0Maybe you missed my point.

A little history: for years engineers from coast to coast= (me on the East and Steve Yegge on the West) have primarily used two tools= every day: Emacs and (some) Browser (Chrome for Steve and I). =A0Steve onc= e asked the pointed question: Wouldn't it be great if Emacs could brows= e (taking for granted that Emacs w3 doesn't count as a real browser) or= a Browser could do what Emacs does? =A0I answered the question with a defi= nite Yes and posited that Emacs will never provide a real WWW browsing expe= rience, at least not in our lifetime and not in Gnu Emacs' current impl= ementation. =A0So clearly that leaves Emacs to run inside the Browser. =A0B= ut this was clearly not a priority with the Brpwser developers so the two w= onderful tools have lived apart lo these many years. =A0With the advent of = NativeClient, there is now a more likely path to realizing Emacs functional= ity inside a browser tab but that path could be filled with all kinds of ro= adside bombs that will make it impossible to get there from here. =A0To me = this means targeting Gnu Emacs to build on a "NativeClient" platf= orm and thus producing a set of bits that will be found in an App Store lik= e the Chrome Web Store.

Another relevant piece of history: =A0I tried using a C= hromeBook device last year. =A0Other than the fact that they were under pow= ered and I could not run Emacs on them, it is a great model --- no machine = maintenance, cheap, easy access to apps (lots of freely available software)= and a very simple interface. =A0Emacs in a tab would make a ChromeBook muc= h more attractive. =A0And Emacs in a tab would be able to leverage browser = APIs to a much higher degree than we see in Emacs out of a tab. =A0Now it m= ight be the case that you don't see the point in a ChromeBook device or= Chrome OS software model. =A0If so you can take comfort in the fact that t= hat probably puts you in a 90% category. =A0But then, on the other hand, di= dn't IE own 90% of the browser market a short while ago? :-)

-pmr

--e89a8f83a931b9384804b61f7911--