From: "James K. Lowden" <jklowden@speakeasy.net>
To: help-gnu-emacs@gnu.org
Subject: Re: A femtolisp based emacs clone
Date: Tue, 23 Aug 2016 23:52:49 -0400 [thread overview]
Message-ID: <20160823235249.b49733686b125af962883642@speakeasy.net> (raw)
In-Reply-To: ec83b5cd-e586-4de8-804b-07e8d120c7b5@googlegroups.com
On Mon, 22 Aug 2016 14:32:35 -0700 (PDT)
edu500ac@gmail.com wrote:
> In many situations, I need a small editor for a mobile computer or
> for a cloud computer. It would be great if I had emacs in such a
> situations, but emacs is large big and difficult to install for this
> kind of applications.
To your point, my biggest disappointment with emacs is its
client-server model. We have tramp. We have remote-X. For
high-latency connections, though, I always revert to terminal emuiation.
For some reason, it's the most responsive. Hurrah for 1982.
What we don't have is something like HTTP (or RDP), where the UI agent
is local and the "editing" is executed on the remote, minimizing the
communication between the two. It's funny to think that the interaction
between the GUI and the daemon should need high bandwidth, given that
the data rate is limited by the ability of the human to type and read.
Why should transmitting a page to the GUI be more expensive than
transmitting a page to an xterm?
Imagine if "emacs --daemon" opened a TCP port instead of a unix domain
socket. You start emacsclient on whatever gadget you have. Maybe
it's a Windows box; maybe it's an iPad. Maybe there's a javascript
implementation, and it runs in the browser. You connect to your
editor daemon, deal with your document. Save, exit, disconnect. If
Amtrak finds a dead spot, you're summarily disconnected, but when you
resume, the client -- just like HTTP -- learns from the server what the
current display looks like, rebuilds it, and you start again.
If you want to build something new and light, I'd suggest separating
the concern of editing a document from interacting with a user. It's
not a new idea: arguably screen, sed, and ed do it. But there's no
editor I know designed for unreliable, slow connections, which often as
not is what the Internet still is .
--jkl
next prev parent reply other threads:[~2016-08-24 3:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-21 20:15 A femtolisp based emacs clone edu500ac
2016-08-22 4:17 ` Gene
2016-08-22 5:22 ` Rusi
2016-08-22 21:32 ` edu500ac
2016-08-23 1:23 ` Thien-Thi Nguyen
2016-08-24 3:52 ` James K. Lowden [this message]
2016-08-24 4:35 ` Yuri Khan
2016-08-24 21:38 ` edu500ac
2016-08-25 12:28 ` Stefan Monnier
2016-08-26 8:28 ` Michael Albinus
2016-08-26 13:08 ` Stefan Monnier
2016-08-25 21:22 ` Ben Bacarisse
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160823235249.b49733686b125af962883642@speakeasy.net \
--to=jklowden@speakeasy.net \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.