News for hackers. Stuff that matters.
Re:What do Unix command names stand for? by jzl on Friday June 15, 2018 @07:12PM (#17324511)
The emacs "JOKES" file contains an extended section of proposed backronyms, along with a bunch of other 20-30 year-old jokey bits from usenet:

https://github.com/emacs-mirror/emacs/blob/master/etc/JOKES

  EMACS may stand for "Editing MACroS," but some friends of mine suggested some more creative definitions.
  Here they are. Anyone have any additions?

  Eight Megabytes And Constantly Swapping
  Even a Master of Arts Comes Simpler
  ...
Re:What do Unix command names stand for? by vram22 on Friday June 15, 2018 @07:37PM (#17324692)
I've heard it as Emacs Makes All Computers Slow.

Probably was more applicable in the old days (as one call tell from the "megabytes" in the parent comment) than nowadays :)

Re:What do Unix command names stand for? by shagie on Friday June 15, 2018 @08:21PM (#17324901)
Thats because it Eventually Mallocs All Computer Storage.
Re:What do Unix command names stand for? by justinian on Saturday June 16, 2018 @12:25AM (#17325828)
Escape-meta-alt-ctrl-shift!
Re:What do Unix command names stand for? by duozerk on Friday June 15, 2018 @09:09PM (#17325143)
I'm often surprised how Emacs can struggle sometimes on modern hardware, like for example when chain-executing complex keyboard macros - though mostly yeah, it doesn't apply all that much anymore.
Re:What do Unix command names stand for? by cup-of-tea on Saturday June 16, 2018 @03:38AM (#17326427)
Emacs is actually faster than most editors, but it lets you do anything so of course you can slow it down.
Re:What do Unix command names stand for? by masklinn on Saturday June 16, 2018 @04:22AM (#17326562)
The issue is it remains non-concurrent and any code (macros, extensions, …) executes in place of the editor doing its thang, so any non-trivial operation (or trivial operation on an entire buffer) locks up the editor until it's done and does its thing.

And while it might technically be faster for the process, as is the case with e.g. STW GCs on large processes it 1. feels horrible and 2. as an editor is interactive it stops the user in their tracks and slows them down to hell