text stringlengths 0 2.02k |
|---|
[96.30 --> 102.34] Not just for developers working for the Googles, Facebooks, or Shopifys who left local development already for several years. |
[102.72 --> 109.00] Gitpod is open source and provisions for every development team on GitHub, GitLab, and Bitbucket cloud-powered dev environments. |
[109.00 --> 116.48] You can access your developer environments via upstream VS Code, running on your desktop or in the browser, and soon also all JetBrains IDs. |
[117.00 --> 120.86] Very cool. If this gets you excited, learn more and get started for free at gitpod.io. |
[121.16 --> 127.94] Gitpod is free for individual developers for 50 hours a month, can be self-hosted, and is available for every developer today. |
[128.30 --> 129.58] Again, gitpod.io. |
[139.00 --> 155.04] We are back for a follow-up episode to episode 450 on VIM. |
[155.04 --> 161.04] First of all, I want to say that I appreciate all of the positive feedback around our VIM episode. |
[161.34 --> 164.06] We put a lot of work into that, and it sounds like everybody enjoyed it. |
[164.12 --> 165.00] We're happy to hear that. |
[165.58 --> 169.20] And one of the things that we heard over and over and over and again was, |
[169.64 --> 170.36] When NeoVIM? |
[170.70 --> 173.58] So similar to the crypto kitties say, |
[173.64 --> 176.46] When Moon, the NeoVIM kitties were saying, |
[176.88 --> 178.02] Hey, you've done VIM. |
[178.02 --> 181.24] Now give us the NeoVIM treatment. |
[181.50 --> 187.50] So by popular demand, we have TJ DeVries here to talk NeoVIM with us. |
[187.54 --> 188.78] TJ, thanks for coming on the show. |
[189.24 --> 189.90] Yeah, it's my pleasure. |
[190.04 --> 193.66] Really excited to chat and just explore some fun topics together. |
[194.06 --> 195.00] We are excited too. |
[195.16 --> 201.92] And I have with me, not Adam Stack, it is Nick Neesey, my co-patriot at JS Party. |
[202.06 --> 203.36] Nick, welcome to the changelog. |
[203.80 --> 204.22] Hoi hoi. |
[204.36 --> 205.30] I'm happy to be here. |
[205.38 --> 206.86] Excited to talk about NeoVIM. |
[206.86 --> 211.08] And just for the record, it wasn't just me hounding Jared to get a NeoVIM episode. |
[211.48 --> 214.18] That wasn't your bot just telling me over and over again. |
[214.86 --> 218.56] I can't confirm or deny that, but it wasn't me specifically. |
[219.20 --> 223.84] Well, if you know JS Party, you know Nick is often trying to turn it into VIM Party. |
[224.54 --> 227.12] And he brings up VIM whenever he has opportunity. |
[227.36 --> 229.86] And he has been for a little while a NeoVIM user. |
[229.96 --> 231.32] How long have you been on NeoVIM, Nick? |
[231.78 --> 232.92] It's been a couple of years. |
[232.92 --> 238.76] But I'm a recent convert to the NeoVIM 0.5 slash Lua lifestyle that I'm excited to talk |
[238.76 --> 239.30] about today. |
[239.30 --> 246.34] I will also confess that after our VIM episode and our modern Unix tooling episode, I've been |
[246.34 --> 249.24] reinvigorated and I installed NeoVIM. |
[249.44 --> 250.94] And I threw away my VIM config. |
[250.94 --> 257.74] And I'm doing survivor style, which configs make it into the new config game, line by line. |
[257.90 --> 259.28] And I'm having lots of fun. |
[259.78 --> 265.38] I feel like a kid again, just tweaking and changing and kind of relearning how to use VIM. |
[265.44 --> 270.34] Because I've been using it for a very long time in a dual capacity with a full-time GUI. |
[270.44 --> 271.90] So I was on Sublime Text for years. |
[272.10 --> 273.32] I switched to VS Code. |
[273.32 --> 275.92] And I always had VIM open in a shell. |
[276.14 --> 277.30] And I would use it on servers. |
[277.30 --> 278.88] And I would use it kind of casually. |
[279.12 --> 281.80] As you know from that episode, I always use VIM mode whenever available. |
[281.98 --> 287.60] But I was not using it full-time as my programming editor until a few weeks ago. |
[287.70 --> 288.30] So I'm back. |
[288.60 --> 289.72] And I'm giving NeoVIM a try. |
[290.20 --> 291.44] And I'm having a lot of fun. |
[291.52 --> 293.30] But TJ, give us some of the backstory here. |
[293.72 --> 295.54] Because NeoVIM has been around for a while. |
[295.62 --> 298.36] And we've never done a show on it, despite multiple cries to do so. |
[298.84 --> 300.04] Who created NeoVIM? |
[300.20 --> 301.14] When did they start it? |
[301.40 --> 301.76] Why? |
[301.76 --> 303.40] Why did this have to exist? |
[303.56 --> 303.92] Et cetera. |
[304.02 --> 304.68] Give us the backstory. |
[305.18 --> 305.32] Yeah. |
[305.42 --> 310.56] So I think the main person who first started it was Tiago Taruda on GitHub. |
[311.46 --> 314.08] And it was probably about 10 years ago. |
[314.14 --> 315.60] I don't remember the exact date. |
[315.98 --> 320.28] The main thing that happened was Taruda was really interested in getting |
[320.28 --> 328.50] sort of some of the ability to run external jobs asynchronously from within VIM. |
[328.90 --> 329.12] Right? |
[329.12 --> 331.16] And that was the first main push. |
[331.16 --> 337.06] And Taruda submitted some patches to VIM Dev, which is the mailing list for VIM. |
[337.56 --> 342.50] But unfortunately, at the time, Taruda, the patches didn't work for Windows. |
[342.50 --> 346.68] And there were some other problems that would have broken compatibility with like a lot of |
[346.68 --> 349.08] the places that VIM expects to build. |
[349.72 --> 354.46] And so due to that, it was sort of like this struggle of, I don't know if struggle is the |
[354.46 --> 358.66] right word, but just sort of a difficulty trying to figure out how these features could work |
[358.66 --> 363.62] within VIM and all the places that VIM needs to build and the size requirements and all these |
[363.62 --> 364.06] other things. |
[364.06 --> 364.30] Right. |
[364.56 --> 370.42] Which are like super valid concerns to have if you're on all the places that VIM can build. |
[370.58 --> 370.78] Right. |
[370.84 --> 372.84] Like, do you want to still be able to do that? |
[372.90 --> 377.14] That's one of the selling points is sort of the universalism of where VIM is. |
[377.24 --> 379.48] He didn't have an old Solaris machine to test it on? |
[380.04 --> 380.44] Right. |
[380.44 --> 383.16] He did not make any patches that work there. |
[383.62 --> 388.56] So basically, at that point, Taruda was kind of like, well, I don't want to necessarily |
[388.56 --> 389.70] have to support those. |
[389.80 --> 392.98] Like, I want to do different things that can work differently. |
[393.08 --> 398.16] And I want to like push forward in some of these areas that might make us end up in a |
[398.16 --> 400.18] place that's not the same place that VIM is. |
[400.30 --> 400.46] Right. |
[400.98 --> 404.28] And so Taruda basically started NeoVIM. |
[404.28 --> 409.28] And then from there, Taruda also had several other sort of like large ideas in combination |
[409.28 --> 414.06] with people like Justin MK, who's still part of the project, as well as Zix, who is one |
[414.06 --> 417.56] of the largest early contributors to NeoVIM. |
[417.72 --> 422.34] And they added other things like remote plugin support and started doing LUA scripting and |
[422.34 --> 423.06] things like that. |
[423.70 --> 430.18] But that was sort of the main branching point that started to allow NeoVIM to go down a separate |
[430.18 --> 431.00] path from VIM. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.