WEBVTT 00:00:00.000 --> 00:00:02.100 If you're listening to this as a podcast, remember 00:00:02.100 --> 00:00:04.679 that it was originally recorded as a video. If 00:00:04.679 --> 00:00:06.120 you're not following along, you can go to my 00:00:06.120 --> 00:00:08.720 YouTube channel. My username is Linkarzu. And 00:00:08.720 --> 00:00:10.460 if you want to support me to keep this podcast 00:00:10.460 --> 00:00:13.240 going, you can donate in Ko -Fi. I'm going to 00:00:13.240 --> 00:00:15.400 leave a link in the description. All right, so 00:00:15.400 --> 00:00:17.820 let's get started with this chapter then. Hey 00:00:17.820 --> 00:00:20.500 everyone, I have another guest today. It's a 00:00:20.500 --> 00:00:24.160 new BIM Core maintainer. Her name is Maria. How's 00:00:24.160 --> 00:00:27.660 it going, Maria? Doing good. Yeah, it's a Friday 00:00:27.660 --> 00:00:31.469 and happy to be here. Yeah, it's holidays. Is 00:00:31.469 --> 00:00:35.369 it holidays where you're at or no? Yeah, so I'm 00:00:35.369 --> 00:00:38.289 in Seattle and I mean, I don't have the day off 00:00:38.289 --> 00:00:40.649 of work or anything. So it's not really like 00:00:40.649 --> 00:00:44.310 it's Easter weekend, but we don't it's not a 00:00:44.310 --> 00:00:50.789 work holiday. OK, OK, wonderful. OK, so you currently 00:00:50.789 --> 00:00:54.649 work on Nioven, right? And the core team, would 00:00:54.649 --> 00:00:58.060 you like to share a little bit more about? Yeah, 00:00:58.179 --> 00:01:02.659 so I'm the kind of person that when I see that 00:01:02.659 --> 00:01:05.959 there's a bug in my plugin or even if it's outside 00:01:05.959 --> 00:01:10.340 the NeoVim ecosystem, if I know enough about 00:01:10.340 --> 00:01:13.739 the bug, I will try to fix it. And so I've made 00:01:13.739 --> 00:01:17.000 a lot of open source contributions like that. 00:01:17.140 --> 00:01:19.120 I think that that's the reason that I don't have 00:01:19.120 --> 00:01:22.480 like a single successful side project because 00:01:22.480 --> 00:01:25.310 I get... distracted with all of the tools that 00:01:25.310 --> 00:01:27.510 i'm using and then i i just end up contributing 00:01:27.510 --> 00:01:32.150 to like the editor or the lsp instead um but 00:01:32.150 --> 00:01:34.670 yes right now the main project that i'm i've 00:01:34.670 --> 00:01:37.790 been contributing for um for almost two years 00:01:37.790 --> 00:01:40.950 now or longer than that actually um has been 00:01:40.950 --> 00:01:45.489 november and yeah right now i'm working on a 00:01:45.489 --> 00:01:49.510 feature um and an lsp feature that i'm looking 00:01:49.510 --> 00:01:54.840 forward to okay wonderful Okay, so LSP related 00:01:54.840 --> 00:01:57.099 stuff. That's what you're currently working on. 00:01:57.159 --> 00:02:00.599 Any other stuff that you have worked on on Neovim 00:02:00.599 --> 00:02:05.239 directly? So something that's not LSP related. 00:02:05.939 --> 00:02:09.240 I've done some TreeSeeder stuff as well. That 00:02:09.240 --> 00:02:11.400 was actually my first contribution to Neovim 00:02:11.400 --> 00:02:15.840 was adding the query editor. And that was because 00:02:15.840 --> 00:02:18.520 I wanted to learn more about the TreeSeeder APIs. 00:02:18.740 --> 00:02:22.689 And then I thought that... contributing something 00:02:22.689 --> 00:02:28.129 that use those APIs would be great. And I say 00:02:28.129 --> 00:02:30.830 that sometimes my contributions are a bit selfish 00:02:30.830 --> 00:02:33.569 in that regard, that it's not that I just contribute 00:02:33.569 --> 00:02:36.770 for to make the world a better place. I do it 00:02:36.770 --> 00:02:39.729 because I want the feature myself or I just want 00:02:39.729 --> 00:02:41.889 to learn how to do something. And I'm like, well, 00:02:41.990 --> 00:02:45.330 while I learn, might as well give something back 00:02:45.330 --> 00:02:50.319 to the community. Yeah. Yeah. I would definitely 00:02:50.319 --> 00:02:53.740 do the same. If I contributed to something, it's 00:02:53.740 --> 00:02:56.199 because it's something that I want or that I 00:02:56.199 --> 00:03:01.259 need. So, yeah. Yeah, that's definitely a good 00:03:01.259 --> 00:03:04.680 motivation to have, to know that you also want 00:03:04.680 --> 00:03:08.120 that feature. Yeah, but it helps improve the 00:03:08.120 --> 00:03:11.740 product, right? So that keeps the product alive. 00:03:11.819 --> 00:03:14.460 Right, right, right, right. Busters innovations 00:03:14.460 --> 00:03:16.979 and all that stuff, okay? And for how long have 00:03:16.979 --> 00:03:25.310 you been using NeoVim? Like a couple of months 00:03:25.310 --> 00:03:27.889 before I started contributing to it. So I remember 00:03:27.889 --> 00:03:36.710 that it was around March of 2023, around that 00:03:36.710 --> 00:03:40.650 time. And the reason that I remember that it's 00:03:40.650 --> 00:03:42.949 because my birthday, it's in March. And I remember 00:03:42.949 --> 00:03:48.050 spending my, like around my birthday, just playing 00:03:48.050 --> 00:03:51.250 around with these gyros. And then I found Kickstart. 00:03:51.930 --> 00:03:55.969 And I remember spending an entire weekend just 00:03:55.969 --> 00:03:59.229 playing around with the Kickstarter configuration 00:03:59.229 --> 00:04:03.969 and being so overwhelmed of like, how do I configure 00:04:03.969 --> 00:04:07.389 this? How do I get the highlight name for this 00:04:07.389 --> 00:04:09.530 thing that I want to change? And I spent like 00:04:09.530 --> 00:04:12.250 an entire weekend trying to make the perfect 00:04:12.250 --> 00:04:15.469 editor. And I was so happy with it. But then 00:04:15.469 --> 00:04:18.350 I realized, gosh, I just spent an entire weekend 00:04:18.350 --> 00:04:20.610 on this. And I still feel that I have like no 00:04:20.610 --> 00:04:24.370 idea what, And I was also new to Vim Motions. 00:04:25.089 --> 00:04:28.949 And so I thought after that, I don't have time 00:04:28.949 --> 00:04:31.329 for this. I need an editor to actually like be 00:04:31.329 --> 00:04:36.310 productive at work. But it was kind of very funny 00:04:36.310 --> 00:04:39.370 because I spent almost like a month using Neoving 00:04:39.370 --> 00:04:42.290 during my free time and feeling addicted to it, 00:04:42.350 --> 00:04:44.810 but also realizing that I didn't have like enough 00:04:44.810 --> 00:04:47.410 time to tweak my configuration and all of that. 00:04:47.509 --> 00:04:50.970 And I tried going back to VS Code and I like... 00:04:51.319 --> 00:04:56.540 removed my .config .neovim files and removing 00:04:56.540 --> 00:05:00.079 my .files to me like I cannot do this again and 00:05:00.079 --> 00:05:03.639 then I would always go back and I spent months 00:05:03.639 --> 00:05:08.360 that my my keyboard skills and just like my muscle 00:05:08.360 --> 00:05:10.939 memory was broken because I was still not entirely 00:05:10.939 --> 00:05:14.319 used to the motions but I was not like able to 00:05:14.319 --> 00:05:16.939 use the mouse again and so I felt that I I just 00:05:16.939 --> 00:05:20.899 couldn't type anymore. But yeah, to answer that 00:05:20.899 --> 00:05:23.240 question, I guess it needs to be like three years. 00:05:23.959 --> 00:05:27.459 Okay. I do remember the first times that I met 00:05:27.459 --> 00:05:31.680 BIM, right? In servers. Right. And I didn't like 00:05:31.680 --> 00:05:34.899 it. I always say the same thing, you know? I 00:05:34.899 --> 00:05:37.459 was like, who uses this? And why did they go 00:05:37.459 --> 00:05:40.500 through all this trouble? And I just went back 00:05:40.500 --> 00:05:43.639 to Nano. I was like, no, I was a happy Nano user. 00:05:43.959 --> 00:05:47.519 But I just decided to learn it. It took me like... 00:05:47.920 --> 00:05:50.980 four times. I even created a blog post before 00:05:50.980 --> 00:05:55.480 I even started taking Vim seriously. So emotions 00:05:55.480 --> 00:05:58.420 and all the stuff that I wanted to learn, but 00:05:58.420 --> 00:06:01.740 I never did it. You know, I don't know why it 00:06:01.740 --> 00:06:06.079 happened, but I cannot go back now. Yeah, I think 00:06:06.079 --> 00:06:08.920 that the last thing that truly made me lead VS 00:06:08.920 --> 00:06:11.779 Code, which was my main editor before now Vim, 00:06:11.819 --> 00:06:16.500 was Copilot. I was just... so fed up that every 00:06:16.500 --> 00:06:19.199 single time that i would hit tab it would accept 00:06:19.199 --> 00:06:21.519 the copilot suggestion instead of like navigating 00:06:21.519 --> 00:06:25.000 the completion menu and i i have like a super 00:06:25.000 --> 00:06:27.800 tab setup that i use tab to navigate through 00:06:27.800 --> 00:06:31.019 the completions and also navigate through a snippet 00:06:31.019 --> 00:06:33.279 and so it's like a conditional tab that it depends 00:06:33.279 --> 00:06:36.920 on the context that i am that i'm on and so um 00:06:36.920 --> 00:06:40.079 that's something that a super top setup it's 00:06:40.079 --> 00:06:42.800 great in elven because you have full control 00:06:42.800 --> 00:06:45.560 over that but then in vs code when i was like 00:06:45.560 --> 00:06:49.240 i don't want compiler to be taking over all of 00:06:49.240 --> 00:06:51.939 my language features i just want to control this 00:06:51.939 --> 00:06:56.540 myself um so i think that yeah that was one of 00:06:56.540 --> 00:07:01.360 the that was like the last thing that truly made 00:07:01.360 --> 00:07:05.129 me get tired of vs code entirely Okay, okay. 00:07:05.269 --> 00:07:08.110 You mentioned distributions. You started with 00:07:08.110 --> 00:07:10.689 distributions, then you mentioned also Kickstart. 00:07:10.990 --> 00:07:16.209 What did you end up with? So I didn't really, 00:07:16.370 --> 00:07:20.610 I was never really a user of a full distribution. 00:07:20.769 --> 00:07:24.089 I am someone that I really like understanding 00:07:24.089 --> 00:07:26.930 how the configuration works and all of these 00:07:26.930 --> 00:07:30.860 distros hide. By design, they hide all of the 00:07:30.860 --> 00:07:32.680 details so that you don't need to worry about 00:07:32.680 --> 00:07:34.920 that. You just configure a couple of variables 00:07:34.920 --> 00:07:38.740 and then they deal with installing the necessary 00:07:38.740 --> 00:07:42.800 packages, installing the LSPs. But then I didn't 00:07:42.800 --> 00:07:47.500 like that black box experience. And so I decided 00:07:47.500 --> 00:07:50.899 to use Kickstarter instead. And that was definitely, 00:07:51.079 --> 00:07:54.259 I think, the best choice. I think that's the 00:07:54.259 --> 00:07:57.300 best way to get started with Nelvin. But what 00:07:57.300 --> 00:07:59.899 I did is that instead of just copy pasting the 00:07:59.899 --> 00:08:06.339 thousand long file, a thousand, that file with 00:08:06.339 --> 00:08:09.060 a thousand lines right now, that is huge. What 00:08:09.060 --> 00:08:12.420 I did instead is that I would, I created the 00:08:12.420 --> 00:08:16.100 file. I created my init .lua file and I would 00:08:16.100 --> 00:08:20.740 copy paste the snippets of kickstart as I learned 00:08:20.740 --> 00:08:23.519 what they did. And so instead of just like copy 00:08:23.519 --> 00:08:25.720 pasting the entire tree seeder code, I was like, 00:08:25.740 --> 00:08:29.360 okay. this starts tree seeder let me see like 00:08:29.360 --> 00:08:32.240 what does that mean and once i understood like 00:08:32.240 --> 00:08:34.879 okay this is like enabling tree seeder highlighting 00:08:34.879 --> 00:08:38.299 this is enabling indentation then at that point 00:08:38.299 --> 00:08:40.740 once i understood what that piece of this did 00:08:40.740 --> 00:08:43.940 at that point i would paste it into my configuration 00:08:43.940 --> 00:08:49.679 um and so that i followed that approach for a 00:08:49.679 --> 00:08:55.580 couple of weeks and then i Once I needed more 00:08:55.580 --> 00:08:58.360 than one file for my configuration, because my 00:08:58.360 --> 00:09:02.100 init .lua file was just huge, then that's when 00:09:02.100 --> 00:09:05.879 I got fancy and started importing modules and 00:09:05.879 --> 00:09:09.779 then creating a folder for my plugins and creating 00:09:09.779 --> 00:09:12.039 all of my setup. And since then, I've always 00:09:12.039 --> 00:09:15.779 maintained my own .files. Okay, you started with 00:09:15.779 --> 00:09:19.220 Kickstart then. Okay, and do you consider your... 00:09:19.710 --> 00:09:22.809 new VM setup done already or do you constantly 00:09:22.809 --> 00:09:28.570 tweak it? I think that it's pretty done. It's 00:09:28.570 --> 00:09:31.029 actually, I think that it is a very funny fact 00:09:31.029 --> 00:09:35.190 that my most popular repo on GitHub are my .files. 00:09:35.350 --> 00:09:37.450 I'm like, okay, I guess this is what I'm going 00:09:37.450 --> 00:09:41.389 to be known for. But yes, right now they're in 00:09:41.389 --> 00:09:43.789 a state where I'm pretty happy with the plugins 00:09:43.789 --> 00:09:47.470 that I have installed. And I'm not the kind of 00:09:47.470 --> 00:09:50.110 person that... If I see like a new plugin on 00:09:50.110 --> 00:09:52.590 Reddit, I will be like, okay, let me try it and 00:09:52.590 --> 00:09:55.330 like refactor my entire configuration. I'm like, 00:09:55.350 --> 00:09:58.370 no, like what I have, I'm pretty happy with what 00:09:58.370 --> 00:10:01.269 I currently have. So yeah, I think that it's 00:10:01.269 --> 00:10:03.870 pretty stable. Although I do have to say that 00:10:03.870 --> 00:10:06.549 I do miss those days when I was twinkering with 00:10:06.549 --> 00:10:09.769 my configuration all the time. Right now I almost 00:10:09.769 --> 00:10:11.990 want something to break so that I have an excuse 00:10:11.990 --> 00:10:15.429 to configure none of them again. Yeah, that's 00:10:15.429 --> 00:10:17.629 one thing with distributions, right? Depending 00:10:17.629 --> 00:10:20.149 on the person that manages that distribution, 00:10:20.450 --> 00:10:23.809 the one that I use is LazyVim, right? So I don't 00:10:23.809 --> 00:10:25.690 know how to pronounce it. Folky, Folk, everyone 00:10:25.690 --> 00:10:28.649 says it different, right? Yeah, I also don't 00:10:28.649 --> 00:10:31.070 know how to pronounce his name. Folky, yeah. 00:10:31.269 --> 00:10:35.110 Yeah, I call him Folky, but that's the way that 00:10:35.110 --> 00:10:37.470 I know about new plugins. That's the way that 00:10:37.470 --> 00:10:40.090 I learned, for example, about Blink, that CMP, 00:10:40.269 --> 00:10:43.710 because suddenly... my stuff was broken and i 00:10:43.710 --> 00:10:47.850 was like what's happening here right and i do 00:10:47.850 --> 00:10:50.389 have to say that a lot of the code that i use 00:10:50.389 --> 00:10:53.009 for my own configuration has just been inspired 00:10:53.009 --> 00:10:56.789 by folky because he he's basically like holding 00:10:56.789 --> 00:10:59.389 with our like neovim ecosystem on his shoulders 00:10:59.389 --> 00:11:06.230 um together with um mini plugins but but yeah 00:11:06.230 --> 00:11:11.509 i think that um yeah um i i've Definitely taking 00:11:11.509 --> 00:11:15.289 a lot of code from LazyVim in my own .files just 00:11:15.289 --> 00:11:19.629 because those are probably the nicest plugins 00:11:19.629 --> 00:11:24.490 that are worth trying out. Yeah, and if it's 00:11:24.490 --> 00:11:27.269 approved by Fonky, you know that it's going to 00:11:27.269 --> 00:11:30.389 be good. Yeah, for sure. Did you migrate already 00:11:30.389 --> 00:11:34.289 to Blink or you're still on NVIDIA? I did. Yeah, 00:11:34.330 --> 00:11:39.480 I did. I did migrate to Blink. To be entirely 00:11:39.480 --> 00:11:42.940 honest, I don't think that it is like much faster. 00:11:43.259 --> 00:11:47.759 I didn't migrate with the motivation of like, 00:11:47.940 --> 00:11:50.139 oh, it's Grittany Rust. It's going to be like 00:11:50.139 --> 00:11:53.080 super fast. I didn't have a performance issue 00:11:53.080 --> 00:11:57.779 with VMCMP. The main reason that I ended up switching, 00:11:57.860 --> 00:12:01.879 it's because it was making me a little bit worried 00:12:01.879 --> 00:12:05.299 to see that VMCMP wasn't being very much maintained. 00:12:05.600 --> 00:12:09.490 And there were like a lot of PRs. um with bug 00:12:09.490 --> 00:12:12.309 fixes and like performance improvements and the 00:12:12.309 --> 00:12:17.450 last change had been made months ago um and that's 00:12:17.450 --> 00:12:19.970 the reason that i think someone else opened magazine 00:12:19.970 --> 00:12:23.429 which is like a fork of mvmcmp but but with all 00:12:23.429 --> 00:12:26.230 of those prs merged so i was like yeah i don't 00:12:26.230 --> 00:12:30.149 like it when projects just like um look a bit 00:12:30.149 --> 00:12:34.029 dead right okay and how did it go with breaking 00:12:34.029 --> 00:12:38.259 changes blink and breaking changes I mean, so 00:12:38.259 --> 00:12:43.019 I'm a core maintainer and I build Neobim from 00:12:43.019 --> 00:12:46.899 source. And I remember like around the, it was 00:12:46.899 --> 00:12:49.279 like around two years ago, I remember there was 00:12:49.279 --> 00:12:53.659 like this bug in Neobim core, like the core C 00:12:53.659 --> 00:12:58.919 code that it would make Neobim segfault every 00:12:58.919 --> 00:13:01.559 couple of minutes. And that ended up happening 00:13:01.559 --> 00:13:04.480 like around a week. And it was like a bug in 00:13:04.480 --> 00:13:08.009 them. It got fixed. It's fine. But the reason 00:13:08.009 --> 00:13:10.889 I'm telling you this is because I build now them 00:13:10.889 --> 00:13:13.370 from source. I'm used to breaking changes. I'm 00:13:13.370 --> 00:13:16.110 used to sometimes I will build now them or update 00:13:16.110 --> 00:13:21.429 a plugin and stuff will break. I've even been 00:13:21.429 --> 00:13:23.769 the cause of some of those like breaking changes. 00:13:23.870 --> 00:13:27.009 And so I'm pretty comfortable with handling those. 00:13:28.389 --> 00:13:30.990 And often when that happens, I end up making 00:13:30.990 --> 00:13:34.799 the, if it's a fix that I know how to. uh resolve 00:13:34.799 --> 00:13:37.460 then i'll make the pre nail them or in the plugin 00:13:37.460 --> 00:13:42.139 itself interesting yeah yeah people tend to forget 00:13:42.139 --> 00:13:44.299 that blink i don't know if it's still in beta 00:13:44.299 --> 00:13:48.080 um but it yeah it's not in beta anymore i believe 00:13:48.080 --> 00:13:51.080 that the maintainer released version one a couple 00:13:51.080 --> 00:13:54.879 of weeks ago i think okay okay so we should expect 00:13:54.879 --> 00:13:57.980 uh less breaking changes but the few the past 00:13:57.980 --> 00:14:00.980 few months were a little bit crazy in that aspect 00:14:02.029 --> 00:14:04.409 It's a lot. Yeah. And I guess that with a district 00:14:04.409 --> 00:14:06.889 gets a bit harder because if there's a breaking 00:14:06.889 --> 00:14:10.389 change there, then, and if you're a LazyVim user, 00:14:10.490 --> 00:14:13.610 then you need to wait until Folky makes a change 00:14:13.610 --> 00:14:16.049 and Folky goes on vacation like every month. 00:14:16.389 --> 00:14:20.049 So it takes a while. Yeah. Yeah. I don't wait. 00:14:20.129 --> 00:14:22.690 I try to fix them myself because I configure 00:14:22.690 --> 00:14:25.710 LazyVim to update my plugins when I open it. 00:14:25.730 --> 00:14:27.929 Right. And that's a good thing and a bad thing. 00:14:28.360 --> 00:14:32.759 Because of breaking changes, it's bad. For sure. 00:14:33.320 --> 00:14:38.539 Yeah, okay. And where can people find you? Do 00:14:38.539 --> 00:14:41.419 you want to share about that a little bit? Yeah, 00:14:41.419 --> 00:14:43.240 for sure. Do you want to share your screen and 00:14:43.240 --> 00:14:49.779 just show your stuff? Yeah, so you can find me 00:14:49.779 --> 00:14:53.240 on GitHub. I'm not too active on like a lot of 00:14:53.240 --> 00:14:56.700 social media places, but... um you can follow 00:14:56.700 --> 00:15:01.039 my contributions to um now vim um right now let's 00:15:01.039 --> 00:15:06.139 see i think that i have a single pr open um but 00:15:06.139 --> 00:15:09.519 yes you can see like go there see what i'm working 00:15:09.519 --> 00:15:17.019 on um yeah i have those um i also have twitter 00:15:17.019 --> 00:15:21.820 or x or all of that um you can see my cat and 00:15:21.820 --> 00:15:27.029 myself um yeah i usually use like a variation 00:15:27.029 --> 00:15:29.649 of the same username in all of my social media 00:15:29.649 --> 00:15:36.509 so it is maria solos or maria solano os um but 00:15:36.509 --> 00:15:40.070 yeah a variation of that and you'll find me um 00:15:40.070 --> 00:15:44.929 i've also been very active on reddit um especially 00:15:44.929 --> 00:15:50.070 on the november subreddit and um i also have 00:15:50.070 --> 00:15:53.320 a couple of videos I've been a speaker at the 00:15:53.320 --> 00:15:55.820 Nailbeam conference during the last two years. 00:15:56.159 --> 00:16:00.580 So you can take a look at those videos as well. 00:16:01.360 --> 00:16:06.259 Interesting. Yeah, the first one. Yep. And are 00:16:06.259 --> 00:16:12.100 there any plans to keep creating videos or? So 00:16:12.100 --> 00:16:15.259 outside the Nailbeam conference videos, I did 00:16:15.259 --> 00:16:17.940 make a video about how I go around debugging 00:16:17.940 --> 00:16:21.809 my Nailbeam configuration using. the Lua debugger 00:16:21.809 --> 00:16:25.649 and that was just because people on Reddit were 00:16:25.649 --> 00:16:31.110 asking for it but not really I guess that I'm 00:16:31.110 --> 00:16:34.750 a bit camera shy and there's like a lot of work 00:16:34.750 --> 00:16:39.370 on video editing but I mean if maybe if a lot 00:16:39.370 --> 00:16:42.230 of people on Reddit go like crazy and say that 00:16:42.230 --> 00:16:44.590 they want more videos or like specific topics 00:16:44.590 --> 00:16:50.250 then I might create a couple more yeah but i 00:16:50.250 --> 00:16:52.210 don't think that i will join the cool kids and 00:16:52.210 --> 00:16:55.570 become a streamer anytime soon yeah it's yeah 00:16:55.570 --> 00:16:58.889 it's a lot of work because you basically have 00:16:58.889 --> 00:17:01.590 to run like a company you have to do everything 00:17:01.590 --> 00:17:06.349 it's right and i i don't even understand how 00:17:06.349 --> 00:17:10.910 twitch works like oh yeah like it is too much 00:17:10.910 --> 00:17:15.309 work and so um yeah yeah me neither i'm just 00:17:15.309 --> 00:17:20.009 used to youtube you know And I have no idea how 00:17:20.009 --> 00:17:24.630 Twitch works. And can you tell us a little bit 00:17:24.630 --> 00:17:28.210 more about the experience of maintaining open 00:17:28.210 --> 00:17:35.849 source? How do you feel about it? Yeah, so what 00:17:35.849 --> 00:17:40.470 I... So far, my experience with open source has 00:17:40.470 --> 00:17:44.609 only been with DevTooling. I used to work at 00:17:44.609 --> 00:17:46.970 Microsoft with the VS Code and TypeScript team, 00:17:47.069 --> 00:17:49.509 which are, of course, two open source projects, 00:17:49.809 --> 00:17:53.269 according to Microsoft's definition of open source. 00:17:54.029 --> 00:18:00.369 But I feel that with dev tooling, with every 00:18:00.369 --> 00:18:03.990 feature, I remember that the first piece of feedback 00:18:03.990 --> 00:18:06.950 that I would receive, it would be, how do I disable 00:18:06.950 --> 00:18:10.089 it? And so that's something that with dev tooling, 00:18:10.210 --> 00:18:12.730 you will never make a feature that will make 00:18:13.019 --> 00:18:16.019 everyone happy that will fit everyone's workflow 00:18:16.019 --> 00:18:19.420 and so i think that my experience with open source 00:18:19.420 --> 00:18:27.299 is that you you will need to um like have a very 00:18:27.299 --> 00:18:29.619 good self -esteem that sometimes you will receive 00:18:29.619 --> 00:18:31.579 negative feedback and people will be unhappy 00:18:31.579 --> 00:18:35.500 about um a feature and it's fine it's perfectly 00:18:35.500 --> 00:18:39.440 fine i think that my main goal when i make features 00:18:39.440 --> 00:18:42.180 to know them it's not making everyone already 00:18:42.180 --> 00:18:44.980 happy, although that does make me feel pretty 00:18:44.980 --> 00:18:48.380 good. But my main goal is what is Navim's core 00:18:48.380 --> 00:18:51.259 philosophy and make sure that those features 00:18:51.259 --> 00:18:54.460 stick to that. And so when I was working on VS 00:18:54.460 --> 00:18:59.519 Code and adding new features there, I wasn't 00:18:59.519 --> 00:19:02.819 thinking of, okay, but how does this fit into 00:19:02.819 --> 00:19:06.809 the VS Code editor? Like philosophy, it was more 00:19:06.809 --> 00:19:09.750 of like, what does suit Microsoft better? But 00:19:09.750 --> 00:19:12.269 with NelVim, I kind of want to know, okay, NelVim 00:19:12.269 --> 00:19:16.049 is very strict. And we truly believe that we 00:19:16.049 --> 00:19:18.509 should implement everything that the LSP says. 00:19:19.329 --> 00:19:22.250 And we don't want like an extra feature just 00:19:22.250 --> 00:19:25.230 because there's a nice plugin that does the same 00:19:25.230 --> 00:19:27.430 thing. But it's like, no, but the protocol doesn't 00:19:27.430 --> 00:19:32.710 say that we should do that. And so, yeah, like 00:19:32.710 --> 00:19:37.670 a good example for that. It is how I implemented 00:19:37.670 --> 00:19:42.869 the snippet engine. And the main motivation to 00:19:42.869 --> 00:19:46.450 do that is because we wanted to have native completion, 00:19:46.710 --> 00:19:52.549 which I also helped implement in port. And when 00:19:52.549 --> 00:19:54.809 I implemented that, a lot of people were saying, 00:19:54.890 --> 00:19:57.529 oh, can we also have third -party libraries and 00:19:57.529 --> 00:20:00.369 write our custom snippets that would be loaded 00:20:00.369 --> 00:20:04.240 by Delphi directly in? well that that was not 00:20:04.240 --> 00:20:06.980 the goal like we want snippets in order to be 00:20:06.980 --> 00:20:10.180 able to process snippets in completions when 00:20:10.180 --> 00:20:13.619 an lsp server sends that in the completion response 00:20:13.619 --> 00:20:17.380 um loading your custom snippets that would be 00:20:17.380 --> 00:20:20.480 part of an external library and we do have plans 00:20:20.480 --> 00:20:23.220 on exposing that api maybe in the future but 00:20:23.220 --> 00:20:28.099 um oh yeah would you mind explaining a little 00:20:28.099 --> 00:20:30.160 bit more then on that part of the snippet so 00:20:30.750 --> 00:20:34.250 I use my custom snippets. I use Lua Snip for 00:20:34.250 --> 00:20:39.390 that. So this is not what you're mentioning, 00:20:39.569 --> 00:20:41.970 right? It's something different. You mind just 00:20:41.970 --> 00:20:44.890 explaining it to me like I'm five years old so 00:20:44.890 --> 00:20:46.809 that I understand? I don't know if you want to 00:20:46.809 --> 00:20:49.549 share your screen and show it. Yeah, I can do 00:20:49.549 --> 00:20:56.150 that. And so let's see. So here is a PR in November. 00:20:56.230 --> 00:21:03.210 I added the snippet API. and so um the and actually 00:21:03.210 --> 00:21:08.690 let me open the snippet the documentation um 00:21:08.690 --> 00:21:20.549 maybe game segmentation for that but there we 00:21:20.549 --> 00:21:26.990 go so now vim has this minimal snippet api that 00:21:26.990 --> 00:21:32.509 it follows the um the grammar defined by the 00:21:32.509 --> 00:21:39.829 protocol, which is here, which looks very mathy, 00:21:39.910 --> 00:21:42.269 but basically you would be familiar with it if 00:21:42.269 --> 00:21:45.509 you've ever written your custom snippet in LuaSneak 00:21:45.509 --> 00:21:48.430 or in VS Code, where you have placeholders using 00:21:48.430 --> 00:21:55.529 the dollar sign and square braces. And yes, you 00:21:55.529 --> 00:21:58.470 would write your own snippets, and this is the 00:21:58.470 --> 00:22:03.369 grammar that... VS Code uses that the LSP uses. 00:22:03.710 --> 00:22:08.410 And so then the goal of this feature was to be 00:22:08.410 --> 00:22:12.029 able to process those custom snippets when an 00:22:12.029 --> 00:22:16.529 LSP server sends that from the editor. Right 00:22:16.529 --> 00:22:21.430 now, this API, it's only used in the editor when 00:22:21.430 --> 00:22:24.230 processing completion responses. And so, for 00:22:24.230 --> 00:22:26.470 example, if you have your custom snippets in 00:22:26.470 --> 00:22:30.579 your NetBean configuration, there would be nothing 00:22:30.579 --> 00:22:33.759 in the editor loading that file. And so there's 00:22:33.759 --> 00:22:39.539 currently no support for that there. I am aware, 00:22:39.759 --> 00:22:45.500 because I did try it out with LinkCMP, that LinkCMP 00:22:45.500 --> 00:22:49.079 is able to use this snippet API from Nelden, 00:22:49.240 --> 00:22:54.079 and it will also load your custom snippets that 00:22:54.079 --> 00:22:59.519 you have in your... inside your snippets folders 00:22:59.519 --> 00:23:03.119 in your runtime path. And so I do know that other 00:23:03.119 --> 00:23:07.619 third -party libraries have been able to use 00:23:07.619 --> 00:23:11.440 this. Okay, okay. So if I want to have my custom 00:23:11.440 --> 00:23:14.019 snippets, I continue to use lua -snip the way 00:23:14.019 --> 00:23:17.400 that I have been doing it, right? Yes. Well, 00:23:17.599 --> 00:23:23.539 you can actually not have lua -snip and have 00:23:23.539 --> 00:23:31.779 bling -cmp. Let me actually check that here. 00:23:32.319 --> 00:23:36.160 Oh, BlinkCMP has a documentation website. But 00:23:36.160 --> 00:23:42.500 you can also use BlinkCMP without having LulaSleep, 00:23:42.579 --> 00:23:47.640 and BlinkCMP will automatically load your snippets 00:23:47.640 --> 00:23:51.559 from config and theme snippets. Theme snippet, 00:23:51.559 --> 00:24:00.210 okay. Okay. Okay. Yep. i have used those um snippets 00:24:00.210 --> 00:24:02.490 that's what i was using actually i don't know 00:24:02.490 --> 00:24:06.490 i just migrated to lua snippets i wanted stuff 00:24:06.490 --> 00:24:10.450 really i don't know a lot of crazy stuff happening 00:24:10.450 --> 00:24:13.329 in my snippets so i guess that i i don't know 00:24:13.329 --> 00:24:16.829 i just moved uh to lua snippets yeah friendly 00:24:16.829 --> 00:24:19.910 snippets feels like an overkill to me um what 00:24:19.910 --> 00:24:28.690 i personally do is that i um So I do have a snippets 00:24:28.690 --> 00:24:32.690 folder. And I just, personally, I find that most 00:24:32.690 --> 00:24:38.109 LSPs have enough snippets. But I do find that 00:24:38.109 --> 00:24:41.609 TypeScript or TS Server in general doesn't have 00:24:41.609 --> 00:24:44.589 enough snippets in their own completions. And 00:24:44.589 --> 00:24:47.650 so these snippets that I have here are the ones 00:24:47.650 --> 00:24:53.690 that VS Code uses. And so instead of like... 00:24:54.109 --> 00:24:56.690 When I feel that the snippets that are in my 00:24:56.690 --> 00:25:00.529 completion menu don't feel great enough, I will 00:25:00.529 --> 00:25:02.710 say, like, okay, let me see what VS Code has 00:25:02.710 --> 00:25:08.069 over here. And VS Code has, like, the code for 00:25:08.069 --> 00:25:13.950 most LSPs in Microsoft VS Code, and it is inside 00:25:13.950 --> 00:25:17.549 extensions. And so here, if I go to TypeScript 00:25:17.549 --> 00:25:22.849 basics, here is where they have their snippets. 00:25:23.279 --> 00:25:26.680 And so I basically like copy pasted the snippets 00:25:26.680 --> 00:25:30.059 and the ones that I wanted. And this is the snippets 00:25:30.059 --> 00:25:33.940 following the grammar that I showed over here. 00:25:34.079 --> 00:25:37.839 And so that's why they work. Because Friendly 00:25:37.839 --> 00:25:41.759 Snippets has thousands, right? I know about Friendly 00:25:41.759 --> 00:25:45.579 Snippets because Folky loads them into Blink 00:25:45.579 --> 00:25:49.039 Blink, loads Friendly Snippets and Mailua Snip 00:25:49.039 --> 00:25:51.529 Snippets. So I have... a lot but i i get what 00:25:51.529 --> 00:25:54.650 you mean it has a lot those um friendly ones 00:25:54.650 --> 00:25:59.650 have tables anything you can imagine right great 00:25:59.650 --> 00:26:04.609 okay okay wonderful so um we already went over 00:26:04.609 --> 00:26:08.789 um the distribution you use your own config of 00:26:08.789 --> 00:26:11.289 course i noticed that the file explorer that 00:26:11.289 --> 00:26:14.470 you use is minidad files is that your yes preferred 00:26:14.470 --> 00:26:19.930 one yeah yeah i love mini files um When I first 00:26:19.930 --> 00:26:22.549 started using NeoVM, one of the first plugins 00:26:22.549 --> 00:26:25.730 that I installed was NeoTree because I felt like, 00:26:25.769 --> 00:26:29.250 well, I just need a Tree Explorer because that 00:26:29.250 --> 00:26:31.710 was the regular VS Code layout that I was using. 00:26:31.930 --> 00:26:35.890 Tree Explorer on the left, Terminal at the bottom. 00:26:37.509 --> 00:26:40.890 But then I was like, wait, I don't actually need 00:26:40.890 --> 00:26:44.210 to look at my File Explorer at the time. And 00:26:44.210 --> 00:26:47.809 a couple of months later, Minifiles came out. 00:26:48.960 --> 00:26:52.940 I was one of the first users. I loved it because 00:26:52.940 --> 00:26:55.819 I find that compared to, for example, with other 00:26:55.819 --> 00:27:00.839 buffer explorers like oil and then mini facets, 00:27:00.839 --> 00:27:04.240 like the perfect combination of having a buffer 00:27:04.240 --> 00:27:06.099 in the sense that you can still use like the 00:27:06.099 --> 00:27:10.579 motions inside that explorer, but you also have 00:27:10.579 --> 00:27:16.039 the intuitive tree structure. And so I really 00:27:16.039 --> 00:27:20.220 like that. So yes, mini files is definitely one 00:27:20.220 --> 00:27:23.319 of my favorite plugins. Okay. And the preview. 00:27:23.460 --> 00:27:26.059 That's one of the reasons. Yeah. Cause I always 00:27:26.059 --> 00:27:28.859 say that to me personally, meaning that files 00:27:28.859 --> 00:27:32.140 is like a mix between oil. Cause it allows me 00:27:32.140 --> 00:27:34.359 what you said. So use the motions everywhere 00:27:34.359 --> 00:27:39.579 and Neo tree, but with the telescope preview, 00:27:39.779 --> 00:27:42.819 it's like, I don't know. I don't actually use 00:27:42.819 --> 00:27:47.380 a preview. You have it disabled. Yeah. I don't. 00:27:48.400 --> 00:27:52.819 Yeah, I don't use a preview when I, and I also 00:27:52.819 --> 00:27:57.859 use FSLua. And so, for example, if in my file 00:27:57.859 --> 00:28:00.319 explorer, I don't have the preview enabled by 00:28:00.319 --> 00:28:04.539 default. But then if I tab through it, I can 00:28:04.539 --> 00:28:07.420 see it. But yeah, normally I don't find a preview 00:28:07.420 --> 00:28:10.660 to be very useful for my workflow personally. 00:28:11.400 --> 00:28:15.220 You have it disabled. Okay. Okay. Yeah. Interesting. 00:28:15.319 --> 00:28:18.329 Yeah, I do keep it enabled all the time. maybe 00:28:18.329 --> 00:28:21.829 for no reason well yeah sometimes i think i find 00:28:21.829 --> 00:28:25.170 it useful i'm like what is this file and i don't 00:28:25.170 --> 00:28:28.069 want to open it maybe i just want to yyp you 00:28:28.069 --> 00:28:30.269 know just duplicate the file or something i'm 00:28:30.269 --> 00:28:33.430 like oh okay yeah this is the file so i think 00:28:33.430 --> 00:28:36.930 i do i do like the preview and is that um from 00:28:36.930 --> 00:28:39.150 neotree then you switch to minidat files and 00:28:39.150 --> 00:28:40.930 that's the one that you use all the time now 00:28:40.930 --> 00:28:45.190 yes that's my preferred file explorer for sure 00:28:45.190 --> 00:28:49.900 okay and um what about your picker what do you 00:28:49.900 --> 00:28:55.299 use fcf lua yes um i was a telescope user and 00:28:55.299 --> 00:28:59.680 then um i was working the typescript code base 00:28:59.680 --> 00:29:04.099 and um you can see we go to microsoft typescript 00:29:04.099 --> 00:29:11.799 um sorry script um the moment that i switched 00:29:11.799 --> 00:29:17.470 to fslua was um When I had to navigate through 00:29:17.470 --> 00:29:22.950 this folder, which as you can see, like GitHub 00:29:22.950 --> 00:29:26.589 just builds because it has like more than 5 ,000 00:29:26.589 --> 00:29:31.089 files. And this was just a pain to use a file 00:29:31.089 --> 00:29:34.589 picker with. And I found FSLua to be so much 00:29:34.589 --> 00:29:39.130 faster. And the file picker is probably the one 00:29:39.130 --> 00:29:43.509 that I use the most. And I love it. And I think 00:29:43.509 --> 00:29:47.299 that the maintainer is, absolutely amazing um 00:29:47.299 --> 00:29:53.480 yeah and i i also use fslua for my code actions 00:29:53.480 --> 00:29:57.640 and so here my code action menu is there and 00:29:57.640 --> 00:30:00.940 i even have like a preview well i guess this 00:30:00.940 --> 00:30:05.140 code action doesn't have a preview um but let's 00:30:05.140 --> 00:30:12.559 see um i think that this one yeah so this one 00:30:13.519 --> 00:30:17.059 yeah so i do get a preview of what like the workspace 00:30:17.059 --> 00:30:19.079 edit that the code actually would apply would 00:30:19.079 --> 00:30:25.279 be okay and have you tried bulky's um snacks 00:30:25.279 --> 00:30:28.980 picker because he migrated all of us from telescope 00:30:28.980 --> 00:30:34.160 to fc and i was like i had some issues with fc 00:30:34.160 --> 00:30:37.000 of lua with images it i don't know it got stuck 00:30:37.000 --> 00:30:40.039 it was an issue on my side for sure skill issue 00:30:40.730 --> 00:30:43.309 And I don't know what else, what other issues 00:30:43.309 --> 00:30:48.390 I had. Going back to like our earlier topic on 00:30:48.390 --> 00:30:52.309 how my configuration is pretty much stable. And 00:30:52.309 --> 00:30:55.450 when there's like a new sensation already, everyone's 00:30:55.450 --> 00:30:58.509 like, oh, let's try this new thing. I know that 00:30:58.509 --> 00:31:00.789 everyone has been like creating new pickers and 00:31:00.789 --> 00:31:03.470 there's like snacks picker. And then there's 00:31:03.470 --> 00:31:07.230 mini picker, mini pick as well. And I did try 00:31:07.230 --> 00:31:09.150 mini pick. I thought that it was pretty nice, 00:31:09.210 --> 00:31:12.660 pretty minimal. um but i'm very happy with fslua 00:31:12.660 --> 00:31:17.380 um i'm also i like the fact that fsf it's also 00:31:17.380 --> 00:31:20.299 available on the terminal um outside nail them 00:31:20.299 --> 00:31:23.000 and i also use fsf natively and so it's nice 00:31:23.000 --> 00:31:25.480 to have this tool that i'm already familiar with 00:31:25.480 --> 00:31:29.220 outside nail them available in my editor okay 00:31:29.220 --> 00:31:31.619 yeah and it's a good point that you brought up 00:31:31.619 --> 00:31:35.119 there um People, I read in Reddit, you know, 00:31:35.140 --> 00:31:37.480 that people mentioned that they had issues with 00:31:37.480 --> 00:31:41.059 the telescope and big repos, right? You didn't 00:31:41.059 --> 00:31:44.099 have that problem with FCF Lua. I wonder how 00:31:44.099 --> 00:31:49.720 Snack Speaker works with that huge repo. If Alki 00:31:49.720 --> 00:31:53.400 uses it, I guess it must be all right. Yeah. 00:31:54.380 --> 00:31:57.059 Okay. And what color scheme was the one that 00:31:57.059 --> 00:32:01.069 you were showing on your screen? So I use a variation 00:32:01.069 --> 00:32:05.630 of Dracula and I maintain my own color scheme. 00:32:07.230 --> 00:32:11.930 But yeah, and this is actually like, I copy pasted 00:32:11.930 --> 00:32:14.670 most of the code of the Dracula and theme color 00:32:14.670 --> 00:32:17.309 theme. And then I made some variations of it. 00:32:17.890 --> 00:32:20.630 But anytime that I need to pick a color theme, 00:32:20.769 --> 00:32:24.450 I'll use Dracula. I do tend to use Dracula and 00:32:24.450 --> 00:32:26.490 then I tweak it to make the background darker. 00:32:27.930 --> 00:32:32.970 And so I'm, I'm very much a fan of Dracula. Okay. 00:32:33.130 --> 00:32:36.670 And do you have it in your .files? Or did you 00:32:36.670 --> 00:32:39.890 create a color scheme by a repo? Or it's just 00:32:39.890 --> 00:32:43.609 in your .files? It's just in my .files. And the 00:32:43.609 --> 00:32:47.869 reason I have it just here is because most color 00:32:47.869 --> 00:32:53.130 schemes would have overrides for most of the 00:32:53.130 --> 00:32:58.720 plugins. when you open a color scheme on repo 00:32:58.720 --> 00:33:00.900 you would see that they have the highlight groups 00:33:00.900 --> 00:33:06.740 for um snacks and blink and fslua and telescope 00:33:06.740 --> 00:33:09.579 and all of that and so here by just having it 00:33:09.579 --> 00:33:11.359 here i just have the groups that i'm interested 00:33:11.359 --> 00:33:15.279 on of the plugins that i'm actually using okay 00:33:15.279 --> 00:33:22.200 okay okay interesting okay and um what so moving 00:33:22.200 --> 00:33:25.130 on to to something else What tool do you use 00:33:25.130 --> 00:33:29.710 to push to versioning control? Do you use LazyGit 00:33:29.710 --> 00:33:34.450 or just terminal? LazyGit. I use LazyGit. I love 00:33:34.450 --> 00:33:38.190 LazyGit. Well, if I need to push, I will just 00:33:38.190 --> 00:33:42.289 use native GitHub commands. But I think LazyGit 00:33:42.289 --> 00:33:46.390 is great. It's actually, there's a funny story 00:33:46.390 --> 00:33:49.150 behind it. So I guess that I can show you too. 00:33:50.369 --> 00:33:55.990 So here. um let me open new them and so here 00:33:55.990 --> 00:33:59.529 opening gaze lazy gets and maybe zooming out 00:33:59.529 --> 00:34:05.609 a bit yeah so you see these numbers beside like 00:34:05.609 --> 00:34:09.550 status and files and local branches like the 00:34:09.550 --> 00:34:13.449 one two three and four and so that's because 00:34:13.449 --> 00:34:16.610 if you press one you navigate to that one so 00:34:16.610 --> 00:34:18.469 it's like the labels of the keys that you need 00:34:18.469 --> 00:34:20.570 to press in order to navigate through those things 00:34:21.260 --> 00:34:24.320 And so I added that feature to Lazy Git. And 00:34:24.320 --> 00:34:27.320 that has been the only feature that I've added 00:34:27.320 --> 00:34:31.099 to Lazy Git. My only experience with Go, because 00:34:31.099 --> 00:34:36.039 Lazy Git is great in Go. And yeah, I did add 00:34:36.039 --> 00:34:39.780 that feature. I added the feature without even 00:34:39.780 --> 00:34:44.559 installing Go LSP or Go LS, because I knew that 00:34:44.559 --> 00:34:47.969 I wouldn't become a... a go developer anytime 00:34:47.969 --> 00:34:50.309 soon and i didn't want to do all of that setup 00:34:50.309 --> 00:34:54.989 just for this one feature um but yeah i i think 00:34:54.989 --> 00:35:01.090 that lazy git is great um let me just maybe open 00:35:01.090 --> 00:35:04.130 the pr real fast yeah yeah go ahead i use that 00:35:04.130 --> 00:35:08.369 all the time i use two um so i always press two 00:35:08.369 --> 00:35:10.969 to go to my files that's the one that is the 00:35:10.969 --> 00:35:14.170 most or three as well to go to the branches two 00:35:14.170 --> 00:35:18.260 three Or, yeah, the numbers. And the reason that 00:35:18.260 --> 00:35:20.960 I ended up adding the feature, it's because, 00:35:21.039 --> 00:35:24.980 you know, as your regular dot file tweaker, I 00:35:24.980 --> 00:35:27.280 was really happy with LazyGit. But then I thought, 00:35:27.380 --> 00:35:30.380 let me see if there's something else, something 00:35:30.380 --> 00:35:33.480 different, something better. And there's like 00:35:33.480 --> 00:35:36.179 a LazyGit that's written in Rust. It's called 00:35:36.179 --> 00:35:40.639 Git to UI. And I didn't really like it. Yeah, 00:35:40.699 --> 00:35:43.659 I didn't really like it more, but I did like 00:35:43.659 --> 00:35:45.940 that feature of having the numbers because I 00:35:45.940 --> 00:35:47.920 would always forget, like, which is the number 00:35:47.920 --> 00:35:50.139 that I need to press in order to go to that pane. 00:35:50.679 --> 00:35:54.519 And so I ended up adding the feature, well, opening 00:35:54.519 --> 00:35:58.960 the issue and then adding the feature to PlacingIt. 00:35:59.480 --> 00:36:02.239 And when you have a feature like this one, for 00:36:02.239 --> 00:36:04.480 example, do you usually just submit the code 00:36:04.480 --> 00:36:06.820 or you have a discussion with the maintainer 00:36:06.820 --> 00:36:09.269 first? Because sometimes they will not accept 00:36:09.269 --> 00:36:13.690 them, right? Right. And so usually I always start 00:36:13.690 --> 00:36:16.389 by creating a new issue and saying like, do you 00:36:16.389 --> 00:36:19.289 think that this feature makes sense in your repo? 00:36:19.389 --> 00:36:22.469 It aligns with your goals and like your philosophy. 00:36:23.230 --> 00:36:27.110 And so, and I even said like, I don't even know 00:36:27.110 --> 00:36:29.389 if this is already supported and this is just 00:36:29.389 --> 00:36:31.329 a skill issue and I haven't read the manual. 00:36:32.809 --> 00:36:37.679 But yeah, at that point. The maintainer of Lazy 00:36:37.679 --> 00:36:40.699 Gate told me like, yeah, go for it. And they 00:36:40.699 --> 00:36:44.380 were super nice. They were even like telling 00:36:44.380 --> 00:36:50.179 me exactly what to do. And they were super nice. 00:36:50.800 --> 00:36:54.559 I was also telling them, I don't know if it's 00:36:54.559 --> 00:36:59.960 somewhere in the discussion here. Yeah, maybe 00:36:59.960 --> 00:37:05.510 not here, but. I also did this in my first NLVM 00:37:05.510 --> 00:37:07.449 PR. There's a lot of people that are afraid to 00:37:07.449 --> 00:37:10.010 open that first PR because they say like, oh, 00:37:10.030 --> 00:37:12.369 I've never contributed to an open source project 00:37:12.369 --> 00:37:14.289 and I don't know how Git works. And I'm like, 00:37:14.329 --> 00:37:18.090 just go for it, people. I used to be the kind 00:37:18.090 --> 00:37:21.030 of person that if I had a merge conflict, I would 00:37:21.030 --> 00:37:24.489 delete the entire repo and clone it again. And 00:37:24.489 --> 00:37:27.610 it was via my open source contributions that 00:37:27.610 --> 00:37:31.880 I stopped being scared of Git. And I think that 00:37:31.880 --> 00:37:37.480 it's perfectly fine to just open the PR and ask 00:37:37.480 --> 00:37:41.139 maintainers like, hey, tests are failing and 00:37:41.139 --> 00:37:44.000 I don't know why. Or can you help me with this? 00:37:44.059 --> 00:37:48.460 I'm not very familiar with Go. I mean, I did 00:37:48.460 --> 00:37:52.360 this just right here. Like, hey, I'm having issues 00:37:52.360 --> 00:37:56.460 reading this setting. And then I get this error 00:37:56.460 --> 00:38:01.969 when running Go run. Oh, yeah. And it was kind. 00:38:02.170 --> 00:38:07.150 Okay. Interesting. That's good to know. And to 00:38:07.150 --> 00:38:09.809 get, you know, if there's people that want to, 00:38:09.829 --> 00:38:12.789 I saw a Reddit post the other day. I don't know 00:38:12.789 --> 00:38:15.389 if you saw it or not. People asking, like, what 00:38:15.389 --> 00:38:20.230 is needed to start contributing to NeoVim? Well, 00:38:20.309 --> 00:38:22.190 I don't know if you have any idea or not, but 00:38:22.190 --> 00:38:25.070 what would you recommend to someone that wants 00:38:25.070 --> 00:38:28.730 to get started contributing to NeoVim? I would 00:38:28.730 --> 00:38:33.050 say. If you don't know what you want, if you 00:38:33.050 --> 00:38:34.949 just want to contribute and you don't have a 00:38:34.949 --> 00:38:38.230 specific feature that you would like to work 00:38:38.230 --> 00:38:43.789 on, try to look for an open issue. And I would 00:38:43.789 --> 00:38:49.369 say before you jump right away into the implementation, 00:38:49.750 --> 00:38:54.730 try to think in your mind, like, okay, if I want 00:38:54.730 --> 00:38:58.730 this, which code would I need to modify? Where 00:38:58.730 --> 00:39:02.210 does the implementation live? and just read through 00:39:02.210 --> 00:39:06.469 the code base um and once you have like a a rough 00:39:06.469 --> 00:39:08.829 idea in your mind like okay i would need to add 00:39:08.829 --> 00:39:14.570 this function to this file then open a pr and 00:39:14.570 --> 00:39:19.510 open a draft pr so and these might be like a 00:39:19.510 --> 00:39:23.150 controversial topic um but i think that i prefer 00:39:23.150 --> 00:39:26.889 to open a draft pr with maybe just updating the 00:39:26.889 --> 00:39:29.230 documentation of what i'm adding just to make 00:39:29.230 --> 00:39:32.409 sure that other people know that there's already 00:39:32.409 --> 00:39:34.909 someone working on that issue because it would 00:39:34.909 --> 00:39:36.909 suck that you start working on this and then 00:39:36.909 --> 00:39:39.230 a couple of days later someone else starts working 00:39:39.230 --> 00:39:41.449 on that and then it's like okay which implementation 00:39:41.449 --> 00:39:44.889 do we keep so it's it's a good idea to open the 00:39:44.889 --> 00:39:47.809 draft pr just to tell i'm interested in working 00:39:47.809 --> 00:39:51.610 on this if you later decide not to finish it 00:39:51.610 --> 00:39:53.690 because it ends up being more complicated than 00:39:53.690 --> 00:39:56.429 you initially thought it's perfectly fine to 00:39:56.429 --> 00:39:59.369 do that i've Sometimes I will open a PR and be 00:39:59.369 --> 00:40:01.670 like, I abandoned it. Someone please take over. 00:40:02.190 --> 00:40:06.030 And that's fine. But yeah, I would say going 00:40:06.030 --> 00:40:10.769 through open issues, sometimes we add labels 00:40:10.769 --> 00:40:15.389 of difficulty, easy, or good for first -time 00:40:15.389 --> 00:40:19.429 contributors. So you can also try filtering by 00:40:19.429 --> 00:40:22.789 those. Okay, interesting. Yeah, so if it's a 00:40:22.789 --> 00:40:25.449 draft, if you open a draft, PR is just a draft. 00:40:26.409 --> 00:40:29.030 Um, you can get feedback there, right? Hey, don't 00:40:29.030 --> 00:40:31.309 work on this or yeah, we're interested in this 00:40:31.309 --> 00:40:34.590 or no, no, no. Right. Okay. Good idea. Okay. 00:40:34.690 --> 00:40:40.690 Okay. And, um, are you a T -Mox fan or no, there's 00:40:40.690 --> 00:40:44.889 just two sides of it. I, so it's not that I'm 00:40:44.889 --> 00:40:47.969 not a fan. Um, I just, I've never used it. I've 00:40:47.969 --> 00:40:51.489 never had the need to use it. Um, I use ghosty 00:40:51.489 --> 00:40:54.530 right now. I used to be a Western user. Um, Western 00:40:54.530 --> 00:40:56.829 is great. I'm happy with ghosting right now. 00:40:56.969 --> 00:41:00.630 Um, but normally my workflow is that I would, 00:41:00.630 --> 00:41:05.289 I will have a single tab per folder that I'm 00:41:05.289 --> 00:41:08.690 working on. And then if I, for example, sometimes 00:41:08.690 --> 00:41:13.469 I will have them open. Um, yeah, that would be 00:41:13.469 --> 00:41:17.769 a good idea. And so here, um, what I do is that 00:41:17.769 --> 00:41:21.739 I prefer to run terminal commands. directly from, 00:41:21.800 --> 00:41:25.099 like, another split instead of from nilvim directly. 00:41:25.519 --> 00:41:29.179 From the nilvim terminal. Right. And so here, 00:41:29.480 --> 00:41:33.539 yeah, I guess that I can just run make doc. And 00:41:33.539 --> 00:41:36.920 then I would have nilvim here open. And so this 00:41:36.920 --> 00:41:40.559 is usually my regular workflow. I will have a 00:41:40.559 --> 00:41:45.199 tab for working directory. And then I will usually 00:41:45.199 --> 00:41:49.659 have nilvim open and then a terminal if I need 00:41:49.659 --> 00:41:53.920 to. Okay. So each tab for you is a project, right? 00:41:53.980 --> 00:41:56.900 Like one tab is your files. Another tab is any 00:41:56.900 --> 00:41:59.099 of them. I don't know core feature you're working 00:41:59.099 --> 00:42:01.280 on. Another tab is, I don't know, a personal 00:42:01.280 --> 00:42:05.820 project. So exactly. Yeah. Okay. Interesting. 00:42:06.000 --> 00:42:10.239 And any of them you, um, to open multiple files, 00:42:10.360 --> 00:42:12.500 I noticed that you don't have tabs at the top. 00:42:12.539 --> 00:42:15.440 Oh yeah. You do have tabs right at the top. Yeah. 00:42:15.539 --> 00:42:20.750 I do use, um, a buffer line for, um, my buffers 00:42:20.750 --> 00:42:26.650 yeah okay okay okay got it and um okay thanks 00:42:26.650 --> 00:42:30.489 for sharing that what else do we have here i 00:42:30.489 --> 00:42:33.630 don't think we have any other well let's talk 00:42:33.630 --> 00:42:36.090 about technical stuff first let's just cover 00:42:36.090 --> 00:42:38.510 all of those i noticed that you're using mac 00:42:38.510 --> 00:42:44.630 os um is there a reason why so i i also have 00:42:44.630 --> 00:42:48.429 a framework laptop and um I use Linux. I'm an 00:42:48.429 --> 00:42:52.349 Arch Linux user as well. The reason that I'm 00:42:52.349 --> 00:42:56.030 using macOS for this call is because I don't, 00:42:56.030 --> 00:42:59.690 I mean, I've done some videos with my Linux setup, 00:42:59.829 --> 00:43:03.789 but given that I'm screen sharing and camera 00:43:03.789 --> 00:43:07.489 and all of this, I just prefer to use macOS and 00:43:07.489 --> 00:43:12.130 be safe. Then, yeah, you know, Linux can be a 00:43:12.130 --> 00:43:15.679 bit flaky with all of those. Okay, so Arch is 00:43:15.679 --> 00:43:19.199 your main one then, right? For development, yes. 00:43:19.480 --> 00:43:23.960 For work, I do use macOS. Okay, you jump between 00:43:23.960 --> 00:43:27.059 the two. Okay, interesting. Yeah, and I personally 00:43:27.059 --> 00:43:30.440 prefer Linux much more. Yeah, if I could use 00:43:30.440 --> 00:43:34.300 Linux for everything, it would be great. I also 00:43:34.300 --> 00:43:37.179 tried the best of both worlds of Asahi Linux. 00:43:39.039 --> 00:43:42.920 And I used the Fedora distribution that they 00:43:42.920 --> 00:43:46.699 had. It worked nicely. But again, there were 00:43:46.699 --> 00:43:49.760 issues with screen sharing and I couldn't use 00:43:49.760 --> 00:43:56.079 my Apple monitor. And then the main maintainer 00:43:56.079 --> 00:43:59.239 of that project kind of left open source entirely. 00:43:59.679 --> 00:44:04.860 So yeah, it's not going great. Oh yeah, I asked 00:44:04.860 --> 00:44:06.880 yesterday. I did a live stream yesterday and 00:44:06.880 --> 00:44:10.179 I asked the two Discord friends that joined what 00:44:10.179 --> 00:44:13.789 they thought about Asahi. I have... I did follow 00:44:13.789 --> 00:44:16.730 the project. I never installed it. But, yeah, 00:44:16.849 --> 00:44:19.510 it's, you know, you can use the Apple hardware. 00:44:19.750 --> 00:44:24.829 It's a Linux distro. Yeah. Yeah. And I do have 00:44:24.829 --> 00:44:29.449 to say that Framework has been great. And I really 00:44:29.449 --> 00:44:33.769 love Arch Linux. And right now, Asahi doesn't 00:44:33.769 --> 00:44:38.250 have Arch Linux support anymore. So, yeah. Okay. 00:44:38.409 --> 00:44:41.869 Okay. The Framework laptops. Okay. Yeah. Why 00:44:41.869 --> 00:44:44.010 did you decide to go with the framework? Because 00:44:44.010 --> 00:44:46.670 usually it's those frameworks. I've seen it a 00:44:46.670 --> 00:44:53.889 lot lately and System76. Yeah. So I had seen 00:44:53.889 --> 00:44:59.150 very positive reviews of framework. The CEO of 00:44:59.150 --> 00:45:02.090 framework used to work at Apple. And so I feel 00:45:02.090 --> 00:45:05.110 that framework laptops do have that feeling of 00:45:05.110 --> 00:45:11.119 a Mac. When I wanted to install Art Linux, I 00:45:11.119 --> 00:45:14.780 did buy a ThinkPad and it just feels too rough. 00:45:15.320 --> 00:45:20.159 I think pads are great, but my first computer 00:45:20.159 --> 00:45:24.940 was a MacBook and I've been using Apple laptops 00:45:24.940 --> 00:45:27.059 all of my life. And so I'm used to that, like 00:45:27.059 --> 00:45:30.579 how delicate they feel. And I think that just 00:45:30.579 --> 00:45:33.360 felt like a brick. And so I think that frameworks 00:45:33.360 --> 00:45:37.460 are a great balance of that MacBook feeling with 00:45:37.460 --> 00:45:42.900 a laptop that can still run Linux natively. Okay. 00:45:43.000 --> 00:45:46.340 Okay. Interesting. What are your thoughts on 00:45:46.340 --> 00:45:50.719 the other operating system, Windows? I hate Windows. 00:45:51.000 --> 00:45:54.139 I mean, as I mentioned, I used to work at Microsoft 00:45:54.139 --> 00:46:01.429 and Windows sucks. I hate the fact that... the 00:46:01.429 --> 00:46:03.690 PowerShell, not PowerShell, but like the command 00:46:03.690 --> 00:46:08.230 line, you cannot LS. So it's not even POSIX commands. 00:46:08.389 --> 00:46:12.190 You need to use dir. And so I really hate that. 00:46:13.210 --> 00:46:15.449 Same with PowerShell. I'm like, yeah, PowerShell 00:46:15.449 --> 00:46:17.469 might be great and you have all of these powerful 00:46:17.469 --> 00:46:22.750 functions, but I need to use LS. And yeah, I 00:46:22.750 --> 00:46:27.309 really don't like Windows in that regard. It's 00:46:27.309 --> 00:46:32.219 too slow. It's too ugly. I do think that some 00:46:32.219 --> 00:46:34.900 of the most nostalgic sounds ever are like the 00:46:34.900 --> 00:46:38.420 Windows Vista from the early 2000s, like when 00:46:38.420 --> 00:46:43.019 you're turning on a Windows machine. But yes, 00:46:43.099 --> 00:46:48.539 I am not a fan of Windows at all. Yeah, I don't 00:46:48.539 --> 00:46:51.039 do it on purpose. Every guest that I have had 00:46:51.039 --> 00:46:54.619 so far is not into Windows. Elijah, he's the 00:46:54.619 --> 00:46:57.280 creator of Harper, the Harper language server, 00:46:57.480 --> 00:46:59.789 which is like a grammarly alternative. It was 00:46:59.789 --> 00:47:03.530 like, I don't like Windows. Nobody in this development 00:47:03.530 --> 00:47:08.590 environment likes Windows, actually. But I guess 00:47:08.590 --> 00:47:12.909 I haven't had any Windows. And game developers 00:47:12.909 --> 00:47:16.690 probably love Windows, for sure. I do have to 00:47:16.690 --> 00:47:20.550 say that I did a lot of work with Visual Studio. 00:47:20.869 --> 00:47:27.530 In Visual Studio, Windows is very powerful in 00:47:27.530 --> 00:47:30.710 the sense that it allows it exposes a lot of 00:47:30.710 --> 00:47:33.150 operating system specifics to other applications. 00:47:33.929 --> 00:47:36.730 And so, for example, from Visual Studio, when 00:47:36.730 --> 00:47:42.409 we have new features, the day that those get 00:47:42.409 --> 00:47:46.030 released is by using feature flags that get registered 00:47:46.030 --> 00:47:49.110 in the Windows registry. And so that's basically 00:47:49.110 --> 00:47:52.409 like a binary flag that's like, I don't know, 00:47:52.510 --> 00:47:57.420 new copilot feature. And then... that's written 00:47:57.420 --> 00:48:01.179 to the Windows registry from Visual Studio and 00:48:01.179 --> 00:48:03.460 that's written in red. It's like you have this 00:48:03.460 --> 00:48:08.860 ID that's using this API to hook up into a registry 00:48:08.860 --> 00:48:13.219 that's only accessible via COM APIs. I think 00:48:13.219 --> 00:48:15.980 that that's pretty cool how you can do a lot 00:48:15.980 --> 00:48:23.289 of hacky stuff from Visual Studio itself. It's 00:48:23.289 --> 00:48:25.869 also definitely like shooting yourself in the 00:48:25.869 --> 00:48:27.710 foot. You can imagine the kind of bugs that you 00:48:27.710 --> 00:48:29.869 sometimes encounter when you have like the super 00:48:29.869 --> 00:48:33.469 powerful API that exposes so much operating system 00:48:33.469 --> 00:48:36.630 information to like other applications. Yeah. 00:48:37.289 --> 00:48:40.210 Yeah, that's a good point. But I don't know about 00:48:40.210 --> 00:48:42.329 you. I spend most of the day in the terminal 00:48:42.329 --> 00:48:46.690 and I cannot work on the Windows terminal. Of 00:48:46.690 --> 00:48:49.489 course, there's stuff like WSL, but still you're 00:48:49.489 --> 00:48:52.880 virtualizing Linux there and it's slower. yeah 00:48:52.880 --> 00:48:56.980 yeah okay for sure do you use a special tool 00:48:56.980 --> 00:49:01.000 for note -taking or how do you take notes um 00:49:01.000 --> 00:49:08.099 i use obs and yeah i yeah yeah not obvious um 00:49:08.099 --> 00:49:12.920 um yes i use obsidian um i use it like for my 00:49:12.920 --> 00:49:17.260 grocery shopping um notes and um not a huge note 00:49:17.260 --> 00:49:20.059 taker um i used to have like lots of agendas 00:49:20.059 --> 00:49:22.829 but then i would forget about the agenda and 00:49:22.829 --> 00:49:25.530 i would need a note to remember to take notes 00:49:25.530 --> 00:49:29.449 um but yes like when i need to take notes i will 00:49:29.449 --> 00:49:33.969 be succeeding okay okay wonderful and uh how 00:49:33.969 --> 00:49:37.010 many minutes do you have left because we still 00:49:37.010 --> 00:49:39.570 have a few questions we can end that we can finish 00:49:39.570 --> 00:49:42.610 the call here if you if you want to i'm happy 00:49:42.610 --> 00:49:46.050 to stay here like for another 10 minutes okay 00:49:46.050 --> 00:49:50.960 okay I'm just going to ask, let me see the most 00:49:50.960 --> 00:49:57.559 important ones and we can wrap it up. Is there 00:49:57.559 --> 00:49:59.900 any one of these that you would like to discuss? 00:50:00.820 --> 00:50:05.400 I guess that I can share about my keyboard. Okay, 00:50:05.539 --> 00:50:12.780 okay, okay, okay. I've been using a Moonlander 00:50:12.780 --> 00:50:17.829 keyboard. It's been like almost a year since 00:50:17.829 --> 00:50:21.730 I used it. I used to just use the trackpad and 00:50:21.730 --> 00:50:26.150 like the keyboard on my laptops. But then I started 00:50:26.150 --> 00:50:29.130 noticing that I would get a bit of pain using 00:50:29.130 --> 00:50:31.489 the trackpad. So a lot of people say that it's 00:50:31.489 --> 00:50:33.449 like the keyboard itself. For me, it was most 00:50:33.449 --> 00:50:36.409 using the mouse. And I was like watching all 00:50:36.409 --> 00:50:38.909 of these. Like I still watch his videos. I think 00:50:38.909 --> 00:50:42.349 he's hilarious. Prime's videos. And I thought 00:50:42.349 --> 00:50:45.389 that it looks like. It looks very cool when someone 00:50:45.389 --> 00:50:48.610 uses a split keyboard. And so I got the Moonlander. 00:50:49.909 --> 00:50:52.190 It is one of the best purchases that I've ever 00:50:52.190 --> 00:50:55.389 made. I think that it's great. I also, I don't 00:50:55.389 --> 00:50:57.090 know if you saw it, but I have like the rainbow 00:50:57.090 --> 00:51:00.449 colors. So it makes me feel like, I don't know, 00:51:00.510 --> 00:51:04.690 it makes me feel great. So yeah, I'm very happy 00:51:04.690 --> 00:51:06.489 with the Moonlander. I would totally recommend 00:51:06.489 --> 00:51:09.869 it. When did you get it? Around a year ago. I 00:51:09.869 --> 00:51:14.590 remember that I got it on May of last year. okay 00:51:14.590 --> 00:51:18.650 it did take a while to get used to yeah um because 00:51:18.650 --> 00:51:22.429 especially with the thumb clusters um it is weird 00:51:22.429 --> 00:51:26.150 to start using your thumbs when typing um but 00:51:26.150 --> 00:51:29.570 i think it's it's great i take it to work i take 00:51:29.570 --> 00:51:32.889 it everywhere when i travel as well so yeah i 00:51:32.889 --> 00:51:35.349 was also deciding you know i was thinking about 00:51:35.349 --> 00:51:38.630 this one that i got is the glove 80 but i was 00:51:38.630 --> 00:51:41.260 thinking about the moonlander the glove 80 or 00:51:41.260 --> 00:51:44.099 the one that prime uses and i was like yeah the 00:51:44.099 --> 00:51:47.579 kinesis yeah i cannot afford more than one of 00:51:47.579 --> 00:51:50.920 these my wife would kill me if i come and tell 00:51:50.920 --> 00:51:54.139 her i need to buy another one so i don't know 00:51:54.139 --> 00:51:56.659 i went with this one i have no experience with 00:51:56.659 --> 00:51:58.260 the other ones i don't know how good they are 00:51:58.260 --> 00:52:04.659 or not yeah okay and um we don't have much time 00:52:04.659 --> 00:52:08.019 um left anymore you mentioned that you used uh 00:52:08.829 --> 00:52:13.989 ghosty ai we don't need to cover this uh oh last 00:52:13.989 --> 00:52:17.010 thing do you want to share three or your favorite 00:52:17.010 --> 00:52:23.429 neobim plugins yeah for sure um so let me maybe 00:52:23.429 --> 00:52:29.730 open my dot files to make sure that i um don't 00:52:29.730 --> 00:52:37.530 miss any of these um so three i would say that 00:52:38.059 --> 00:52:42.639 FS Lua, for sure. I think it's the best picker 00:52:42.639 --> 00:52:48.059 ever. Very customizable. Then I would say Nini 00:52:48.059 --> 00:52:50.659 Files, for sure. That would be the second one. 00:52:52.079 --> 00:52:56.199 And then I also really like Flash from Polki. 00:52:56.420 --> 00:52:59.280 And so I know that there are a lot of people 00:52:59.280 --> 00:53:05.769 that have opinions regarding... like using these 00:53:05.769 --> 00:53:08.590 kind of motion plugins instead of using like 00:53:08.590 --> 00:53:11.969 F and like the native ones from Beanmotions. 00:53:12.170 --> 00:53:15.829 But I think that Flash is great. One of my favorite 00:53:15.829 --> 00:53:19.409 things about Flash is, for example, what it calls 00:53:19.409 --> 00:53:26.250 remote motions, I guess. So here, when I'm in 00:53:26.250 --> 00:53:29.409 pending mode, and so if I want to, for example, 00:53:29.510 --> 00:53:33.090 like yank, and so that's like in pending mode 00:53:33.090 --> 00:53:35.840 because it's waiting for... like the motion for 00:53:35.840 --> 00:53:41.360 the jack and so if at that point i press um uppercase 00:53:41.360 --> 00:53:46.019 r that will start flash and so here i think this 00:53:46.019 --> 00:53:49.119 one would be better so say that i want to paste 00:53:49.119 --> 00:53:53.679 tree cedar search the string inside the parentheses 00:53:53.679 --> 00:53:56.840 of the remote and so i would say yank capital 00:53:56.840 --> 00:54:01.190 r and then I would use Flash to select the thing 00:54:01.190 --> 00:54:03.230 that I want to paste. And so I want to select 00:54:03.230 --> 00:54:06.170 TreeSeeder search. So at this point, I press 00:54:06.170 --> 00:54:12.269 L and I say around quotes and paste. Oh. And 00:54:12.269 --> 00:54:14.869 that's pretty cool because it allows you, because 00:54:14.869 --> 00:54:18.309 otherwise I would need to like. Jump there. Here 00:54:18.309 --> 00:54:23.550 and then go back and then paste. And so I find 00:54:23.550 --> 00:54:27.480 that to be pretty cool. And I definitely use 00:54:27.480 --> 00:54:31.820 that a lot with Flash. That is wonderful. Yeah, 00:54:31.900 --> 00:54:34.500 it did take me a very long time to learn how 00:54:34.500 --> 00:54:38.599 to, like, how it works. Because Folky does document 00:54:38.599 --> 00:54:41.599 it, but you really need to understand, like, 00:54:41.699 --> 00:54:44.840 what does that remoteness mean? But once you 00:54:44.840 --> 00:54:48.679 get it, I think it's great. Yeah. Yeah, good 00:54:48.679 --> 00:54:51.000 point. Because I jump. Let's say that I need 00:54:51.000 --> 00:54:54.000 to copy something. I jump. BI quotes, you know. 00:54:54.519 --> 00:54:58.139 Or I quotes to copy it and then I jump back to 00:54:58.139 --> 00:55:01.400 where I was pasted. Exactly. Makes you save a 00:55:01.400 --> 00:55:04.500 lot of time. OK, wonderful. OK, so we don't have 00:55:04.500 --> 00:55:07.119 much time. Do you have any final words before 00:55:07.119 --> 00:55:11.420 we end the call? Anything you want to say? No, 00:55:11.619 --> 00:55:13.739 I think that I've shared everything that I had 00:55:13.739 --> 00:55:16.579 in mind. This was great. Thanks for having me 00:55:16.579 --> 00:55:20.170 again. OK, wonderful. Thanks to you for showing 00:55:20.170 --> 00:55:22.449 up. And if there's someone still watching, if 00:55:22.449 --> 00:55:24.969 you like these type of videos, remember, let 00:55:24.969 --> 00:55:27.269 me know that in the comments, like the video 00:55:27.269 --> 00:55:31.030 as well. So that tells me, OK, they liked it 00:55:31.030 --> 00:55:33.889 or not. I'll share it in Reddit as well. Maria, 00:55:34.010 --> 00:55:37.010 if you're OK with that. And yeah, for sure. OK, 00:55:37.090 --> 00:55:39.349 we're going to see what people say. OK, so thanks 00:55:39.349 --> 00:55:42.210 for stopping by. Till the next time. Thanks to 00:55:42.210 --> 00:55:43.730 you. A good one.