4 ms·
No, I am specifically not talking about this. I'm actually not sure at this point what you mean - I have a vision of somebody communicating with an emacs backen
by rusk 6y ago
No, I am specifically not talking about this. I'm actually not sure at this point what you mean - I have a vision of somebody communicating with an emacs backend via forms?
I'm just talking about a thin client, such as you typically use when you have emacs running as a server. You only have to manage text and windowing, and capturing user commands and communicating with the back end. These are the kind of things browsers are good at.
- skissane 6y agoWell, think of a 3270 editor, such as ISPF EDIT on MVS or XEDIT on VM/CMS. Now imagine using that editor through a 3270-to-HTML gateway. That's what I was really talking about. But, you could actually implement a similar style of interaction in pure HTML, without the 3270 layer. Indeed, a lot of classic server-side web apps, even if they weren't text editors, worked with that UI style. Of course, Emacs doesn't support 3270. But that was my point – that there are UI styles which Emacs doesn't support. They might not be useful UI styles, especially in 2020. But historically they were important, and any suggestion that Emacs is some kind of magic which supports all UI styles isn't really true, although maybe it supports all contemporarily practically relevant UI styles.