text stringlengths 0 2.02k |
|---|
**TJ DeVries:** Yeah, so there's a couple things still baking for sure in Telescope. I mean fzf is just like a rock-solid piece of software that's super-cool. If you're doing things that might be searching millions of files, for example, you should stick with fzf. Go is going to be a better solution for you than what I... |
We are nearing completion of merging a very important PR that will greatly improve performance for really, really large searches, like 500,000 items; it will still feel fast and not really block the editor. So it's up to you... I would say if your primary concern is speed, then you should probably stick with fzf, at le... |
We're working on some projects in C to compile as optional dependencies that you can throw in here and work super-fast and cool... But we're not there yet, and it's cool. Like I said, I like fzf, but I use it every day; I no longer use fzf inside of Neovim. I have lots of friends who no longer use it inside of Neovim, ... |
So I would say it's ready for daily use, but if you're gonna be searching ten million things or something like that, then running something inside of the program that you're doing is probably not a good call. You should use an external executable that's gonna manage that memory a little bit tighter. |
**Nick Nisi:** I have an answer for you... Why not both? |
**TJ DeVries:** Yeah, I have recommended that for some use cases for people... Like, if they're trying to grep every line in their very large monorepo, there's no reason not to keep fzf around, at least for a while. |
For me, I have a hard time if the UI isn't as consistent. It's just sometimes I notice that, or I'm like "Oh, it's not the same as what I'm used to." So for some people, that really bothers them, and I understand; that's totally cool, and they say they're gonna stick with fzf, and I say "Awesome. That's great." |
**Nick Nisi:** That is one thing that I think Telescope really has going for it, is it just has a really beautiful UI. |
**TJ DeVries:** Thanks. |
**Jerod Santo:** That does help, doesn't it? |
**TJ DeVries:** Yeah. It is very interesting when you actually start using it and you notice that you get exactly the same colors as what the rest of your editor is... |
**Nick Nisi:** I don't have that with fzf. |
**TJ DeVries:** Yes. It is not possible as far as I understand, because for example, when you open up a buffer inside of Neovim and if you have tree-sitter, it will literally tree-sitter highlight the same way, with the same exact colors, because it is just another buffer. It would be like if you did :edit this file; i... |
**Jerod Santo:** Very cool. So one thing I wanna touch on maybe as a closer - I mentioned the enthusiasm around the 0.5 release... I mentioned how many people said "When Neovim on the Changelog?" There's a lot of people very excited about this project, they love the ability to write plugins in Lua, they like the new ca... |
**TJ DeVries:** \[01:07:56.23\] Yeah, so we did a 0.5 release stream on Twitch, on my livestream channel, and the excitement and enthusiasm was really mind-blowing for me. You know, I've been working on Neovim for a long time, and sometimes you're sort of just working and you're pushing stuff to GitHub, and like "Okay,... |
Just as a general note, if you're using open source software, and especially if it's maintained by people who aren't getting FANG-like salary to do the maintenance, it means a lot when you get a thank you, or like "Wow, I really like this" to that. I was really pleased to see Neovim in the top spot for most loved edito... |
But yeah, I think the community is great, and it's really exciting to see how much people are excited... And I've really appreciated it and it's been fun being on the receiving end of that. |
In terms of where can people get started and how can they help - first thing is we're on Element, or Matrix, I guess; there's a Neovim chat there. I believe it's linked from the readme. If it's not, then it should be... \[laughs\] So you can go there. Or it's on Gitter, or it's on IRC. They're all sort of bridged to be... |
There's a lot of issues that if you commented on and said "I wanna work on this" or "How can I fix this?", people are super-glad to help. That's how I got involved. I did a PR maybe during my senior year of college, adding a new thing to status line, and I just had a ton of really nice people be there to help and to en... |
I hope, and I think it's a goal to other maintainers as well, that we basically make a welcoming and happy place for people to learn a lot more. So don't be afraid to ask questions or to comment and say "I'd love to work on this. Where should I start?" That's how I got started, so I think that's a really great way to g... |
There's some labels, like "Good first issue" or "Mentored project" or things like that that you could look into, but don't be afraid to leave a comment or say hello. We're super-happy to see you. Or just say "Thanks for working on it." That always makes me feel better and gives me energy to keep on improving Neovim and... |
**Jerod Santo:** Awesome. Well, we definitely appreciate all of the work that you're doing. I'll just echo your sentiment - if you have a piece of software that you use and love, find the people that make that software and let them know, especially if it's open source, but proprietary as well; there's people behind the... |
Nick, I wanna thank you for being my Changelog co-pilot. Hopefully, none of the things you generated today were GPL code... \[laughter\] But happy to have you here with me. I think I broke the show with that one. |
TJ, we really appreciate you coming on the Changelog. To everybody who requested this episode, we thank you as well. We do take requests. Head to our website, Changelog.com/request, fill out the form there, let us know guests you'd like to hear, topics you'd like to hear, if you want Nick to come back, if you'd like us... |
Any final words, TJ or Nick? |
**TJ DeVries:** Just thanks for having me. It's cool to see Neovim be requested on the show, and I'm always happy to talk about it. If you wanna see more of me or hear my voice, I stream a lot on Twitch.tv/teej\_dv. You could come hang out there. We're live pretty often, and I do a lot of Neovim-related work there. Oth... |
**Nick Nisi:** Yeah. And thanks for having me on as well. TJ, I would gladly take you up on that offer to dig into some custom LSP stuff. That's really cool. |
**TJ DeVries:** Cool. |
**Jerod Santo:** We are tentatively planning some related livestreams. We have nothing locked in, but definitely follow TJ on Twitch, and maybe on Twitter as well, for announcements. Of course, follow @changelog on Twitter. You can also follow Nick Nisi on Twitter, but... I don't know; you decide if you wanna do that. |
**Nick Nisi:** Thanks, Jerod. |
**Jerod Santo:** Alright, that's our show for this week. We'll talk to everybody next time. Sorry, Nick... In true JS Party fashion I had to roast you a little bit, just at the end. |
**Nick Nisi:** Absolutely. \[laughter\] |
• Introduction to The Change Log podcast and its guest, TJ DeVries, a core maintainer of NeoVim |
• Discussion of NeoVim, including its creation, differences from Vim, and features such as Lua configuration and plugins |
• Introduction of the guest, Nick Neesey, and his experience with NeoVim |
• Discussion of the process of switching to NeoVim from Vim and the benefits of doing so |
• Mention of a previous episode on Vim and the popularity of NeoVim |
• Introduction to Gitpod, a platform for automated dev environments, and its features and benefits |
• Tiago Taruda created NeoVIM about 10 years ago as a way to add external job functionality to VIM |
• Taruda's patches were initially rejected due to compatibility issues with Windows and other platforms |
• NeoVIM was created as a separate project to allow for more experimental and forward-thinking development |
• NeoVIM and VIM share a large codebase and many patches are ported from VIM to NeoVIM |
• NeoVIM has some key differences, including: |
• Not shipping with a GUI by default |
• Implementing GUIs over RPC instead of tightly coupling it to a GUI application |
• Removing some plugins and features that are specific to VIM |
• Having a different set of default keybindings and commands |
• Discussion of NeoVIM and VIM usability and performance |
• Comparison of NeoVIM and VIM async job support and other features |
• Bram's development approach and potential influence from NeoVIM |
• Differences in APIs and implementation between NeoVIM and VIM |
• Discussion of NeoVIM's use of lib UV and its event loop |
• Discussion of implementation differences between Vim and NeoVim |
• Portability of plugins and code between Vim and NeoVim |
• Shared APIs and libraries between Vim and NeoVim |
• Challenges and complexities of maintaining shared codebases |
• Plans for creating a unified Lua API for floating windows |
• Expectations for future code sharing and porting between Vim and NeoVim |
• Retool's program for startups and its features |
• Frustrations with VimScript and its limitations |
• Contrast with Emacs Lisp and its relationship to the editor |
• Introduction of Lua as the new scripting language for NeoVim |
• Advantages of Lua, including performance, embeddability, and static language |
• Comparison with JavaScript, which was considered but ultimately discarded |
• Design principles of Lua and its purpose as an embedded scripting language |
• NeoVim's architecture and its suitability for using Lua |
• Performance benefits of using Lua in NeoVim, including speed and efficiency |
• The conversation is about porting a Vim config to Lua in NeoVim |
• The speaker, Nick, has experience with Vim script but not with Lua |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.