Datasets:
willtheorangeguy
/
2021-Changelog-Interviews-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
2.02k
[431.50 --> 433.66] Exactly how different is it?
[433.66 --> 439.48] Yeah, so this is, I think, a pretty common misconception that VIM and NeoVIM are like
[439.48 --> 441.02] very, very, very different.
[441.68 --> 445.62] VIM and NeoVIM still share much of the same code base.
[446.14 --> 450.26] NeoVIM still ports patches from VIM, like all the time.
[450.56 --> 456.78] We have some contributors, especially like Jan Lazo, who in the last 0.5 release helped
[456.78 --> 461.56] to get us to over a thousand VIM patches ported from VIM into NeoVIM.
[461.56 --> 467.82] So there's still sort of like an insane amount of similarity between the two.
[468.08 --> 468.22] Right.
[468.32 --> 475.32] And if you open them up, like you won't really see in effect, like any differences from like
[475.32 --> 479.92] lightly configured and it dot VIM or VIMRC, whatever you want.
[480.04 --> 484.12] You know, that's an important sort of like backwards compatting that we're interested in
[484.12 --> 485.92] trying to work hard on.
[485.92 --> 489.96] There are some things that are removed from NeoVIM that are in VIM.
[490.12 --> 494.52] Like, for example, NeoVIM doesn't ship with a GUI by default, like GVIM.
[495.12 --> 502.00] NeoVIM sort of removed all of the code that tightly coupled it to a GUI application and
[502.00 --> 504.16] instead implements GUIs over RPC.
[504.38 --> 508.46] So that's like an example of if you were expecting to be able to just open up GVIM.
[508.68 --> 512.50] But with NeoVIM, that doesn't happen because those two things have been sort of decoupled,
[512.50 --> 514.52] as well as various other things.
[514.52 --> 519.72] Like if you installed NeoVIM, it wouldn't install like Vue, the command Vue, which is like opening
[519.72 --> 526.02] VIM and read only mode, because you can instead do like nvim dash R or something.
[526.14 --> 527.88] I don't remember what it is off the top of my head.
[527.94 --> 528.50] Sorry, everybody.
[528.60 --> 533.02] But you could just alias that to be the same and then it would retain the same behavior.
[533.16 --> 537.34] So of course, there are some, you know, similarities that are obvious at the start and some things
[537.34 --> 539.84] that are a bit different when you're first encountering them.
[539.96 --> 544.60] But in general, there's a incredible amount of overlap still between the two projects,
[544.60 --> 545.12] I would say.
[545.66 --> 551.44] That would be my experience so far is that I haven't noticed a difference in just like
[551.44 --> 552.60] regular text editing.
[552.94 --> 554.84] Like I could just alias it and never notice.
[554.94 --> 558.78] Now, once I started configuring it and trying to do some more advanced things, you start
[558.78 --> 560.68] to see where the seams are, the differences are.
[560.74 --> 561.22] Go ahead, Nick.
[561.24 --> 561.64] What were you going to say?
[561.64 --> 565.90] Oh, I was going to say something similar in that when I started using it, I actually
[565.90 --> 569.10] started using it, I think for the same reason that it might have been created now that I'm
[569.10 --> 569.62] hearing that.
[570.00 --> 573.78] And that's because I heard about this async job support and I had just gotten into like,
[574.02 --> 575.94] you know, configuring linting and things like that.
[576.02 --> 578.68] But every time it would lint, it would like completely freeze VIM.
[579.06 --> 580.26] And that was just super annoying.
[580.42 --> 584.10] So then I heard about NeoVIM and how it could do that asynchronously.
[584.24 --> 586.98] And so I set it up, but I was like, this is just temporary.
[587.42 --> 589.98] I'm sure VIM is going to catch up and I'm just going to switch back to it.
[589.98 --> 593.96] So I installed it and I did that alias, alias VIM equals NVIM.
[594.38 --> 595.66] And I still have that.
[595.70 --> 596.94] And that's still how I invoke it.
[597.00 --> 600.48] But that alias is like five years old at this point or five or six years old.
[601.14 --> 607.16] And now I, yeah, it's just interesting that I really can't tell the difference or couldn't
[607.16 --> 611.76] tell the difference in the beginning, aside from like where your config lies and that.
[611.86 --> 615.60] But otherwise, when you start up, it said instead of VIM, it said NVIM.
[615.78 --> 617.22] That was pretty much the big difference.
[617.22 --> 617.94] Yeah.
[618.08 --> 622.88] And like just to mention as well, like VIM does have those capabilities now, right?
[622.92 --> 625.00] Like it does have asynchronous jobs and other things.
[625.06 --> 628.18] I just figure I want to throw that out there in case people are interested in adding some
[628.18 --> 630.52] of those things to their own VIM config.
[630.94 --> 633.20] But it does exist in both now.
[633.42 --> 635.00] Yeah, that's one of the cool things that I've noticed.
[635.00 --> 640.60] I wonder if NEOVIM is directly to blame or to accredit for this.
[640.68 --> 645.98] But it seems like VIM's development picked up with regard to performance, asynchronization
[645.98 --> 649.32] and certain things that maybe weren't being advanced.
[649.32 --> 653.52] And maybe there was a little bit of, you know, competition spurs innovation thing going on.
[653.60 --> 655.42] That was just my casual observation.
[655.70 --> 658.04] Is that your thoughts as well?
[658.04 --> 662.22] Or if we ask Bram about it, would he say, yeah, I saw NEOVIM coming and I was like,
[662.26 --> 663.58] holy cow, I need to start doing more.
[663.72 --> 665.14] Or what's the story there?
[665.68 --> 669.04] I actually think that this is probably like a common misconception.
[669.42 --> 673.98] I think Bram likes implementing things that he thinks people are going to use.
[673.98 --> 679.90] And like, it wasn't really clear, like from the community that this was an important thing
[679.90 --> 682.94] for them to like have previous to this.
[683.12 --> 685.92] My personal opinion, obviously, I'm not inside Bram's head.
[686.12 --> 690.46] And we've only spoken just casually a few times, you know, on GitHub issues or email.
[690.96 --> 695.92] Is that Bram just was like, oh, there's people requesting this now in VIM dev.
[695.98 --> 697.66] And they're like thinking about it a lot.
[697.74 --> 699.54] Like, oh, we can implement that.
[699.62 --> 701.72] And so then he implements it and it works well.
[701.72 --> 704.18] And then he's happy with like the solution.
[704.48 --> 710.64] I'm not 100% confident that like the NEOVIM like spurred him on to do that.
[710.74 --> 712.66] I don't necessarily think that that's exactly the case.
[712.72 --> 717.74] I think it's much more that Bram saw that people in VIM dev were like, this is cool.
[717.82 --> 718.50] We should have this.
[718.52 --> 721.14] And he was like, OK, I'll make one that works well for inside of him.
[721.22 --> 722.38] And then that's what he did.
[722.68 --> 722.82] Yeah.
[723.30 --> 727.50] And to that point, both of them have like async and other similar features.
[727.60 --> 729.92] But have they arrived there in different ways?
[729.92 --> 733.92] Like, is it different APIs or ways to like invoke async, for example?
[734.46 --> 734.72] Yes.
[734.82 --> 739.82] So to like start external jobs, the jobs APIs aren't compatible.
[740.06 --> 744.28] There are like plugins that sort of wrap them to make them very similar.
[744.58 --> 750.94] So you could like have one that's shared and you call my shared lib dot start job or whatever.
[751.14 --> 751.36] Right.
[751.40 --> 755.18] And you could be doing that and sort of experiencing working them in both.
[755.18 --> 757.60] But their implementations are different.
[757.90 --> 767.10] Like NeoVim is really focused a lot on building around like lib UV, which is the stuff that like I think Node, if I remember correctly, is built on top of.
[767.30 --> 769.72] Probably know about that in JS Party Land.