WEBVTT 00:00:00.000 --> 00:00:02.660 what are the brazilian guys gonna say brazil 00:00:02.660 --> 00:00:06.719 mentioned you're destroying new i want to know 00:00:06.719 --> 00:00:13.980 what you think about this emux man this has been 00:00:13.980 --> 00:00:17.019 like uh this has been actually fun because you're 00:00:17.019 --> 00:00:19.160 doing the question the right question in the 00:00:19.160 --> 00:00:23.079 right time me as a terminal user yep i don't 00:00:23.079 --> 00:00:26.460 care but i do understand the pain that terminal 00:00:26.460 --> 00:00:30.170 maintainers go through with T -MUX, I just want 00:00:30.170 --> 00:00:33.210 to hear your thoughts. It's helpful. It helps 00:00:33.210 --> 00:00:38.189 you see where you're at, right? At least to me, 00:00:38.210 --> 00:00:41.590 it helps me see. It's a cosmetic, man. Let's 00:00:41.590 --> 00:00:45.329 not lie here. It just makes everything feel better. 00:00:45.469 --> 00:00:48.450 Let's put it that way. I think that is like a 00:00:48.450 --> 00:00:52.750 big mistake of Nelby in general. Like, people 00:00:52.750 --> 00:00:55.229 don't really care. They don't really want to 00:00:55.229 --> 00:00:58.130 spend, you know, like, polishing. Like, too much 00:00:58.130 --> 00:01:02.009 stuff. It's like it's a no -ending cycle. Like, 00:01:02.009 --> 00:01:04.670 you just keep finding new stuff. And then you 00:01:04.670 --> 00:01:07.010 develop this mentality where you actually start 00:01:07.010 --> 00:01:09.150 to think about plugins all the time and, you 00:01:09.150 --> 00:01:11.430 know, seek for plugins. I don't want to be the 00:01:11.430 --> 00:01:13.930 guy that criticizes that. But you did. Because... 00:01:13.930 --> 00:01:17.109 No, I did. And I will keep doing it. But it's 00:01:17.109 --> 00:01:19.870 like... Maybe I have something against VS Code. 00:01:19.930 --> 00:01:24.109 I don't know. But it's like... But... No, I think... 00:01:24.109 --> 00:01:26.769 I think VS Code comes from... You're ashamed? 00:01:27.439 --> 00:01:30.200 You're ashamed that people see you using VS Code. 00:01:30.359 --> 00:01:32.480 Is that it? If you're listening to this as a 00:01:32.480 --> 00:01:34.859 podcast, remember that it was originally recorded 00:01:34.859 --> 00:01:37.180 as a video. If you're not following along, you 00:01:37.180 --> 00:01:39.159 can go to my YouTube channel. My username is 00:01:39.159 --> 00:01:41.400 Linkarzu. And if you want to support me to keep 00:01:41.400 --> 00:01:43.900 this podcast going, you can donate in Ko -Fi. 00:01:44.000 --> 00:01:45.500 I'm going to leave a link in the description. 00:01:45.859 --> 00:01:47.939 All right. So let's get started with this chapter 00:01:47.939 --> 00:01:51.659 then. What do we have today? We have Rafa here 00:01:51.659 --> 00:01:54.840 with us. He's the creator of the Rio Terminal. 00:01:55.019 --> 00:01:58.790 How's it going, Rafa? Good. Excited to be here. 00:01:59.150 --> 00:02:04.069 Okay. Thanks for your time. Thanks for sharing 00:02:04.069 --> 00:02:09.110 with us about Rio. You mind just letting us know 00:02:09.110 --> 00:02:13.689 what Rio is? I tried it a few days ago. Well, 00:02:13.689 --> 00:02:17.129 no, a few months ago. We talked on Twitter. Not 00:02:17.129 --> 00:02:20.310 sure if you remember. I remember, yeah. Yeah? 00:02:20.590 --> 00:02:24.349 I do remember. You want to share about Rio? What 00:02:24.349 --> 00:02:28.379 is it? Yeah, RIO is like a terminal emulator. 00:02:28.539 --> 00:02:33.719 It's like KT and Ghosty and Elacrid. Actually, 00:02:33.719 --> 00:02:36.580 RIO is like built from a lot of stuff from Elacrid, 00:02:36.659 --> 00:02:41.419 like originally. And, you know, like there's 00:02:41.419 --> 00:02:43.719 so many actually terminal emulators everywhere, 00:02:44.039 --> 00:02:46.759 right? Like it's hard to, it's like a browser. 00:02:46.900 --> 00:02:51.830 There's like every little one. And I think that 00:02:51.830 --> 00:02:55.090 this is a very exciting thing about emulators 00:02:55.090 --> 00:02:57.789 in general, because you can choose the one that 00:02:57.789 --> 00:03:03.569 you feel that you are more attached to or connected 00:03:03.569 --> 00:03:11.770 to. It's like browsers. I choose my browser because 00:03:11.770 --> 00:03:18.400 I have this memory attachment from my past. But 00:03:18.400 --> 00:03:23.740 in the same way, it is supposed to get the terminal 00:03:23.740 --> 00:03:26.199 emulator at the end of the day with the basic 00:03:26.199 --> 00:03:33.180 emulator functionalities. Okay. So it's just, 00:03:33.319 --> 00:03:37.960 well, it is a terminal emulator then. And why 00:03:37.960 --> 00:03:42.259 the name Rio? Man, this is actually a funny question 00:03:42.259 --> 00:03:45.419 because like... I was thinking about this these 00:03:45.419 --> 00:03:48.479 days, like, people are often associated with 00:03:48.479 --> 00:03:52.800 Rio from my city, like Rio de Janeiro. But, and 00:03:52.800 --> 00:03:57.599 kind of is, is kind of, like, the story is almost 00:03:57.599 --> 00:04:00.699 there, but actually has a bit more. I was going 00:04:00.699 --> 00:04:05.919 to marry, like, or was going to fly to Brazil, 00:04:05.960 --> 00:04:09.439 like, in that time, but I could not go due to, 00:04:09.539 --> 00:04:11.659 like, some immigration stuff. I was waiting for 00:04:11.659 --> 00:04:15.479 my visa to go out. And then back in time, the 00:04:15.479 --> 00:04:18.920 emulator had another name. It was like Ox. Ox 00:04:18.920 --> 00:04:23.420 is like a reserved word. And someone was just 00:04:23.420 --> 00:04:27.540 like, yeah, I need to rename this. And I thought, 00:04:27.540 --> 00:04:30.199 I bought Hue actually as a placeholder because 00:04:30.199 --> 00:04:33.240 we could not buy tickets to Hue. I literally 00:04:33.240 --> 00:04:36.879 could not buy tickets to Hue to fly. And I thought 00:04:36.879 --> 00:04:38.839 like, okay, we'll just put this as a joke. And 00:04:38.839 --> 00:04:43.029 then it remained there. I never really changed 00:04:43.029 --> 00:04:47.709 it back to any other thing. So I wanted to do 00:04:47.709 --> 00:04:50.410 the things that Goldfee and Alacrit does, you 00:04:50.410 --> 00:04:53.670 know, the TTY. I thought that was actually cool 00:04:53.670 --> 00:04:56.930 to do, but I kind of got attached to that for 00:04:56.930 --> 00:04:59.629 a while. Like, it worked for a few months with 00:04:59.629 --> 00:05:01.910 that name, which is like, you don't see that 00:05:01.910 --> 00:05:04.069 thing with a different name, right? It didn't 00:05:04.069 --> 00:05:09.050 end up being that way. Real. So it's related 00:05:09.050 --> 00:05:13.240 to Brazil then, right? Yeah, it's from my hometown, 00:05:13.399 --> 00:05:17.680 yeah. Rio de Janeiro. Brazil mentioned, like, 00:05:17.699 --> 00:05:20.339 the prime minister. Yeah, exactly. With the flag. 00:05:20.360 --> 00:05:24.139 Yeah, he went there in, I think he went for Sao 00:05:24.139 --> 00:05:26.740 Paulo. A few friends of mine met him. It was 00:05:26.740 --> 00:05:30.019 very nice, like, that he went there. Oh, yeah. 00:05:30.120 --> 00:05:34.939 I did see that. It was at Turso Convention or 00:05:34.939 --> 00:05:38.540 something. I don't remember what it was. I think 00:05:38.540 --> 00:05:41.660 actually they made, I don't know the whole story, 00:05:41.680 --> 00:05:46.680 so it could be actually not being, like someone 00:05:46.680 --> 00:05:48.699 could correct me later, but I thought that they 00:05:48.699 --> 00:05:51.399 actually built the whole thing for him, you know, 00:05:51.480 --> 00:05:55.279 like was the whole conference like just about 00:05:55.279 --> 00:05:57.839 him or something like that. I don't know the 00:05:57.839 --> 00:06:00.439 whole story, but I thought it was that. Okay, 00:06:00.639 --> 00:06:05.220 okay. And Lua, what language is it written in? 00:06:05.879 --> 00:06:11.360 I'm sorry, Lua. Rio. Yeah, Lua is from... Brazil 00:06:11.360 --> 00:06:15.620 mentioned again. Yeah. And Nelvin as well. Nelvin. 00:06:15.839 --> 00:06:19.699 And Htop. Like, I joke with, like, a few people 00:06:19.699 --> 00:06:23.560 from Charm that if you use terminals, it's very 00:06:23.560 --> 00:06:26.879 likely that you use, like, a Brazilian, like, 00:06:26.899 --> 00:06:31.439 stack. Yeah. Because, like, yeah, Nelvin starts 00:06:31.439 --> 00:06:36.339 from, like, a few Brazilians as well. but it's 00:06:36.339 --> 00:06:41.980 built in Rust and yeah, like, you know, everyone 00:06:41.980 --> 00:06:44.759 has opinions about Rust, like positive or negative. 00:06:46.019 --> 00:06:49.660 Oh, and why did you choose Rust? Is it because 00:06:49.660 --> 00:06:55.899 of performance reasons or? Yeah, I always liked 00:06:55.899 --> 00:07:02.790 Rust, like, I think I had been... you know people 00:07:02.790 --> 00:07:06.629 say that they're google fanboy apple fanboy i 00:07:06.629 --> 00:07:09.610 think i always has been a mozilla fanboy like 00:07:09.610 --> 00:07:13.050 since i started my career like i use it firefox 00:07:13.050 --> 00:07:16.370 because i like it then like so when they started 00:07:16.370 --> 00:07:18.430 a new language i thought like oh one day i'm 00:07:18.430 --> 00:07:22.329 gonna give it a try and i i like it the fact 00:07:22.329 --> 00:07:25.870 that they did a lot of things open and i don't 00:07:25.870 --> 00:07:28.790 know how is now, like, it's not like I have been 00:07:28.790 --> 00:07:31.889 following them that much, like, now, but, like, 00:07:31.889 --> 00:07:35.949 when they started developing Rust, I was following 00:07:35.949 --> 00:07:40.370 Rust very close, but I never used it, because 00:07:40.370 --> 00:07:43.449 I was working with other languages, like Python, 00:07:43.810 --> 00:07:51.170 JavaScript, Ruby, and, like, in my life came 00:07:51.170 --> 00:07:54.250 opportunity to work with Rust in the work, so 00:07:54.250 --> 00:07:57.560 I thought, like, well, Let's just write real 00:07:57.560 --> 00:08:02.040 projects in Rust, like in my free time, to learn 00:08:02.040 --> 00:08:04.620 the language. So I started to write in the Game 00:08:04.620 --> 00:08:07.420 Boy emulator that also runs in the terminal. 00:08:09.139 --> 00:08:13.899 And after the Game Boy, I kind of had a taste 00:08:13.899 --> 00:08:19.019 of, you know, you learn about registers and how 00:08:19.019 --> 00:08:23.000 the things work, the CPU, the memory, the GPU. 00:08:23.899 --> 00:08:25.740 And then you're just like, man, I actually want 00:08:25.740 --> 00:08:27.939 to keep going that way. And then I wanted to 00:08:27.939 --> 00:08:30.819 do something that uses GPU, but was not just 00:08:30.819 --> 00:08:35.700 GPU -based. And I kind of clicked it when I was 00:08:35.700 --> 00:08:39.559 using Kitty. And I was just like, oh, I could 00:08:39.559 --> 00:08:41.700 do something like that. So I started to work 00:08:41.700 --> 00:08:47.279 on here because of that. Okay. So Rust started 00:08:47.279 --> 00:08:50.320 it. You were using Kitty at that time when you 00:08:50.320 --> 00:08:54.370 decided to start with it. i actually use it all 00:08:54.370 --> 00:08:58.269 the terminals i'd say like it's it's true like 00:08:58.269 --> 00:09:02.009 uh i use it a bit of everything like it's kind 00:09:02.009 --> 00:09:04.590 of like we're joke i was joking with you before 00:09:04.590 --> 00:09:07.009 we recorded that you have ghosty and kitty as 00:09:07.009 --> 00:09:09.929 well right yeah but i i can't relate i could 00:09:09.929 --> 00:09:12.330 have all the terminals installed the mainstream 00:09:12.330 --> 00:09:17.429 and i mean i work for charm so it's like uh it's 00:09:17.429 --> 00:09:19.649 also i need to test things in different terminals 00:09:19.649 --> 00:09:22.309 but before work for them i had all the terminals 00:09:22.309 --> 00:09:25.990 i think that is it's like they're fantastic like 00:09:25.990 --> 00:09:29.009 piece of software to be honest like uh it's almost 00:09:29.009 --> 00:09:31.149 like pokemon you need you need to catch them 00:09:31.149 --> 00:09:36.169 all yeah definitely yeah i started with iterm 00:09:36.169 --> 00:09:39.970 i don't have iterm installed anymore no but then 00:09:39.970 --> 00:09:42.870 i moved to alacrity i don't have alacrity installed 00:09:42.870 --> 00:09:47.740 anymore But I have now Ghosty, Kitty, Western, 00:09:48.000 --> 00:09:52.019 Rio I have it installed as well. What else? Rio 00:09:52.019 --> 00:09:57.259 mentioned. Yeah, Brazil mentioned. Which ones 00:09:57.259 --> 00:10:00.200 do you use? Which terminals? Which is your main 00:10:00.200 --> 00:10:04.620 one? Is it Rio? It is Rio. I mean, it would be 00:10:04.620 --> 00:10:07.440 weird if I maintained Rio and didn't use it as 00:10:07.440 --> 00:10:13.629 the main one. But I think I use Rio. 95 percent 00:10:13.629 --> 00:10:18.610 or 98 percent but often when i'm developing stuff 00:10:18.610 --> 00:10:21.529 like for example now i'm developing box characters 00:10:21.529 --> 00:10:26.490 like to be draw like as ghosting alacrity does 00:10:26.490 --> 00:10:30.230 and kitty does so in these moments i actually 00:10:30.230 --> 00:10:32.730 opened all the terminals because i need to compare 00:10:32.730 --> 00:10:37.330 like how how they do and how i want to do so 00:10:37.330 --> 00:10:42.200 like i think in like um maybe at charm as well 00:10:42.200 --> 00:10:47.159 i do but it's not also like if you work with 00:10:47.159 --> 00:10:49.259 terminals like for example if you work for charm 00:10:49.259 --> 00:10:53.179 you also need to give a very good compatibility 00:10:53.179 --> 00:10:56.039 support so you need to test a lot of things in 00:10:56.039 --> 00:10:59.779 apple terminal like you cannot just ignore those 00:10:59.779 --> 00:11:04.720 terminals so you have to take the apple terminal 00:11:04.720 --> 00:11:08.620 and also iterm into account Yeah, I didn't have, 00:11:08.700 --> 00:11:11.820 like, actually, I tried to use everything, so, 00:11:11.919 --> 00:11:15.360 like, I see what's good from which and try to 00:11:15.360 --> 00:11:19.340 take a bit. I think my favorite outside of him 00:11:19.340 --> 00:11:25.620 has been Ghosty, but I think, like, I have a 00:11:25.620 --> 00:11:29.519 different view from Mishu, which is a great guy, 00:11:29.559 --> 00:11:32.539 by the way. Like, when he started, like, the 00:11:32.539 --> 00:11:34.860 terminal, he reached it out by email. I didn't 00:11:34.860 --> 00:11:38.700 know who he was. And it was funny because everyone 00:11:38.700 --> 00:11:43.419 knew him. I talked about him in the conference 00:11:43.419 --> 00:11:46.100 one time and then people were like, oh, so you're 00:11:46.100 --> 00:11:48.039 friends with Hashimoto. And I was just like, 00:11:48.179 --> 00:11:52.379 how do you guys know him? I came from a different 00:11:52.379 --> 00:11:56.000 background. I didn't know. I came from front 00:11:56.000 --> 00:12:00.740 end. So I was like, what's going on? And I used 00:12:00.740 --> 00:12:05.240 to work with Beckham early in my career. It was 00:12:05.240 --> 00:12:09.379 like a long time ago. So I used to float back 00:12:09.379 --> 00:12:13.720 end, front end. I did a bit of working data analysis. 00:12:13.860 --> 00:12:18.539 Like, I like to switch. So in that time of my 00:12:18.539 --> 00:12:20.539 career, I was working back end. And then people 00:12:20.539 --> 00:12:24.059 thought, like, I didn't know who he was. And 00:12:24.059 --> 00:12:26.139 then, you know, he reached out. I thought that 00:12:26.139 --> 00:12:28.539 he was just like, you know, a random guy. Then 00:12:28.539 --> 00:12:31.120 I used to talk with him. And then suddenly everyone 00:12:31.120 --> 00:12:33.320 was, you know, like, oh, this guy, like, really 00:12:33.320 --> 00:12:36.580 famous and blah, blah, blah. But, you know, it 00:12:36.580 --> 00:12:39.019 never appeared to me that he was that way. Oh, 00:12:39.120 --> 00:12:42.960 yeah. You were not aware of the HashiCorp products? 00:12:43.019 --> 00:12:46.059 Yeah, no, I never connected those things. Like, 00:12:46.059 --> 00:12:48.899 I learned it actually in the conference. Oh, 00:12:48.980 --> 00:12:51.700 okay. I sent a message to him actually after 00:12:51.700 --> 00:12:53.259 that. I was just like, dude, you're actually 00:12:53.259 --> 00:12:57.710 pretty famous. Like, he didn't even know. Okay, 00:12:57.830 --> 00:13:02.529 that's a funny story. Okay. Why did he reach 00:13:02.529 --> 00:13:06.870 out to talk about terminals? He sent an email. 00:13:07.309 --> 00:13:09.990 I think someone, because he tweeted something 00:13:09.990 --> 00:13:13.570 about his terminal back in time. And someone 00:13:13.570 --> 00:13:18.210 told him, do you know Rio? And then he was like, 00:13:18.429 --> 00:13:23.740 no, I have used Rio and I like it. I'm going 00:13:23.740 --> 00:13:28.179 to try to talk with the developer up here. And 00:13:28.179 --> 00:13:31.000 then, I don't know, I think I had my email public. 00:13:31.100 --> 00:13:33.200 I don't remember the whole story. This was made 00:13:33.200 --> 00:13:38.080 a few years ago. And he sent an email with a 00:13:38.080 --> 00:13:42.419 few paragraphs. And I told him, dude, let's just 00:13:42.419 --> 00:13:47.399 talk into Discord. And so I started to just talk 00:13:47.399 --> 00:13:50.960 about Ervinos and what we thought was cool and 00:13:50.960 --> 00:13:54.090 how... I think that is the thing actually that 00:13:54.090 --> 00:13:57.289 is missing a bit more in the universe of terminals. 00:13:57.549 --> 00:14:01.090 There's like this collab between terminal alters. 00:14:01.750 --> 00:14:05.529 Because like there's so much specs that we could 00:14:05.529 --> 00:14:08.250 be working together and everyone is doing kind 00:14:08.250 --> 00:14:12.470 of their own protocol. Like now Kitty is developing 00:14:12.470 --> 00:14:17.429 their own phone protocol. And I think it's... 00:14:17.629 --> 00:14:20.529 is great but also i was working something similar 00:14:20.529 --> 00:14:24.769 to that that looks a bit different so it you 00:14:24.769 --> 00:14:28.110 know kind of like it's just like i feel the kind 00:14:28.110 --> 00:14:32.450 of needs like this how come all each other sometimes 00:14:32.450 --> 00:14:35.789 the collaboration so you don't do the same thing 00:14:35.789 --> 00:14:39.289 over and over right yeah and and also discuss 00:14:39.289 --> 00:14:41.710 right you have this in the web like with the 00:14:41.710 --> 00:14:45.529 working group or committee the people state and 00:14:45.529 --> 00:14:48.750 they go, I like this idea, or this idea is not 00:14:48.750 --> 00:14:52.710 good. Before you actually add protocols, like 00:14:52.710 --> 00:14:55.629 you start to validate with people. I don't know, 00:14:55.710 --> 00:14:58.629 like, because if you get quick traction, like 00:14:58.629 --> 00:15:00.610 sometimes the things just stay there forever, 00:15:00.850 --> 00:15:03.789 then like all the terminals just are going to 00:15:03.789 --> 00:15:06.690 implement because everybody's asking. So I don't 00:15:06.690 --> 00:15:10.529 know. I see. Yeah, so if the feature becomes 00:15:10.529 --> 00:15:13.830 popular. all of the other terminals are going 00:15:13.830 --> 00:15:16.409 to implement it and probably create a version 00:15:16.409 --> 00:15:21.110 when you could use something common, all of the 00:15:21.110 --> 00:15:25.070 terminals, right? Yeah. Yeah. I mean, something 00:15:25.070 --> 00:15:28.529 in that line of thought, right? Like we could 00:15:28.529 --> 00:15:33.230 go do more things together. I don't know. But 00:15:33.230 --> 00:15:37.830 I think also that every terminal emulator developer, 00:15:38.009 --> 00:15:43.350 they also kind of, they, like day on on day on 00:15:43.350 --> 00:15:46.230 sometimes like the profiles that I have on top 00:15:46.230 --> 00:15:50.289 of my mind is like They they're pretty much developing 00:15:50.289 --> 00:15:53.690 stuff alone. And then it's also I understand 00:15:53.690 --> 00:15:59.169 them as well a bit like that. So I I think it's 00:15:59.169 --> 00:16:05.190 complicated And isn't there like a discord? Channel 00:16:05.190 --> 00:16:08.289 where all the terminal guys are where you can 00:16:08.289 --> 00:16:12.159 talk. No, there's not Yeah, someone from Charm 00:16:12.159 --> 00:16:17.139 told me that there is this place where people 00:16:17.139 --> 00:16:21.980 discuss stuff. I haven't tried, to be honest. 00:16:22.179 --> 00:16:27.059 And I feel like I didn't know if they had the 00:16:27.059 --> 00:16:30.980 terminal. Because sometimes, I think it's like, 00:16:31.120 --> 00:16:34.399 sometimes people, they have the idea that it 00:16:34.399 --> 00:16:36.779 would be good to have. Like, they come with their 00:16:36.779 --> 00:16:39.529 own protocol. but without the real understanding 00:16:39.529 --> 00:16:45.210 of how a terminal emulator works. And it's like, 00:16:45.289 --> 00:16:50.769 for example, Accurate. I understand why they 00:16:50.769 --> 00:16:53.629 never developed the image protocols. You hear 00:16:53.629 --> 00:16:57.049 everyone asking for it. Yeah, I was asking for 00:16:57.049 --> 00:17:02.259 it as well. Yeah, because in some way... if you 00:17:02.259 --> 00:17:05.019 if you develop your own render in the terminal 00:17:05.019 --> 00:17:07.480 and later you see that they they have like the 00:17:07.480 --> 00:17:12.700 architecture and they part particularities uh 00:17:12.700 --> 00:17:16.480 where they base the the like i i know when i 00:17:16.480 --> 00:17:18.819 entered like in the technical approach of it 00:17:18.819 --> 00:17:22.420 was like to add something as the image protocol 00:17:22.420 --> 00:17:25.140 like you need to change stuff and that's how 00:17:25.140 --> 00:17:28.980 ghosty also adapted how they do stuff like because 00:17:29.829 --> 00:17:32.430 you need to actually revamp your architecture 00:17:32.430 --> 00:17:36.849 to do that and you're gonna pay performance it's 00:17:36.849 --> 00:17:40.049 like i think one thing that hashimoto talks that 00:17:40.049 --> 00:17:43.410 i like that i like you know his article was like 00:17:43.410 --> 00:17:47.170 when he people are comparing alacrit and his 00:17:47.170 --> 00:17:50.130 terminal he says like yeah sure like but in the 00:17:50.130 --> 00:17:52.269 same way the more stuff you add for the terminal 00:17:52.269 --> 00:17:56.150 like it's likely that you're gonna i mean sure 00:17:56.150 --> 00:18:00.000 it's gonna be fast but it's like not necessarily 00:18:00.000 --> 00:18:02.759 going to be faster than something that does the 00:18:02.759 --> 00:18:06.420 simple job so it's like if you if you have like 00:18:06.420 --> 00:18:11.240 a really small module that just procs that process 00:18:11.240 --> 00:18:16.359 text like so takes that text and you know plots 00:18:16.359 --> 00:18:19.920 on the screen like just rendering how that's 00:18:19.920 --> 00:18:24.839 gonna be faster than like um i don't know something 00:18:24.839 --> 00:18:27.680 that deals with images ui everything like it 00:18:27.680 --> 00:18:31.130 does so the more features you're actually asking 00:18:31.130 --> 00:18:33.950 like oh i want to have like all ligatures i want 00:18:33.950 --> 00:18:36.430 to have this so you're going to end up paying 00:18:36.430 --> 00:18:39.890 price for it because like it's how it works and 00:18:39.890 --> 00:18:42.630 you can of course optimize the terminal to be 00:18:42.630 --> 00:18:45.690 really fast you could like write a lot of logic 00:18:45.690 --> 00:18:50.210 like you use like parallel processing scene everything 00:18:50.210 --> 00:18:52.890 but in the same way if the other version that 00:18:52.890 --> 00:18:55.089 is simple to the same optimization is still going 00:18:55.089 --> 00:18:57.720 to be faster it's like it's the same concept 00:18:57.720 --> 00:19:01.859 of like algorithms like there is no way like 00:19:01.859 --> 00:19:05.640 uh you know what i mean like one four like this 00:19:05.640 --> 00:19:10.839 is lower than like two four i mean of course 00:19:10.839 --> 00:19:14.059 like they think this is the very raw mode like 00:19:14.059 --> 00:19:16.720 you know there's case in case but you see what 00:19:16.720 --> 00:19:18.200 i mean it's like if you're dealing with more 00:19:18.200 --> 00:19:21.519 input they need to do more process they are and 00:19:22.319 --> 00:19:25.039 And they're like, work, work, work. And you can, 00:19:25.140 --> 00:19:28.039 like, you want to keep increasing the time. So 00:19:28.039 --> 00:19:33.319 I respect Alakrit a lot for the decisions that 00:19:33.319 --> 00:19:37.019 they take. But I also understand the community 00:19:37.019 --> 00:19:40.700 necessities that they, people just want, like, 00:19:40.799 --> 00:19:47.380 to modernize a bit. So I feel that, yeah, I think 00:19:47.380 --> 00:19:52.759 it's a very great key. uh situation because like 00:19:52.759 --> 00:19:57.319 right i think there's like uh i think alacrit 00:19:57.319 --> 00:20:00.440 needs to exist like they need to exist like they 00:20:00.440 --> 00:20:03.859 need to be they need to be the the the example 00:20:03.859 --> 00:20:06.980 of like a option for people that just want the 00:20:06.980 --> 00:20:11.660 basic and the fastest yep definitely and you 00:20:11.660 --> 00:20:13.900 know what i mean like and and other options should 00:20:13.900 --> 00:20:15.960 exist everywhere i was talking that like i have 00:20:15.960 --> 00:20:19.470 all the terminals because Like every terminal 00:20:19.470 --> 00:20:22.690 does something different and I kind of like it. 00:20:23.390 --> 00:20:28.450 Yep. I would probably still be in alacrity if 00:20:28.450 --> 00:20:33.470 it wasn't for images. It's not like I need images, 00:20:33.609 --> 00:20:38.410 you know, but I kind of need images. You're feeling 00:20:38.410 --> 00:20:41.930 they're missing out, right? Yeah, but like you 00:20:41.930 --> 00:20:44.390 mentioned, right? That's why we have so many 00:20:44.390 --> 00:20:48.400 different options. Yeah. I don't know. I just 00:20:48.400 --> 00:20:52.259 like just like viewing images because I just 00:20:52.259 --> 00:20:54.799 quickly want to see. OK, so let's say that I'm 00:20:54.799 --> 00:20:57.119 working on something. I always open this file. 00:20:57.259 --> 00:21:01.200 This is the file. But I just want to see. OK, 00:21:01.339 --> 00:21:05.180 yeah, this is the image right now. I just want 00:21:05.180 --> 00:21:07.460 to see that. I just want to confirm basically 00:21:07.460 --> 00:21:10.380 when I paste an image in the oven that I have 00:21:10.380 --> 00:21:13.960 the right image. Right. Because otherwise I would 00:21:13.960 --> 00:21:16.400 have to open a preview. I can't do that, you 00:21:16.400 --> 00:21:20.000 know, in the browser. But I don't know. It's 00:21:20.000 --> 00:21:24.500 just... But I have options. No, I am with you. 00:21:24.700 --> 00:21:26.940 I am with you. That's why you use Kitty and, 00:21:27.059 --> 00:21:31.539 like, Ghosty. Yeah. Like, and Rio. But I think 00:21:31.539 --> 00:21:35.099 that, like, in terms of image protocol, like, 00:21:35.140 --> 00:21:40.359 he was far behind, like, Kitty and, like, he 00:21:40.359 --> 00:21:43.960 still needs to catch up with Ghosty. But, like... 00:21:44.440 --> 00:21:48.440 What does Ghosty use? Does it use the KDE graphics 00:21:48.440 --> 00:21:54.160 protocol? Yeah, exactly. And here it does support 00:21:54.160 --> 00:21:59.440 6 .0. I think KDE does not support 6 .0 and Ghosty 00:21:59.440 --> 00:22:05.420 does not support 6 .0. And all the terminals 00:22:05.420 --> 00:22:11.180 support the iTerm2 protocol as well. And I have 00:22:11.180 --> 00:22:16.660 a very... important question for you as a terminal 00:22:16.660 --> 00:22:21.440 developer right go for it i want to know what 00:22:21.440 --> 00:22:28.279 you think about this emux man this has been like 00:22:28.279 --> 00:22:30.980 uh this has been actually fun because you're 00:22:30.980 --> 00:22:33.140 doing the question the right question in the 00:22:33.140 --> 00:22:37.900 right time uh last week in charm we're discussing 00:22:37.900 --> 00:22:40.420 this like because everyone have their opinions 00:22:40.420 --> 00:22:51.059 right And I think the following. Do you use Tmux? 00:22:51.319 --> 00:22:57.279 I use Tmux, yeah. Right. So I think this. Tmux 00:22:57.279 --> 00:23:00.920 is great. And if you think from a user perspective, 00:23:01.859 --> 00:23:07.880 you don't care what is a terminal developer perspective 00:23:07.880 --> 00:23:12.079 because you don't maintain a terminal. exactly 00:23:12.079 --> 00:23:15.180 right so you just want like something that works 00:23:15.180 --> 00:23:18.339 for you yeah you don't really care me as a terminal 00:23:18.339 --> 00:23:22.819 user yep i don't care but i do understand the 00:23:22.819 --> 00:23:26.160 pain that terminal maintainers go through with 00:23:26.160 --> 00:23:29.440 tmux i just want to hear your thoughts yeah no 00:23:29.440 --> 00:23:33.740 exactly i i think like uh i think like uh in 00:23:33.740 --> 00:23:36.180 overall i think it's a great like uh tooling 00:23:37.899 --> 00:23:41.420 It's hard to even imagine like something replacing 00:23:41.420 --> 00:23:46.420 Teamworks nowadays like this is so why use it 00:23:46.420 --> 00:23:49.859 everyone they use Terminal sort of how uses it 00:23:49.859 --> 00:23:54.259 or uses LGA and back in time use it to use Scream 00:23:54.259 --> 00:24:02.380 but I think like I'm not in that position to 00:24:02.380 --> 00:24:04.720 judge people they also don't maintain Terminal 00:24:04.720 --> 00:24:07.569 so it's like Why are you going to judge then? 00:24:07.710 --> 00:24:10.250 You know what I mean? I actually started to develop 00:24:10.250 --> 00:24:14.970 a multiplexer on my own just to... Because... 00:24:14.970 --> 00:24:19.329 Okay, so here's the deal. TMAX is like a program 00:24:19.329 --> 00:24:22.869 that creates TTY and then manages that for you. 00:24:23.230 --> 00:24:27.390 And the terminal gets a bit confused because 00:24:27.390 --> 00:24:30.089 you're running a program that is managing TTY 00:24:30.089 --> 00:24:34.670 and returning it for you. And then, you know, 00:24:34.750 --> 00:24:37.259 like... You're talking about capabilities, you're 00:24:37.259 --> 00:24:40.220 talking about a lot of stuff that Tmux is doing 00:24:40.220 --> 00:24:45.559 out of the hood. So is Tmux running another terminal 00:24:45.559 --> 00:24:49.559 in your terminal? Exactly. So they keep creating 00:24:49.559 --> 00:24:55.160 terminal instances for you and managing that 00:24:55.160 --> 00:25:00.779 for you. So it's hard to think, okay, it's kind 00:25:00.779 --> 00:25:04.279 of like a layer between the terminal program, 00:25:05.359 --> 00:25:09.960 no sorry the emulator the program and the terminal 00:25:09.960 --> 00:25:14.400 because like so the problem is the layer between 00:25:14.400 --> 00:25:19.660 the host and the terminal itself the pty is the 00:25:19.660 --> 00:25:25.279 terminal and uh so i started to work on the proof 00:25:25.279 --> 00:25:28.480 of concept that is like i don't know when this 00:25:28.480 --> 00:25:31.960 is gonna be done But I started to create, like, 00:25:31.980 --> 00:25:34.700 okay, so what if I create and manage instances 00:25:34.700 --> 00:25:39.720 through the terminal via, like, ANSI? So, like, 00:25:39.720 --> 00:25:41.680 I ask the terminal to create, like, an instance. 00:25:42.480 --> 00:25:44.960 And then, like, once I have an instance, I can 00:25:44.960 --> 00:25:47.920 just ask for, like, any information about the 00:25:47.920 --> 00:25:50.940 running instance to the terminal. So I started 00:25:50.940 --> 00:25:54.839 to work on the multiplexer that, like, that does 00:25:54.839 --> 00:25:58.000 not feel like a hack, like, for the terminal 00:25:58.000 --> 00:26:01.180 perspective. so i give to the terminal the power 00:26:01.180 --> 00:26:04.099 to create and manage instances and just notify 00:26:04.099 --> 00:26:08.960 the running program um i don't know when it's 00:26:08.960 --> 00:26:11.980 gonna be done i was able to work like to get 00:26:11.980 --> 00:26:14.420 this working but it's not the same way it's just 00:26:14.420 --> 00:26:19.559 like just here for self is a lot of work in my 00:26:19.559 --> 00:26:22.380 daily basis so it's just like i don't know when 00:26:22.380 --> 00:26:25.420 i'm gonna be you know finishing wrapping that 00:26:25.420 --> 00:26:32.549 up oh yeah and How is compatibility? Let's say 00:26:32.549 --> 00:26:35.250 that Tmux adds a new feature. What does that 00:26:35.250 --> 00:26:38.170 mean for you as a terminal maintainer? Do you 00:26:38.170 --> 00:26:41.569 need to make it compatible with your terminal? 00:26:42.369 --> 00:26:47.769 Yeah, like as long as it... This is a bit complex 00:26:47.769 --> 00:26:50.369 because it depends on the feature, right? So 00:26:50.369 --> 00:26:54.049 it's like when we're talking about image protocols 00:26:54.049 --> 00:26:58.420 or stuff like that. TeamBucks needs to recognize 00:26:58.420 --> 00:27:01.059 and understand the capabilities that you have 00:27:01.059 --> 00:27:04.859 from the host so that's why people a lot of times 00:27:04.859 --> 00:27:07.440 do open issues and like it's funny because like 00:27:07.440 --> 00:27:11.140 for example ssh like you try to connect from 00:27:11.140 --> 00:27:15.420 a service from a server and then or you know 00:27:15.420 --> 00:27:18.000 like trying to do something somewhere but the 00:27:18.000 --> 00:27:20.519 host the server that you have is a different 00:27:20.519 --> 00:27:23.990 host Oh, sorry. The host that you are is in a 00:27:23.990 --> 00:27:26.789 different term than the server that you are running 00:27:26.789 --> 00:27:30.730 at. So it starts to have a very weird response. 00:27:31.170 --> 00:27:34.369 It starts to, you know, like, oh, I am typing 00:27:34.369 --> 00:27:38.450 in something very... Strange happens. Yeah. And 00:27:38.450 --> 00:27:40.910 I think that that is the thing with the... So 00:27:40.910 --> 00:27:46.869 you often need to map that out to TMAX. But that 00:27:46.869 --> 00:27:50.700 does not necessarily... It's just... because 00:27:50.700 --> 00:27:53.319 that's why i said depends on the feature in general 00:27:53.319 --> 00:27:55.920 there's enough but there is a lot of other stuff 00:27:55.920 --> 00:27:58.500 that you also need to map it out because you 00:27:58.500 --> 00:28:03.599 also need like tmux to uh again like from a third 00:28:03.599 --> 00:28:08.440 of developer perspective is a bit of it is not 00:28:08.440 --> 00:28:12.339 nice like because a lot of a lot of user issues 00:28:12.339 --> 00:28:16.599 that comes to you is like tmux you know intervening 00:28:16.599 --> 00:28:19.740 in this stuff and actually doing stuff that he 00:28:19.740 --> 00:28:24.420 should be doing or and i understand why people 00:28:24.420 --> 00:28:27.839 like they talk about tmux but i think like i 00:28:27.839 --> 00:28:29.579 don't want to be the terminal developer that 00:28:29.579 --> 00:28:33.299 just read silence because i use tmux for a long 00:28:33.299 --> 00:28:38.539 time and then so if you're a user like there's 00:28:38.539 --> 00:28:40.660 no that's not really matter like you want the 00:28:40.660 --> 00:28:43.380 terminal to work for you and you want you just 00:28:44.029 --> 00:28:46.230 understand like you just want to go to you and 00:28:46.230 --> 00:28:48.150 open your issue and say like hey man this is 00:28:48.150 --> 00:28:52.789 broke but then like but then you you most of 00:28:52.789 --> 00:28:54.730 the times people are forgetting the configuration 00:28:54.730 --> 00:28:58.549 so you just ask in the issue are you using tmux 00:28:58.549 --> 00:29:01.349 and if they answer yes you just close the issue 00:29:01.349 --> 00:29:04.410 right away yeah i know some people actually did 00:29:04.410 --> 00:29:07.049 that well i'm gonna mention names but like uh 00:29:07.049 --> 00:29:10.970 it is it's not it's not the best like i try to 00:29:10.970 --> 00:29:15.029 to be kind to people over the issues Yeah, it's 00:29:15.029 --> 00:29:17.950 really complex. As a user as well, getting Tmux 00:29:17.950 --> 00:29:21.930 in between, you know, terminal Tmux in your application, 00:29:22.269 --> 00:29:24.529 it's another layer that you have to take into 00:29:24.529 --> 00:29:26.250 consideration. So if you don't know what you're 00:29:26.250 --> 00:29:28.809 doing, it's because I remember I had an issue 00:29:28.809 --> 00:29:32.470 with Western, right? So I tried to view images 00:29:32.470 --> 00:29:37.230 in Western, but I was using Tmux. And I had weird 00:29:37.230 --> 00:29:41.210 issues. What I had to do was to download the 00:29:41.210 --> 00:29:44.529 kitty term info file. used that in Westterm, 00:29:44.630 --> 00:29:48.769 and that worked with T -Max, right? Yeah, that's 00:29:48.769 --> 00:29:52.130 one type of features that you get with regarding 00:29:52.130 --> 00:29:55.730 the capabilities. And I think one thing that's 00:29:55.730 --> 00:29:59.009 funny, so I was like, man, terminals are like 00:29:59.009 --> 00:30:01.430 a word. Like, it's just like a lot of stuff. 00:30:01.569 --> 00:30:03.990 But one thing that's like, people often ask me, 00:30:04.069 --> 00:30:09.890 like, when CXO is landing at EU or Windows? And 00:30:09.890 --> 00:30:13.640 then the thing is like, For HEU to have 6 working 00:30:13.640 --> 00:30:17.900 at Windows, we need to use a specific version 00:30:17.900 --> 00:30:23.920 of the COM -PTY. And either I wait for Windows 00:30:23.920 --> 00:30:28.140 to bundle that up, and basically that's what 00:30:28.140 --> 00:30:32.880 I have been doing, or either I bundle it up, 00:30:32.900 --> 00:30:36.000 like I actually get the COM -PTY, put in HEU 00:30:36.000 --> 00:30:40.700 binary, and then run, you know, HEU. like actually 00:30:40.700 --> 00:30:44.079 triggering that binary which is how Westerm has 00:30:44.079 --> 00:30:46.960 been doing and a lot of other projects has been 00:30:46.960 --> 00:30:51.900 doing as well but for me it's so bad they actually 00:30:51.900 --> 00:30:56.019 need to you know like get something from Microsoft 00:30:56.019 --> 00:31:00.420 like and make it work compile it to something 00:31:00.420 --> 00:31:03.019 and then it's like okay now you're running the 00:31:03.019 --> 00:31:07.420 ARM now you're running the x86 and then do this 00:31:07.420 --> 00:31:11.450 like just instead of like relying on something 00:31:11.450 --> 00:31:15.089 that should exist for you know like like in every 00:31:15.089 --> 00:31:20.009 system basically so i don't know like i i have 00:31:20.009 --> 00:31:23.109 no i maybe i'm gonna actually bundle it up in 00:31:23.109 --> 00:31:26.970 here to get the issue sorted out but i also patient 00:31:26.970 --> 00:31:32.529 man so i can wait a bit more how do you feel 00:31:32.529 --> 00:31:35.390 as a terminal maintainer when i use your like 00:31:35.390 --> 00:31:40.210 me right comes along tries rio and the first 00:31:40.210 --> 00:31:42.990 thing they do is install tmux do you feel that 00:31:42.990 --> 00:31:45.670 they're not using rio anymore it's like so why 00:31:45.670 --> 00:31:49.089 are you using rio just use whatever how do you 00:31:49.089 --> 00:31:53.130 know no i feel great actually like uh i i have 00:31:53.130 --> 00:31:57.849 no strong bad opinions about tmux like again 00:31:57.849 --> 00:32:01.049 like i was a user before like i used to use tmux 00:32:01.049 --> 00:32:04.319 like everyone that complained about tmux i think 00:32:04.319 --> 00:32:06.779 that's a moment of their career they use a tmux 00:32:06.779 --> 00:32:10.079 you know what i mean like all the all the the 00:32:10.079 --> 00:32:13.400 terminal developers like they use a tmux before 00:32:13.400 --> 00:32:16.619 i don't want to mention names so it's like sure 00:32:16.619 --> 00:32:19.880 like kind of changes your your perspective after 00:32:19.880 --> 00:32:23.420 you maintain a terminal like you start to see 00:32:23.420 --> 00:32:26.900 things differently but uh but i don't want to 00:32:26.900 --> 00:32:29.099 be this person that judges like and say like 00:32:29.099 --> 00:32:33.069 oh this is this is poop like in the end of the 00:32:33.069 --> 00:32:35.589 day people are doing what i was doing before 00:32:35.589 --> 00:32:39.349 you know what i mean like they're not and frankly 00:32:39.349 --> 00:32:41.630 bad for them like they don't need to maintain 00:32:41.630 --> 00:32:43.789 a terminal at the end of the day they can just 00:32:43.789 --> 00:32:47.690 live their life and and like you know just chill 00:32:47.690 --> 00:32:50.990 i think that that actually is great for them 00:32:50.990 --> 00:32:57.049 yeah let me tell you why i love tmux okay the 00:32:57.049 --> 00:33:01.029 only reason yeah that is basically everyone has 00:33:01.029 --> 00:33:03.670 everyone has like a different reason i actually 00:33:03.670 --> 00:33:06.789 have been asking that like in the past week because 00:33:06.789 --> 00:33:09.569 i was just like okay i want to write a multiplexer 00:33:09.569 --> 00:33:12.789 myself so what features of tmux i need to copy 00:33:12.789 --> 00:33:15.930 and everyone has like they they own stuff like 00:33:15.930 --> 00:33:19.710 my my boss was like oh i love the way they integrate 00:33:19.710 --> 00:33:25.509 with ssh and my my other friend was like talking 00:33:27.119 --> 00:33:29.579 what was the thing i think was about the server 00:33:29.579 --> 00:33:32.019 they can just have like it running in different 00:33:32.019 --> 00:33:35.400 places and then you have like so that's why i 00:33:35.400 --> 00:33:37.779 think the tmux is a good it's a great piece of 00:33:37.779 --> 00:33:41.180 software in terms of like it gets the job done 00:33:41.180 --> 00:33:43.880 and it's hard to see it being replaced serving 00:33:43.880 --> 00:33:47.029 a goal like your virtual something oh no no go 00:33:47.029 --> 00:33:49.049 ahead yeah it's pretty interesting what you're 00:33:49.049 --> 00:33:51.529 saying everyone has something different yeah 00:33:51.529 --> 00:33:54.470 and it's like i think like people saying like 00:33:54.470 --> 00:33:56.650 about the configuration that they liked about 00:33:56.650 --> 00:33:59.950 the leader key but all these features they are 00:33:59.950 --> 00:34:04.329 reproducible like for example it's just like 00:34:04.329 --> 00:34:08.269 tmux has so much love from the terminal community 00:34:08.269 --> 00:34:11.510 that no one came and said like oh i'm gonna rewrite 00:34:11.510 --> 00:34:17.280 tmux in I don't know, like in C or in Rust. Oh, 00:34:17.300 --> 00:34:20.519 in Rust? Is that Selige? Is it written in Rust? 00:34:21.079 --> 00:34:23.579 No, it is, right. But it's like, if you think 00:34:23.579 --> 00:34:25.320 with me, it's like, yeah, sure, it's one guy, 00:34:25.460 --> 00:34:27.780 but how many multiplexers have you heard about 00:34:27.780 --> 00:34:31.119 it? It's not like Terminals. Yep, no, just Tmux. 00:34:31.239 --> 00:34:34.380 And Selige, but it's not that popular. Yeah, 00:34:35.079 --> 00:34:40.309 exactly. And I started to do my... Yeah, exactly. 00:34:40.570 --> 00:34:42.849 No, I think it would be fun, actually, to do 00:34:42.849 --> 00:34:45.969 the multiplayer. I did already work with four 00:34:45.969 --> 00:34:51.010 panels and with the leader key, and I was able 00:34:51.010 --> 00:34:54.570 to do some of the debug speed functionalities 00:34:54.570 --> 00:35:00.449 in three days. But it's like, it's so great when 00:35:00.449 --> 00:35:03.449 you think like, oh, it's such a lot of pieces 00:35:03.449 --> 00:35:07.269 of software that people, it's like Git. Like 00:35:07.269 --> 00:35:09.579 you don't come to... It's like Git, yep. You 00:35:09.579 --> 00:35:11.519 know what I mean? Like, you don't come to a developer 00:35:11.519 --> 00:35:13.679 and say, like, hey, man, like, do you want to 00:35:13.679 --> 00:35:16.179 use a different stuff than Git? And they'll be 00:35:16.179 --> 00:35:18.539 like, why? Like, it's been working already. It 00:35:18.539 --> 00:35:21.179 works well. And I think that this is the thing 00:35:21.179 --> 00:35:24.179 with the TMAX. So it's like, to replace it, you 00:35:24.179 --> 00:35:27.719 need to come with a very good approach, like, 00:35:27.719 --> 00:35:29.480 of how you're doing in terms of architecture. 00:35:30.480 --> 00:35:33.820 And I love, for example, the Western does have 00:35:33.820 --> 00:35:38.630 its own Mood Flexor. for me is like i love it 00:35:38.630 --> 00:35:41.289 i think that is like it's so interesting that 00:35:41.289 --> 00:35:45.489 they do that um and i think actually terminals 00:35:45.489 --> 00:35:48.969 some way should be doing that but it's also like 00:35:48.969 --> 00:35:52.130 as a terminal should be doing that as well like 00:35:52.130 --> 00:35:55.170 i think you know like it's all part of the question 00:35:55.170 --> 00:35:59.530 yeah and uh so i love it but i also have like 00:36:00.519 --> 00:36:02.719 Yeah, you know like it's probably people who 00:36:02.719 --> 00:36:04.679 look to him and Bill they would be like, yeah, 00:36:04.739 --> 00:36:07.920 why did you put like a retro art? like future 00:36:07.920 --> 00:36:13.440 support and People be like Kevin the look too 00:36:13.440 --> 00:36:18.940 much. Like why did you do that? Yeah Yeah, nobody 00:36:18.940 --> 00:36:21.539 is gonna be happy. There's always people that 00:36:21.539 --> 00:36:26.480 is gonna be happy with whatever You decide to 00:36:26.480 --> 00:36:29.400 take so You're going to show something with Tmux, 00:36:29.460 --> 00:36:33.000 man. Go ahead. Yeah, yeah, yeah. The only reason 00:36:33.000 --> 00:36:37.519 why I love Tmux is... Where is my terminal? Here. 00:36:37.659 --> 00:36:42.079 Here. Sessions, right? Because for me, sessions 00:36:42.079 --> 00:36:45.820 are projects, right? So this is my .files, right? 00:36:45.860 --> 00:36:48.579 So here's the Tmux name, right? So if I want 00:36:48.579 --> 00:36:51.719 to jump to my nodes with a single key map, I'm 00:36:51.719 --> 00:36:54.760 in my nodes, right? So if I want to jump to my 00:36:54.760 --> 00:36:58.820 blog post... I just type another keymap, it opens 00:36:58.820 --> 00:37:01.980 that session, and I'm there. If I want to jump 00:37:01.980 --> 00:37:06.019 to my home session, right? Another keymap, I'm 00:37:06.019 --> 00:37:08.340 there, right? Here's where I type my commands. 00:37:08.639 --> 00:37:11.900 Or if I want to go to my daily notes, for example, 00:37:12.000 --> 00:37:19.119 another TMAG session. So personally, right? Yeah, 00:37:19.179 --> 00:37:24.460 it feels like a workspace. Yeah. like a workspace 00:37:24.460 --> 00:37:28.500 right so each one of these is like um a github 00:37:28.500 --> 00:37:32.300 repo right so i can navigate between my different 00:37:32.300 --> 00:37:36.539 repos quite fast right so that is i don't care 00:37:36.539 --> 00:37:40.860 about the um the windows right i don't care about 00:37:40.860 --> 00:37:44.980 the split panes and all that stuff no i like 00:37:44.980 --> 00:37:48.639 no i i i get to like uh i think like this is 00:37:48.639 --> 00:37:52.619 the thing that i I actually will try to do in 00:37:52.619 --> 00:37:59.059 the next HEU version, I think. Not the version 00:37:59.059 --> 00:38:03.239 itself. I actually have been trying to do it. 00:38:03.800 --> 00:38:06.460 I will leave this to the end. But I have been 00:38:06.460 --> 00:38:09.320 trying to do experimental HEU with more native 00:38:09.320 --> 00:38:13.300 stuff. So I have been working on the SwiftUI 00:38:13.300 --> 00:38:17.079 version of HEU in the parallel. That's closed 00:38:17.079 --> 00:38:20.610 source yet. But it's like, I have been trying 00:38:20.610 --> 00:38:23.829 to call it like art browser and some stuff that 00:38:23.829 --> 00:38:25.949 they have like this concept of workspace where 00:38:25.949 --> 00:38:29.449 you can name stuff and stuff like that. And like, 00:38:29.449 --> 00:38:32.730 it's a thing that I really see value. Like sometimes 00:38:32.730 --> 00:38:36.010 I'm working on the work. Sometimes I'm working 00:38:36.010 --> 00:38:38.650 on my personal stuff. Yeah. Sometimes I just 00:38:38.650 --> 00:38:41.929 bring them stuff. Yeah. and like uh you don't 00:38:41.929 --> 00:38:45.949 want to quit the application then cd into the 00:38:45.949 --> 00:38:49.389 other one open your editor there it's you know 00:38:49.389 --> 00:38:54.530 exactly no i will work you 100 like so it's like 00:38:54.530 --> 00:38:56.949 i think that i want to explore in the future 00:38:56.949 --> 00:39:00.849 i didn't hear you or either i don't know if i 00:39:00.849 --> 00:39:03.849 want to do the mood but who knows like if i get 00:39:03.849 --> 00:39:06.750 excited i will do and it's a lot of work man 00:39:06.750 --> 00:39:10.460 so Yeah. No, but I've worked on so many stuff 00:39:10.460 --> 00:39:13.659 in parallel. I'm doing the batch, like, in virtual, 00:39:13.800 --> 00:39:17.860 in Rust, and, like, I think it's, like, sometimes 00:39:17.860 --> 00:39:21.699 I get bored with Heave. Like, I think it's, like, 00:39:21.760 --> 00:39:26.599 how can I say? It's, like, in Heave, you kind 00:39:26.599 --> 00:39:29.920 of work in some specific type of work. Like, 00:39:30.000 --> 00:39:32.179 you know, you fix bugs, you add features. You 00:39:32.179 --> 00:39:35.539 fix bugs, you add features. And... Sometimes 00:39:35.539 --> 00:39:39.139 you have the space to be creative and when that 00:39:39.139 --> 00:39:41.500 happens, it's great, but you can also break things 00:39:41.500 --> 00:39:43.960 for users. So it's like you need to also respect. 00:39:44.820 --> 00:39:52.420 I think with the MoodPlexer is a different subject 00:39:52.420 --> 00:39:55.139 because sometimes I have a space to be, okay, 00:39:55.199 --> 00:39:58.059 I want to do some crazy stuff. I want to create 00:39:58.059 --> 00:40:01.199 like a protocol that I can send, like, please 00:40:01.199 --> 00:40:05.280 create this TTY, please delete that TTY. what 00:40:05.280 --> 00:40:08.360 is the output, what is the input, and they connect 00:40:08.360 --> 00:40:11.800 with, I mean, now explaining how the architecture 00:40:11.800 --> 00:40:14.800 works, like, but you see, like, you can actually 00:40:14.800 --> 00:40:19.440 explore stuff, and I think with here, sometimes 00:40:19.440 --> 00:40:22.219 the things are more straightforward, and people, 00:40:22.320 --> 00:40:28.440 they are more, they're more concerned in terms 00:40:28.440 --> 00:40:32.340 of, like, oh, because it's, like, in the terminal, 00:40:32.420 --> 00:40:35.739 in the maintaining terminal life. Sure, people 00:40:35.739 --> 00:40:38.559 get excited when they have cool stuff that they 00:40:38.559 --> 00:40:41.659 never saw before. Like, for example, the RetroArch 00:40:41.659 --> 00:40:45.019 filters were very exciting and everyone was like, 00:40:45.119 --> 00:40:48.380 whoa. But I think also they get the same level 00:40:48.380 --> 00:40:51.099 of excitement if I fix a lot of bugs in a row. 00:40:51.639 --> 00:40:55.119 So it's like, you know what I mean? It's not 00:40:55.119 --> 00:40:59.480 like you kind of need to treat your users in 00:40:59.480 --> 00:41:02.199 the way that they want to use reliable software. 00:41:04.489 --> 00:41:07.869 sometimes it's great like i'm excited and other 00:41:07.869 --> 00:41:11.329 times i just want to work on crazy stuff so it's 00:41:11.329 --> 00:41:14.989 hard to find the the balance i think yeah and 00:41:14.989 --> 00:41:19.989 how how is it working with that tmux maintainer 00:41:19.989 --> 00:41:23.610 have you talked to him what's his name um it's 00:41:23.610 --> 00:41:29.909 um nicholas nicholas i don't remember the last 00:41:29.909 --> 00:41:33.449 name have you worked with them No, not really. 00:41:33.670 --> 00:41:37.510 Like, I never did. But I heard that, like, they're 00:41:37.510 --> 00:41:43.710 cool, you know, like, never, like, I don't have 00:41:43.710 --> 00:41:46.050 personal opinions, but I just heard that they're 00:41:46.050 --> 00:41:51.469 cool. Okay, okay. And how is it with Windows? 00:41:51.769 --> 00:41:55.309 Is Rio, can you run it on Windows? Of course, 00:41:55.409 --> 00:41:59.030 like, this is a thing that for me is, like, a 00:41:59.030 --> 00:42:03.300 must, actually. Because when I started my career, 00:42:03.460 --> 00:42:07.400 I didn't have much money. Windows was the only 00:42:07.400 --> 00:42:12.159 machine that I could actually afford. And I didn't 00:42:12.159 --> 00:42:17.900 know Linux. It just started my career. It was 00:42:17.900 --> 00:42:22.800 not like my co -work. He was already a Linux 00:42:22.800 --> 00:42:25.619 fan without even having a computer. He was reading 00:42:25.619 --> 00:42:28.079 Linux magazines before he could have his first 00:42:28.079 --> 00:42:31.199 computer. But I didn't even know Linux at all. 00:42:31.380 --> 00:42:37.860 So for me, it's kind of a democrat way of software. 00:42:38.059 --> 00:42:41.820 Think about everyone. I just don't want to be 00:42:41.820 --> 00:42:46.159 developing the good stuff for macOS and ignoring 00:42:46.159 --> 00:42:48.800 the rest, or developing good stuff for Linux 00:42:48.800 --> 00:42:52.880 and ignoring the rest. I want to be... I think 00:42:52.880 --> 00:42:56.260 that this is the part I think is inclusive. And 00:42:56.260 --> 00:43:00.320 for me... Like when I was a teenager or a kid, 00:43:00.519 --> 00:43:04.800 I didn't have any money to just upgrade for the 00:43:04.800 --> 00:43:10.400 Mac OS. And it was like a big deal when I actually 00:43:10.400 --> 00:43:16.340 changed for Mac OS. So, man, as long as I maintain 00:43:16.340 --> 00:43:19.400 here, I will try to give priority on the Windows. 00:43:19.619 --> 00:43:23.400 It's tough for me because it's not my main driver 00:43:23.400 --> 00:43:26.760 right now. So some stuff is hard for me to... 00:43:27.179 --> 00:43:29.480 keep up but this works actually putting some 00:43:29.480 --> 00:43:34.880 love and doing the native steps for windows uh 00:43:34.880 --> 00:43:37.039 which is a thing that people have been asking 00:43:37.039 --> 00:43:43.380 for a long time and uh and blur is something 00:43:43.380 --> 00:43:46.340 that's also calling me there's like all these 00:43:46.340 --> 00:43:49.159 things you know like and it's great when you 00:43:49.159 --> 00:43:51.139 actually add these things like you see the love 00:43:51.139 --> 00:43:54.179 from people like that they because they they 00:43:54.179 --> 00:43:56.440 have been using the weight of all that feature 00:43:56.440 --> 00:43:59.579 and then when you do that it's kind of nice because 00:43:59.579 --> 00:44:04.420 like you see the yeah you know like i think it's 00:44:04.420 --> 00:44:07.019 a nice thing like the way that people tweak software 00:44:07.019 --> 00:44:12.519 i guess and how has that experience been how 00:44:12.519 --> 00:44:16.360 has it you know the open source experience with 00:44:16.360 --> 00:44:20.829 issues discussions is it a lot of work a lot 00:44:20.829 --> 00:44:24.210 of burden have you had bad experiences how is 00:44:24.210 --> 00:44:29.909 that side of things yeah i i i i used to do a 00:44:29.909 --> 00:44:32.349 lot of open source i don't know if in the same 00:44:32.349 --> 00:44:37.550 as rio but i used to work for jquery like you 00:44:37.550 --> 00:44:42.230 know the javascript like framework uh oh my work 00:44:42.230 --> 00:44:45.610 there was very little and i used to work for 00:44:45.610 --> 00:44:49.210 jquery caller And just by that time, it was a 00:44:49.210 --> 00:44:51.489 bit overwhelming. We were talking about, I don't 00:44:51.489 --> 00:44:56.230 know, 12 years ago. Am I that old? I don't know. 00:44:56.309 --> 00:45:02.889 Something like 9 or 10 years ago. But after that, 00:45:02.989 --> 00:45:06.150 I started to work on my own stuff. I call it 00:45:06.150 --> 00:45:10.150 React TV, which was like a render for TV, televisions 00:45:10.150 --> 00:45:15.309 and stuff. And it was great. But I think the 00:45:15.309 --> 00:45:20.699 real... Like, the real open source experience 00:45:20.699 --> 00:45:24.880 that I really had was when I started to contribute 00:45:24.880 --> 00:45:29.340 for WebAssembly. And then I started to deal with 00:45:29.340 --> 00:45:33.739 people asking stuff. Like, I think my first job 00:45:33.739 --> 00:45:36.579 in the WebAssembly working group was to extend 00:45:36.579 --> 00:45:43.099 the interpreter to actually allow receive function, 00:45:43.280 --> 00:45:45.460 name it functions to run in the interpreter. 00:45:46.409 --> 00:45:49.690 And it was funny because it was C++ and it was 00:45:49.690 --> 00:45:53.630 not my area of expertise. So I was still learning 00:45:53.630 --> 00:45:56.429 at the time. And people were like, oh, I'm going 00:45:56.429 --> 00:45:58.289 to do, I'm going to do. And I was just like, 00:45:58.369 --> 00:46:02.269 hey, man, I will do. So that was, I think, my 00:46:02.269 --> 00:46:10.150 real kind of like... It's like when you start, 00:46:10.469 --> 00:46:13.010 even if you work on your own stuff and people 00:46:13.010 --> 00:46:17.219 use, it's like... Like, I don't know, like I 00:46:17.219 --> 00:46:20.260 had like a lot of, I spent a lot of time working 00:46:20.260 --> 00:46:22.679 outside of open source. So it was like, I felt 00:46:22.679 --> 00:46:26.019 more as like, you know, like something extra. 00:46:26.579 --> 00:46:31.300 But as I was growing up, like getting older as 00:46:31.300 --> 00:46:34.059 well, like I started to see more as a lifestyle. 00:46:35.059 --> 00:46:38.000 Like, you know, like I think that that's why 00:46:38.000 --> 00:46:40.960 I liked Mozilla at first. That was like everyone, 00:46:41.099 --> 00:46:43.989 you know, people doing open stuff and like. I 00:46:43.989 --> 00:46:46.489 would say, like, man, it's hard for me to imagine 00:46:46.489 --> 00:46:49.909 taking money from Hive. Like, of course, people 00:46:49.909 --> 00:46:53.590 can donate and stuff, but it's like, I don't 00:46:53.590 --> 00:46:56.110 imagine myself charging people for using it. 00:46:56.929 --> 00:47:00.230 And it's also because, like, I learned so much 00:47:00.230 --> 00:47:03.650 with OpenCode that, you know what I mean? Like, 00:47:03.670 --> 00:47:06.789 so after the experience of the WebAssembly, I 00:47:06.789 --> 00:47:09.710 started to work the Game Boy, then I started 00:47:09.710 --> 00:47:14.769 to work on Hive, and... it was kind of a boom 00:47:14.769 --> 00:47:17.289 in the beginning because someone posted the link 00:47:17.289 --> 00:47:21.050 in the hardware news and man was like it went 00:47:21.050 --> 00:47:26.190 from zero to three thousand stars like in three 00:47:26.190 --> 00:47:30.550 or two days and he was not even done like you 00:47:30.550 --> 00:47:33.530 know what i mean like that was full of bugs so 00:47:33.530 --> 00:47:38.269 i kind of sometimes regret opening that quick 00:47:38.269 --> 00:47:43.480 because like uh it it I mean, it's also good 00:47:43.480 --> 00:47:49.320 for it. I think it's like, you know, like it 00:47:49.320 --> 00:47:51.880 has the good side and the bad side. The bad side 00:47:51.880 --> 00:47:55.980 is like, man, people come bursting or like, and 00:47:55.980 --> 00:47:58.099 they're like, man, where is this picture? Like 00:47:58.099 --> 00:48:01.519 you guys are supposed to be done. And then... 00:48:01.519 --> 00:48:05.079 More responsibility, right? Yeah, exactly. The 00:48:05.079 --> 00:48:08.380 good side is actually... that you get to know 00:48:08.380 --> 00:48:11.280 a lot of people like I got to know so many wonderful 00:48:11.280 --> 00:48:15.519 people like through Hiyu and even the Hashimoto 00:48:15.519 --> 00:48:20.280 that is like from another like terminal man like 00:48:20.280 --> 00:48:23.260 Hiyu basically allow me to connect with them 00:48:23.260 --> 00:48:26.639 to him with him sorry and like connect with SHARM 00:48:26.639 --> 00:48:30.219 as well like that works with terminal So it's 00:48:30.219 --> 00:48:33.420 like, in some ways, like, it has been, like, 00:48:33.460 --> 00:48:36.079 really good to work with. But in other ways, 00:48:36.159 --> 00:48:39.199 sometimes I just don't want to do, like, for 00:48:39.199 --> 00:48:42.360 example, font ligatures. I didn't really want 00:48:42.360 --> 00:48:44.579 to do it. Because I wrote the Hebrew for myself 00:48:44.579 --> 00:48:49.739 and was working for my case. You know what I 00:48:49.739 --> 00:48:51.579 mean? Like, I didn't want to do that for other 00:48:51.579 --> 00:48:55.690 people. And I was just like, screw this, man. 00:48:55.789 --> 00:48:58.190 It was like three months rewriting stuff and 00:48:58.190 --> 00:49:02.989 making you capable to rewriting and fixing other 00:49:02.989 --> 00:49:05.050 people's bugs. Rewriting and fixing other people's 00:49:05.050 --> 00:49:09.449 bugs. But you know, at the end of the day, you 00:49:09.449 --> 00:49:11.630 look back and you learn so much from the process 00:49:11.630 --> 00:49:15.510 that actually makes me want to continue. So it 00:49:15.510 --> 00:49:23.449 supports ligatures now. Yeah, it does. And yeah, 00:49:23.550 --> 00:49:27.030 it was such a fun journey to do that. Because 00:49:27.030 --> 00:49:30.030 it's the type of challenges that you don't expect 00:49:30.030 --> 00:49:35.809 to face in your regular job. So for me, it was 00:49:35.809 --> 00:49:40.489 like, as I was speaking, sometimes I saw Michel 00:49:40.489 --> 00:49:44.730 and other people complaining about font in general, 00:49:44.829 --> 00:49:47.929 like font rendering is such a word. There's a 00:49:47.929 --> 00:49:49.849 lot of stuff that actually happens under the 00:49:49.849 --> 00:49:54.780 hood. and then and like before i'll be like yeah 00:49:54.780 --> 00:49:56.940 these people are complaining about who cares 00:49:56.940 --> 00:49:59.739 but now i'm just like man actually it's a lot 00:49:59.739 --> 00:50:07.260 of work okay okay interesting and um let's get 00:50:07.260 --> 00:50:09.539 to know you a little bit more if that's okay 00:50:09.539 --> 00:50:13.059 we already talked about rio a lot and i think 00:50:13.059 --> 00:50:17.559 um you did cover all of the questions that i 00:50:17.559 --> 00:50:22.500 had about it i would like to to see a demo on 00:50:22.500 --> 00:50:26.639 the cool stuff that you have for Rio. If you 00:50:26.639 --> 00:50:29.019 want to share that a little bit later, but you 00:50:29.019 --> 00:50:31.079 want to share. Yeah. Okay. You want to share 00:50:31.079 --> 00:50:34.639 a little bit more about you. So where you're 00:50:34.639 --> 00:50:38.860 from, whatever you want to share. Sounds good. 00:50:39.039 --> 00:50:45.000 I am from Brazil. Like I was born and raised 00:50:45.000 --> 00:50:50.900 in Rio de Janeiro. Well, not really raised there. 00:50:51.079 --> 00:50:54.760 I was born here, but I grew up in other cities 00:50:54.760 --> 00:51:01.420 close by. And I started my career because I wanted 00:51:01.420 --> 00:51:06.300 to work with games. I never worked at anything 00:51:06.300 --> 00:51:11.300 with games. Terminals. Yeah, maybe at some moment 00:51:11.300 --> 00:51:17.360 of my life I will do, but I wanted to work with... 00:51:17.690 --> 00:51:20.389 Games and that never happened actually started 00:51:20.389 --> 00:51:24.809 working. I started to program with PHP and C 00:51:24.809 --> 00:51:29.369 sharp so it was like I was doing games for Xbox 00:51:29.369 --> 00:51:33.190 and you know so excited about it and like yeah, 00:51:33.329 --> 00:51:38.710 and I honestly didn't know that Programmers would 00:51:38.710 --> 00:51:40.750 get any money. I thought that was going to be 00:51:40.750 --> 00:51:45.190 poor for the rest of my life and and then like 00:51:45.190 --> 00:51:50.139 it was funny because like it kind of like it 00:51:50.139 --> 00:51:54.159 changed like like programming did allow to change 00:51:54.159 --> 00:51:56.860 my life in terms of like you know came from poor 00:51:56.860 --> 00:52:00.199 place and then fly go all the place and travel 00:52:00.199 --> 00:52:03.739 the world like learning a language because back 00:52:03.739 --> 00:52:06.380 in time i only knew portuguese so i started to 00:52:06.380 --> 00:52:10.260 learn so now i speak spanish english like swedish 00:52:10.260 --> 00:52:14.860 like i speak other languages as well but i don't 00:52:14.860 --> 00:52:19.630 want to say that i speak conference they come 00:52:19.630 --> 00:52:21.710 you know they come talking to you like in their 00:52:21.710 --> 00:52:24.969 languages and then you're just like uh they talk 00:52:24.969 --> 00:52:29.409 yeah yeah exactly that actually happened in the 00:52:29.409 --> 00:52:32.429 my interview with spotify i told the guy that 00:52:32.429 --> 00:52:36.769 like the whiteboard i told the guy that spoke 00:52:36.769 --> 00:52:40.650 a bit of japanese which i do but uh but the guy 00:52:40.650 --> 00:52:44.289 spoke really fluent japanese he lived there for 00:52:44.289 --> 00:52:47.579 10 years And then he started speaking Japanese, 00:52:47.760 --> 00:52:54.719 which was like, oh, man, I know how to maintain 00:52:54.719 --> 00:52:57.619 a very basic conversation. Like, take it easy. 00:52:57.780 --> 00:53:03.519 Yeah, calm down. Yeah, exactly. And for me, programming 00:53:03.519 --> 00:53:10.539 was a very important aspect. And, you know, I 00:53:10.539 --> 00:53:13.199 used to work for different companies, worked 00:53:13.199 --> 00:53:18.070 a lot in Brazil. then to start work for us and 00:53:18.070 --> 00:53:21.869 then now work in sweden i have the experience 00:53:21.869 --> 00:53:25.329 of work for different like very different like 00:53:25.329 --> 00:53:27.170 i think the companies that are working were very 00:53:27.170 --> 00:53:29.550 different from each other so allow me to do stuff 00:53:29.550 --> 00:53:32.670 that were like i just work with back -end and 00:53:32.670 --> 00:53:36.929 front -end and designer then you know like then 00:53:36.929 --> 00:53:40.050 i used to work for data science then you know 00:53:40.050 --> 00:53:43.170 like you know devops and then i would just go 00:53:43.170 --> 00:53:46.090 for embed systems it was like i always have been 00:53:46.090 --> 00:53:48.650 curious to do everything like i never wanted 00:53:48.650 --> 00:53:53.110 to be just that guy that's just front end and 00:53:53.110 --> 00:53:56.510 uh or just the guy that's back in the house like 00:53:56.510 --> 00:54:00.789 everything and i i think that that was a big 00:54:00.789 --> 00:54:04.150 issue in my career in the beginning because in 00:54:04.150 --> 00:54:07.480 the beginning i like uh i'm sure they remember 00:54:07.480 --> 00:54:10.500 people put names as like uh you know like this 00:54:10.500 --> 00:54:15.679 guy he's like a web developer and the web developer 00:54:15.679 --> 00:54:18.860 was like doing everything but then some moment 00:54:18.860 --> 00:54:23.280 the web developer became front -end back -end 00:54:23.280 --> 00:54:28.019 you know like all this splitted stuff and uh 00:54:28.019 --> 00:54:32.260 so for me it was like i i was saw myself as someone 00:54:32.260 --> 00:54:35.719 that was very generalistic like i like to do 00:54:35.719 --> 00:54:40.119 everything but uh i also fear that people that 00:54:40.119 --> 00:54:43.820 do everything they're not very good in one specific 00:54:43.820 --> 00:54:48.619 thing so it's like uh i i don't know if that's 00:54:48.619 --> 00:54:51.300 true either because like i did actually interviews 00:54:51.300 --> 00:54:55.599 for front -end and back -end and i i patented 00:54:55.599 --> 00:54:59.219 for both in as a specialist for both companies 00:54:59.219 --> 00:55:03.389 in different big companies So in the same way, 00:55:03.590 --> 00:55:08.570 I think it's just bullshit. That's my personal 00:55:08.570 --> 00:55:11.230 opinion. I think it's like people being lazy 00:55:11.230 --> 00:55:14.170 and they don't want to assume that there's so 00:55:14.170 --> 00:55:17.369 much to learn in software. And then you're just 00:55:17.369 --> 00:55:21.130 going to keep learning until you die. And yeah, 00:55:21.969 --> 00:55:25.670 I think in terms of background, I did university 00:55:25.670 --> 00:55:30.110 as many people did. you know, like came out of 00:55:30.110 --> 00:55:33.070 university and realized that things from university 00:55:33.070 --> 00:55:36.650 were not that useful in the real world. Like, 00:55:36.769 --> 00:55:40.150 like people, you know, like they, they want the 00:55:40.150 --> 00:55:46.510 daughter stuff. Um, and yeah, like, uh, I was 00:55:46.510 --> 00:55:50.369 taught that we work with games until so far never 00:55:50.369 --> 00:55:54.170 happened, but one day might be. Oh, wonderful. 00:55:54.329 --> 00:55:58.059 Okay. You have, Where can people find you? I 00:55:58.059 --> 00:56:02.000 guess in github, right? Yeah Yeah, now we're 00:56:02.000 --> 00:56:05.139 open like a youtube channel. So let's see. Oh, 00:56:05.340 --> 00:56:09.139 you opened it already? Yeah, I'm trying to do 00:56:09.139 --> 00:56:13.820 because I don't know man like it's like there's 00:56:13.820 --> 00:56:19.260 twitter mastodon and uh and blue sky and I feel 00:56:19.260 --> 00:56:22.260 that it's kind of like crazy when you're posting 00:56:22.260 --> 00:56:24.679 everywhere and then you deal with people in every 00:56:24.679 --> 00:56:27.820 place because Like, you know, like people want 00:56:27.820 --> 00:56:30.559 to be in one specific network. I have friends 00:56:30.559 --> 00:56:33.900 from different places. So it's like, although 00:56:33.900 --> 00:56:41.800 I really hate some people, like, you know, from 00:56:41.800 --> 00:56:45.719 like, I don't know, like, I don't know if I should 00:56:45.719 --> 00:56:47.960 answer that topic, but I have friends from all 00:56:47.960 --> 00:56:51.420 the three, like, networks. So it's like, for 00:56:51.420 --> 00:56:53.139 me, it's like, man, I don't want to stop losing, 00:56:53.360 --> 00:56:58.800 like, you know like lose touch contact with someone 00:56:58.800 --> 00:57:03.219 so like i was trying to keep out the tree but 00:57:03.219 --> 00:57:05.420 it's just getting like in the point there is 00:57:05.420 --> 00:57:08.900 very unhealthy like to follow these three so 00:57:08.900 --> 00:57:12.320 maybe that though like i just post on youtube 00:57:12.320 --> 00:57:15.679 like uh casually people want to follow about 00:57:15.679 --> 00:57:18.679 here that they follow if they don't want like 00:57:18.679 --> 00:57:21.199 i don't give a damn like i do software because 00:57:21.199 --> 00:57:24.880 i like it not like uh You know, it's not like 00:57:24.880 --> 00:57:28.860 doing this because like when I like many stars. 00:57:31.539 --> 00:57:35.900 Yeah. I think it's about having fun. Do you want 00:57:35.900 --> 00:57:38.000 to share your YouTube channel? You have it already? 00:57:38.159 --> 00:57:42.539 Of course. Yeah, I have it. I will. No, I actually 00:57:42.539 --> 00:57:44.780 want to get my handle name for you because I 00:57:44.780 --> 00:57:50.300 always forget. Okay. I can share your screen 00:57:50.300 --> 00:57:53.380 and you can show it. All right. Alright, then 00:57:53.380 --> 00:57:56.960 I'll get one more and go for it. Yeah, you ready? 00:57:58.320 --> 00:58:07.579 I am almost... Now I'm ready. Okay. Let's see. 00:58:09.199 --> 00:58:14.920 There we go. Okay. Yeah, there is the... There 00:58:14.920 --> 00:58:21.210 is my channel. and uh yeah here is like the demo 00:58:21.210 --> 00:58:29.210 with the oops i'm clicking the the now here is 00:58:29.210 --> 00:58:34.670 the demo with the the retroarch like uh taters 00:58:34.670 --> 00:58:40.150 is that a real uh -huh it is it's like you can 00:58:40.150 --> 00:58:46.150 actually configure a real to have the like Yeah, 00:58:46.210 --> 00:58:49.349 like, to render the way they want, right? So, 00:58:49.510 --> 00:58:53.849 people used to do crazy stuff, like, so one guy 00:58:53.849 --> 00:58:59.250 actually did, like, some characters would be 00:58:59.250 --> 00:59:01.829 blurred in the bottom, and, you know, like, have 00:59:01.829 --> 00:59:06.369 this hollow effect. I think that's, like, it's 00:59:06.369 --> 00:59:09.190 fun. I like to see the terminal getting this 00:59:09.190 --> 00:59:14.989 video game vibe. It's interesting, I guess. Okay, 00:59:14.989 --> 00:59:18.360 yeah. That looks cool. And you have videos there, 00:59:18.480 --> 00:59:21.719 and they are related to Rio only or development 00:59:21.719 --> 00:59:26.599 or? Yeah, mostly Rio. Like here was the, oops. 00:59:27.239 --> 00:59:31.739 Here was like talk about the, let me take out 00:59:31.739 --> 00:59:34.840 that. Here was talking about the changes that 00:59:34.840 --> 00:59:38.420 are coming, like to have like, you know, like 00:59:38.420 --> 00:59:42.739 to improve the render for use, like to draw actually 00:59:42.739 --> 00:59:45.559 some chairs. characters so like this how it was 00:59:45.559 --> 00:59:48.960 before you know you see the borders here like 00:59:48.960 --> 00:59:53.360 like it's not really looking good and now it's 00:59:53.360 --> 00:59:55.559 like could be looking like that actually this 00:59:55.559 --> 00:59:58.920 looks much better in the latest version and this 00:59:58.920 --> 01:00:02.360 is awesome but so like i try to talk a bit like 01:00:02.360 --> 01:00:05.179 in the like in terms of like things they are 01:00:05.179 --> 01:00:09.340 doing they're coming to here and like performance 01:00:09.340 --> 01:00:12.619 is gonna be like twice as faster now like for 01:00:12.619 --> 01:00:15.559 the next version as well so there's a lot of 01:00:15.559 --> 01:00:18.360 like small things that like i tried to just do 01:00:18.360 --> 01:00:24.840 a drop there oh yeah like uh like the game boy 01:00:24.840 --> 01:00:31.199 that i also did for terminal what is that to 01:00:31.199 --> 01:00:36.710 play uh game boy games in rio Yeah, you can play 01:00:36.710 --> 01:00:40.489 here terminal any terminal that has image protocol 01:00:40.489 --> 01:00:50.090 It was like I wrote in rust it's like It's actually 01:00:50.090 --> 01:00:55.630 in my github like it's just like the I can show 01:00:55.630 --> 01:01:01.070 it There's like here it's like the whole emulator 01:01:01.070 --> 01:01:07.150 I get that runs in the web and then runs in the 01:01:07.150 --> 01:01:14.110 like as desktop or terminal as a blog project 01:01:14.110 --> 01:01:18.690 okay interesting so i'm going to leave a link 01:01:18.690 --> 01:01:23.190 to your youtube channel into your github in the 01:01:23.190 --> 01:01:26.110 video description i leave those at the top so 01:01:26.110 --> 01:01:28.710 people can find you don't expect for a lot of 01:01:28.710 --> 01:01:30.869 people to watch the video you know because not 01:01:30.869 --> 01:01:33.429 a lot of people watch my videos but at least 01:01:34.760 --> 01:01:38.500 A hundred views. Sounds good. That is more than 01:01:38.500 --> 01:01:44.579 perfect. Yep. And do you want to show something 01:01:44.579 --> 01:01:47.539 about Rio? Like any features that you want to 01:01:47.539 --> 01:01:49.380 show about it now that we're looking at your 01:01:49.380 --> 01:01:53.760 screen? Sounds good. I think like that. Let me 01:01:53.760 --> 01:01:56.599 think what I was working. Actually, before I 01:01:56.599 --> 01:02:00.039 show Rio, can I show one thing before? Yep, yep, 01:02:00.059 --> 01:02:04.309 yep. Sure. Because I have been working. on this 01:02:04.309 --> 01:02:08.150 project call it misty which oops which is like 01:02:08.150 --> 01:02:12.610 uh which is basically a shell parser formatter 01:02:12.610 --> 01:02:17.929 and interpreter and i wrote down here i just 01:02:17.929 --> 01:02:21.409 want to learn but actually it's more than that 01:02:21.409 --> 01:02:23.730 i realized that there was like few projects to 01:02:23.730 --> 01:02:29.110 parse so and interpret shell in rust so i was 01:02:29.110 --> 01:02:31.230 just like man i want to do this like i want to 01:02:31.230 --> 01:02:34.269 you know like do this so other people can use 01:02:34.269 --> 01:02:39.309 so technically like uh either you would have 01:02:39.309 --> 01:02:42.510 your parser like you would like to use the parser 01:02:42.510 --> 01:02:49.809 to test something like perfect cargo like my 01:02:49.809 --> 01:02:52.429 keyboard actually i've changed it let me see 01:02:52.429 --> 01:02:55.670 if i can configure okay i'll try it this way 01:02:55.670 --> 01:02:59.960 should be okay Now it's working as a shell. You 01:02:59.960 --> 01:03:03.940 see it's basically a batch, a real writing batch 01:03:03.940 --> 01:03:08.739 to Rust. And there's so much actually to do. 01:03:08.860 --> 01:03:12.039 For example, if you want to set the environment 01:03:12.039 --> 01:03:18.400 variable, like that variable, one, two, three, 01:03:18.599 --> 01:03:27.650 then this is set in the environment. and like 01:03:27.650 --> 01:03:29.610 should be there and i think that this is like 01:03:29.610 --> 01:03:32.590 uh it's a long project like uh one thing that 01:03:32.590 --> 01:03:36.309 i'm looking forward to see is like people actually 01:03:36.309 --> 01:03:40.809 from different like perspective and like uh like 01:03:40.809 --> 01:03:45.190 different products to use because like like for 01:03:45.190 --> 01:03:47.130 example there is many products that are written 01:03:47.130 --> 01:03:51.329 in rust and they have to like parse bash or shell 01:03:51.880 --> 01:03:54.260 in a very weird way and i hope that this project 01:03:54.260 --> 01:03:57.400 actually can help that like so people get for 01:03:57.400 --> 01:04:04.420 the you know test or like write that better totally 01:04:04.420 --> 01:04:08.539 like better code with like a proper parser so 01:04:08.539 --> 01:04:12.119 instead of using uh well instead of creating 01:04:12.119 --> 01:04:15.579 a bash script that that's going to use bash your 01:04:15.579 --> 01:04:18.760 script would use this tool that you're creating 01:04:18.760 --> 01:04:26.860 right Almost there. I'm gonna show you. Forget 01:04:26.860 --> 01:04:36.900 what you saw now here. This is basically the 01:04:36.900 --> 01:04:40.300 interpreter. I'm running the interpreter. So 01:04:40.300 --> 01:04:44.079 it is not connected to the parse. But one thing 01:04:44.079 --> 01:04:46.320 that I'm looking forward with the parse is basically 01:04:46.320 --> 01:04:51.519 like, for example, let's say that you write let's 01:04:51.519 --> 01:04:55.639 say cat uh i don't know like and then readme 01:04:55.639 --> 01:05:01.659 dot md like how do you actually parse that in 01:05:01.659 --> 01:05:05.219 rust like there is no parse to batch at least 01:05:05.219 --> 01:05:08.340 i could not find any parser to batch so you don't 01:05:08.340 --> 01:05:11.320 know if cat is like a keyword this is a string 01:05:11.320 --> 01:05:15.619 like it sure so it's a string but then if all 01:05:15.619 --> 01:05:18.380 this is like strings what if what happens if 01:05:18.380 --> 01:05:22.599 i do this You know what I mean? So there is no 01:05:22.599 --> 01:05:27.539 tooling to distinct the tokens of that content 01:05:27.539 --> 01:05:31.840 in rough. And so I have been working on this 01:05:31.840 --> 01:05:37.739 for people actually use to write good tests or 01:05:37.739 --> 01:05:40.980 if they want to use a batch for something or 01:05:40.980 --> 01:05:44.280 a shell for something. So they'll be able to, 01:05:44.340 --> 01:05:48.340 for example, get this content here. and and then 01:05:48.340 --> 01:05:51.500 no like oh it's like two two strings with like 01:05:51.500 --> 01:05:55.619 a one like operator and then other string and 01:05:55.619 --> 01:05:58.119 then do whatever they want with the information 01:05:58.119 --> 01:06:01.199 so it's like uh for example if you have like 01:06:01.199 --> 01:06:05.260 a if you're a maintain of like a package manager 01:06:05.260 --> 01:06:09.519 and you have like package build files like you 01:06:09.519 --> 01:06:11.940 probably would like to write that for that so 01:06:11.940 --> 01:06:16.940 you will need a parser as well so like i think 01:06:16.940 --> 01:06:18.980 that this is something that i'm looking forward 01:06:18.980 --> 01:06:24.300 to contributing for the rust scenario uh and 01:06:24.300 --> 01:06:27.480 i saw actually some some projects that are real 01:06:27.480 --> 01:06:31.440 right of back the rust which are very exciting 01:06:31.440 --> 01:06:35.599 but i could not find like a proper parser that 01:06:35.599 --> 01:06:40.130 i could use like in my you know i mean like like 01:06:40.130 --> 01:06:43.070 i just wanted to use like a parser of bash and 01:06:43.070 --> 01:06:45.210 i saw some projects that i could use partially 01:06:45.210 --> 01:06:48.530 but every project that like something that was 01:06:48.530 --> 01:06:52.130 lacking like i wanted to have that x glob so 01:06:52.130 --> 01:06:56.829 i cannot do like this you know like uh i cannot 01:06:56.829 --> 01:06:59.769 do like this so everything was like in something 01:06:59.769 --> 01:07:04.690 um but yeah it's like it's a big project i think 01:07:04.690 --> 01:07:07.530 should be i will open this project soon like 01:07:09.019 --> 01:07:11.099 people reached me out that they wanted to use 01:07:11.099 --> 01:07:14.840 but i'm looking forward to to see so this is 01:07:14.840 --> 01:07:18.519 going to be used by people that develop in rust 01:07:18.519 --> 01:07:22.960 mainly correct yeah exactly or if they want to 01:07:22.960 --> 01:07:25.679 use the the because there's two projects on that 01:07:25.679 --> 01:07:28.960 one right they can either use that or they can 01:07:28.960 --> 01:07:32.780 use the shell rewrite so they can use the bash 01:07:32.780 --> 01:07:41.500 like basically in rust it's a it's a big a real 01:07:41.500 --> 01:07:44.380 product i would say okay looking forward and 01:07:44.380 --> 01:07:48.260 i after i have the multiplexer done if i do i'll 01:07:48.260 --> 01:07:50.960 ask you to give it a try and see what you think 01:07:50.960 --> 01:07:54.760 yeah i want to try the the sessions let me know 01:07:54.760 --> 01:07:58.260 when the sessions are are ready i will give it 01:07:58.260 --> 01:08:00.900 a try for sure no exactly i need to port most 01:08:00.900 --> 01:08:02.920 of the features of the micro the ones people 01:08:02.920 --> 01:08:05.579 are not going to use oh yeah You know that's 01:08:05.579 --> 01:08:08.260 going to be tough because Steamworks has a lot 01:08:08.260 --> 01:08:10.280 of different features. So much stuff, yeah. So 01:08:10.280 --> 01:08:14.280 much stuff. All right. Hey, you, man. I think 01:08:14.280 --> 01:08:16.680 the things that I've been working on here has 01:08:16.680 --> 01:08:21.460 been actually quarantine box characters. So it's 01:08:21.460 --> 01:08:24.800 like I want to make the hero render looks better 01:08:24.800 --> 01:08:29.300 and has been complaints over the time, over the 01:08:29.300 --> 01:08:34.550 year. that, like, Unicode icons, they should 01:08:34.550 --> 01:08:37.850 be looking better, and, like, the box drawing 01:08:37.850 --> 01:08:41.270 characters should be looking better. So I have 01:08:41.270 --> 01:08:45.949 been working in many PRs I can show, like, so, 01:08:46.069 --> 01:08:50.850 like, you guys have a better idea. I'll just 01:08:50.850 --> 01:08:54.470 pop here. So it's, like, this is the current 01:08:54.470 --> 01:08:57.970 PR that I'm working now. And then you see I need 01:08:57.970 --> 01:09:02.359 to do every character here. because like so it 01:09:02.359 --> 01:09:06.020 all right they should look better right yeah 01:09:06.020 --> 01:09:10.319 it's like uh like it does not feel weird when 01:09:10.319 --> 01:09:16.279 i render them either like many terminals what 01:09:16.279 --> 01:09:19.920 they do is like they they resize or they fit 01:09:19.920 --> 01:09:24.619 they scale the character to the cell dimension 01:09:24.619 --> 01:09:29.289 and he actually will do that as well but You 01:09:29.289 --> 01:09:32.430 cannot draw the character by yourself. It just 01:09:32.430 --> 01:09:34.630 feels better. You know what I mean? Like, Kitty 01:09:34.630 --> 01:09:39.890 does that so good. And Ghost as well. Both Terminals 01:09:39.890 --> 01:09:43.250 actually, they draw a lot of characters. And 01:09:43.250 --> 01:09:47.489 then, like, they know, like, for example, Alacrita. 01:09:47.590 --> 01:09:51.850 So there's a lot of box characters. And... but 01:09:51.850 --> 01:09:53.970 it's like if they get this and they're like okay 01:09:53.970 --> 01:09:55.989 like it's a double cross like then i'm gonna 01:09:55.989 --> 01:09:58.649 draw myself instead of you know get from the 01:09:58.649 --> 01:10:02.250 text belief or you know for you know the font 01:10:02.250 --> 01:10:06.390 atlas or something and it just feels better because 01:10:06.390 --> 01:10:09.550 like it it is kind of the drawing is based on 01:10:09.550 --> 01:10:13.170 the font data they have so for example if you're 01:10:13.170 --> 01:10:16.029 using a specific type of font he's gonna try 01:10:16.029 --> 01:10:19.970 to match with the stroke of that font so it feels 01:10:21.379 --> 01:10:25.699 Much like I can say it feels that the the icon 01:10:25.699 --> 01:10:29.840 was made that font but was like, uh, which is 01:10:29.840 --> 01:10:31.859 funny because many people create issues in here 01:10:31.859 --> 01:10:36.319 like Oh, why? Why my this is not working? Why 01:10:36.319 --> 01:10:39.560 that is not working? No, I mean and then I don't 01:10:39.560 --> 01:10:42.920 know how to explain to them that some fonts They're 01:10:42.920 --> 01:10:44.960 not being coming from anywhere. They're being 01:10:44.960 --> 01:10:49.500 wrong and it's just like the people don't really 01:10:49.500 --> 01:10:52.100 understand there is a magic happening in the 01:10:52.100 --> 01:10:54.739 background it's like the the terminal is actually 01:10:54.739 --> 01:10:58.680 making that look better for you so it's like 01:10:58.680 --> 01:11:02.739 man it's a lot of stuff there's a lot of stuff 01:11:02.739 --> 01:11:09.600 to do like but i now i did the most part i think 01:11:09.600 --> 01:11:13.600 it's just a matter of like fixing a test but 01:11:13.600 --> 01:11:16.000 for example if i go for the double cross and 01:11:16.000 --> 01:11:22.970 i run here and then you see like they're still 01:11:22.970 --> 01:11:30.229 ongoing stuff like uh get this here like it should 01:11:30.229 --> 01:11:34.569 be like it looks like you know that fits this 01:11:34.569 --> 01:11:38.130 font you know what i mean so it's like it does 01:11:38.130 --> 01:11:41.649 not overflow it fits the dimension of the cell 01:11:41.649 --> 01:11:46.369 and it looks you know like handmade or the terminal 01:11:48.239 --> 01:11:50.119 yeah it's something that i've been working a 01:11:50.119 --> 01:11:54.640 lot in the past weeks like uh hope that i'll 01:11:54.640 --> 01:11:56.779 get this done like the beginning of the next 01:11:56.779 --> 01:12:00.220 month and meanwhile you know fixing other stuff 01:12:00.220 --> 01:12:04.159 like i was picking fixing like uh the flickering 01:12:04.159 --> 01:12:06.699 like was flickering for some applications within 01:12:06.699 --> 01:12:10.359 the ty and then i fixed it that yesterday so 01:12:10.359 --> 01:12:13.939 it's like it's you know there's a lot of things 01:12:13.939 --> 01:12:18.180 like this small stuff that comes up and then 01:12:18.180 --> 01:12:24.380 you need to like do the proper fixes and the 01:12:24.380 --> 01:12:27.500 the filters as well that you were mentioning 01:12:27.500 --> 01:12:31.300 are those similar to the filters that goes i 01:12:31.300 --> 01:12:35.920 can show too yeah i can show too like uh so the 01:12:35.920 --> 01:12:40.020 filters in here they're based on retro arc like 01:12:40.020 --> 01:12:44.960 uh and that means that is like Yes, actually. 01:12:46.340 --> 01:12:54.039 Basically, this guy. That's a lot of everything. 01:12:55.079 --> 01:12:57.840 Basically, I don't know if you guys ever used 01:12:57.840 --> 01:13:03.720 RetroArch for emulation. They have a lot of filters 01:13:03.720 --> 01:13:09.899 for playing old games and stuff. And RetroArch 01:13:09.899 --> 01:13:16.699 filters. So you have this shader process, but 01:13:16.699 --> 01:13:19.960 there's a place in the kit of Disneyland shaders 01:13:19.960 --> 01:13:24.720 where you can do a lot of magic. And I can show 01:13:24.720 --> 01:13:31.720 some to you guys already. But you see, it's funny 01:13:31.720 --> 01:13:38.729 because it does change how you see stuff. Yep. 01:13:38.810 --> 01:13:42.810 And there's two, actually, filters that are pivoting 01:13:42.810 --> 01:13:46.010 here. Otherwise, you need to... I can show the... 01:13:46.010 --> 01:13:54.310 Otherwise, like, this is the pivoting, for example. 01:13:54.729 --> 01:13:58.729 But otherwise, you will need to map. Like, you 01:13:58.729 --> 01:14:02.090 need to, like, pass the path of this lengthy 01:14:02.090 --> 01:14:05.229 pipe, and then it will do something for you. 01:14:05.920 --> 01:14:09.000 i'll not scroll down so there is no spoiler but 01:14:09.000 --> 01:14:11.960 you guys already saw in the in the video and 01:14:11.960 --> 01:14:16.979 like yeah so let me get all right let me get 01:14:16.979 --> 01:14:26.779 that so all right so i'll just go for render 01:14:28.359 --> 01:14:30.479 And I think one important thing to mention is 01:14:30.479 --> 01:14:34.600 that he has a render mode that is like a video 01:14:34.600 --> 01:14:39.699 game, so it renders forever. But you don't necessarily 01:14:39.699 --> 01:14:45.899 need to have that. You can use it with events 01:14:45.899 --> 01:14:48.760 that basically how the nodes work. They type 01:14:48.760 --> 01:14:51.579 something, they render something. That's kind 01:14:51.579 --> 01:15:01.539 of a random necessity. But all right. So filters. 01:15:03.079 --> 01:15:11.600 And then all right. Oops. So I do this. And then 01:15:11.600 --> 01:15:15.000 boom. Like that. All right. I didn't know like 01:15:15.000 --> 01:15:20.199 that. The CRT effect. Exactly. Then you can do 01:15:20.199 --> 01:15:26.359 like you go here. I forgot I had actually one 01:15:26.359 --> 01:15:29.939 good example, CRT. I don't remember now. But, 01:15:30.020 --> 01:15:35.100 you know, like, it feels like... Like, ideally, 01:15:35.260 --> 01:15:37.140 it's like giving power to people to make the 01:15:37.140 --> 01:15:40.260 terminal how they want to feel. So there's many 01:15:40.260 --> 01:15:42.380 people now that are writing their own filters 01:15:42.380 --> 01:15:46.960 to him. And, like, one guy actually in the Discord 01:15:46.960 --> 01:15:52.199 has been quite active, like, right here. on that 01:15:52.199 --> 01:15:55.979 matter like he even has video writing like a 01:15:55.979 --> 01:16:00.380 blog post on how to write your own like shader 01:16:00.380 --> 01:16:07.739 type effect so let's see how it goes oh and yeah 01:16:07.739 --> 01:16:12.479 i remember i don't know was it you the one that 01:16:12.479 --> 01:16:16.600 shared in twitter like uh some effects that it 01:16:16.600 --> 01:16:20.090 looked like fire and i don't know when you were 01:16:20.090 --> 01:16:25.689 typing stuff yeah that was this guy i think he 01:16:25.689 --> 01:16:31.550 did for his editor zach uh and i thought i was 01:16:31.550 --> 01:16:34.649 going to do that for him as well which i which 01:16:34.649 --> 01:16:37.649 i want to do actually but i think first i will 01:16:37.649 --> 01:16:42.369 start with the the cursor of the animated oh 01:16:42.369 --> 01:16:46.689 the neopi thingy right Yeah, it's amazing. I 01:16:46.689 --> 01:16:49.630 actually have it here. I cannot wait to finish 01:16:49.630 --> 01:16:52.050 porting that to you so I can use that in my daily 01:16:52.050 --> 01:16:56.069 life. Yeah, because it's helpful. It helps you 01:16:56.069 --> 01:17:01.010 see where you're at, right? At least to me, it 01:17:01.010 --> 01:17:04.430 helps me see. It's a cosmetic, man. Let's not 01:17:04.430 --> 01:17:08.050 lie here. It just makes everything feel better. 01:17:08.210 --> 01:17:11.569 Let's put it that way. Yeah, let's not lie. It's 01:17:11.569 --> 01:17:15.100 just cosmetic. You're right. No, but my boss 01:17:15.100 --> 01:17:19.119 and I, like, we... Man, we're such a big fan 01:17:19.119 --> 01:17:22.300 of that, like, and actually had a project from 01:17:22.300 --> 01:17:25.420 one guy that he was able to do that working for 01:17:25.420 --> 01:17:34.060 any VIN. So it works for, you know, Apple Terminal 01:17:34.060 --> 01:17:38.340 and everything. So, like, basically he did a 01:17:38.340 --> 01:17:41.579 VIN plugin that works for every terminal. It 01:17:41.579 --> 01:17:46.180 looks like the animated cursor. I see. So it's 01:17:46.180 --> 01:17:49.539 great. Yeah. Neovite is the one that started 01:17:49.539 --> 01:17:53.640 with all that. I remember when I saw the cursor 01:17:53.640 --> 01:17:56.399 in Neovite, it was like, what is this thing? 01:17:56.520 --> 01:17:59.420 And it looked, yeah, liked it. So now... Man, 01:17:59.439 --> 01:18:01.960 but this is the thing. Like, I want to do more 01:18:01.960 --> 01:18:04.039 versions of the cursor. I just don't want to 01:18:04.039 --> 01:18:07.100 spoil it, spoil it to the spoiler yet. But I 01:18:07.100 --> 01:18:09.720 think, like... we have like that version from 01:18:09.720 --> 01:18:12.760 new environment that is great but we have like 01:18:12.760 --> 01:18:16.260 i have other ideas that are based on vs code 01:18:16.260 --> 01:18:19.439 cursor there's one cursor from vs code that looks 01:18:19.439 --> 01:18:22.979 like chunks a bit like um and then open long 01:18:22.979 --> 01:18:27.239 and i'll i'll try to copy that to you as well 01:18:27.239 --> 01:18:31.279 i think it'll be fun yeah and you know if you 01:18:31.279 --> 01:18:35.859 come up with something um creative it's gonna 01:18:35.859 --> 01:18:39.449 call attention people's gonna be like what is 01:18:39.449 --> 01:18:41.949 that how did he do that what is that terminal 01:18:41.949 --> 01:18:45.289 they're gonna install that they're gonna port 01:18:45.289 --> 01:18:48.090 that to ghost and kitty but then like but you 01:18:48.090 --> 01:18:51.710 were first yeah i don't know i don't know if 01:18:51.710 --> 01:18:55.630 i actually i think i have a thing with here that's 01:18:55.630 --> 01:18:59.430 like as long my friends use all good it's like 01:18:59.430 --> 01:19:02.970 it's like if the people that i work with use 01:19:02.970 --> 01:19:07.439 then i'm good so it's like yeah i'm happy that 01:19:07.439 --> 01:19:13.100 it's like how people use like how my co -workers 01:19:13.100 --> 01:19:16.420 use i still need to convince the rest actually 01:19:16.420 --> 01:19:19.479 one one co -worker of mine he he really wants 01:19:19.479 --> 01:19:23.260 to use but uh there is one issue here that i 01:19:23.260 --> 01:19:26.239 need to fix for him to join which i hopefully 01:19:26.239 --> 01:19:30.880 fix will fix like in this version but i think 01:19:30.880 --> 01:19:33.039 that you know there's my main drive like get 01:19:33.039 --> 01:19:36.949 people that i know using it because it kind of 01:19:36.949 --> 01:19:39.890 gets like it gets nice like when you talk with 01:19:39.890 --> 01:19:43.369 people and then they're like hey man like you're 01:19:43.369 --> 01:19:46.369 you're you're perfect there's no work and i think 01:19:46.369 --> 01:19:50.789 that that's cool okay yeah that's that's interesting 01:19:50.789 --> 01:19:54.270 and what is the game boy thing that you mentioned 01:19:54.270 --> 01:19:56.909 that you're working on so what is that you want 01:19:56.909 --> 01:20:00.130 to show it like do you run it and you said that 01:20:00.130 --> 01:20:03.689 you run it on rio right Oh yeah, but I don't 01:20:03.689 --> 01:20:06.729 actually have it in this computer. Oh, you don't 01:20:06.729 --> 01:20:14.270 have it here. Yeah, I have it here. This Linux 01:20:14.270 --> 01:20:18.670 machine. Oh, okay. In the other computer. Yeah, 01:20:19.369 --> 01:20:22.550 my ARC actually is. And I have it in my personal 01:20:22.550 --> 01:20:26.329 Mac. Oh, okay. I don't remember the last time 01:20:26.329 --> 01:20:30.520 I opened my personal Mac. Oh, okay. the instructions 01:20:30.520 --> 01:20:34.539 are in your in the github repo right yeah exactly 01:20:34.539 --> 01:20:39.460 so but you can actually run uh no mistake and 01:20:39.460 --> 01:20:43.100 you can do cargo and actually show let me get 01:20:43.100 --> 01:20:49.840 like i think it's basically yes let me get this 01:20:49.840 --> 01:20:53.899 to here so basically you can just run cargo install 01:20:53.899 --> 01:20:59.279 game boy like and and then you run game boy with 01:20:59.279 --> 01:21:02.640 the path of the file then you want to run the 01:21:02.640 --> 01:21:06.619 game and it should work but i don't have any 01:21:06.619 --> 01:21:10.539 like any legal rule here because i think that 01:21:10.539 --> 01:21:13.300 they think like emulation is legal like we use 01:21:13.300 --> 01:21:18.199 like games from nintendo like and it's like then 01:21:18.199 --> 01:21:21.779 becomes illegal because quickly you know so i 01:21:21.779 --> 01:21:26.289 used to download everything from uh Like from 01:21:26.289 --> 01:21:30.229 this side each IO they love to like so they made 01:21:30.229 --> 01:21:34.390 a lot of games and they post the room there But 01:21:34.390 --> 01:21:37.909 they're legal, right? Yeah, there you go. And 01:21:37.909 --> 01:21:40.189 then you can just like a download for example 01:21:40.189 --> 01:21:45.510 open here Actually this one was like man people 01:21:45.510 --> 01:21:49.069 are so excited about this one it's like and you 01:21:49.069 --> 01:21:55.939 can just download the demo Well, unless you own 01:21:55.939 --> 01:22:00.319 the game and then you put the date of the game 01:22:00.319 --> 01:22:04.800 that you have to, you know, a room file, which 01:22:04.800 --> 01:22:08.680 I did one time, but it's like too much work, 01:22:08.720 --> 01:22:14.239 man. It's just like, you know, like just download 01:22:14.239 --> 01:22:15.920 from the legal one, you're going to be okay. 01:22:16.399 --> 01:22:21.439 Okay. Okay. Okay. So the cursor animation is 01:22:21.439 --> 01:22:24.520 coming soon. now you mentioned that you work 01:22:24.520 --> 01:22:28.899 at charm i have seen seen that charm name a lot 01:22:28.899 --> 01:22:31.920 of different places videos but i don't know what 01:22:31.920 --> 01:22:35.439 it is like you want to talk about it or maybe 01:22:35.439 --> 01:22:40.760 show it like of course of course i i actually 01:22:40.760 --> 01:22:44.840 okay let's let's do it okay let me let me just 01:22:44.840 --> 01:22:47.979 get yeah get ready and you let me know and i 01:22:47.979 --> 01:22:50.640 will switch to your screen when you're when you're 01:22:50.640 --> 01:22:55.140 ready all right so because i was working on this 01:22:55.140 --> 01:23:02.140 branch and then now all right so let's go okay 01:23:02.140 --> 01:23:07.560 here we go so charm basically i can actually 01:23:07.560 --> 01:23:13.420 open there and do you want to remove the real 01:23:13.420 --> 01:23:18.000 filter so we can see so we can see it but i can't 01:23:18.000 --> 01:23:20.300 i can't do it for now so like some effects are 01:23:20.300 --> 01:23:22.720 cool to see with this but i can't remove later 01:23:22.720 --> 01:23:27.899 okay okay that's okay yep so like charm is like 01:23:27.899 --> 01:23:30.979 man we do a lot of stuff for terminals and like 01:23:30.979 --> 01:23:34.880 uh it's very likely that you use it some like 01:23:34.880 --> 01:23:40.380 terminal ui app that has been using something 01:23:40.380 --> 01:23:45.210 the charm made and it's like um I was actually 01:23:45.210 --> 01:23:48.630 surprised because I realized these days, Super5, 01:23:49.010 --> 01:23:53.750 you know, the terminal program, Super5? I don't 01:23:53.750 --> 01:23:57.470 think I have heard it. No. Yeah, I think it's 01:23:57.470 --> 01:24:05.149 getting Super5. Oops, Super5. It's to show your 01:24:05.149 --> 01:24:11.430 file, basically. It's like a Yassi type of thing, 01:24:11.510 --> 01:24:16.829 like a file. Yeah, you know, like, he had another 01:24:16.829 --> 01:24:21.489 Prime Explorer, like, you know, like, Yasi, Ranger, 01:24:21.930 --> 01:24:25.930 everything. And, but, like, I was surprised that 01:24:25.930 --> 01:24:30.449 it was made with Charm stuff. And, you know, 01:24:30.470 --> 01:24:34.329 they have so much stuff, like, ah, this is heavily 01:24:34.329 --> 01:24:38.289 used, like, it's used by GitHub. Like, this thing 01:24:38.289 --> 01:24:41.979 for sending emails through Terminal. And like 01:24:41.979 --> 01:24:45.420 bubble tea, there's like this huge, like in the 01:24:45.420 --> 01:24:49.500 goal ecosystem. It's like, you know, like it's 01:24:49.500 --> 01:24:54.380 like a terminal UI framework. And then like you 01:24:54.380 --> 01:24:57.779 can create like, like, you know, applications 01:24:57.779 --> 01:25:04.840 using like bubble tea and like wish like to create 01:25:04.840 --> 01:25:10.899 like apps. What do you mean SSH apps with Wish? 01:25:12.060 --> 01:25:15.420 Let's say that you go for like, I think there's 01:25:15.420 --> 01:25:18.880 a good example here. For example, you go, you 01:25:18.880 --> 01:25:22.659 do like, there's actually someone added here. 01:25:23.199 --> 01:25:26.220 When you, that's a product actually people added. 01:25:26.539 --> 01:25:30.380 The thing is like, when you go, let's say they 01:25:30.380 --> 01:25:34.739 want to go and buy coffee. Like you go for the 01:25:34.739 --> 01:25:38.090 website, right? Yep. I don't know, like buycoffee 01:25:38.090 --> 01:25:41.609 .co. So one thing they could do is just like 01:25:41.609 --> 01:25:46.550 SSH that domain and then you could just integrate, 01:25:46.750 --> 01:25:50.210 you know, like use that to, you know, buy coffee. 01:25:50.810 --> 01:25:57.189 Like Prime and TJ's and all of those guys' coffee 01:25:57.189 --> 01:26:01.369 thingy, right? Yeah, if I'm not mistaken, it 01:26:01.369 --> 01:26:07.060 uses like Wish actually. Terminal dot... Terminal 01:26:07.060 --> 01:26:11.239 dot shop. Yeah, if I'm not mistaken, I'm not 01:26:11.239 --> 01:26:15.899 sure that they use Wish. Because I remember we 01:26:15.899 --> 01:26:19.420 actually demoed something from them, I guess. 01:26:19.560 --> 01:26:21.479 I don't remember now. But it's basically the 01:26:21.479 --> 01:26:25.619 idea. You can go there and then you buy the thing 01:26:25.619 --> 01:26:28.060 through there. Which I think is awesome. You 01:26:28.060 --> 01:26:31.880 know, bring the terminal back to the game. and 01:26:31.880 --> 01:26:36.359 the lip gloss is basically to create like layout 01:26:36.359 --> 01:26:40.680 without depending on faculty there's so much 01:26:40.680 --> 01:26:44.079 projects actually glamour like for render markdown 01:26:44.079 --> 01:26:49.220 is that like a markdown editor that glamour yeah 01:26:49.220 --> 01:26:55.060 okay exactly so it's like uh let me get oh it's 01:26:55.060 --> 01:27:01.489 like uh yeah you see it's basically like But 01:27:01.489 --> 01:27:09.390 here you're having in go like But Like if you 01:27:09.390 --> 01:27:11.810 want the render itself like you have to go low, 01:27:11.970 --> 01:27:18.369 which is basically the episode Okay, so this 01:27:18.369 --> 01:27:22.909 is Assuming you don't use any of them, right? 01:27:23.010 --> 01:27:27.449 So the reason why mine looks like this right 01:27:27.449 --> 01:27:32.680 now is because um i'm inside new of him and that's 01:27:32.680 --> 01:27:35.479 where all the styles are applied and all that 01:27:35.479 --> 01:27:39.100 stuff so this other one that you're showing right 01:27:39.100 --> 01:27:42.760 now is if you're will be with yeah if you're 01:27:42.760 --> 01:27:46.960 not using it without it right oh so you just 01:27:46.960 --> 01:27:50.859 open the file with this glow thing and it looks 01:27:50.859 --> 01:27:56.520 like that yeah but man so much so many projects 01:27:56.520 --> 01:27:58.699 actually i think there's like it's hard to to 01:27:58.699 --> 01:28:01.479 summarize i think that mod is one that's getting 01:28:01.479 --> 01:28:05.079 really fun now there's like it's like you can 01:28:05.079 --> 01:28:08.119 connect with the ai in the terminal it's like 01:28:08.119 --> 01:28:12.539 it you know so good i think that this is by far 01:28:12.539 --> 01:28:17.060 my favorite of sean and if charm allowed me to 01:28:17.060 --> 01:28:19.739 rewrite this to rust i would do it the blink 01:28:19.739 --> 01:28:24.500 of eye but it's like i love gun i think that 01:28:24.500 --> 01:28:26.500 it's like i don't know i'm not sure if it actually 01:28:26.500 --> 01:28:28.859 needs to be rewritten in rust it's just because 01:28:28.859 --> 01:28:35.100 i am like to rewrite everything. Too rough, I 01:28:35.100 --> 01:28:37.920 guess. But it's like... And what does that come 01:28:37.920 --> 01:28:45.520 for? Like, alright, so take a look with me. So 01:28:45.520 --> 01:28:49.159 this is a good example. So you do that. Oh, wait. 01:28:49.380 --> 01:28:54.760 I mean... Yeah, okay. There's a lot of things 01:28:54.760 --> 01:28:57.479 happening now, so it gets a bit confused. But 01:28:57.479 --> 01:29:01.619 for example... let's do the tutorial so you write 01:29:01.619 --> 01:29:04.960 like gun choose so you give the options right 01:29:04.960 --> 01:29:10.199 fix fit talk style and then you put like a placeholder 01:29:10.199 --> 01:29:15.880 and you do like you know like you can also do 01:29:15.880 --> 01:29:19.020 in the different way and you can do like a conform 01:29:19.020 --> 01:29:22.439 and then it you know like it does that automatically 01:29:22.439 --> 01:29:26.899 for you like it kind of like and it will return 01:29:26.899 --> 01:29:31.229 for you in the shell script the value so it's 01:29:31.229 --> 01:29:34.229 like it's useful for shell scripts and if it's 01:29:34.229 --> 01:29:36.770 useful for shell scripts you can actually pipe 01:29:36.770 --> 01:29:39.770 that information right so it's like you can do 01:29:39.770 --> 01:29:42.569 like a gun to do something and then you add a 01:29:42.569 --> 01:29:45.210 pipe and then you return the information to the 01:29:45.210 --> 01:29:50.289 other combat so it's like people doing like a 01:29:50.289 --> 01:29:53.829 combo of gun so many times like gun this gun 01:29:53.829 --> 01:29:57.000 that pipe and this and that I think that that's 01:29:57.000 --> 01:29:59.720 actually my favorite feature, to be honest. And 01:29:59.720 --> 01:30:06.060 then, like, you know, input and move to an answer. 01:30:07.079 --> 01:30:11.500 And then it has so much stuff that it kind of 01:30:11.500 --> 01:30:14.279 feels like a better shell, you know what I mean? 01:30:15.239 --> 01:30:19.159 Like, it's not really a better shell. It does 01:30:19.159 --> 01:30:22.859 not have the shell power, but it kind of gives 01:30:22.859 --> 01:30:29.539 you, like, utility to use as like a shell assistant 01:30:29.539 --> 01:30:34.960 or something but but i also buy the work there 01:30:34.960 --> 01:30:38.479 if i was fan of charm before being hired so take 01:30:38.479 --> 01:30:44.899 that in consideration okay so this is if you 01:30:44.899 --> 01:30:48.579 this is if you run a lot of bash scripts right 01:30:48.579 --> 01:30:51.840 it makes them look nice because i see that it 01:30:51.840 --> 01:30:55.220 looks nice it has like a code block type of thingy 01:30:55.220 --> 01:30:59.220 there at the bottom yeah exactly and then yeah 01:30:59.220 --> 01:31:01.600 there's like other things that people do as well 01:31:01.600 --> 01:31:10.539 there's like let me see like file page here like 01:31:10.539 --> 01:31:14.159 spin there's tape as well i don't know where's 01:31:14.159 --> 01:31:18.979 the print like in the case of this style right 01:31:18.979 --> 01:31:24.470 like yeah but yeah it makes looks My shell looks 01:31:24.470 --> 01:31:28.310 better, I guess. Yeah, because, for example, 01:31:28.529 --> 01:31:34.289 I run bash scripts a lot, right? If I want to 01:31:34.289 --> 01:31:36.289 create a new VM, or let's say that I want to 01:31:36.289 --> 01:31:40.449 create four VMs in my home lab, right? I have 01:31:40.449 --> 01:31:44.189 bash scripts, but it doesn't look as nice. So 01:31:44.189 --> 01:31:47.710 I guess I could use that gum thingy that you 01:31:47.710 --> 01:31:52.869 showed right now to, I don't know. But do I have 01:31:52.869 --> 01:31:57.020 to? Do I have to rewrite my bash scripts? No, 01:31:57.359 --> 01:32:00.720 you actually keep your bash script the way that 01:32:00.720 --> 01:32:03.260 you want, but the part that you actually need 01:32:03.260 --> 01:32:07.479 the data, you integrate with GAN. For example, 01:32:07.840 --> 01:32:11.180 if you, for example, wait for a read line in 01:32:11.180 --> 01:32:15.119 the shell, instead of you wait for the read line, 01:32:15.199 --> 01:32:19.979 you can call GAN input, and then magically that 01:32:19.979 --> 01:32:23.470 would happen for you. like, magically, you know? 01:32:23.590 --> 01:32:27.210 It's like, that would happen for you. I was like, 01:32:27.430 --> 01:32:29.689 you would need to integrate by small pieces. 01:32:30.569 --> 01:32:34.670 I have to take a look. And are these tools free? 01:32:34.750 --> 01:32:38.390 Like, how does Charm sustain itself? Is it open 01:32:38.390 --> 01:32:43.369 source? How does all of that work? Man, I think 01:32:43.369 --> 01:32:45.930 it's funny because everyone actually asked that 01:32:45.930 --> 01:32:50.119 question. Like, Sharp nowadays, like, is a company 01:32:50.119 --> 01:32:53.539 that, like, leads up for investment as well. 01:32:53.680 --> 01:32:57.760 So, like, he's, like, invested by big companies. 01:32:58.439 --> 01:33:04.619 And, you know, like, I confess they're not the 01:33:04.619 --> 01:33:07.880 most business. So, it's like, I could be actually 01:33:07.880 --> 01:33:11.979 talking about, like, venture capital. I don't 01:33:11.979 --> 01:33:15.979 know what disturbs me. I'm just a humble programmer. 01:33:16.680 --> 01:33:20.699 but uh but it's like we we actually get like 01:33:20.699 --> 01:33:24.640 investments and like charm has like always has 01:33:24.640 --> 01:33:28.119 done open source so it's like uh in the way the 01:33:28.119 --> 01:33:31.500 companies rely on charm as well so like for example 01:33:31.500 --> 01:33:37.279 github use a lot of stuff from charm um so frankly 01:33:37.279 --> 01:33:41.960 i i don't think i'm this person like to give 01:33:41.960 --> 01:33:44.720 the best answer but i know that things work like 01:33:44.720 --> 01:33:49.739 that like out of the out of the hood and everything 01:33:49.739 --> 01:33:54.279 is open source and as a user do i have to pay 01:33:54.279 --> 01:33:58.600 for any of the tools no you don't need to just 01:33:58.600 --> 01:34:02.720 choose and do the best you want with it interesting 01:34:02.720 --> 01:34:06.800 i didn't know i did watch some videos and it 01:34:06.800 --> 01:34:10.300 looks quite nice really polished and i was like 01:34:10.680 --> 01:34:15.699 but what is this company doing then like i i 01:34:15.699 --> 01:34:18.699 kind of get it now so everyone ever gives the 01:34:18.699 --> 01:34:22.000 same question even before drawing charm and i 01:34:22.000 --> 01:34:25.180 had i don't know if i had the the same question 01:34:25.180 --> 01:34:28.659 because like before joining charm i thought like 01:34:28.659 --> 01:34:32.100 well if it's a company that is used by so many 01:34:32.100 --> 01:34:35.460 people thousands and thousands i feel like yeah 01:34:35.460 --> 01:34:38.399 in some way it's gonna be someone's gonna be 01:34:38.399 --> 01:34:41.600 paying for that like like to keep that company 01:34:41.600 --> 01:34:43.859 alive and that's what i thought before joining 01:34:43.859 --> 01:34:47.520 but it's like uh boy confess that it's not like 01:34:47.520 --> 01:34:51.579 and i don't think i'm the money person to be 01:34:51.579 --> 01:34:54.699 honest i otherwise i probably would have charged 01:34:54.699 --> 01:35:00.840 for here okay and um thanks for sharing about 01:35:00.840 --> 01:35:03.939 charm you know i didn't i didn't know much about 01:35:03.939 --> 01:35:07.579 it but now i get a better idea yep now i know 01:35:07.579 --> 01:35:14.649 and um You have this blog post. Let's see. What 01:35:14.649 --> 01:35:17.310 is this about? You want to share? You want to 01:35:17.310 --> 01:35:20.850 show that? Of course. I don't want to show the 01:35:20.850 --> 01:35:25.609 editor yet. But I can talk about it. All right. 01:35:25.649 --> 01:35:32.810 Let me share this. And so in November, I started 01:35:32.810 --> 01:35:37.159 to draft. why I'm working on the new, like I 01:35:37.159 --> 01:35:39.739 write a post about why I'm working on the new 01:35:39.739 --> 01:35:45.699 code editor. And like, I mean, I can summarize, 01:35:45.960 --> 01:35:48.699 like I feel that most of the code editors, they 01:35:48.699 --> 01:35:51.079 feel the same, they look the same. And it's just 01:35:51.079 --> 01:35:54.279 like, at the end of the day, you're probably 01:35:54.279 --> 01:35:57.460 just going to end up like returning to VS Code, 01:35:57.720 --> 01:36:01.539 Veeam, or Emacs, wherever you feel comfortable, 01:36:01.819 --> 01:36:07.729 right? I think for me, like, I started to think, 01:36:07.770 --> 01:36:11.289 like, man, I would like to have what Veeam does, 01:36:11.510 --> 01:36:14.630 but in the way that was, like, for everyone. 01:36:15.229 --> 01:36:18.250 Like, a designer could just sit and use a Veeam 01:36:18.250 --> 01:36:22.149 without having to have a learning curve. You 01:36:22.149 --> 01:36:24.149 know what I mean? Like, anyone that's not from 01:36:24.149 --> 01:36:29.189 tech, just use Veeam without need to learn, actually, 01:36:29.270 --> 01:36:33.000 how the editor works. Yep. So... i started to 01:36:33.000 --> 01:36:36.420 think a lot about it and although i was playing 01:36:36.420 --> 01:36:40.159 video games and i was just like yeah i think 01:36:40.159 --> 01:36:43.000 like actually if you do games they are kind of 01:36:43.000 --> 01:36:45.220 self -explanatory you don't need to teach much 01:36:45.220 --> 01:36:48.399 like it just happens like you at some moment 01:36:48.399 --> 01:36:50.739 it starts to get the gameplay you don't think 01:36:50.739 --> 01:36:54.640 like i used to have i used to use now being being 01:36:54.640 --> 01:36:58.100 for a long time like i don't use as i used to 01:36:58.100 --> 01:37:02.640 use now like i before i think that was like I 01:37:02.640 --> 01:37:07.000 used to use those tools a lot to the point where 01:37:07.000 --> 01:37:10.220 I was actually giving trouble to my teammates 01:37:10.220 --> 01:37:13.020 where they had to type on my computer normally 01:37:13.020 --> 01:37:16.920 because they didn't know, like, V, so they were 01:37:16.920 --> 01:37:18.359 like, man, what the hell? Like, I don't know 01:37:18.359 --> 01:37:23.119 what I'm doing here. And it made me thought, 01:37:23.260 --> 01:37:26.659 like, man, I don't know. Like, in the end of 01:37:26.659 --> 01:37:30.500 the day, I think, like, the keyboard -based editor 01:37:30.500 --> 01:37:33.829 should be simple. It should be something that 01:37:33.829 --> 01:37:37.550 is like, like best for you and best for other 01:37:37.550 --> 01:37:42.069 person. And I started to work on Boo. And Boo 01:37:42.069 --> 01:37:44.710 is like, it does work as a GUI and does work 01:37:44.710 --> 01:37:48.289 as like a terminal editor as well. So I can use 01:37:48.289 --> 01:37:51.569 whatever I want, like can use in the terminal 01:37:51.569 --> 01:37:56.390 or you can use as a desktop app. And my idea 01:37:56.390 --> 01:38:00.050 was like to reinvent mouse and mouse free editors. 01:38:00.909 --> 01:38:05.270 So, like, you can actually, you know, like, do 01:38:05.270 --> 01:38:07.390 stuff without feeling like you're playing guitar. 01:38:07.930 --> 01:38:11.090 Because I play guitar, and I feel that every 01:38:11.090 --> 01:38:14.890 time that I type on VIN, I feel like I'm playing 01:38:14.890 --> 01:38:19.989 a note, you know what I mean? And then that mentality 01:38:19.989 --> 01:38:25.850 actually drove me to write Boo. I think my goal 01:38:25.850 --> 01:38:28.270 now is, like, getting to the point where I'd 01:38:28.270 --> 01:38:31.000 share it. like where i am actually comfortable 01:38:31.000 --> 01:38:35.180 to share with other people because like i see 01:38:35.180 --> 01:38:38.140 like in my daily basis like it's really good 01:38:38.140 --> 01:38:42.380 for rust code but it's not really optimized for 01:38:42.380 --> 01:38:47.819 other like language yet so i don't know why like 01:38:47.819 --> 01:38:49.899 i try all the editors i always do that they are 01:38:49.899 --> 01:38:52.539 bloated like you know like there's so much things 01:38:52.539 --> 01:38:55.170 happening and then the end of the day You don't 01:38:55.170 --> 01:38:57.430 really want to be there. Like the editor has 01:38:57.430 --> 01:39:01.270 like a terminal built in. It has like a git div. 01:39:01.569 --> 01:39:04.409 There is so much stuff happening there. And then 01:39:04.409 --> 01:39:05.949 at the end of the day, it's just like, man, what 01:39:05.949 --> 01:39:08.829 are you doing here? Like, it's not really about 01:39:08.829 --> 01:39:11.069 editing code. It's like, it's about everything 01:39:11.069 --> 01:39:14.590 else. I feel like there, this is the thing that 01:39:14.590 --> 01:39:18.149 I like about Tmux, like that you say, I think 01:39:18.149 --> 01:39:20.930 it connects with Boo. When you are in the workspace, 01:39:21.680 --> 01:39:24.079 you don't know which workspace you are you're 01:39:24.079 --> 01:39:26.960 just there it does not feel bloated you know 01:39:26.960 --> 01:39:28.859 what i mean like of course you can put like a 01:39:28.859 --> 01:39:31.479 message there hey you're in the number three 01:39:31.479 --> 01:39:35.859 like in the top of the in the top of tmux you 01:39:35.859 --> 01:39:38.020 can configure stuff but you don't feel like oh 01:39:38.020 --> 01:39:41.659 they are taking your space you know what i mean 01:39:41.659 --> 01:39:44.520 and and this is the thing i noticed in all the 01:39:44.520 --> 01:39:47.520 code editors like the more stuff you add more 01:39:47.520 --> 01:39:51.880 folders you open you just feel like it looks 01:39:51.880 --> 01:39:53.880 like completely different from what it was supposed 01:39:53.880 --> 01:39:56.539 to be. So I feel that most of the actors, they 01:39:56.539 --> 01:40:02.159 were not designed to be, you know, like that 01:40:02.159 --> 01:40:07.800 big sculpted. I feel like being in some way does 01:40:07.800 --> 01:40:11.439 that well because like you change your mentality 01:40:11.439 --> 01:40:16.420 to from editing a folder to edit a file. But 01:40:16.420 --> 01:40:20.390 it's like you're still stuck to the to the guitar 01:40:20.390 --> 01:40:24.130 instrument. So it's like, Oh, I want to, I want 01:40:24.130 --> 01:40:26.750 to go to the Boston. How a person that does not 01:40:26.750 --> 01:40:29.010 knows how to use a beam would do that. They will 01:40:29.010 --> 01:40:32.029 need to Google about it and learn. Oh, I want 01:40:32.029 --> 01:40:33.850 to move to the side. They will need to do this 01:40:33.850 --> 01:40:37.810 and learn. So I have been working on pool, like 01:40:37.810 --> 01:40:43.710 mostly to try to make mouse pre -editors for 01:40:43.710 --> 01:40:46.869 everyone. like you know like a person that does 01:40:46.869 --> 01:40:49.670 not know anything of tech should be able to use 01:40:49.670 --> 01:40:56.670 it as well so yeah is it going to use vim motions 01:40:56.670 --> 01:41:01.710 or vi motions or something different man people 01:41:01.710 --> 01:41:03.949 actually have been asking a lot about it and 01:41:03.949 --> 01:41:06.890 people got excited this is the logo by the way 01:41:06.890 --> 01:41:14.229 i'm sharing now what is that the logo it's like 01:41:14.229 --> 01:41:19.210 uh the logo from the editor who opens like what 01:41:19.210 --> 01:41:22.989 are yeah what is mitchell gonna think with the 01:41:22.989 --> 01:41:27.850 ghosty logo i don't know man this is is a subject 01:41:27.850 --> 01:41:31.430 that like uh but the thing is like he sort of 01:41:31.430 --> 01:41:34.590 inspired me as well like with the ghost because 01:41:34.590 --> 01:41:37.130 the way that he did you know like putting the 01:41:37.130 --> 01:41:40.890 the dev logs and stuff like that it kind of affected 01:41:40.890 --> 01:41:43.359 me like in that way that was just like okay i 01:41:43.359 --> 01:41:46.060 want to do something similar i just didn't know 01:41:46.060 --> 01:41:48.640 that was going to be this similar but the same 01:41:48.640 --> 01:41:55.239 way like uh in the same way it's just like let's 01:41:55.239 --> 01:41:57.899 just think as a ghost from rough version like 01:41:57.899 --> 01:42:04.119 like ghost has the as the zig version but it's 01:42:04.119 --> 01:42:08.199 gonna have no rust version as well but it's like 01:42:08.199 --> 01:42:13.119 how can i say I feel like there's so much room 01:42:13.119 --> 01:42:15.939 for improvements in terms of the experience of 01:42:15.939 --> 01:42:21.439 that, if you know what I mean. For example, you 01:42:21.439 --> 01:42:26.300 said about the enemy now with the README, but 01:42:26.300 --> 01:42:29.399 that thing does not work out of the box with 01:42:29.399 --> 01:42:32.859 the README, like with the Markdown vibes. They 01:42:32.859 --> 01:42:35.439 actually need to configure that, right? They 01:42:35.439 --> 01:42:37.560 need to add a plugin or something that makes 01:42:37.560 --> 01:42:40.579 it look better. I think that this is like a big 01:42:40.579 --> 01:42:45.039 mistake of Nelpy in general. Like people don't 01:42:45.039 --> 01:42:47.460 really care. They don't really want to spend, 01:42:47.520 --> 01:42:50.359 you know, like polishing, like too much stuff. 01:42:50.699 --> 01:42:54.199 And most of the people that polish stuff, they 01:42:54.199 --> 01:42:58.460 use similar stuff. So it's like, oh, I have the 01:42:58.460 --> 01:43:03.720 space. I have this plugin that should mark down 01:43:03.720 --> 01:43:06.539 better. Or I have this other plugin that should 01:43:06.539 --> 01:43:10.810 mark down better. Sure, but one could come as 01:43:10.810 --> 01:43:13.569 default when you could just change as long as 01:43:13.569 --> 01:43:17.470 you wanted, you know what I mean? And I think 01:43:17.470 --> 01:43:21.310 that this is, in my opinion, one of the problems 01:43:21.310 --> 01:43:27.170 with Bing in general. Because sometimes people 01:43:27.170 --> 01:43:29.470 just want to code. They just don't want to spend 01:43:29.470 --> 01:43:34.909 weekends customizing. Months configuring. Yeah, 01:43:34.909 --> 01:43:38.329 exactly. Yeah, I have a colleague that he's years 01:43:38.329 --> 01:43:43.350 actually doing this. So is this more like something 01:43:43.350 --> 01:43:47.270 already just ready for you to code, right? You 01:43:47.270 --> 01:43:49.770 don't need to customize anything. It'll just 01:43:49.770 --> 01:43:53.289 work out of the box and you will not have many 01:43:53.289 --> 01:43:56.930 options to configure as a user, right? It's just... 01:43:56.930 --> 01:44:01.829 Yeah, one thing that Ghosty does well, and I 01:44:01.829 --> 01:44:04.890 agree as well, is like the less configurations, 01:44:05.090 --> 01:44:09.939 the better. like they have this philosophy and 01:44:09.939 --> 01:44:13.300 i don't know if for hew i want to follow that 01:44:13.300 --> 01:44:16.159 philosophy let's leave that for them like they're 01:44:16.159 --> 01:44:18.500 doing that like why he needs to copy them in 01:44:18.500 --> 01:44:22.680 the terminal perspective but for the editor i 01:44:22.680 --> 01:44:28.100 can try to copy that philosophy and try to actually 01:44:28.100 --> 01:44:31.260 making the way where people can just you know 01:44:31.949 --> 01:44:36.409 tune in and just code. But I also think there's 01:44:36.409 --> 01:44:38.710 one thing that's like everything should be removable. 01:44:39.350 --> 01:44:42.510 And I also think that is a mistake from, you 01:44:42.510 --> 01:44:46.010 know, editors that make everything like people. 01:44:46.710 --> 01:44:50.090 But it's like, sometimes like people don't want 01:44:50.090 --> 01:44:54.289 that crap. And it's just like, everything should 01:44:54.289 --> 01:44:57.270 be like, as long as they are there, they should 01:44:57.270 --> 01:45:01.010 be removable. And if they're removable, like, 01:45:01.770 --> 01:45:03.729 It should not affect the person's performance. 01:45:04.130 --> 01:45:08.369 It's the same with some editors that have AI 01:45:08.369 --> 01:45:13.609 or code, like a static analysis. Sometimes you 01:45:13.609 --> 01:45:16.550 disable that, but it still feels that it's slow 01:45:16.550 --> 01:45:21.729 because they're running something that they have 01:45:21.729 --> 01:45:27.369 a thread that is idle, doing nothing. And I think 01:45:27.369 --> 01:45:29.689 that this is a thing for me with a bow I want 01:45:29.689 --> 01:45:31.970 to do in a way where like if people want to have 01:45:31.970 --> 01:45:35.470 literally anything, they can go with it. Like 01:45:35.470 --> 01:45:37.390 they can go with like something that looks like 01:45:37.390 --> 01:45:42.369 a V, very dumb, like very simple and just works. 01:45:42.489 --> 01:45:44.970 Because like sometimes just playing V is also 01:45:44.970 --> 01:45:48.029 good. It's like, you know, it has been good for 01:45:48.029 --> 01:45:52.630 many people for many years. But I think like 01:45:52.630 --> 01:45:55.750 the editor that I want to do is like, it starts 01:45:55.750 --> 01:45:58.590 for you in the way that you don't need to google 01:45:58.590 --> 01:46:03.189 of how things work is that it's just there and 01:46:03.189 --> 01:46:05.770 you don't need to install anything it's just 01:46:05.770 --> 01:46:08.590 there and it's just like you you can actually 01:46:08.590 --> 01:46:11.869 focus on getting your work done like without 01:46:11.869 --> 01:46:15.770 actually kill i need to press i need to change 01:46:15.770 --> 01:46:18.550 this key bind because like this other thing will 01:46:18.550 --> 01:46:22.159 happen Like, I used Veeam and now Veeam and Emac 01:46:22.159 --> 01:46:25.359 for many years. And, man, I spent a lot of time, 01:46:25.460 --> 01:46:29.260 like, making it, you know, I don't know if looking 01:46:29.260 --> 01:46:33.020 nice was my goal, but I wanted to be more, you 01:46:33.020 --> 01:46:37.220 know, productive. And the thing is, like, it's 01:46:37.220 --> 01:46:40.300 like it's a no -ending cycle. Like, you just 01:46:40.300 --> 01:46:43.260 keep finding new stuff. And they developed this 01:46:43.260 --> 01:46:45.720 mentality where you actually start to think about 01:46:45.720 --> 01:46:47.840 plugins all the time and, you know, seek for 01:46:47.840 --> 01:46:53.329 plugins. and i think that this is like man i 01:46:53.329 --> 01:46:55.949 don't know if that's what i want to be you know 01:46:55.949 --> 01:46:59.310 what i mean like yeah makes sense makes sense 01:46:59.310 --> 01:47:02.970 but i also love it like i think like i don't 01:47:02.970 --> 01:47:05.149 want to be the guy that criticizes that but you 01:47:05.149 --> 01:47:08.229 did because now i did and i will keep doing it 01:47:08.229 --> 01:47:11.890 but it's like by the same way i want to be the 01:47:11.890 --> 01:47:16.000 person that says like what are the what are the 01:47:16.000 --> 01:47:19.100 brazilian guys gonna say brazil mentioned you're 01:47:19.100 --> 01:47:23.880 destroying but replace it replace with another 01:47:23.880 --> 01:47:26.899 one right so keep the brazil section and wait 01:47:26.899 --> 01:47:30.220 what's gonna happen with boo when all of the 01:47:30.220 --> 01:47:33.060 new vim users come in and tell you hey i don't 01:47:33.060 --> 01:47:35.819 have this that i had a new vim implemented and 01:47:35.819 --> 01:47:38.939 then you're gonna end up with new vim again but 01:47:38.939 --> 01:47:42.079 in boo yeah this actually has been concerned 01:47:42.079 --> 01:47:46.859 and i think there's like uh I wrote that in the 01:47:46.859 --> 01:47:49.399 last blog post. There's just, like, many people, 01:47:49.420 --> 01:47:51.319 they have been asking, like, oh, I want Emacs 01:47:51.319 --> 01:47:56.079 or WinBindings. And, yeah, so it's, like, Boo 01:47:56.079 --> 01:47:59.180 does not do any of these bindings. Actually, 01:47:59.239 --> 01:48:03.239 it uses its own bindings. But the reason for 01:48:03.239 --> 01:48:07.100 that is, like, man, I don't want to sound like 01:48:07.100 --> 01:48:10.079 I'm criticizing those tools because I'm actually 01:48:10.079 --> 01:48:13.359 a big fan of Bing. Like, I used Bing for many 01:48:13.359 --> 01:48:16.920 years. And I just see the value actually in the 01:48:16.920 --> 01:48:20.880 tooling. And frankly, just to think that that 01:48:20.880 --> 01:48:26.920 software was written like many years ago is mind 01:48:26.920 --> 01:48:29.359 -blowing. It's like to have that perspective, 01:48:29.699 --> 01:48:33.140 like, you know, like, it's just like, it's insane. 01:48:33.300 --> 01:48:36.680 Like Veeam works well for many, many decades. 01:48:37.420 --> 01:48:41.810 So it's like, I have a really huge respect. for 01:48:41.810 --> 01:48:44.090 being i don't like to be that guy that you know 01:48:44.090 --> 01:48:47.689 like just criticize open source and i i actually 01:48:47.689 --> 01:48:50.350 think that people that they want to keep using 01:48:50.350 --> 01:48:54.350 v man keep using v like boo is not for you like 01:48:54.350 --> 01:48:56.970 there is there is no you know that you're not 01:48:56.970 --> 01:49:01.630 the problem go away yeah exactly go away and 01:49:01.630 --> 01:49:03.989 but it's not the profile that i want to bring 01:49:03.989 --> 01:49:07.449 to boo not because like they they would not fit 01:49:07.449 --> 01:49:11.439 but it's like I told this to Carlos, the guy 01:49:11.439 --> 01:49:13.420 that worked with me, and she's like, man, you 01:49:13.420 --> 01:49:15.479 spent so many years of your life learning something. 01:49:16.159 --> 01:49:20.039 There is no sense in migrating. You're very productive 01:49:20.039 --> 01:49:22.159 on that. Why are you going to become less productive 01:49:22.159 --> 01:49:26.659 in the other two? You know what I mean? So I 01:49:26.659 --> 01:49:30.560 guess, actually, this mentality of, oh, migrate 01:49:30.560 --> 01:49:37.140 from V to Boo, migrate from Emacs to Boo, I think... 01:49:37.399 --> 01:49:40.199 boo is not for this those people okay i think 01:49:40.199 --> 01:49:43.880 boo is for the new generation it's like people 01:49:43.880 --> 01:49:46.359 that don't really want to spend time left learning 01:49:46.359 --> 01:49:51.060 keybind or learning you know lua or learning 01:49:51.060 --> 01:49:55.380 you know other stuff and and they're like okay 01:49:55.380 --> 01:49:58.739 i want to use something simpler like and i think 01:49:58.739 --> 01:50:01.619 boo is for those people yeah because but you 01:50:01.619 --> 01:50:04.930 bring up a really good point you know it's never 01:50:04.930 --> 01:50:08.170 ending with neobim i use neobim i love neobim 01:50:08.170 --> 01:50:12.210 but i do get your point not everyone is willing 01:50:12.210 --> 01:50:15.270 to put the hours that i have to put that i have 01:50:15.270 --> 01:50:18.010 put in my configuration it has exactly months 01:50:18.010 --> 01:50:22.069 right and yeah years i have bad years and the 01:50:22.069 --> 01:50:25.750 thing with linux right like it's like i love 01:50:25.750 --> 01:50:30.590 linux and i think like man it actually came like 01:50:30.590 --> 01:50:32.750 gave people so much freedom you know what i mean 01:50:32.750 --> 01:50:36.539 like and by the same way some people they don't 01:50:36.539 --> 01:50:39.539 want to spend time doing anything like they just 01:50:39.539 --> 01:50:42.340 want something that you know updates itself that 01:50:42.340 --> 01:50:46.760 you know that is mainstream and then does something 01:50:46.760 --> 01:50:51.680 so i think that is like uh who is to target that 01:50:51.680 --> 01:50:54.260 part of the people that would love to have a 01:50:54.260 --> 01:51:00.039 terminal editor but does not want to you know 01:51:00.039 --> 01:51:04.439 and i think the elix you know elix the other 01:51:04.439 --> 01:51:08.239 they they kind of go in the line like they do 01:51:08.239 --> 01:51:11.600 a lot of things inside and i think that boo goes 01:51:11.600 --> 01:51:16.939 a lot similar to them yeah yeah but the difference 01:51:16.939 --> 01:51:20.819 is like i still feel that elix you still need 01:51:20.819 --> 01:51:24.699 to sit in google stuff so i think that that is 01:51:24.699 --> 01:51:27.159 the thing that i want to do i want boo to be 01:51:27.159 --> 01:51:31.079 intuitive i want you to like you write down as 01:51:31.079 --> 01:51:34.159 you would write in the know in the browser and 01:51:34.159 --> 01:51:36.600 if you something is wrong i want the editor to 01:51:36.600 --> 01:51:39.439 correct you like hey you're trying to do this 01:51:39.439 --> 01:51:42.520 then no this doesn't work here like you should 01:51:42.520 --> 01:51:45.000 do this and this this whole thing is actually 01:51:45.000 --> 01:51:48.720 built in in bool so it's like you're trying to 01:51:48.720 --> 01:51:51.359 save a file like this actually happens in bool 01:51:51.359 --> 01:51:54.579 you're trying to save a file with command s and 01:51:54.579 --> 01:51:57.439 in the terminal it notifies you it's not like 01:51:57.439 --> 01:51:59.500 who works here you don't need to google i'm gonna 01:51:59.500 --> 01:52:02.939 tell you how it works and then so it's like everything 01:52:02.939 --> 01:52:06.039 is like part of a game i would say it's like 01:52:06.039 --> 01:52:09.899 it's it's very connected itself so it is like 01:52:09.899 --> 01:52:15.979 uh it's i have been trying to make boo for people 01:52:15.979 --> 01:52:21.340 that don't vote so it's like i'm using them as 01:52:21.340 --> 01:52:25.340 my you know guinea pigs so it's like i have been 01:52:25.340 --> 01:52:27.939 giving to them and see like hey man how would 01:52:27.939 --> 01:52:32.590 you save a fighter and i think boo is for that 01:52:32.590 --> 01:52:35.590 and not for the super programmer that you know 01:52:35.590 --> 01:52:38.989 like that has multiple cars and also for people 01:52:38.989 --> 01:52:42.170 that just get tired of neo vim configuring stuff 01:52:42.170 --> 01:52:44.770 emacs and all that stuff and they're like i just 01:52:44.770 --> 01:52:47.789 want something out of the box that works i have 01:52:47.789 --> 01:52:50.529 a question for you there you mentioned that it's 01:52:50.529 --> 01:52:53.710 optimized right now for rust right because that's 01:52:53.710 --> 01:52:57.390 what you use mostly rust exactly and what's going 01:52:57.390 --> 01:52:59.989 to happen when you need to when you have users 01:52:59.989 --> 01:53:01.750 because not everyone's going to code in rust 01:53:01.750 --> 01:53:04.989 right there's going to go and a lot of other 01:53:04.989 --> 01:53:08.689 programs how are you going to work how isn't 01:53:08.689 --> 01:53:10.670 that going to be a lot of work is it going to 01:53:10.670 --> 01:53:13.750 have like a plug -in system or you're going to 01:53:13.750 --> 01:53:17.890 build everything yourself yeah excellent question 01:53:17.890 --> 01:53:22.369 i think like now so boo used three teacher like 01:53:22.369 --> 01:53:26.869 uh it was like The syntax highlight works for 01:53:26.869 --> 01:53:29.970 every language so far. Most of the languages, 01:53:30.010 --> 01:53:35.289 not every language. But my goal is actually to 01:53:35.289 --> 01:53:38.350 have both of the languages or protocols built 01:53:38.350 --> 01:53:42.970 in. So it's like you download what you need and 01:53:42.970 --> 01:53:47.210 you run with the things that you need. But you 01:53:47.210 --> 01:53:51.069 don't need to go someplace to get, you know, 01:53:51.189 --> 01:53:53.090 like, you don't need to go there and say, like, 01:53:53.359 --> 01:53:57.359 I want to go like a plugin to run this. Like, 01:53:57.399 --> 01:53:59.880 no, it's already there. It's an option there. 01:54:00.300 --> 01:54:03.079 So I think there's like, that's my other challenge 01:54:03.079 --> 01:54:05.680 with food. It's like, I think that the language 01:54:05.680 --> 01:54:09.100 adoption would need to be one by one. And it's 01:54:09.100 --> 01:54:12.539 just like, it's one big time. Like, cause there's 01:54:12.539 --> 01:54:15.119 the thing, like you need to put quality on what 01:54:15.119 --> 01:54:19.899 you do. You need to sit, test, repeat, and then 01:54:19.899 --> 01:54:22.199 say like, oh, people, they use Rust, they don't 01:54:22.199 --> 01:54:25.720 like this. feature and then you extend the rust 01:54:25.720 --> 01:54:29.279 like things in blue and that would be the same 01:54:29.279 --> 01:54:33.020 for glow like people like only to like kind of 01:54:33.020 --> 01:54:36.659 like give in bull is called actually runtime 01:54:36.659 --> 01:54:41.260 so it's like uh it's basically what you would 01:54:41.260 --> 01:54:45.500 call a in being like the plugins and all these 01:54:45.500 --> 01:54:48.520 type of things it's like call it runtime in bull 01:54:48.520 --> 01:54:52.250 and it's like uh it has like the part anyone 01:54:52.250 --> 01:54:55.970 can go there and modify by themselves so it's 01:54:55.970 --> 01:54:58.270 like the community could go there and just say 01:54:58.270 --> 01:55:00.930 like yeah i want now i want the runtime to auto 01:55:00.930 --> 01:55:05.949 like to do like the auto format of the code like 01:55:05.949 --> 01:55:09.390 by default and then they would go and change 01:55:09.390 --> 01:55:14.770 the code there uh i mean it's a long it's a long 01:55:14.770 --> 01:55:18.069 project like i have i work with it like i have 01:55:18.069 --> 01:55:22.539 been working with it for alpha year i i think 01:55:22.539 --> 01:55:25.600 like not even in the end of 2026 it's gonna be 01:55:25.600 --> 01:55:29.500 done but it's like i like to imagine that it's 01:55:29.500 --> 01:55:32.779 gonna have a close bet ready in the end of this 01:55:32.779 --> 01:55:37.039 year for some people it sounds like a lot of 01:55:37.039 --> 01:55:40.100 work and it does sound yeah don't you have enough 01:55:40.100 --> 01:55:45.220 with rio no never enough man the house play you 01:55:45.220 --> 01:55:49.430 love issues in github Oh yeah, apparently I did. 01:55:49.590 --> 01:55:55.170 I did help. Okay, good. Thanks for sharing about 01:55:55.170 --> 01:55:58.250 your editor in progress. We're going to see how 01:55:58.250 --> 01:56:00.770 that continues. I'm going to subscribe to your 01:56:00.770 --> 01:56:02.869 channel. I didn't even know that you had a channel 01:56:02.869 --> 01:56:05.590 because you don't post it on YouTube, on Twitter, 01:56:05.750 --> 01:56:09.130 right? Yeah, I will try to do more often. It's 01:56:09.130 --> 01:56:14.750 true. It's very new. I posted a few times and 01:56:14.750 --> 01:56:17.659 now I try to have some consistency. hmm okay 01:56:17.659 --> 01:56:20.500 yeah i will subscribe so i will be able to see 01:56:20.500 --> 01:56:24.199 the updates there and i'll we'll see how how 01:56:24.199 --> 01:56:29.420 everything turns out by the end of 2026 and um 01:56:29.420 --> 01:56:32.640 we already talked about this fashion rust you 01:56:32.640 --> 01:56:38.720 showed that already um let's talk about this 01:56:38.720 --> 01:56:44.020 is really important ide so you were using new 01:56:44.020 --> 01:56:46.329 vim What are you using now? So you went back 01:56:46.329 --> 01:56:49.449 to Notepad, you went to the basics, or what are 01:56:49.449 --> 01:56:53.430 you using now? Believe it or not, I was using 01:56:53.430 --> 01:56:58.369 Vue for Rust, and I used Sublime for a long time, 01:56:58.550 --> 01:57:01.970 because I got to use it with the frontend fully. 01:57:02.710 --> 01:57:05.949 I think that they had good frontend stuff back 01:57:05.949 --> 01:57:11.510 in 2013, 2015. And frankly, I still think that 01:57:11.510 --> 01:57:15.109 they have... One of the best cursors, multiple 01:57:15.109 --> 01:57:18.409 cursors of the market. I think that they do a 01:57:18.409 --> 01:57:22.149 lot of stuff very well. Supply? Yeah, supply. 01:57:22.630 --> 01:57:30.569 I had a call with one of the Helix. He's a contributor, 01:57:31.010 --> 01:57:34.010 a Helix contributor. I still have to edit the 01:57:34.010 --> 01:57:37.470 video and upload it, but I did really love the 01:57:37.470 --> 01:57:41.359 work that they do with multiple cursors. it's 01:57:41.359 --> 01:57:44.260 amazing it's amazing i think that i think there's 01:57:44.260 --> 01:57:47.819 a thing that i'm trying to copy in boo but it's 01:57:47.819 --> 01:57:51.640 boo has like no but then i just spoiled it the 01:57:51.640 --> 01:57:54.020 thing is like i also had to reinvent the mouse 01:57:54.020 --> 01:57:57.880 the multiple mouse because the thing is like 01:57:57.880 --> 01:58:01.899 since you cannot use mouse in boo it's like it's 01:58:01.899 --> 01:58:04.300 not allowed like you don't even have the functionality 01:58:04.300 --> 01:58:08.949 oh like there's no work so it's like I had to 01:58:08.949 --> 01:58:12.369 write a lot. But then users are going to come 01:58:12.369 --> 01:58:14.590 in. You know how it is. You know how it is. No, 01:58:14.630 --> 01:58:22.529 but this is different. Boo is not built for mainstream. 01:58:23.590 --> 01:58:30.050 It's like real, everyone can use. But Boo is 01:58:30.050 --> 01:58:32.550 like, you like mouse -free editors. You don't 01:58:32.550 --> 01:58:36.470 want mouse. If you like mouse, don't even come 01:58:36.470 --> 01:58:40.000 here. No, exactly. I think that this should be 01:58:40.000 --> 01:58:42.819 part of the premise. I don't think I will be 01:58:42.819 --> 01:58:47.000 ever adding that to Boom. Because if I add it... 01:58:47.000 --> 01:58:50.340 Okay, one thing there I noticed, like, right 01:58:50.340 --> 01:58:55.800 in Boom. If you add any type of functionality, 01:58:56.239 --> 01:59:00.479 partially, it's like, oh, you're going to have 01:59:00.479 --> 01:59:02.939 mouse support. Then you're going to do the things 01:59:02.939 --> 01:59:06.239 as baked. It's like... You're not going to think 01:59:06.239 --> 01:59:10.560 like, oh, this person does not have a mouse. 01:59:10.699 --> 01:59:13.220 What would happen? No, you start to consider 01:59:13.220 --> 01:59:16.319 that people have mouse and then you do like an 01:59:16.319 --> 01:59:19.859 editor that considers that people have mouse 01:59:19.859 --> 01:59:23.739 and they should just click on that. And I think 01:59:23.739 --> 01:59:28.119 that I like about Veeam and Emacs because they 01:59:28.119 --> 01:59:33.000 stayed true for many years. So they actually 01:59:33.000 --> 01:59:36.100 developed quite well. due to the restrictions 01:59:36.100 --> 01:59:38.720 you know what i mean like they had many restrictions 01:59:38.720 --> 01:59:41.239 back in time and they're still thankful for those 01:59:41.239 --> 01:59:45.760 restrictions and i think bull should also understand 01:59:45.760 --> 01:59:49.840 this like hey man there's no mouse like you need 01:59:49.840 --> 01:59:54.439 to make a mouse experience by the terminal and 01:59:54.439 --> 01:59:58.060 you should make that looks good and how you do 01:59:58.060 --> 02:00:02.039 that i think that that is like Well, I have actually 02:00:02.039 --> 02:00:05.840 did so many prototypes. One was called Linkshot, 02:00:06.060 --> 02:00:09.500 which was like you held the key for a while and 02:00:09.500 --> 02:00:12.159 then would scroll up and scroll down, depending 02:00:12.159 --> 02:00:15.119 on the type of the press. But it didn't work 02:00:15.119 --> 02:00:17.420 out. At the end of the day, it was very weird. 02:00:18.579 --> 02:00:22.600 So it's like I've been exploring different ideas 02:00:22.600 --> 02:00:27.500 of how to do an editor that actually makes you 02:00:27.500 --> 02:00:30.600 feel. that you force it to type like you need 02:00:30.600 --> 02:00:35.300 to type there's no other way and uh but yeah 02:00:35.300 --> 02:00:38.699 man it's like it is very i think that this is 02:00:38.699 --> 02:00:41.619 fun you know like this is the fun thing i think 02:00:41.619 --> 02:00:43.800 that this is i think that food is different than 02:00:43.800 --> 02:00:46.520 here there's like one thing that i'm glad about 02:00:46.520 --> 02:00:49.000 who is that close at source so it's like it's 02:00:49.000 --> 02:00:53.060 kind of my laboratory no one has access i do 02:00:53.060 --> 02:00:55.239 crazy stuff and if i don't like it just throwing 02:00:55.239 --> 02:00:59.039 trash yeah but hey you If I do something and 02:00:59.039 --> 02:01:02.220 someone likes, they do a fork and they copy and 02:01:02.220 --> 02:01:06.159 move to Heave. Like today, one time I did something 02:01:06.159 --> 02:01:08.819 and then I didn't like it and I removed it out 02:01:08.819 --> 02:01:12.699 from Heave. But I think it was a Russian guy, 02:01:12.779 --> 02:01:15.340 he forked the project and he was like, oh, but 02:01:15.340 --> 02:01:16.979 I really like this feature, they will remove 02:01:16.979 --> 02:01:21.699 it. And then he started to use, you know, the 02:01:21.699 --> 02:01:24.399 fork from there. yeah from the fork and then 02:01:24.399 --> 02:01:26.579 people started to be like oh i like this work 02:01:26.579 --> 02:01:30.380 like i'm gonna use this and it's very different 02:01:30.380 --> 02:01:33.020 you know like and what happened did you add the 02:01:33.020 --> 02:01:36.399 feature back no i talked with the dude and i 02:01:36.399 --> 02:01:39.300 added in another way like it so i had to actually 02:01:39.300 --> 02:01:43.199 change the architecture of he should fit that 02:01:43.199 --> 02:01:47.920 and uh and follow the behavior work so feature 02:01:47.920 --> 02:01:51.949 that i didn't even want so you have to be really 02:01:51.949 --> 02:01:55.510 careful with which features you introduce once 02:01:55.510 --> 02:02:00.989 it's in beta or out there because yeah no but 02:02:00.989 --> 02:02:03.689 this is the big one now that like it's just like 02:02:03.689 --> 02:02:07.250 it's just me yeah it's just like i break stuff 02:02:07.250 --> 02:02:12.489 i like that i don't like it you know i do i do 02:02:12.489 --> 02:02:16.270 like weird stuff sometimes i do very weird stuff 02:02:16.270 --> 02:02:20.239 and then In the end of the day, I have to do 02:02:20.239 --> 02:02:22.800 it. You know what I mean? Like, okay. Like, I 02:02:22.800 --> 02:02:26.000 live my life. And then, like, if I do that in 02:02:26.000 --> 02:02:29.279 here today, people, like, I start to do the plugins 02:02:29.279 --> 02:02:33.239 in here, in WebAssembly. And then people are 02:02:33.239 --> 02:02:35.859 like, well, why not Lua? Why not this guy? Why 02:02:35.859 --> 02:02:38.880 not that? And I was just like, guys, just let 02:02:38.880 --> 02:02:41.859 me explore. I need the time to think about things. 02:02:42.220 --> 02:02:44.560 Like, you know what I mean? Like, because if 02:02:44.560 --> 02:02:46.619 you don't even try the solution, how would you 02:02:46.619 --> 02:02:51.689 know? Yeah, if that's the best one. But it's 02:02:51.689 --> 02:02:53.970 like, I think that this is a thing where people 02:02:53.970 --> 02:02:56.470 are like, oh, give me access, give me access. 02:02:56.729 --> 02:03:00.050 And I was just like, no, man. Like, I don't want 02:03:00.050 --> 02:03:01.989 people's opinions so far. I don't want people 02:03:01.989 --> 02:03:04.590 saying like, oh, this is good, this is bad. Because 02:03:04.590 --> 02:03:07.430 if they start to say this, then my mind would 02:03:07.430 --> 02:03:10.050 be like, oh, so this was good. Yeah. I would 02:03:10.050 --> 02:03:13.149 start to follow that, you know what I mean? I 02:03:13.149 --> 02:03:14.710 don't know if that makes sense. Maybe it's just 02:03:14.710 --> 02:03:17.649 me. Yeah, yeah, yeah, no. It makes sense. You 02:03:17.649 --> 02:03:20.630 want to make it perfect for you, see how people 02:03:20.630 --> 02:03:24.890 react to it. Yeah, if people don't like it, I'm 02:03:24.890 --> 02:03:27.609 okay with that. I think there's a different relationship 02:03:27.609 --> 02:03:30.970 from here. As long as it works for you, right? 02:03:31.029 --> 02:03:33.829 Because I mean, how many tools have created for 02:03:33.829 --> 02:03:36.930 people themselves, right? You don't think about 02:03:36.930 --> 02:03:40.710 anyone else. As long as it works for me, I'm 02:03:40.710 --> 02:03:43.649 more than happy. And if that happens, there's 02:03:43.649 --> 02:03:45.550 a lot of people that is going to follow along. 02:03:45.949 --> 02:03:48.729 right because if you like it a lot of people 02:03:48.729 --> 02:03:51.090 will like it as well a lot of people will dislike 02:03:51.090 --> 02:03:54.149 it but that's the way it is right so 50 50 all 02:03:54.149 --> 02:03:58.590 the time exactly i think that is the this is 02:03:58.590 --> 02:04:01.430 the issue i think with like products in general 02:04:01.430 --> 02:04:05.869 like everyone wants day two like in in one thing 02:04:05.869 --> 02:04:09.250 in one way that fits the necessity yeah because 02:04:09.250 --> 02:04:13.250 like i use firefox but i use firefox because 02:04:13.250 --> 02:04:18.460 well i'm attach it to mozilla somehow like i 02:04:18.460 --> 02:04:20.640 have this memory people are starting to criticizing 02:04:20.640 --> 02:04:24.600 me for use python and then like it was just like 02:04:24.600 --> 02:04:27.779 sure man like so should i use chrome and and 02:04:27.779 --> 02:04:29.859 and you know like and then you guys are gonna 02:04:29.859 --> 02:04:33.220 be okay so you're happy uh -huh yeah exactly 02:04:33.220 --> 02:04:37.000 and it's like the other person wants me to use 02:04:37.000 --> 02:04:39.500 a tool that they want me to use because they 02:04:39.500 --> 02:04:43.949 believe there's the right to It's just insanity 02:04:43.949 --> 02:04:47.630 at the end of the day. Yeah, that's the world 02:04:47.630 --> 02:04:50.909 we live in. That's the way it is. No, one thing 02:04:50.909 --> 02:04:56.829 I like about Ghostie is one thing that Misha 02:04:56.829 --> 02:05:01.670 did was he wrote everything in Zeke. And man, 02:05:01.710 --> 02:05:03.970 he didn't give a damn. You know what I mean? 02:05:03.989 --> 02:05:07.739 He didn't care if people were going to... be 02:05:07.739 --> 02:05:10.880 like oh why like why is he by this and why not 02:05:10.880 --> 02:05:15.920 yeah people did the question and i think it's 02:05:15.920 --> 02:05:18.840 like he liked it more like he does not need to 02:05:18.840 --> 02:05:23.159 give like a technical reason like uh i think 02:05:23.159 --> 02:05:26.859 one thing that he said i saw in podcast was like 02:05:26.859 --> 02:05:30.220 it's like languages are like different flavors 02:05:30.220 --> 02:05:34.720 like of ice cream sometimes you like more vanilla 02:05:34.720 --> 02:05:38.939 sometimes you like more strawberry And I like 02:05:38.939 --> 02:05:42.239 that mentality as well. It's like, yeah, I want 02:05:42.239 --> 02:05:45.319 to do, I actually have no mouse. You don't like 02:05:45.319 --> 02:05:48.819 that? Dude, just use other stuff. Yeah. Like, 02:05:48.819 --> 02:05:52.699 I'm good with that. Like, you know, I'm going 02:05:52.699 --> 02:05:58.479 to survive. And you don't like him? Man, go with 02:05:58.479 --> 02:06:02.279 Ghost. Go with, like, Apple Terminal. Like, I'm 02:06:02.279 --> 02:06:04.180 good with that. Like, you know, like, it's not 02:06:04.180 --> 02:06:07.859 an offense or anything. Yeah, that's one of the 02:06:07.859 --> 02:06:11.579 reasons why I keep everything in my .dat files, 02:06:11.760 --> 02:06:14.060 because I could keep all of the stuff. Let me 02:06:14.060 --> 02:06:16.659 show you all of the stuff that I have here. I 02:06:16.659 --> 02:06:19.779 have a lot of stuff, man, but I could create 02:06:19.779 --> 02:06:23.260 repos out of these. I don't want to. You know 02:06:23.260 --> 02:06:27.060 why? Because I'm going to start getting a lot 02:06:27.060 --> 02:06:30.220 of issues, discussions. I don't want it there 02:06:30.220 --> 02:06:34.350 for me. and i just modify them to my liking if 02:06:34.350 --> 02:06:38.529 i want to change from csh to bash one day i just 02:06:38.529 --> 02:06:41.369 do it nobody's gonna say anything and if someone 02:06:41.369 --> 02:06:44.390 does it's just like hey man it's my that files 02:06:44.390 --> 02:06:55.649 just yeah them and yeah but yeah i think you 02:06:55.649 --> 02:06:58.430 have to do it for yourself and people is going 02:06:58.430 --> 02:07:00.829 to follow along people with the same mentality 02:07:00.829 --> 02:07:03.989 will find it and say oh i really like this it's 02:07:03.989 --> 02:07:06.510 really interesting and they're gonna start yeah 02:07:06.510 --> 02:07:10.270 it's a big surprises me about here because like 02:07:10.270 --> 02:07:16.390 when i started it's like um like it started and 02:07:16.390 --> 02:07:18.869 there are some people that stay there they aren't 02:07:18.869 --> 02:07:22.210 steering the discord active for two years and 02:07:22.210 --> 02:07:25.689 yeah frankly when i started he was so bad that 02:07:25.689 --> 02:07:29.359 i didn't understand like people were using But 02:07:29.359 --> 02:07:31.899 now I think it's starting to become a really 02:07:31.899 --> 02:07:37.279 competitive editor, like Terminal. And it has 02:07:37.279 --> 02:07:39.760 features that many people like. People write 02:07:39.760 --> 02:07:43.800 in Reddit that they enjoy Rio and stuff like 02:07:43.800 --> 02:07:48.520 that. But when I started, it was not good, man. 02:07:48.640 --> 02:07:50.619 It was not a piece of software that I was proud 02:07:50.619 --> 02:07:56.090 of. but they they stay it you know like i think 02:07:56.090 --> 02:07:58.350 that they maybe like it the way that i approach 02:07:58.350 --> 02:08:02.529 it and like uh and that they stay there and then 02:08:02.529 --> 02:08:05.810 yeah i don't know always surprised me because 02:08:05.810 --> 02:08:09.909 like it kind of like they took you as like uh 02:08:09.909 --> 02:08:14.930 i don't know like a toy project or extra project 02:08:14.930 --> 02:08:17.609 and they just stayed there for fun and then using 02:08:17.609 --> 02:08:20.270 the terminal i think that that is like a very 02:08:20.270 --> 02:08:27.079 tough you would say Hmm. Yep. Okay. And so you 02:08:27.079 --> 02:08:30.760 use Boo right now mainly to write Rust. What 02:08:30.760 --> 02:08:34.600 if you have to edit other type of files like 02:08:34.600 --> 02:08:37.619 a bash script? What do you use? Do you use Vim 02:08:37.619 --> 02:08:41.659 or do you still use Boo there? Man, I actually, 02:08:41.840 --> 02:08:46.640 this is a good question. I have like, I have 02:08:46.640 --> 02:08:50.020 probably six or seven editors where I change 02:08:50.020 --> 02:08:53.880 every day. So it's like I tried to learn with 02:08:53.880 --> 02:08:56.859 a different editor. So it's like mostly I think 02:08:56.859 --> 02:09:02.840 that I've been using Zed. But I use Envy a lot. 02:09:03.739 --> 02:09:07.039 Well, when I'm in Linux, it's just Envy. I don't 02:09:07.039 --> 02:09:11.420 have anything to do other crap. Yeah, when I'm 02:09:11.420 --> 02:09:17.140 on Linux, it's just Envy. But when I'm on Mac, 02:09:17.159 --> 02:09:22.010 I change a lot. Like I use Zed, Sublime. I just 02:09:22.010 --> 02:09:24.710 don't use VS Code, but it's like... It's not 02:09:24.710 --> 02:09:26.770 that I have anything against... Maybe I have 02:09:26.770 --> 02:09:28.630 something against VS Code, I don't know, but 02:09:28.630 --> 02:09:34.489 it's like... But... No, I think VS Code... You're 02:09:34.489 --> 02:09:37.689 ashamed? You're ashamed that people see you using 02:09:37.689 --> 02:09:41.109 VS Code? Is that it? I don't even have it installed 02:09:41.109 --> 02:09:43.649 right now. I think I don't even have it on here. 02:09:43.850 --> 02:09:47.289 Maybe I have it on the computer. But it's like... 02:09:47.289 --> 02:09:50.720 No, the thing is like... I have problems with 02:09:50.720 --> 02:09:56.159 Electro apps. I think they are not paid for that. 02:09:56.579 --> 02:09:59.399 But in the same way, I think VS Code is such 02:09:59.399 --> 02:10:03.960 a great idea because it takes the most popular 02:10:03.960 --> 02:10:07.859 language, JavaScript, and gives to this most 02:10:07.859 --> 02:10:12.760 popular language power enough to break through 02:10:12.760 --> 02:10:19.869 applications. So it's like... I don't think I 02:10:19.869 --> 02:10:22.529 have been thinking a lot about Vue, because it's 02:10:22.529 --> 02:10:26.069 like... I would love to have the VS Code plugin 02:10:26.069 --> 02:10:31.189 working in Vue. So I have actually tested two 02:10:31.189 --> 02:10:35.909 Vue versions, one with the JS Engine and the 02:10:35.909 --> 02:10:39.090 other one without it. And I think I'll give you 02:10:39.090 --> 02:10:41.550 this officially so you download whatever suits 02:10:41.550 --> 02:10:45.750 you. But it's like... I think it's like, man, 02:10:45.789 --> 02:10:48.850 JavaScript has power, you know, like it's just, 02:10:48.890 --> 02:10:51.949 people just love to write JavaScript for, to 02:10:51.949 --> 02:10:58.010 download good stuff. And I think it's like, in 02:10:58.010 --> 02:11:02.390 some ways, like it feels more as a scripting, 02:11:02.390 --> 02:11:04.470 I know it's crazy, I know this is crazy, but 02:11:04.470 --> 02:11:08.050 sometimes I feel that it feels more as a scripting 02:11:08.050 --> 02:11:14.029 language than Google. Not because I dislike Blue. 02:11:14.149 --> 02:11:15.869 I think Blue is great and it's very intuitive. 02:11:16.510 --> 02:11:19.869 But it's just like every person knows JavaScript. 02:11:20.390 --> 02:11:23.829 Have you ever thought about it? Every programmer 02:11:23.829 --> 02:11:26.470 at some moment wrote a JavaScript line of code. 02:11:27.489 --> 02:11:30.109 Even if it was to do something in the browser, 02:11:30.189 --> 02:11:34.770 like to trigger alert. And I have to think a 02:11:34.770 --> 02:11:39.470 lot about it. Should I just do it? Should I just, 02:11:39.470 --> 02:11:41.970 you know, like, do, like, a JavaScript, like, 02:11:41.970 --> 02:11:46.170 board for plugins in Boo efficiently? And what's 02:11:46.170 --> 02:11:48.270 going to happen, because there's a lot of plugins 02:11:48.270 --> 02:11:52.390 in the VS Code ecosystem, aren't you afraid of 02:11:52.390 --> 02:11:55.869 breaking changes, like, breaking stuff in your 02:11:55.869 --> 02:12:00.010 editor? Yeah, I think this is actually what has 02:12:00.010 --> 02:12:04.470 been held in me. But I think, like... That's 02:12:04.470 --> 02:12:08.689 what I say. I think that's great. I think VS 02:12:08.689 --> 02:12:14.350 Code was needed for many people because people 02:12:14.350 --> 02:12:16.909 can just prototype stuff. They can just create 02:12:16.909 --> 02:12:19.770 crazy stuff. It's very quick to do anything. 02:12:20.369 --> 02:12:23.189 But in the same way... Like you said before, 02:12:23.350 --> 02:12:25.050 there's people that just want to open something, 02:12:25.409 --> 02:12:29.550 go through a marketplace, install what they need, 02:12:29.649 --> 02:12:32.069 and start working. You don't have a lot of flexibility. 02:12:32.729 --> 02:12:36.029 You just... you can get started in 10 minutes 02:12:36.029 --> 02:12:40.529 new event on the other hand not that exactly 02:12:40.529 --> 02:12:43.649 simple yeah exactly but i wish there was something 02:12:43.649 --> 02:12:45.850 in the middle because like i think the ds volt 02:12:45.850 --> 02:12:50.729 is like it's just that they do like come on it's 02:12:50.729 --> 02:12:53.689 like a browser running there there's a lot of 02:12:53.689 --> 02:12:58.050 magic yeah but uh i think it's it's it's a great 02:12:58.050 --> 02:13:00.909 piece of software no great piece of software 02:13:00.909 --> 02:13:05.449 maybe i'm not being honest but it's like uh i 02:13:05.449 --> 02:13:10.970 think it's like a great product like it's not 02:13:10.970 --> 02:13:13.149 a great piece of software but i think it's a 02:13:13.149 --> 02:13:17.149 great product it's like it makes people you know 02:13:17.149 --> 02:13:21.270 like forget what they want very quick yeah yeah 02:13:21.270 --> 02:13:25.770 it makes sense yep yep all right and uh let's 02:13:25.770 --> 02:13:28.869 see we've been here for two and a half hours 02:13:28.869 --> 02:13:31.229 i don't think we will have time to go through 02:13:31.229 --> 02:13:34.590 all the questions Because it's really late for 02:13:34.590 --> 02:13:39.130 you already, right? Oh, yeah. Yeah. Let's just 02:13:39.130 --> 02:13:45.409 talk here. We already talked NeoVim. I would 02:13:45.409 --> 02:13:48.369 like, well, we already talked a lot about editors. 02:13:48.770 --> 02:13:53.750 Let's just talk operating systems and we can 02:13:53.750 --> 02:13:59.649 wrap it up there, right? Sounds good. Yep. Mine? 02:13:59.909 --> 02:14:10.989 Yep. man i my favorite to me yeah oh jesus people 02:14:10.989 --> 02:14:13.729 is gonna pick sides so be careful because you're 02:14:13.729 --> 02:14:18.529 gonna get the mac os guys upset or the linux 02:14:18.529 --> 02:14:26.590 guys upset okay so if i if i if i say i think 02:14:26.590 --> 02:14:32.520 like lately for here I feel that I have been 02:14:32.520 --> 02:14:35.279 helping more the macOS side because I have been 02:14:35.279 --> 02:14:41.060 working more with macOS but if I were talking 02:14:41.060 --> 02:14:44.319 about philosophy I think I side more with Linux 02:14:44.319 --> 02:14:49.119 and it's like I have more beliefs on that on 02:14:49.119 --> 02:14:57.949 that side so either I don't know just 50 50. 02:14:58.189 --> 02:15:02.109 your heart is divided yeah i also have a heart 02:15:02.109 --> 02:15:07.329 for windows maybe 10 to 20 percent because like 02:15:07.329 --> 02:15:09.930 as i said like man it's hard to learn how to 02:15:09.930 --> 02:15:12.569 code through windows like i was i didn't have 02:15:12.569 --> 02:15:16.449 money and you know like and when i was in japan 02:15:16.449 --> 02:15:19.550 everyone was using windows there like everyone 02:15:19.550 --> 02:15:23.409 oh really yeah so it was just like it was not 02:15:23.409 --> 02:15:29.399 like it was not like oh 10 people, 40. It was 02:15:29.399 --> 02:15:31.939 like everyone was using, like every coder was 02:15:31.939 --> 02:15:36.539 using it. And it made me think like, yeah, man, 02:15:36.560 --> 02:15:40.159 like, well, OSs are just, you know, like, like 02:15:40.159 --> 02:15:44.079 you get your job done, whatever you use. So I, 02:15:44.140 --> 02:15:47.380 I have a lot of respect for Alu. I think I just, 02:15:47.539 --> 02:15:54.600 I have a few problems like with each in different 02:15:54.600 --> 02:15:57.359 aspects like i don't i think that this linux 02:15:57.359 --> 02:16:00.659 desktop needs to hold a lot of stuff yet and 02:16:00.659 --> 02:16:06.659 i think that like uh match like um i i think 02:16:06.659 --> 02:16:09.039 i'm i'm more use it because i have been using 02:16:09.039 --> 02:16:13.199 more professionally the past years but i i have 02:16:13.199 --> 02:16:15.939 two problems for example with the way that they 02:16:15.939 --> 02:16:22.340 they do things apple does think and uh And I 02:16:22.340 --> 02:16:27.079 think Windows, I have problems with the quality 02:16:27.079 --> 02:16:29.399 of the OS. Like I feel that sometimes people 02:16:29.399 --> 02:16:34.200 just break things like... The blue screen, the 02:16:34.200 --> 02:16:37.360 blue screen out of nowhere. So I think that this 02:16:37.360 --> 02:16:39.760 is a thing for me that I don't like on Windows. 02:16:40.079 --> 02:16:44.260 But man, all the three, they have like strong 02:16:44.260 --> 02:16:49.500 sites, you know what I mean? and if you if you 02:16:49.500 --> 02:16:52.920 if you have a machine that's very weak in terms 02:16:52.920 --> 02:16:57.100 of hardware like linux is so great there like 02:16:57.100 --> 02:17:00.379 uh it's like i have this machine here and it's 02:17:00.379 --> 02:17:04.420 like it i bought this second hand it's very old 02:17:04.420 --> 02:17:08.120 and it's like i run arc there as people say art 02:17:08.120 --> 02:17:14.959 by the way and uh but you have a kid right yeah 02:17:15.549 --> 02:17:19.649 so you're not on an arch user because uh oh i 02:17:19.649 --> 02:17:25.889 cannot be and no i think that the thing with 02:17:25.889 --> 02:17:29.629 arc is like it took a time to get it popular 02:17:29.629 --> 02:17:34.969 already like uh but then man arc scripts they're 02:17:34.969 --> 02:17:38.510 like like once you get that stalling arc script 02:17:38.510 --> 02:17:42.430 right then you're good like you don't need to 02:17:42.430 --> 02:17:48.299 worry more and Why Mac, though? Like, why not 02:17:48.299 --> 02:17:51.860 Linux? At this point in life, right, you seem 02:17:51.860 --> 02:17:55.639 more aligned with Linux. But why are you using 02:17:55.639 --> 02:18:00.620 Mac? I think I still, because I don't know if 02:18:00.620 --> 02:18:03.319 you remember, I used to work with design at some 02:18:03.319 --> 02:18:07.520 moment. So it was like, I think at some moment 02:18:07.520 --> 02:18:10.780 I felt that the hardware for designing Mac OS 02:18:10.780 --> 02:18:14.729 was much better than in Linux. I was just like, 02:18:14.729 --> 02:18:17.590 it was not impossible to be a good designer on 02:18:17.590 --> 02:18:20.549 Linux. But for example, if I wanted to use like 02:18:20.549 --> 02:18:24.170 Retina or like all these, you know, like displays 02:18:24.170 --> 02:18:28.989 that Mac does have. And a friend of mine was 02:18:28.989 --> 02:18:32.090 just like, yeah, sure, but you can run Linux 02:18:32.090 --> 02:18:35.110 on Mac hardware. And I was just like, man, this 02:18:35.110 --> 02:18:37.750 looks good. But I never did. I don't know why. 02:18:37.909 --> 02:18:40.229 So maybe at some moment I should just give it 02:18:40.229 --> 02:18:48.739 a try. In Mac, what CPU are you using? Are you 02:18:48.739 --> 02:18:52.579 on Intel or Apple Silicon? I've been using Intel 02:18:52.579 --> 02:18:56.120 for a long time, but now, thank God, the ARM 02:18:56.120 --> 02:19:02.780 is like a new era. And how do you feel about 02:19:02.780 --> 02:19:08.219 battery life, for example? No, compared to Linux, 02:19:08.420 --> 02:19:12.760 it's not like Linux. sometimes i leave the computer 02:19:12.760 --> 02:19:15.559 up and running for three days and it's just like 02:19:15.559 --> 02:19:21.000 alive with the battery yeah and this guy here 02:19:21.000 --> 02:19:27.040 is just like he gets the job done like i wish 02:19:27.040 --> 02:19:32.379 that i was using this more but i am a lazy person 02:19:32.379 --> 02:19:34.680 so sometimes i just open the computer that is 02:19:34.680 --> 02:19:38.579 in the main and i keep holding it so you get 02:19:38.950 --> 02:19:41.790 Three days of battery life on the Linux computer. 02:19:42.709 --> 02:19:47.229 Yeah, my one, yeah. But I don't have much stuff 02:19:47.229 --> 02:19:52.190 on my Linux, to be honest. Just Rio, Rust, and 02:19:52.190 --> 02:19:55.829 Git. Oh, okay. Okay, yeah, because that's a lot. 02:19:55.989 --> 02:20:00.709 That's a lot. I have used Intel -based machines. 02:20:00.870 --> 02:20:03.290 I used to have a laptop, and the battery didn't 02:20:03.290 --> 02:20:07.850 last not even three hours, right? that's one 02:20:07.850 --> 02:20:13.489 of the reasons i think i'm still in mac os battery 02:20:13.489 --> 02:20:17.889 life because this m1 computer's battery for me 02:20:17.889 --> 02:20:22.790 lasts um a long time but um yeah there's a big 02:20:22.790 --> 02:20:27.389 difference i agree yeah yeah but this one man 02:20:27.389 --> 02:20:30.250 my arc is you can see it's very simple probably 02:20:30.250 --> 02:20:39.409 i think i better have stuff to work I tried to 02:20:39.409 --> 02:20:44.309 keep simple there. Okay. Okay. Good to know. 02:20:45.170 --> 02:20:49.930 All right, Rafa. So is there anything else you 02:20:49.930 --> 02:20:53.510 want to share before we wrap it up? Just remember 02:20:53.510 --> 02:20:57.129 to send me your links, the YouTube, GitHub, all 02:20:57.129 --> 02:20:58.969 that stuff. So I can put it in the video description. 02:21:00.569 --> 02:21:02.950 And yeah, anything you want to share, anything 02:21:02.950 --> 02:21:04.729 you want to, I don't know if there's someone 02:21:04.729 --> 02:21:08.319 watching still, but. probably there's a couple 02:21:08.319 --> 02:21:11.059 guys from my discord that i that are still watching 02:21:11.059 --> 02:21:15.180 so any una anything you want to share i don't 02:21:15.180 --> 02:21:17.680 have anything that i want to share uh so far 02:21:17.680 --> 02:21:22.420 i hope that i have something ready to share about 02:21:22.420 --> 02:21:26.120 bull in the next post but i don't have anything 02:21:26.120 --> 02:21:30.500 now okay wonderful so anytime you want to join 02:21:30.500 --> 02:21:32.700 a call just let me know if you want to share 02:21:32.700 --> 02:21:35.409 stuff let me know and I'm more than glad to have 02:21:35.409 --> 02:21:38.149 you here. No, it was my pleasure. I appreciate 02:21:38.149 --> 02:21:41.069 the talk. It was good. Yeah. Thanks for your 02:21:41.069 --> 02:21:45.770 time. So I'll see you till the next time. All 02:21:45.770 --> 02:21:47.250 right. See you, man. Bye.