We should be so lucky. No, sadly, bruv has repeatedly enticed handing over the keys over a silly dustup like the portable dumper, the long line mishandling, or the c-ts-mode incident where he could not bring himself to admit wrongdoing, then invariably back out hoping no one will remember his tantrum. This emacs thing is really all he has.
I'm not going to argue. If enough people think I'm mistaken and want
to go the portable dumper way, I will resign right here and now. It
is very easy to convince me to step down, because I hesitated to take
this job to begin with. -- lists.gnu.org/archive/html/emacs-devel/2016-11/msg00640.html
Bruv would run the same guilt trip maybe once every couple years, the last time being the c-ts-mode snafu of his own creation. That time, someone snarkily replied, "Please do [resign]!" Bruv hasn't done it again since. This emacs thing is all he has.
The flows are based on experience. The ratings are based on anecdotal evidence and opinion, they are a guide only. AFAIK, there is no public data available on interaction pattern vs token use.
It's not widely known, but GNU Emacs works like this.
When you launch the Emacs editor, you're loading an Emacs Lisp image that was populated at build time by running Lisp code, with the resident Lisp definitions "dumped" to make an image file.
The image file used to actually be the `emacs` executable you'd run, using a clever but non-portable mechanism called `unexec` to make an executable.
But as of version 27.1 (in 2020), the image file is separate from the executable for portability reasons.
There are a number of image-based Scheme systems. Chibi Scheme and Chez Scheme come to mind. In both, you can save an image and reload it at a later time, though for very good reasons, most people start each session with a fresh copy of the default image.
reply