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: Emacs in the Cloud Date: Sun, 24 Jul 2011 02:44:35 -0400 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=0015174c16f02368a804a8cb08e5 X-Trace: dough.gmane.org 1311489885 22526 80.91.229.12 (24 Jul 2011 06:44:45 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 24 Jul 2011 06:44:45 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 24 08:44:42 2011 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 1QksQb-0007kH-JV for ged-emacs-devel@m.gmane.org; Sun, 24 Jul 2011 08:44:41 +0200 Original-Received: from localhost ([::1]:59077 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QksQb-0004RV-1d for ged-emacs-devel@m.gmane.org; Sun, 24 Jul 2011 02:44:41 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:48332) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QksQY-0004RD-M9 for emacs-devel@gnu.org; Sun, 24 Jul 2011 02:44:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QksQX-0000Or-Fl for emacs-devel@gnu.org; Sun, 24 Jul 2011 02:44:38 -0400 Original-Received: from mail-ew0-f41.google.com ([209.85.215.41]:44091) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QksQX-0000Oj-4L for emacs-devel@gnu.org; Sun, 24 Jul 2011 02:44:37 -0400 Original-Received: by ewy9 with SMTP id 9so2538044ewy.0 for ; Sat, 23 Jul 2011 23:44:35 -0700 (PDT) Original-Received: by 10.213.16.83 with SMTP id n19mr1256981eba.66.1311489875208; Sat, 23 Jul 2011 23:44:35 -0700 (PDT) Original-Received: by 10.213.29.12 with HTTP; Sat, 23 Jul 2011 23:44:35 -0700 (PDT) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.215.41 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:142242 Archived-At: --0015174c16f02368a804a8cb08e5 Content-Type: text/plain; charset=ISO-8859-1 I recently tried out a ChromeBook for a month or so. The attraction was primarily the simplicity of the system. I love the idea of not having to deal directly with an underlying OS, not having to configure devices or drivers, not having to do backups, not worrying about losing files, or dealing with security, or having the hardware go belly up. While the experience was a mixed success (I returned the box since it was underpowered and led to very poor Chrome behavior: slow and lots of crashed tabs and extensions). But most of all, life without Emacs, even for just short periods, just plain sucks. But a sufficiently powerful machine could provide a ChromeBook experience and undoubtedly will as ChromeOS matures. But it will not be in Google's interest to provide a native Emacs experience which leads to the likelihood of a ChromeOS derivative, if only to have a clean Emacs integration, (possible but unlikely) or a Cloud based Emacs experience being developed. Before I go on, I think I basically understand Richard's (and others) strong anti-cloud stance: it is crazy to put sensitive data totally in the hands of giant corporations. But there is usefulness in having cloud based organizations provide infrastructure support (data preservation, replication for accessibility, simple security) for information that is not highly sensitive, like a music collection. And there is usefulness in providing access to sensitive data that is provided by Cloud based infrastructure that is under one's own control (a personal server for example) or with third party organizations that one does trust (FSF, FreeCDDB, etc.) So if you buy the premise that there are circumstances where a Cloud based machine makes sense, but you want to have an Emacs experience in that environment, where does that Emacs experience come from? A true Emacs extension/plugin for Chrome? An Emacs built with an embedded web server? A limited Emacs exposed by ChromeOS that supports the existing Emacs extensions? An Emacs protocol supported by an Apache module? My preference leans towards the embedded server and/or the Emacs protocol approaches. I have not been tracking this list for a few years so I don't know if any of this has been discussed already (a browse of the archives did not reveal anything "cloud" related.) And I figured that if there is any work going on of a related nature, this list would be aware of it and provide pointers/references. Thanks, -pmr --0015174c16f02368a804a8cb08e5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I recently tried out a ChromeBook for a month or so. =A0The attraction was = primarily the simplicity of the system. =A0I love the idea of not having to= deal directly with an underlying OS, not having to configure devices or dr= ivers, not having to do backups, not worrying about losing files, or dealin= g with security, or having the hardware go belly up. =A0While the experienc= e was a mixed success (I returned the box since it was underpowered and led= to very poor Chrome behavior: slow and lots of crashed tabs and extensions= ). =A0But most of all, life without Emacs, even for just short periods, jus= t plain sucks.

But a sufficiently powerful machine could provide a ChromeBo= ok experience and undoubtedly will as ChromeOS matures. =A0But it will not = be in Google's interest to provide a native Emacs experience which lead= s to the likelihood of a ChromeOS derivative, if only to have a clean Emacs= integration, (possible but unlikely) or a Cloud based Emacs experience bei= ng developed.

Before I go on, I think I basically understand Richard&= #39;s (and others) strong anti-cloud stance: it is crazy to put sensitive d= ata totally in the hands of giant corporations. But there is usefulness in = having cloud based organizations provide infrastructure support (data prese= rvation, replication for accessibility, simple security) for information th= at is not highly sensitive, like a music collection. =A0And there is useful= ness in providing access to sensitive data that is provided by Cloud based = infrastructure that is under one's own control (a personal server for e= xample) or with third party organizations that one does trust (FSF, FreeCDD= B, etc.)

So if you buy the premise that there are circumstances = where a Cloud based machine makes sense, but you want to have an Emacs expe= rience in that environment, where does that Emacs experience come from? =A0= A true Emacs extension/plugin for Chrome? =A0An Emacs built with an embedde= d web server? =A0A limited Emacs exposed by ChromeOS that supports the exis= ting Emacs extensions? An Emacs protocol supported by an Apache module?

My preference leans towards the embedded server and/or = the Emacs protocol approaches. =A0I have not been tracking this list for a = few years so I don't know if any of this has been discussed already (a = browse of the archives did not reveal anything "cloud" related.) = =A0And I figured that if there is any work going on of a related nature, th= is list would be aware of it and provide pointers/references.

Thanks,

-pmr

--0015174c16f02368a804a8cb08e5--