Vim Versus Emacs. Which Is Better? DistroTube
video description
Date: 2022-03-30
Related videos
Comments and reviews: 9
Marcus
The king of cryptic text editing was, and remains, Teco, which is still available for several platforms. Emacs was originally written in Teco, and Vi/Vim are shameless plagiarisms of the Teco command interface. Teco was written by Dan Murphy on the Digital Equipment PDP-1 computer in 1962-63. The PDP-10 series computers in the late 1970's (the one Bill Gates used to create MBasic) came with a huge security vulnerability - Teco could be used to 'phish' user logins/passwords from the text mode terminal login prompts because it was the only user runnable program other than LOGIN with privileged instruction permission to the SETLCH instruction (by being started under the system user [1,2]). SETLCH allowed LOGIN to turn off terminal echo for the purpose of receiving a password. One could therefore also emulate a login prompt in Teco, receive the login/password keystrokes, save them to a file and then reply with
?INVALID ENTRY - TRY AGAIN-
#
before immediately logging out of Teco and your own account directly to a (real) login prompt.
reply
The king of cryptic text editing was, and remains, Teco, which is still available for several platforms. Emacs was originally written in Teco, and Vi/Vim are shameless plagiarisms of the Teco command interface. Teco was written by Dan Murphy on the Digital Equipment PDP-1 computer in 1962-63. The PDP-10 series computers in the late 1970's (the one Bill Gates used to create MBasic) came with a huge security vulnerability - Teco could be used to 'phish' user logins/passwords from the text mode terminal login prompts because it was the only user runnable program other than LOGIN with privileged instruction permission to the SETLCH instruction (by being started under the system user [1,2]). SETLCH allowed LOGIN to turn off terminal echo for the purpose of receiving a password. One could therefore also emulate a login prompt in Teco, receive the login/password keystrokes, save them to a file and then reply with
?INVALID ENTRY - TRY AGAIN-
#
before immediately logging out of Teco and your own account directly to a (real) login prompt.
reply
iAmTheArm
Can't really call Emacs bloated, but it is noticeably slower than Vim. However, there is indeed so much possibilities for what you can have your particular build of Emacs that it is 100% possible to never leave it.
Man, Lisps are such a great family of languages I'm still salty about Java having been so heavily promoted that Netscape just had to forrce Eich into turning his project into a Java lookalike for no benefit to the Web, but at least people start walking up to OOP having been way too overhyped. We might've lived in a much better world where Netscape made Cloj -or something like that years ago.
reply
Can't really call Emacs bloated, but it is noticeably slower than Vim. However, there is indeed so much possibilities for what you can have your particular build of Emacs that it is 100% possible to never leave it.
Man, Lisps are such a great family of languages I'm still salty about Java having been so heavily promoted that Netscape just had to forrce Eich into turning his project into a Java lookalike for no benefit to the Web, but at least people start walking up to OOP having been way too overhyped. We might've lived in a much better world where Netscape made Cloj -or something like that years ago.
reply
Jaehyun
I think Emacs is like a web browser as now we run various of web applications on the browser. The primary purpose of JavaScript was to handle DOM in HTML. Emacs LISP was to handle text in buffer. Both can run the language to run many application using HTML (web browser) or text as a user interface.
reply
I think Emacs is like a web browser as now we run various of web applications on the browser. The primary purpose of JavaScript was to handle DOM in HTML. Emacs LISP was to handle text in buffer. Both can run the language to run many application using HTML (web browser) or text as a user interface.
reply
eric
I haven't used Vim (used to be stuck with vi before there were options), but I can't imagine a better Lisp editor than emacs. As to the danger of the default emacs key bindings, I just remapped the caps lock key so I don't have to stretch my pinky. Why we even have a caps lock key today is a mystery.
reply
I haven't used Vim (used to be stuck with vi before there were options), but I can't imagine a better Lisp editor than emacs. As to the danger of the default emacs key bindings, I just remapped the caps lock key so I don't have to stretch my pinky. Why we even have a caps lock key today is a mystery.
reply
R69NiX
Vim is BY FAR the most popular. You hardly ever hear of Emacs these days. I think these days pretty much all devs would try Vim first. Then they might hear about Emacs and try that and prefer it, but I don't think many people start with Emacs.
reply
Vim is BY FAR the most popular. You hardly ever hear of Emacs these days. I think these days pretty much all devs would try Vim first. Then they might hear about Emacs and try that and prefer it, but I don't think many people start with Emacs.
reply
Peter
Now ... I'm an Emacs user.
I don't do everything in Emacs. (although I know most of it).
I do prefer, say, Thunderbird, for email.
One thing I don't understand though is evil-mode emacs users ... That's just confusing.
reply
Now ... I'm an Emacs user.
I don't do everything in Emacs. (although I know most of it).
I do prefer, say, Thunderbird, for email.
One thing I don't understand though is evil-mode emacs users ... That's just confusing.
reply
Stefan
For editing config files and small scripts I generally prefer nano over vi/vim. I never really tried emacs, as I use dedicated IDE for software development and nano is capable of what I need for small edits.
reply
For editing config files and small scripts I generally prefer nano over vi/vim. I never really tried emacs, as I use dedicated IDE for software development and nano is capable of what I need for small edits.
reply
Matthew
The easiest way to comment or uncomment in ViM is with regular expressions
:s/-/#
That'll add a # to the beginning of each line you have selected.
reply
The easiest way to comment or uncomment in ViM is with regular expressions
:s/-/#
That'll add a # to the beginning of each line you have selected.
reply
Willow
Some1 probably mentioned it but the commenting functionality you mentioned in evil emacs is inspired by the very popular vim plugin tpope/vim-commentary
reply
Some1 probably mentioned it but the commenting functionality you mentioned in evil emacs is inspired by the very popular vim plugin tpope/vim-commentary
reply
Add a review, comment
Other channel videos
