unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Subject: Re: Emacs in the Cloud
Date: Sun, 24 Jul 2011 09:07:56 +0200	[thread overview]
Message-ID: <4E2BC4CC.1000209@online.de> (raw)
In-Reply-To: <CAGwjgEgtwBAmrdvuG7oinWSruRk3hhNWdyAmb5DcFp8c4TG7gg@mail.gmail.com>

Am 24.07.2011 08:44, schrieb Paul Michael Reilly:
> 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
>

Hi,

would support extending interest from pure code onto computers reality,
ie aggregating data and conclude from it.

If we want stay free, resp. become free, we can't permit establishing 
knowledge in the hands of some multis only:

what about "Sharing the benefits of free services" as a goal?

As for Emacs themselfes

"simplicity of the system" seems a focus worth attention.

Andreas

--
https://launchpad.net/python-mode
https://launchpad.net/s-x-emacs-werkstatt/





  reply	other threads:[~2011-07-24  7:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-24  6:44 Emacs in the Cloud Paul Michael Reilly
2011-07-24  7:07 ` Andreas Röhler [this message]
2011-07-24 22:17 ` Richard Stallman
2011-07-25 12:51   ` Dimitri Fontaine
2011-07-25 13:06     ` Julien Danjou
2011-07-25 13:52       ` joakim
2011-07-25 14:09         ` Julien Danjou
2011-07-25 15:02           ` James Cloos
2011-07-25 18:02           ` Richard Stallman
2011-07-25 22:31           ` Bill Wohler
2011-07-26  6:07             ` Ken Raeburn
2011-07-26  6:11             ` David Engster
2011-07-26  8:52               ` Dimitri Fontaine
2011-07-26  9:11                 ` Dimitri Fontaine
2011-07-26  9:09               ` joakim
2011-07-26  7:21             ` Michael Albinus
2011-08-27 19:16               ` Bill Wohler
2011-08-28 12:44                 ` Piet van Oostrum
2011-07-29 22:59           ` Andrew W. Nosenko
2011-07-30 16:41             ` Julien Danjou
2011-07-30 18:09               ` Andrew W. Nosenko
2011-07-31  2:38             ` Tim Cross
2011-07-25 17:29         ` Dimitri Fontaine
2011-07-25 21:33           ` joakim
2011-07-25 14:26     ` Masatake YAMATO
2011-07-25 15:15       ` Paul Michael Reilly
2011-07-25 18:02     ` Richard Stallman
2011-07-25 19:39       ` Dimitri Fontaine
2011-07-25 22:38       ` Klotz, Leigh
2011-07-28  5:54         ` Richard Stallman
2011-07-25  1:49 ` Tim Cross
2011-07-25 18:01   ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E2BC4CC.1000209@online.de \
    --to=andreas.roehler@online.de \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).