Search Results
6/19/2025, 5:40:23 PM
>>105637542
it is garbage, but emacs' bindings suck. half of them aren't mnemonic, okay fine that's normal.
but then the existing mnemonics are fucking worthless because the jargon is totally foreign to the modern computer user and it's not even intuitive.
"killing" and "yanking" are the most obvious examples, but then you have shit like "org mode", "tramp mode", on top of all the programmer jargon.
i remember trying to set up emacs to do development work in scheme when i was a young programmer and getting lost in a sea of jargon and vagueness. most people aren't going to put up with that any more than they're going to put up with vim's autistic modal editing. they're going to use one of the billion other highly extensible editors that are floating around now that work out of the box with familiar verbs, interfaces and bindings. in vs code you just open up your sidepane, click on a search bar and install an extension to get full language support. even if you're doing something wacky, all you ever do is fiddle with a couple fields of a json, a markup language most people are familiar with. in emacs you need to get up to speed on lisp and sexprs which itself is a non-trivial task, a very quirky variant of a lisp at that, and then you need to comb through a massive mountain of documentation to even find where the fuck you're going and what you need to change. installing extensions is a configuration nightmare for a new user.
i love emacs, it's very powerful and good, but it's really not any less opaque than vi/vim/neovim when you're starting out, and it's far from being the only extensible text editor in town anymore.
it is garbage, but emacs' bindings suck. half of them aren't mnemonic, okay fine that's normal.
but then the existing mnemonics are fucking worthless because the jargon is totally foreign to the modern computer user and it's not even intuitive.
"killing" and "yanking" are the most obvious examples, but then you have shit like "org mode", "tramp mode", on top of all the programmer jargon.
i remember trying to set up emacs to do development work in scheme when i was a young programmer and getting lost in a sea of jargon and vagueness. most people aren't going to put up with that any more than they're going to put up with vim's autistic modal editing. they're going to use one of the billion other highly extensible editors that are floating around now that work out of the box with familiar verbs, interfaces and bindings. in vs code you just open up your sidepane, click on a search bar and install an extension to get full language support. even if you're doing something wacky, all you ever do is fiddle with a couple fields of a json, a markup language most people are familiar with. in emacs you need to get up to speed on lisp and sexprs which itself is a non-trivial task, a very quirky variant of a lisp at that, and then you need to comb through a massive mountain of documentation to even find where the fuck you're going and what you need to change. installing extensions is a configuration nightmare for a new user.
i love emacs, it's very powerful and good, but it's really not any less opaque than vi/vim/neovim when you're starting out, and it's far from being the only extensible text editor in town anymore.
Page 1