5 ms·
Which part of ”we have to pretend to be a deprecated system that pretends to be an even more deprecated system that pretends to be an obsolete system to prevent
by dmitriid 8y ago
Which part of ”we have to pretend to be a deprecated system that pretends to be an even more deprecated system that pretends to be an obsolete system to prevent Emacs from flickering” is a feature?
- TeMPOraL 8y agoThat is an implementation detail. The feature is "witness the firepower of this fully armed and operational battle station/editor, of which 99% works and looks the same both in GUI and terminal, at zero extra effort from feature developers". Whether or not the implementation is truly necessary to achieve the feature, that I don't know.
- dmitriid 8y agoIt’s not an implementation detail. It’s decades of technical debt, and it’s very strange to see it defended. When a simple task of making a program not flicker (a solved, well understood and fairly trivial problem) requires quite a sizable effort, it’s no longer just an “implementation detail”. LOL at people decrying the bloat and inefficiency of Electron apps and calling this a perfect program with just implementation details: — start quote — GNU Emacs is an old-school C program emulating a 1980s Symbolics Lisp Machine emulating an old-fashioned Motif-style Xt toolkit emulating a 1970s text terminal emulating a 1960s teletype. Compiling Emacs is a challenge. Adding modern rendering features to the redisplay engine is a miracle. — end quote —
- TeMPOraL 8y agoLet me rephrase my thoughts. I'm not defending this cruft per se. I'll be glad to see it gone iff it doesn't affect the text-orientedness of Emacs UI, as this specific style of text UI is a feature.
- barrkel 8y agoDon't focus in the mechanism. People aren't defending the mechanism. They are defending the benefit, which is currently a side effect of the mechanism: feature invariance with respect to render target, whether GUI or terminal. My own use is about 50:50 of each. Only a few things don't work the same way in the terminal and that's extremely valuable.
- bitwize 8y agoNo, it's not really. In order to get window toolkit independence, and terminal- or GUI-independence, Emacs pretty much has to pretend to be a deprecated system pretending to be an even more deprecated system pretending to be an obsolete system. It needs a rewrite with modern tools and frameworks. And it needs to abandon the terminal (the obsolete system) altogether.
- tonyarkles 8y agoUp until about a year ago, I used emacs exclusively from a terminal. The only reason I switched was because I usually have a number of tmux sessions open (with multiple “windows” in each one), and I kept losing emacs :). Having it in its own window made it easier to jump back to. I’ll still often SSH home from a Chromebook and edit remotely. The fact that everything still works exactly the same is awesome. If you want to make an editor that doesn’t support that, you’re welcome to, but it won’t become my editor :)
- deleted 8y ago[deleted]
- Tcepsa 8y ago"Now that I've SSH'ed into this system I sure wish I couldn't use Emacs!" --Nobody, ever (My point being that I think abandoning the terminal would be a huge loss to many people and therefore a poor decision)
- TheCoelacanth 8y agoWhy would you SSH into a system and use Emacs there when you can just have Emacs handle SSH for you[1]? What do you gain by running the whole UI over SSH when you can just send the reads and writes instead? Especially since Emacs might not even be installed on the remote machine. [1] http://www.gnu.org/software/emacs/manual/html_node/emacs/Remote-Files.html http://www.gnu.org/software/emacs/manual/html_node/emacs/Rem...
- TeMPOraL 8y ago