text
stringlengths
0
2.02k
[4425.56 --> 4426.20] Bye.
[4426.30 --> 4427.16] Bye.
[4427.16 --> 4427.68] Bye.
[4427.68 --> 4427.82] Bye.
[4427.88 --> 4428.08] Bye.
[4428.12 --> 4428.92] Bye.
[4428.92 --> 4429.02] Bye.
[4429.02 --> 4429.44] Bye.
[4429.44 --> 4429.86] Bye.
[4430.04 --> 4430.06] Bye.
[4430.06 --> 4430.22] Bye.
[4430.50 --> 4430.52] Bye.
[4430.52 --> 4430.96] Bye.
[4431.10 --> 4431.26] Bye.
[4431.36 --> 4431.66] Bye.
[4431.82 --> 4432.10] Bye.
[4432.10 --> 4432.52] Bye.
[4432.52 --> 4439.52] Game on!
• The origins of Vim, a modal text editor from 1991, and its roots in Vi from 1976.
• The guests' experiences and reasons for using Vim, including:
• Julia Evans using Vim for 17 years for programming and writing comics.
• Drew Neil's introduction to Vim at a job where Textmate didn't run on Linux.
• Gary Bernhardt switching to Vim to prevent RSI (repetitive strain injury) from programming long-term.
• Suz Hinton using Vim due to its presence on Linux machines and her need to edit files in shell sessions.
• The importance of text editors as primary interfaces for developers and the impact of their choices on daily work.
• The ubiquity of Vim on Linux machines makes it a valuable skill to have, even for those who don't use it daily
• Vim's design allows for efficient shortcuts and muscle memory, reducing frustration and increasing productivity
• The modal nature of Vim, particularly the concept of normal mode and insert mode, is a key aspect of its design and can be difficult to grasp at first
• The ability to select and manipulate text using visual mode is a powerful feature of Vim
• Customizability and the ability to install plugins are also major advantages of using Vim
• Customizability of Vim
• Plugin community and popular plugins
• Drew Neil's favorite plugins (surround.vim, Fugitive, Exchange)
• Suz Hinton's minimalist approach to plugins
• Git integration and plugins (Fugitive, Gitgutter)
• Custom text objects and operators (vim-textobj-user, Commentary)
• Aesthetics and minimalism in plugins (Vim-airline, Ctrl+P)
• Discussion of the versatility of Vim and its ability to support different languages, including TypeScript
• Gary Bernhardt's minimalistic approach to Vim plugins, using only 8 plugins for basic functionality
• The importance of a fuzzy file finder plugin for new Vim users
• Customization of Vim's configuration file (vimrc) for basic editing configuration
• Julia Evans' preference for her vimrc settings that automatically jump to the last position in a file
• The concept of Vim mode, where other editors and apps mimic Vim's command mode
• Gary Bernhardt's experience with Vim emulations and his frustration with their limitations
• Discussion of the ergonomic benefits of Vim and its complex codebase
• Suz Hinton's experience with Vim mode in various apps, including Facebook and Twitter
• Julia Evans' use of Vim mode in multiple editors and her preference for it over native editors
• Vim mode and navigation in email clients
• Ubiquity and adoption of Vim-like keybindings in various applications
• Benefits of using Vim, including efficiency and customization
• Reasons for Vim's popularity, including sticky factor and persistence as a tool
• Limitations and frustrations with using Vim, including language support and file type plugins
• Comparison of Vim with other text editors and IDEs
• Vim's flexibility and configurability can be both a blessing and a curse, with some users finding it overwhelming.
• Vim's file type plugin system can be awkward to use for files containing multiple languages.
• Configuration syntax, particularly Vimscript, can be frustrating to understand and use.
• The Vim community and culture can be intimidating and dogmatic, with a focus on customization and shortcuts.
• The editor's default settings and behavior can be unfamiliar and frustrating for users who are used to a different setup.
• Accidental use of Vim's "Jump to Man Page" feature and other keyboard shortcuts causing frustration
• Common mistakes in Vim, such as hitting the wrong keys in macro recording mode
• Learning curve of Vim and its perceived difficulty for many programmers
• Gary Bernhardt's reasons for recommending learning Vim, including:
• Preventing RSI
• Increased speed
• Long-term relevance and compatibility of Vim keystrokes
• Importance of mastering a single, efficient editor to improve productivity and reduce distractions
**Jerod Santo:** Vim, the final frontier... Sorry, that's so lame. I've just always wanted to do that. Let's run it back. Vim, a modal text editor from 1991, with roots in Vi that go back to 1976. That's 45 years ago, and yet here we are in 2021, 30 years after Vim's initial release, and it's still used and loved by ne...
On this special episode of the Changelog we thought it would be fun to hear a bit of Vim's story from the mouths of its users, so I gathered some friends, new and old, and asked them to tell me all about Vim and why they love it.
Thank you to our friends at Sourcegraph for partnering with us to make this episode interruption-free. Teams with large codebases and many repos struggle with the usefulness that grep and Cmd+Shift+F offer. They need a better way to search and discover all their code and open source dependencies. They need Sourcegraph....
Alright, let's meet our guests, starting with Julia Evans.
**Julia Evans:** I'm Julia, I've been using Vim for (I think) 17 years, and I'm a programmer and I currently for a living write comics about programming.
**Drew Neil:** Hi, I'm Drew Neil. You may know me as the voice of Vimcasts. I also wrote Practical Vim and Modern Vim. And aside from my sort of Vim work, I'm a web developer by day, and I also do, sort of related to all the Vimcasts and books and so on, I do training sessions about Vim. I've been using Vim since about...
**Gary Bernhardt:** I'm Gary Bernhardt. The thing people are most likely to know me from is a lightning talk called WAT, which is almost ten years old now... Right now I'm working on Execute Program, which is an interactive learning program that's kind of unique in that we mix lots of real code examples in with explana...
I've been using Vim for about 15 years, since 2006. I was an Emacs user before that, and before that - Visual Studio, and more mainstream Windowsy kinds of editors. I also went back and forth between Emacs and Vim a number of times in the early days, so I have a lot of comparison reference points there.
**Suz Hinton:** I'm Suz Hinton. I do software development professionally, and also in my spare time as a hobby. I most frequently work in Golang, Ruby, JavaScript, but I kind of like to do a little bit of everything, from the top of the stack, right down to almost the bare metal; not quite Assembly. And I switched to u...
**Jerod Santo:** One thing that has always fascinated me is how people come to select their tools, techniques, programming languages and so on. As a developer, your text editor is one of the most important choices you make, because you use it all day, every day. It is the primary interface to the work that you do.
I learned Vim not because I chose to, but by dictate. My programming teacher in college was a staunch Vim proponent and forced us to write all of our programs SSH-ed into a Linux machine using Vim. I kind of hated him for it at the time, but I definitely appreciated in retrospect. Shout-out to John Clark if he's out th...
**Drew Neil:** \[03:50\] Switching jobs... I was at a job where we all used Macs, and back then we were a Rails shop and everyone was using Textmate... And I switched to a job where it was all Linux workstations, and Textmate didn't run on Linux. So I had to pick another editor. I think the ones I was considering at th...
It was a small company, but there were a fair few Vim users, so I thought "Well, if I start using Vim, I've got a few more people I can ask questions of..." So that was kind of what got me into Vim. And I knew -- at the time, I was aware that Vim had really good support for Rails, which was what I was mainly working wi...
**Jerod Santo:** It's funny how the social -- not social pressure, but just the social environment around you helped make that decision.
**Drew Neil:** Yeah, that's true. I could have moved to a job where there were five Emacs users and two Vim users, and it would have worked out differently.
**Jerod Santo:** We'd be all watching EmacsCasts.
**Drew Neil:** Yeah. \[laughs\]