1 00:00:06,639 --> 00:00:10,960 Hello, Welcome to Adventures and Angler, the podcast where we keep you updated 2 00:00:11,000 --> 00:00:15,320 on all things Angular related. This show is produced by two companies, Top 3 00:00:15,359 --> 00:00:19,160 and Doves and Void. Top and Doves is where we create Top and Doves, 4 00:00:19,160 --> 00:00:24,120 so get top and pay and recognition while working on interesting problems and making 5 00:00:24,160 --> 00:00:30,239 meaningful community contributions. An Onvoid, which provides remote design and software development services 6 00:00:30,280 --> 00:00:35,359 on a performance basis, so clients only pay for delivered tasts. In today's 7 00:00:35,399 --> 00:00:41,679 episode, we will talk about the Angular renaissance. This is how they're mentioning 8 00:00:41,719 --> 00:00:47,880 this new movie. Angler was recently rebranded and we also got a new version 9 00:00:48,000 --> 00:00:52,119 Anglar version seventeen. So we have a lot of things to talk about. 10 00:00:52,200 --> 00:00:57,320 We're going to introduce you all on what is new, just taking it from 11 00:00:57,359 --> 00:01:00,479 the top and Yeah. So my name is Lucas Paganini. I am the 12 00:01:00,520 --> 00:01:03,519 CEO of Void and your host and the podcast. Joining me in today's episode 13 00:01:03,920 --> 00:01:11,359 is Charles Maxwood. Hey, folks, it's been a little bit yeah, 14 00:01:11,560 --> 00:01:21,239 and Subrett Mishra Hello, everyone. All right, Okay, so let's get 15 00:01:21,239 --> 00:01:26,239 into it. So, so Brett, let's talk about the rebrand. What 16 00:01:26,280 --> 00:01:32,120 do you think about the new Angular logo? Yeah, I think When I 17 00:01:32,200 --> 00:01:36,760 saw the logo first, I thought like someone just caated I got it in 18 00:01:36,879 --> 00:01:41,079 my LinkedIn that angular it's dedicated. I thought someone just cut it from the 19 00:01:41,120 --> 00:01:45,480 side and is trying it to animate it as some grady and and something. 20 00:01:46,000 --> 00:01:48,799 But I saw that. Okay. Now Anglar is also coming up with the 21 00:01:49,280 --> 00:01:55,200 new new document side and which looks pretty cool, like if you go, 22 00:01:55,400 --> 00:02:00,640 they have an Apple style branding and then so scrolling effect and now it's that 23 00:02:00,719 --> 00:02:06,959 think Anglarre going is a good way of catching the market again, hope like 24 00:02:07,280 --> 00:02:12,879 with all these changes, all this optimization with Angler seventeen, let's hope for 25 00:02:12,919 --> 00:02:20,080 the best. And I like the I like the old one actual a little 26 00:02:20,120 --> 00:02:27,319 more, but the new one also quite good. The old branding an old 27 00:02:27,360 --> 00:02:31,319 logo, old Angler and logo, a simple material design. Now it's a 28 00:02:31,400 --> 00:02:37,080 Signee logo. But yeah, I thought my opinion would be unpopular. I 29 00:02:37,159 --> 00:02:44,319 like the old logo a lot better than a new one. Whatever. Yeah, 30 00:02:45,759 --> 00:02:49,759 I mean, I am still a bit divided. The new logo looks 31 00:02:49,919 --> 00:02:55,759 really cool, but I just feel like it looks like a lot of other 32 00:02:57,280 --> 00:03:01,680 startup logos that are trying to look cool. And the old logo had this 33 00:03:02,000 --> 00:03:07,439 classic look to it. It was just it was just classic, you know, 34 00:03:07,639 --> 00:03:10,800 the red shield with an A. But at the same time, I 35 00:03:10,919 --> 00:03:16,599 completely agree that they needed a rebrand, and like, I'm not gonna lie. 36 00:03:17,199 --> 00:03:21,800 This week, I think it was Monday, I opened up LinkedIn and 37 00:03:21,840 --> 00:03:30,360 I saw those pools on LinkedIn and somebody was making this question, if you 38 00:03:30,439 --> 00:03:34,280 were to start a new project right now, it's a personal project, you 39 00:03:34,319 --> 00:03:38,680 have full autonomy over the technical decisions. What would you use for the framework 40 00:03:38,879 --> 00:03:45,240 in the front end? And the options were nothing. It was React and 41 00:03:45,360 --> 00:03:51,479 the third option was Angular JS And I was like, dude, really twenty 42 00:03:51,639 --> 00:03:58,560 three like you Yeah, It's like people are still are still like not getting 43 00:03:58,599 --> 00:04:02,479 that Angular and anglar j us are completely different things. So even though it 44 00:04:02,759 --> 00:04:08,439 sounds like we should be over this problem by now, I actually think this 45 00:04:08,680 --> 00:04:15,800 rebranding and distancing ourselves from all that can make people identify Angler as if you 46 00:04:15,879 --> 00:04:18,560 were anglergyass, I think it's for the best. So yeah, I'm on 47 00:04:18,600 --> 00:04:25,120 board with the change. Yeah, the idea of doing a rebrand is different 48 00:04:25,160 --> 00:04:29,120 from having a logo that looks like a second year art student made it. 49 00:04:29,519 --> 00:04:35,879 That that's I'm just saying, Oh, shots fired, No, I really 50 00:04:35,879 --> 00:04:42,879 don't like it, but not my decision. So I like, someone just 51 00:04:43,079 --> 00:04:46,079 slept and opened this is fine. Cut it, cut it, cut it 52 00:04:46,079 --> 00:04:51,959 here and right? How much it five minutes done? Grady, it's awesome. 53 00:04:55,639 --> 00:05:00,160 Yeah, but what one thing I was searching about posting it might my 54 00:05:00,279 --> 00:05:03,480 channel was trying to download the logo, but it's not. It's a gradient. 55 00:05:03,519 --> 00:05:10,040 It says SPG. Now, so either either like if you have animated 56 00:05:10,279 --> 00:05:15,720 logo, you you have TOPG the thing though, but yeah, rebranding is 57 00:05:15,959 --> 00:05:26,439 required and opening Photoshop or something. Yeah, you can get away with that. 58 00:05:26,439 --> 00:05:30,199 That's not a major issue for me. Yeah, okay, so what's 59 00:05:30,279 --> 00:05:34,759 you besides the colors. Yeah, let's get into the other stuff. Let's 60 00:05:34,759 --> 00:05:46,040 see if anything pleases you. Check. I don't have any opinions. Let's 61 00:05:46,040 --> 00:05:49,879 get into the new docs. So we are not gonna rely on Angular dot 62 00:05:49,920 --> 00:05:55,480 i O anymore. We have a new website with a new domain and now 63 00:05:55,600 --> 00:06:00,120 everything is over Angular dot do. So a couple of pros and cons, 64 00:06:00,199 --> 00:06:06,439 just so that we can summarize it. Seems that now we have interactive tutorials, 65 00:06:06,800 --> 00:06:11,800 which is cool. And they said that they revised the entire thing. 66 00:06:11,839 --> 00:06:15,879 I'm saying those things in that way, instead of giving certainty just because I 67 00:06:16,000 --> 00:06:20,720 myself haven't taken the time to actually read to the entire new documentation, I 68 00:06:20,879 --> 00:06:27,000 just scheme to the website and it looks good. It looks really good. 69 00:06:27,360 --> 00:06:32,959 Yeah, it looks it looks better than the old website. And what I 70 00:06:33,000 --> 00:06:38,639 really like is that when they were announcing this new website, they said that 71 00:06:38,680 --> 00:06:45,439 they revisited the entire documentation to make it way easier for people to get started 72 00:06:45,480 --> 00:06:49,720 on Angler, and they also made sure that every lesson was contained in itself. 73 00:06:49,920 --> 00:06:56,600 So for example, if you want to learn just how dependence injection works, 74 00:06:56,639 --> 00:07:00,399 you can read only the lesson about the pend this injection. You don't 75 00:07:00,439 --> 00:07:05,279 need to read anything that came before. So they made it in a way 76 00:07:05,480 --> 00:07:11,839 in which it requires a minimum amount of context from the lessons that are in 77 00:07:12,000 --> 00:07:16,079 other sections. So that's really good for people that just want to like a 78 00:07:16,199 --> 00:07:21,519 quick handbook to consult how a particular part of the framework works. I think 79 00:07:21,600 --> 00:07:29,439 that's a major leap forward. I really really really like that. And one 80 00:07:29,639 --> 00:07:35,680 cons is that right now this new website is doing beta and it doesn't have 81 00:07:35,879 --> 00:07:42,959 all the features that the other website had. For example, translations. There 82 00:07:43,040 --> 00:07:48,560 are no other languages. Everything is just in English, and there's no way 83 00:07:48,759 --> 00:07:55,680 for people to go to GitHub and add other languages to it. In their 84 00:07:55,720 --> 00:07:59,879 defense, in the old website, it was also not super easy, like 85 00:08:00,040 --> 00:08:05,800 people would have to clone the website repository to create versions in other languages, 86 00:08:05,839 --> 00:08:09,959 so it wasn't super easy, and Minko said that they are trying to make 87 00:08:11,040 --> 00:08:15,439 it easier this time, so they I'm thinking that they're going to do everything 88 00:08:15,519 --> 00:08:20,319 in the same repository and just kind of have the different languages sitting up there 89 00:08:20,360 --> 00:08:26,560 as markedown files. Probably would probably that would be much better, but unfortunately 90 00:08:26,600 --> 00:08:30,560 we don't have support for that yet. And I totally understand, like they're 91 00:08:30,600 --> 00:08:35,279 just releasing the website. They don't want to make it too rigid because like 92 00:08:35,399 --> 00:08:39,919 structural decisions like this make it harder for you to make changes to the website 93 00:08:39,000 --> 00:08:45,879 later on. But at the same time, I'm not sure if I agree, 94 00:08:46,000 --> 00:08:50,240 just because like they just released it, so everybody is excited, so 95 00:08:50,360 --> 00:08:58,679 I feel like this would they have enough momentum that asking for people to create 96 00:08:58,759 --> 00:09:03,879 translations would probably work really well right now, just because everybody's talking about it, 97 00:09:05,159 --> 00:09:07,360 so that would be a good moment for them to ask people to create 98 00:09:07,360 --> 00:09:13,279 translations, but nobody can't do that yet. So yeah, that's one cost. 99 00:09:13,279 --> 00:09:18,080 But everything else that I've seen so far are just pros. Yeah. 100 00:09:18,080 --> 00:09:22,879 I think one thing I liked a lot is that they have now they have 101 00:09:22,919 --> 00:09:28,240 a playground option and in that if you go to the contact flow, and 102 00:09:28,279 --> 00:09:33,080 it is so that how far Anglar came. Now within only one file you 103 00:09:33,120 --> 00:09:37,679 can host your application like only main dot ts and that's all. So now 104 00:09:37,679 --> 00:09:43,360 a'mular that is going in a like a modelarized way, or you can say, 105 00:09:43,399 --> 00:09:48,399 like how minimalistic way. Now new people coming to Angular, they don't 106 00:09:48,440 --> 00:09:52,159 have to learn about modules a lot of things. They can start building it 107 00:09:52,279 --> 00:09:58,120 and on in process they will learn a lot a lot of things. Yeah, 108 00:09:58,120 --> 00:10:01,879 I think they're using stacklets for that, aren't they. Ah, But 109 00:10:03,080 --> 00:10:07,759 uh, it's it's pretty slick, yeah, because it's yeah, it's building 110 00:10:07,840 --> 00:10:13,840 and injecting dependencies for like polyphills and stuff. But yeah, I I really 111 00:10:13,039 --> 00:10:18,840 like that piece. And like you said, it's all simplified too, yep. 112 00:10:20,480 --> 00:10:24,399 And here we can write it everything builder application, then down download it, 113 00:10:24,799 --> 00:10:28,200 then put it so that's off. Sen is also there, so yeah, 114 00:10:28,360 --> 00:10:35,320 you always didn't they not have to start from the scratch YEP. I 115 00:10:35,320 --> 00:10:43,399 also like that there's a key command for search and then it does dark mode. 116 00:10:43,440 --> 00:10:46,240 My computer's on dark mode, so it went to dark mode automatically. 117 00:10:46,799 --> 00:10:50,840 But I'm starting to like websites in light mode better even now. I like 118 00:10:50,879 --> 00:10:56,320 my computer and dark mode. Don't ask me why, but it just a 119 00:10:56,320 --> 00:11:01,159 lot of that makes it a lot simpler. Just you know, the the 120 00:11:01,360 --> 00:11:05,399 command K for search, and then any other key commands that you know you 121 00:11:05,480 --> 00:11:11,639 expect to work in other systems tend to work here, and so that is 122 00:11:11,759 --> 00:11:16,879 pretty approachable to your point, Lucas. With the translations, yeah, every 123 00:11:16,879 --> 00:11:20,879 translation is a bit of work. I was gonna joke and say they should 124 00:11:20,879 --> 00:11:24,600 just put it Google Translate right right, But the reality is is, yeah, 125 00:11:24,639 --> 00:11:28,679 you you want it to be correct, and Google Translate isn't always so 126 00:11:31,000 --> 00:11:37,120 yeah. What would be interesting too, is if they got bona fide translations 127 00:11:37,159 --> 00:11:41,320 going, and then they could maintain their momentum by saying, hey, now 128 00:11:41,360 --> 00:11:45,360 we have a French version, right, just let everybody know, Hey, 129 00:11:45,399 --> 00:11:46,840 we've got the French version. Now, we got the Spanish version, now 130 00:11:46,840 --> 00:11:52,240 we've got the Japanese version. Now you're right, because then every community is 131 00:11:52,240 --> 00:11:56,759 going to be going, yeah, you got to us. So that's a 132 00:11:56,759 --> 00:12:01,840 good point. Yes, so they can to do that. That's a good 133 00:12:01,840 --> 00:12:07,120 point. Yeah. And well, in terms of the website itself, before 134 00:12:07,159 --> 00:12:11,120 we actually get into Angular version seventeen, another thing that I also liked is 135 00:12:11,159 --> 00:12:16,480 that at the bottom of the side menu they also added a section for it. 136 00:12:16,679 --> 00:12:20,600 Well, there are a lot of new sections, a lot of new 137 00:12:20,840 --> 00:12:24,639 lessons, but there's this new section called extended Ecosystem, and I thought that 138 00:12:24,799 --> 00:12:33,120 was so smart because there's more to the extended native ecosystem of Angular than just 139 00:12:33,159 --> 00:12:37,120 Angular Material. But unfortunately a lot of people think they're like, oh, 140 00:12:37,200 --> 00:12:39,759 there's Angular, there's Angular Material, and everything else is just third party. 141 00:12:41,080 --> 00:12:48,519 So now they are adding all those other extended libraries to this Angular dot dev 142 00:12:48,559 --> 00:12:54,039 documentation, which makes it really clear that they are supported by Google itself. 143 00:12:54,120 --> 00:12:58,720 So we have Angular fire which is to work with Firebase. We also have 144 00:12:58,759 --> 00:13:03,360 one for Google Maps, another for Google Pay, the YouTube player, and 145 00:13:03,399 --> 00:13:09,399 then we have the traditional ones like the Angler CDK and Angler material, as 146 00:13:09,440 --> 00:13:13,120 well as some other stuff for service workers and PWAs. So I really like 147 00:13:13,240 --> 00:13:18,240 that. It's like a it's a nice call to action for people to go 148 00:13:18,320 --> 00:13:26,639 beyond what's just on the core angular dogs and learn more about those other things 149 00:13:26,639 --> 00:13:33,480 that they might want to use in their applications too. Right, I think 150 00:13:33,720 --> 00:13:37,879 one thing I would like to like to maybe in some future some may be 151 00:13:37,879 --> 00:13:41,720 Angler or React. They will also integrate some AI with it, and people 152 00:13:41,759 --> 00:13:46,759 that go to the dog and say I need this application, and then they 153 00:13:46,879 --> 00:13:50,120 prepared application and give it to them. That reminds me of when I first 154 00:13:50,200 --> 00:13:58,200 got started freelancing. So I was doing Reviy on rails and Twitter when it 155 00:13:58,240 --> 00:14:01,279 came out was written in Ruby on rails. They've moved a lot of their 156 00:14:01,320 --> 00:14:05,120 stack off into other pieces depending on anyway. So I would get emails from 157 00:14:05,159 --> 00:14:09,080 people that said, hey, can you write me a script that will be 158 00:14:09,120 --> 00:14:18,279 a Twitter app? Oh man? I love talking to people that want to 159 00:14:18,279 --> 00:14:22,919 build to tack business and have no idea how it is to code. Well. 160 00:14:24,240 --> 00:14:26,399 The other thing that gets me though, is just like, look, 161 00:14:26,639 --> 00:14:31,080 is there any other part of business anywhere where if I could crank you out 162 00:14:31,120 --> 00:14:35,320 of Twitter clone in two days, then it would be worth anything because anybody 163 00:14:35,320 --> 00:14:39,960 wanting to compete with you can do the exact same thing. Right, The 164 00:14:41,039 --> 00:14:43,440 profitable businesses are the ones that are out there. Yeah, they make it 165 00:14:43,480 --> 00:14:46,879 easy for you to do a thing, but it's not trivial to copy what 166 00:14:46,960 --> 00:14:56,159 they did exactly exactly. Yeah, I don't know why, but okay, 167 00:14:56,240 --> 00:15:01,639 So in terms of the last new thing is a new version of Angler. 168 00:15:01,879 --> 00:15:07,720 So we have Angular version seventeen now, and that was actually released today. 169 00:15:09,279 --> 00:15:15,559 So the website was released Monday, but Angler seventeen was released today a few 170 00:15:15,600 --> 00:15:20,679 hours ago. But we already know what's in it because they said the in 171 00:15:20,720 --> 00:15:24,919 the launch of the new brand Monday. And let's go over what's new. 172 00:15:26,080 --> 00:15:33,559 So first, we have much a much more improved build performance because now Yes 173 00:15:33,720 --> 00:15:39,600 Build and Vite are no longer just experimental. They're actually stable bundlers. Cool. 174 00:15:39,960 --> 00:15:45,720 Yeah, and if you replace Webpack with Yes Build or vite, you're 175 00:15:45,759 --> 00:15:50,919 gonna get I don't even know it by a head, but it's like maybe 176 00:15:50,080 --> 00:15:54,919 ninety percent faster. It's like something egregious like that, just like much, 177 00:15:56,039 --> 00:16:00,279 much, much faster. I think it's funny because people I've heard some people 178 00:16:00,320 --> 00:16:03,799 bagging on Webpack, you know now that we have an es builder of Eat. 179 00:16:04,120 --> 00:16:08,559 But the reality is is that Webpack kind of opened the gate to this 180 00:16:08,600 --> 00:16:11,360 whole thing, so you have to give them a ton of credit and then 181 00:16:11,440 --> 00:16:15,840 recognize that, yeah, we want faster builds and so we're going to use 182 00:16:15,879 --> 00:16:18,840 a different tool now because they are better tools. But yeah, props to 183 00:16:18,879 --> 00:16:26,320 the Webpack folks for solving some of these problems early. Definitely, definitely they 184 00:16:27,159 --> 00:16:33,200 as you said, they opened up the gates. And the only reason why 185 00:16:33,720 --> 00:16:41,600 other competitors can differentiate themselves just because they are faster is because Webpack already differentiated 186 00:16:41,639 --> 00:16:45,279 itself by having all the features, so everybody else can just say we have 187 00:16:45,360 --> 00:16:48,720 the features and we are fast the plug ins. Yeah, exactly exactly, 188 00:16:49,519 --> 00:16:53,440 but it's really nice that we have that. This is definitely going to improve 189 00:16:53,480 --> 00:16:57,240 the overall developer experience, which by the way, I was already feeling that 190 00:16:57,320 --> 00:17:02,360 it was much better. I was. I was getting like less than one 191 00:17:02,399 --> 00:17:07,799 second hot reload when developing on the latest versions of Anglers. So now that 192 00:17:07,920 --> 00:17:15,599 we have the other build modules, I'm guessing that this will be even less 193 00:17:15,680 --> 00:17:22,400 noticeable. So yeahs yeah, exactly exactly, And I mean, sorry, 194 00:17:22,440 --> 00:17:26,400 go ahead, you know I'm saying that with this week they have also like 195 00:17:26,559 --> 00:17:32,680 have a eighty seven percent rendering sixty seven percent client set rendering, so after 196 00:17:32,720 --> 00:17:37,359 you build, also when you're rendering with some ankle universala something that that is 197 00:17:37,400 --> 00:17:48,559 also quite fast. Now yeah, I feel like the most noticeable performance improvement 198 00:17:48,599 --> 00:17:53,039 now it's going to be in continuous integration, because if you're just developing locally, 199 00:17:53,240 --> 00:17:57,960 I don't feel like the speed right now is a problem. But when 200 00:17:59,000 --> 00:18:03,319 you actually send your code and you open up your PR and then you have 201 00:18:03,359 --> 00:18:07,920 to wait for your continuous integration system to build and run all the checks and 202 00:18:08,000 --> 00:18:14,480 tests, then that still takes up a while. If you have Like at 203 00:18:14,759 --> 00:18:19,119 Void, we generally use NX to organize all of our Angular code basis, 204 00:18:19,240 --> 00:18:23,839 and then we can break it into smaller pieces and we can use caching for 205 00:18:23,920 --> 00:18:29,400 all the individual pieces. So when we send something to CI, it builds 206 00:18:29,480 --> 00:18:33,200 up much faster because it's only building smaller parts of the application instead of having 207 00:18:33,200 --> 00:18:41,480 to rebuild the entire thing all the time. But still it's still not blazingly 208 00:18:41,640 --> 00:18:47,440 fast. Like I would say, it takes a minute and a half to 209 00:18:47,559 --> 00:18:55,960 two minutes on average for our Angular libraries to build on continuous integration, even 210 00:18:56,039 --> 00:19:00,720 with part of them being cashed. So if there's no cash, I would 211 00:19:00,759 --> 00:19:03,319 say that it takes like two minutes to two and a half on average. 212 00:19:03,720 --> 00:19:08,400 So I really like the idea of eating things up on CI. I think 213 00:19:08,400 --> 00:19:14,759 it's going to give us a much faster feedback loop. Because sometimes I gotta 214 00:19:14,799 --> 00:19:21,079 be honest, Sometimes I send coach to CI and I go make some coffee. 215 00:19:23,759 --> 00:19:27,920 It's like that x KCD where they're fencing and the boss walks by, 216 00:19:29,079 --> 00:19:33,680 like, what are you guys doing? Oh, it's the Yeah, yeah, 217 00:19:33,119 --> 00:19:36,640 okay. I think now it's pretty good. Yeah. Like I think 218 00:19:37,119 --> 00:19:44,119 we just have to have a look on like how Angular is growing. I 219 00:19:44,119 --> 00:19:47,799 think be pour Anglar nine or something till Angle and nine people are saying Angular 220 00:19:47,920 --> 00:19:53,240 building, we have a very high high amount of any cell bundle size and 221 00:19:53,279 --> 00:19:59,119 that is reduced then Ivy game, then then slowly stand alone everything. Now 222 00:19:59,759 --> 00:20:04,480 with Anglar seventeen we have control flow. So now Angler is also making how 223 00:20:04,559 --> 00:20:11,440 flexible you want to write a code. It's in your way, how how 224 00:20:11,480 --> 00:20:17,720 you can divide your code to a different function and use them as you like 225 00:20:17,799 --> 00:20:23,359 it. It's I think it's removing the rigidity from Angular and giving more flexibility 226 00:20:23,359 --> 00:20:29,599 to the developer. And that's that that's a very good way which anglized. 227 00:20:29,799 --> 00:20:33,640 I think seventeen is the might be a very big religion in terms of Angular 228 00:20:33,680 --> 00:20:38,160 ecosystem. Yeah, let's talk more about that. So build in control flow. 229 00:20:38,680 --> 00:20:44,559 It's not really a new feature itself, but it's it's a way for 230 00:20:44,640 --> 00:20:48,720 you to clean up your code a lot, and it's also going to make 231 00:20:48,759 --> 00:20:52,799 it much more easier for beginners to get into Angular. So now you don't 232 00:20:52,920 --> 00:20:56,559 need and let me be clear, it's not that you can't. You can 233 00:20:56,559 --> 00:21:03,359 still use NGF and four and switch, but you don't need to use that 234 00:21:03,599 --> 00:21:10,279 because right now we have building functionalities for the So you have a building at 235 00:21:10,440 --> 00:21:15,680 if statement. You also have l's if and l's already built in into the 236 00:21:15,680 --> 00:21:22,039 Angler template language, so you don't need to import the common module and use 237 00:21:22,240 --> 00:21:27,799 NGF, NG four, eng switch. You can get rid of those unnecessary 238 00:21:29,079 --> 00:21:33,599 elements or engine containers that you are using just to provide country flow. And 239 00:21:33,799 --> 00:21:40,799 they are also faster. So they are also faster. But I think the 240 00:21:40,839 --> 00:21:44,279 main benefit is not really the speed, is really the syntax. It's just 241 00:21:44,400 --> 00:21:52,799 much clearer to read and understand how the component is being rendered and in which 242 00:21:52,839 --> 00:22:00,160 steps things are being rendered, and now what is actually new not just like 243 00:22:00,200 --> 00:22:04,160 a synthactic change. But an actual new feature is deferable views, and it 244 00:22:04,240 --> 00:22:08,440 goes on top of the new built in control flows. So it's using the 245 00:22:08,519 --> 00:22:17,559 same syntax as if for and switch statements, but it's a different thing. 246 00:22:17,839 --> 00:22:23,240 Like we don't have a way like an energy deferable view, you know, 247 00:22:23,480 --> 00:22:30,880 like there's no that right now on Angler sixteen. But we do have this 248 00:22:30,160 --> 00:22:37,519 at the fur command right now, which is going to allow you to tell 249 00:22:38,039 --> 00:22:45,559 your template that parts of it should only be rendered after a given a synchronous 250 00:22:45,599 --> 00:22:49,039 condition happens. And this a synchronous condition can be one of the presets that 251 00:22:49,079 --> 00:22:55,720 they have, like once the component is on the viewpoort, once it loads, 252 00:22:55,839 --> 00:22:57,680 like you have a bunch of triggers, but you can also have your 253 00:22:57,720 --> 00:23:03,839 custom triggers, so you can say when this property is equal to true, 254 00:23:03,000 --> 00:23:07,200 or when this array is not empty. You know, you can have things 255 00:23:07,240 --> 00:23:14,119 like that to indicate that the request that you made to the backhand was successful, 256 00:23:14,200 --> 00:23:18,400 the data was retrieved and now you're ready to show it. So you 257 00:23:18,440 --> 00:23:22,680 can put the parts of your component that depend on this data already being available 258 00:23:22,720 --> 00:23:30,400 inside a defer condition, and then you can give it the condition of when 259 00:23:30,400 --> 00:23:34,480 that part of the deferable view is supposed to be rendered, and it's going 260 00:23:34,519 --> 00:23:37,720 to be rendered when that happened. And it also has a lot of other 261 00:23:37,880 --> 00:23:45,240 utilities, right, So red like you now have a very declarative way of 262 00:23:48,279 --> 00:23:53,759 saying like what should be showed to the user when the data is being loaded? 263 00:23:55,359 --> 00:24:00,200 Or you can even add what's it called, like that template that you 264 00:24:00,279 --> 00:24:03,559 show when you don't have data, but it feels like you have the components 265 00:24:03,559 --> 00:24:10,319 there I forgot the name of it. Placeholders. Yeah, you can also 266 00:24:10,319 --> 00:24:17,839 show these placeholder components and it's so declarative it's really really easy to understand what's 267 00:24:17,880 --> 00:24:21,920 going on. You even have a section to tell what happens if there's an 268 00:24:22,039 --> 00:24:27,759 error. So that sounds really promising. I really liked this the first statement. 269 00:24:30,559 --> 00:24:34,519 Yeah, I think by using up viewport and by different sell loading, 270 00:24:36,359 --> 00:24:41,240 by different loading, it's also like I think going in a way of which 271 00:24:41,240 --> 00:24:48,559 Angler has in future in mind that change detection will work as a view basis, 272 00:24:48,599 --> 00:24:52,319 like currently it's working as a component basis, so only on your component 273 00:24:52,319 --> 00:24:56,400 if you flag, if your component is flagged, it will be registered for 274 00:24:56,480 --> 00:25:00,799 change detection. Then the whole flow is down that now you can convert that 275 00:25:00,920 --> 00:25:06,039 to So in future, what will happen. They'll convert each suppose a fur 276 00:25:06,160 --> 00:25:11,359 loop or a statement to a view and that view only be redent and not 277 00:25:11,519 --> 00:25:15,880 the whole component. So I think this is a new way, starting way, 278 00:25:17,480 --> 00:25:23,279 and that is only possible with standalone based component and signals and everything. 279 00:25:23,319 --> 00:25:30,039 So I think in few a lot of things yet to come in eighteen nineteen, 280 00:25:30,759 --> 00:25:36,680 yeah, yeah, and everything else. I think we can put it 281 00:25:36,720 --> 00:25:41,799 in a box of developer experience. So I'm going to just list some of 282 00:25:41,839 --> 00:25:47,279 the other things that we have, but honestly, there's just so much here 283 00:25:47,440 --> 00:25:52,359 that we're probably going to have to do other episodes to get deeper into it 284 00:25:52,440 --> 00:25:55,559 and actually show examples, and we focused on each of them, but just 285 00:25:55,599 --> 00:26:00,279 so that we actually have a complete podcast where we list all the new things 286 00:26:00,319 --> 00:26:04,960 for you. The other things that we have are like improvements to service side 287 00:26:06,000 --> 00:26:10,480 rendering, so there are performance improvements to service I render and they're also like 288 00:26:11,440 --> 00:26:15,480 quality of life improvements. For example, right now, before Anglar seventeen, 289 00:26:15,559 --> 00:26:21,799 if you wanted to start a code base from scratch and add Angular Universal to 290 00:26:21,880 --> 00:26:25,160 it, you needed to do just that. You needed to start the code 291 00:26:25,160 --> 00:26:27,440 base, and then at Angular Universal, there was no way for you to 292 00:26:27,599 --> 00:26:33,359 just already start with Anglar Universal setup. It wasn't super hard to set up 293 00:26:33,400 --> 00:26:38,599 Angular Universal, but it was that extra step, right, And now you 294 00:26:38,599 --> 00:26:42,200 can have that already in the CLI, so you can start a new project 295 00:26:42,279 --> 00:26:48,319 and use dash dash assr and it's going to already start with Angular Universal. 296 00:26:48,759 --> 00:26:52,880 Also, they renamed it so it's no longer called Angular Universal. It's called 297 00:26:53,279 --> 00:27:02,720 Angular SSR, which is much more Yeah, it's much easier to I liked 298 00:27:02,880 --> 00:27:08,440 the idea of Angular Universal because when it originally came up, the idea was 299 00:27:08,599 --> 00:27:14,920 to have Angular running in all sorts of environments, So it wasn't like just 300 00:27:15,200 --> 00:27:21,559 for service ARE rendering. It was supposed to provide all the necessary structure to 301 00:27:21,640 --> 00:27:23,680 make Angular run in any environment that you want, so which is why it 302 00:27:23,759 --> 00:27:30,720 was called universal. But the truth is, over time we really only used 303 00:27:30,720 --> 00:27:34,839 it to do service I rendering, so it just makes sense to call it 304 00:27:34,880 --> 00:27:38,759 Service I rendering. And if you're going to support other platforms, you can 305 00:27:38,839 --> 00:27:45,119 have modules or packages that have the names of that of those platforms specifically. 306 00:27:45,200 --> 00:27:52,799 So for example, if Angler ever releases a native way to build hybrid apps, 307 00:27:52,839 --> 00:27:56,880 I know that we already have Ionic, but if Angler decides to release 308 00:27:56,920 --> 00:28:03,319 a native version instead of using Universal and putting all those platforms into the scope 309 00:28:03,359 --> 00:28:07,359 of Universal, they can have like an at Angular Slash Mobile for example, 310 00:28:07,720 --> 00:28:11,839 which is also going to be much easier to understand. So I like this 311 00:28:11,000 --> 00:28:22,480 movement of calling it angular SSR. Then we also had some other improvements to 312 00:28:22,000 --> 00:28:27,440 the bugging, so now we have dependency injection Debugging in Depth DULs. So 313 00:28:27,559 --> 00:28:32,720 the Angular dept DoLS now has a dedicated page for dependency injection, and you 314 00:28:32,720 --> 00:28:37,720 can understand where your instance is coming from, and also if you were not 315 00:28:37,880 --> 00:28:44,720 able to to if Angler wasn't able to provide an instance of what you wanted, 316 00:28:45,240 --> 00:28:52,559 like how it traversed up to the root node and all the steps that 317 00:28:52,599 --> 00:28:56,279 it went to get there, so you can see if the module that you're 318 00:28:56,319 --> 00:29:06,119 providing this dependency is not in this hierarchical tree, and you can understand why 319 00:29:06,720 --> 00:29:08,839 you're not able to inject the dependency that you want to inject. So that 320 00:29:08,880 --> 00:29:15,880 also helps the ton And yeah, like a lot of other quality improvement, 321 00:29:15,920 --> 00:29:18,759 one that I really liked, I really like, but I want Suprett's opinion 322 00:29:18,799 --> 00:29:26,920 on this one. So let's see suberred. Have you taken a look into 323 00:29:27,079 --> 00:29:34,319 the how do they call it? I think it's transform input value transforms. 324 00:29:34,519 --> 00:29:40,119 So it's basically like you have you know, when you have a buttom and 325 00:29:40,160 --> 00:29:44,640 you want to have like this disabled parameter, but you don't want people to 326 00:29:44,720 --> 00:29:48,200 actually have to set up a value to it. It's like just the mere 327 00:29:48,359 --> 00:29:55,160 presence of the disabled attribute should already tell the component that it is disabled. 328 00:29:55,319 --> 00:30:00,920 But the thing is for you to support that that synax. We needed to 329 00:30:00,160 --> 00:30:07,279 convert the existence of this attribute into a bullion to indicate if disabled was true 330 00:30:07,400 --> 00:30:12,400 or false. Uh, And that added up other boilerplate to the co base. 331 00:30:12,480 --> 00:30:18,400 And now we can do all that with a single, natively supported way 332 00:30:18,480 --> 00:30:22,759 to transform the input. But I wanted your opinion, so Brette, like, 333 00:30:22,240 --> 00:30:27,960 do you think the way they did it is Yeah, I'm just wondering 334 00:30:27,960 --> 00:30:34,039 about the signature of the function itself and the way in which we build those 335 00:30:34,240 --> 00:30:37,440 transformers. Have you had a chance to take a look at that. I 336 00:30:37,440 --> 00:30:44,200 have used that though in angles sixteen. If you passed a transform attribute to 337 00:30:44,559 --> 00:30:51,319 the to input and past and that the corresponding component and that you can just 338 00:30:51,480 --> 00:30:56,960 report it now. But yeah, it's the required actually how people should do 339 00:30:57,039 --> 00:31:02,440 it, because I so a lot of sides they just put it digble and 340 00:31:02,519 --> 00:31:07,480 they go and change remove that part. It re enables it and you can 341 00:31:07,559 --> 00:31:11,599 go and fast forward. So the first thing is to not do that, 342 00:31:11,799 --> 00:31:15,599 like you should not have an option to have a user can edit in the 343 00:31:15,759 --> 00:31:21,640 STML and then just passed the passityjable. Second way is yeah, I think 344 00:31:21,640 --> 00:31:27,039 the input way is good in terms of passing the state from parent to child. 345 00:31:27,119 --> 00:31:33,240 And now I think but I guess it's not on the seventeen right, 346 00:31:33,279 --> 00:31:38,759 so I it started at the sixteen, I guess, or just came seventeen 347 00:31:38,759 --> 00:31:45,000 because I remember using it sixteen. It actually came like officially came on version 348 00:31:45,079 --> 00:31:51,759 seventeen. Okay, experiment sixteen, Yeah, yeah, maybe that was it. 349 00:31:52,599 --> 00:31:56,400 I really only only saw it on Angler seventeen, so I don't think 350 00:31:56,440 --> 00:32:00,920 we had that on sixteen. Well, we did have six thing with Anglar 351 00:32:01,000 --> 00:32:07,839 signals, which now if I recall correctly, they are officially stable. Right. 352 00:32:07,319 --> 00:32:13,640 Oh cool, yeah, yeah, all right, I've got to take 353 00:32:13,680 --> 00:32:16,920 off if you guys want to keep talking and Lucas if you have the end 354 00:32:17,000 --> 00:32:21,920 stream button in the top right corner you can keep going. Otherwise I've got 355 00:32:21,960 --> 00:32:23,960 to wrap us up. Okay, we can keep going. I have it, 356 00:32:24,160 --> 00:32:28,920 Okay, you have it all right, Well this was fun, really 357 00:32:28,960 --> 00:32:32,519 cool, looking forward to good new things to come. Sorry, folks, 358 00:32:32,559 --> 00:32:37,160 I gotta bail. My kids have a My daughter made the honor roll and 359 00:32:37,759 --> 00:32:42,039 so they're having a thing at the school. So anyway, go ahead and 360 00:32:42,119 --> 00:32:46,720 keep talking and we'll catch y'all later. Okay, thanks for Johnny. Thanks. 361 00:32:49,440 --> 00:32:53,480 Yeah, I guess about the transform. I guess they faery member transform 362 00:32:53,559 --> 00:33:00,519 off to bullian or transform like now we can pass it will check your input 363 00:33:00,640 --> 00:33:07,319 type on the on the sub. Suppose you're you're passing a string and somehow 364 00:33:07,880 --> 00:33:12,880 you are passing a number to the to the input. That also transfer will 365 00:33:12,920 --> 00:33:15,720 help that. Okay, it's a bullion. It's not a number. I 366 00:33:15,720 --> 00:33:20,799 think earlier alily to us not you'll get it only on run time, not 367 00:33:20,839 --> 00:33:24,519 on compiled time. That's also another another but I think it's it's game with 368 00:33:25,039 --> 00:33:30,400 sixteen. Maybe I'm wrong with I have used experimental, but I have used 369 00:33:30,440 --> 00:33:37,880 it sixteen. Okay, okay, what else read? Do you think there's 370 00:33:37,920 --> 00:33:43,400 anything here that because we're definitely going to have to do all the episodes getting 371 00:33:43,440 --> 00:33:49,960 deeper. You have to use it like like a hands on develop some change 372 00:33:50,160 --> 00:33:57,119 some app with Hangulas seventeen and try to try to do it. I think 373 00:33:57,920 --> 00:34:01,119 n g r X also maybe it release with new seventeen. Maybe maybe they 374 00:34:01,119 --> 00:34:06,279 have already released out or maybe tomorrow or day after tomorrow. They will really 375 00:34:06,319 --> 00:34:10,440 just super quick with a version, so how it integrates with them and all 376 00:34:10,480 --> 00:34:15,760 the things. A lot of new things to do, and as every six 377 00:34:15,840 --> 00:34:19,960 month we are getting a new versions. So this is maybe fop for you 378 00:34:20,000 --> 00:34:23,920 guys who was watching us or listening to us like it's just a new version, 379 00:34:24,199 --> 00:34:28,119 doesn't things like okay, every six month, I have to learn new 380 00:34:28,159 --> 00:34:32,360 things. It's not like it's just addition up a slight small approach. So 381 00:34:32,400 --> 00:34:40,239 if you just keep listening to to podcast or start doing a project yourself, 382 00:34:42,199 --> 00:34:45,719 like slowly, you will learn everything. You don't have to put so much 383 00:34:45,760 --> 00:34:51,760 better on yourself that I have and read the dogs just to know what at 384 00:34:51,800 --> 00:34:55,719 all in end seventeen to focus on your product and we'll learn that. I 385 00:34:55,800 --> 00:35:02,440 decided definitely, definitely, I think that it was a beautiful disclaimer for us 386 00:35:02,079 --> 00:35:07,360 to start wrapping things up. Is like don't get afraid of it is not 387 00:35:07,519 --> 00:35:15,079 a new framework. It's still Angular, but a new logo though, Like, 388 00:35:15,360 --> 00:35:20,320 yeah, it's a new logo, but there are not too many major 389 00:35:20,440 --> 00:35:27,320 changes. The thing is, it's been a while that Angular itself its new 390 00:35:27,559 --> 00:35:35,400 right Ever since Angular thirteen fourteen fifteen, it already had this feeling that it 391 00:35:35,599 --> 00:35:40,599 was a much more modern framework. Somehow, there was like this big leap 392 00:35:42,079 --> 00:35:47,880 from versions, Like when we were upgrading from Vision like seven to eight to 393 00:35:49,039 --> 00:35:54,360 nine to ten to eleven, it didn't felt like we had many like big 394 00:35:54,480 --> 00:36:00,000 changes that would change the way in which we actually code Angle. There were 395 00:36:00,039 --> 00:36:07,719 a lot of improvements, definitely, but it didn't felt like it was really 396 00:36:07,840 --> 00:36:13,519 catching up with the other stuff that was appearing in other frameworks. But since 397 00:36:13,639 --> 00:36:20,280 Angular thirteen we really started to get momentum. So the fact that they rebranded 398 00:36:20,320 --> 00:36:24,679 it now doesn't mean that Angular seventeen is like a new thing, but I 399 00:36:24,719 --> 00:36:30,360 would say that ever since Angular thirteen it just feels like a new framework. 400 00:36:31,320 --> 00:36:36,800 So yeah, like, if you are on Angolar eight and want to upget 401 00:36:36,840 --> 00:36:42,679 to Anglar seventeen, then you might spend some time and go through everything and 402 00:36:42,800 --> 00:36:45,719 try to check late it's not breaking something. But if you're on Angler fourteen, 403 00:36:45,800 --> 00:36:51,440 fifteen or sixteen, I don't think it will break anything. It just 404 00:36:51,480 --> 00:36:54,239 need to run engy update and it to work. Definitely, definitely is going 405 00:36:54,320 --> 00:37:04,000 to be a breeze. And yeah, going to the promotions, I'm actually 406 00:37:04,039 --> 00:37:08,400 going to use this as a segue because if you are in the situation you 407 00:37:08,480 --> 00:37:13,760 need to upgrade your code base, then I feel free to reached out at 408 00:37:13,840 --> 00:37:19,239 Onvoid dot com is U n Void dot com because we definitely can help you 409 00:37:19,320 --> 00:37:23,000 out with that. And we work on a performance basis, so that means 410 00:37:23,039 --> 00:37:29,519 that you're only going to pay for our work when we actually deliver the work 411 00:37:29,559 --> 00:37:32,000 to you, So there's no risk you're not going to pay per hour. 412 00:37:32,199 --> 00:37:37,719 For example, Oh if we take longer than we anticipate it, that's our 413 00:37:37,800 --> 00:37:42,800 problem, that's not the client's problem. So the client is always in a 414 00:37:42,920 --> 00:37:46,920 much safer position when they're working with us. So if you're at all interested 415 00:37:47,280 --> 00:37:54,840 in either outsourcing a project or augmenting your staff, you can check out Void 416 00:37:55,039 --> 00:38:00,039 dot com. We are currently available for new projects, but I'm not sure 417 00:38:00,079 --> 00:38:04,440 for how long we're going to stay that way because we really have a maximum 418 00:38:04,440 --> 00:38:08,679 of projects in which we do concurrently because we understood that if we do more 419 00:38:08,719 --> 00:38:14,039 than that, it starts affecting our output and we don't want that. We 420 00:38:14,119 --> 00:38:19,960 want to be known as a company that delivers outstanding quality and not a company 421 00:38:20,000 --> 00:38:22,679 that has like thousands of clients. So yeah, if you're interested in that, 422 00:38:22,800 --> 00:38:28,159 go check out Onvoid dot com and we can schedule a meeting. How 423 00:38:28,159 --> 00:38:31,039 about you, Sugred, What would you like to promote? Yeah, I 424 00:38:31,079 --> 00:38:37,840 think nowadays I have a little bit pause. It's not too I think it's 425 00:38:37,159 --> 00:38:42,559 on the blaming on me though, like a little pause by from posting some 426 00:38:42,719 --> 00:38:46,559 videos. Sorry you guys for that. And I think nowadays I either I 427 00:38:46,639 --> 00:38:52,840 need to put a very long video or maybe starts. And that's what trending 428 00:38:52,920 --> 00:39:00,039 right now. YouTube is not promoting it after I guess after chat GPT people 429 00:39:00,440 --> 00:39:07,159 are searching less on programming stuff, so they are getting the answer from charge. 430 00:39:07,800 --> 00:39:10,960 We saw a decline in stack overflow traffic. We saw a decline in 431 00:39:12,039 --> 00:39:17,880 Google search or maybe searching too particular things. But yeah, but it's it's 432 00:39:19,199 --> 00:39:22,760 how it is. So so I will try to I think I'll try to 433 00:39:22,119 --> 00:39:28,280 have like the first podcast too. I will try to add some more podcasts 434 00:39:28,360 --> 00:39:34,079 and try to build with it, and I'm planning to schedule them and launch 435 00:39:34,119 --> 00:39:37,440 them. So yeah, if you, if you would like to go to 436 00:39:37,480 --> 00:39:43,400 my channel. My channel name is fun of Heuristic there we with there. 437 00:39:43,440 --> 00:39:47,119 We have plenty of videos on Angular, a lot of stuff like Angular, 438 00:39:47,199 --> 00:39:52,639 Peter Blu, a service worker working with location, and a lot of things. 439 00:39:52,719 --> 00:39:59,800 So you just go and check that and please keep the comment if you 440 00:40:00,400 --> 00:40:04,000 If you don't like it, scrolled me say that I don't like it, 441 00:40:04,039 --> 00:40:09,320 so I'll try to make it better, but please check it. Yeah, 442 00:40:09,360 --> 00:40:15,559 I sent a link to your YouTube channel here on the on the comment section, 443 00:40:16,119 --> 00:40:20,480 and we got to get used to that, right. It's weird having 444 00:40:20,480 --> 00:40:23,599 a comment section. I wasn't used to that when we were just recording the 445 00:40:23,679 --> 00:40:29,559 podcast, but now that everything is live, it's it's nice to have that. 446 00:40:30,920 --> 00:40:35,800 And I'm also putting it on Avoids website there, so if anyone wants 447 00:40:35,800 --> 00:40:38,440 to wants to check out. But yeah, again, just to reiterate, 448 00:40:38,599 --> 00:40:43,440 like, really, guys, if you like the content that we produce here, 449 00:40:43,599 --> 00:40:49,000 you're definitely going to like Subrett's channel. His content is really good and 450 00:40:49,079 --> 00:40:54,519 there's just so much that we can do with a podcast. Because even though 451 00:40:54,559 --> 00:40:58,800 we have this video version on YouTube right now, we always try to be 452 00:40:58,880 --> 00:41:02,079 mindful of all of you that are just on audio, so we try to 453 00:41:02,119 --> 00:41:08,159 avoid really showing code and depending on visual things to get our message across. 454 00:41:08,800 --> 00:41:14,400 But Subred has none of those limitations in his YouTube channel, so it's much 455 00:41:14,760 --> 00:41:17,679 easier for him to explain some of the concepts that might be harder for us 456 00:41:17,719 --> 00:41:22,599 to do here just because we are in an audio only format. So highly 457 00:41:22,639 --> 00:41:28,599 recommend check out his content, and it's definitely not just for beginners. He 458 00:41:28,679 --> 00:41:34,199 has a ton of very advanced stuff. He has things that I check out 459 00:41:34,239 --> 00:41:38,679 eventually and I learn new things, and like, I'm not trying to say 460 00:41:38,679 --> 00:41:43,800 that that I'm a complete expert in everything, but I would say that I'm 461 00:41:43,800 --> 00:41:46,239 pretty advanced. But still there are a lot of things that I learned from 462 00:41:46,280 --> 00:41:51,760 Subred. So I highly recommend. Thanks Mat, thanks for the nice verse. 463 00:41:52,960 --> 00:41:57,599 No problem, It's easy to recommend when the content is good. All 464 00:41:57,719 --> 00:42:02,480 right, let's start wrapping things up, So thank you everyone from for sticking 465 00:42:02,519 --> 00:42:07,320 with us. We really appreciate all of you with us for so long. 466 00:42:07,360 --> 00:42:15,800 We are approaching the episode number four hundred, Like, oh yeah, that's 467 00:42:15,960 --> 00:42:21,400 so much content, so much. Yeah, I think I joined around two 468 00:42:21,480 --> 00:42:27,280 hundred or three hundred. I joined the podcast around three hundred, I guess, 469 00:42:27,760 --> 00:42:31,400 so I had I was a guest and then then I joined the podcast. 470 00:42:31,440 --> 00:42:37,440 So I think it's a long journey. I think that's all care you 471 00:42:37,480 --> 00:42:43,000 go to Chucks like he's doing it for twelve years, the podcast King. 472 00:42:44,559 --> 00:42:49,320 Yeah, everyone should learn something from from him. You can. You can 473 00:42:49,400 --> 00:42:52,079 discuss with him the day in and day out, like, just discuss with 474 00:42:52,159 --> 00:42:58,360 him about podcasting and he will be definitely definitely. But at the same time, 475 00:42:59,079 --> 00:43:06,039 like, I'm a super fan of Chuck's commitment to this because it is 476 00:43:06,079 --> 00:43:08,559 a very long, a very big effort to keep this up for that long. 477 00:43:09,199 --> 00:43:15,840 But also a big shout out to everyone that actually listens to us, 478 00:43:15,880 --> 00:43:21,039 because we wouldn't really be here if there wasn't an audience. So thank you 479 00:43:21,119 --> 00:43:28,440 so much, and consider this an early thank you as we approach episode four 480 00:43:28,519 --> 00:43:34,920 hundred. All right, thanks everyone, I'll see you in the next one. 481 00:43:35,519 --> 00:43:40,199 See you guys, Bye bye.