1 00:00:06,919 --> 00:00:12,240 Hello and howdy everyone, Welcome to another Adventures in Angular. My name is 2 00:00:12,240 --> 00:00:16,600 Alyssa Nichel and today with me on the panel, I have Brooks for sith. 3 00:00:16,760 --> 00:00:21,160 Hello. I was trying to remember which of you goes first, honestly, 4 00:00:21,239 --> 00:00:24,640 so why I hick up there? So hopefully that was the right order, 5 00:00:24,719 --> 00:00:29,359 Brooks. If the order is more about picks and Chris cost first, 6 00:00:29,600 --> 00:00:32,240 Okay, okay, so you don't care in the beginning. Cool, cool, 7 00:00:32,280 --> 00:00:35,759 I'm off the hook, and of course I lovely Chris Ford is with 8 00:00:35,840 --> 00:00:38,880 us today as well. I mean we've already established I'm here. Thanks for 9 00:00:38,920 --> 00:00:45,479 the spoiler of that, Eb Brooks shocker, and our guest of honor is 10 00:00:45,520 --> 00:00:50,200 Alexi Quincivish. Welcome Alexi. Hello, Hello everyone, goodness, and I 11 00:00:50,240 --> 00:00:54,240 do apologize if I messed up the first, last, or all of it 12 00:00:54,320 --> 00:00:59,039 together as a whole, but welcome, welcome to the show. What are 13 00:00:59,079 --> 00:01:03,119 we actually befo? Before we talk about our topic of the day, can 14 00:01:03,119 --> 00:01:07,000 you introduce yourself for the audience? AH? Me right, so yes, 15 00:01:10,040 --> 00:01:14,680 my name is Alex Concidge. I am an angel expert, mentor and independent 16 00:01:14,719 --> 00:01:19,000 consultant based in Sydney helping companies to adopt ANGLA in the most efficient way by 17 00:01:19,000 --> 00:01:25,760 applying solid architectures and best practices. So also I'm organizing meetups like Angler related 18 00:01:25,799 --> 00:01:30,719 meetups and running online and un flying Angelo workshops and teaching Angle at consideration the 19 00:01:30,799 --> 00:01:37,680 depth. I'm also creator of frontenach frontlage dot com. It's an nilary resource 20 00:01:37,760 --> 00:01:42,239 where you can learn more about modern front front and frameworks. And I recently 21 00:01:42,280 --> 00:01:48,079 become a part of ejecs escorting. Yes, pretty much about that's just a 22 00:01:48,159 --> 00:01:52,840 small list of achievements. A long CV man. That's awesome, very important. 23 00:01:52,959 --> 00:02:04,959 Hired you like, but the job is car and Ury Brocks. Oh 24 00:02:05,040 --> 00:02:08,680 my goodness. So what are we talking about today, Alexi? So today 25 00:02:08,719 --> 00:02:15,439 we're talking about progressive state management with ng access. So what's the progressive state 26 00:02:15,520 --> 00:02:20,719 management? Right? This is the question? Probably, I mean, yeah, 27 00:02:21,080 --> 00:02:24,680 most of the people wonder, like, let's progress that management the way 28 00:02:24,800 --> 00:02:30,599 it's like today. I mean, maybe someone else have their own idea about 29 00:02:30,599 --> 00:02:36,199 progressive state management, but my idea was Progressive state management is development technique when 30 00:02:36,240 --> 00:02:40,280 you progressively enhance in the functionality of the application state in a way it won't 31 00:02:40,319 --> 00:02:46,840 affect the existing data flow and existing structure of your application. So basically you 32 00:02:46,919 --> 00:02:54,199 start in you're up just by implementing reactive services, and then if you won't, 33 00:02:54,479 --> 00:03:00,560 you can go another level of state management. Right and if you like 34 00:03:00,639 --> 00:03:05,639 in jecas, so you choose in Jexas because I'm in JAXA's friend, I'm 35 00:03:05,759 --> 00:03:09,800 recommending to use in jaesas. Maybe someone wants to use different state management right 36 00:03:09,840 --> 00:03:14,520 instead, but still it will be considered that in my world, in my 37 00:03:14,639 --> 00:03:19,240 view as a progressive state management if you go from reactive services to any other 38 00:03:19,319 --> 00:03:30,759 state management solution, and what's reactive services? So you're asking all the questions 39 00:03:30,800 --> 00:03:37,159 just the long term ride. So that's the last one problem I want to 40 00:03:37,199 --> 00:03:43,960 answer. So the reactive services is the services implemented is eric jazz behavior subject. 41 00:03:43,960 --> 00:03:47,080 It's like a wrapper on top of a jazz behavior subject. Yep, 42 00:03:49,000 --> 00:03:54,840 that's all. There's all the basic concepts in my talk today. So the 43 00:03:55,319 --> 00:04:00,800 next logical step from reactive service or reactive services, if you only have one 44 00:04:00,840 --> 00:04:04,639 service I think apps probably in trouble, is to bring in like a state 45 00:04:04,680 --> 00:04:11,039 management solution such as mgxcess. Okay, now I have I have heard of 46 00:04:11,159 --> 00:04:18,319 NNGXSS, I have used NNGRX right, So what I suppose I should probably 47 00:04:18,360 --> 00:04:24,439 ask for the benefit of our day listener, what is what is state management 48 00:04:24,920 --> 00:04:28,319 beyond a reactive service? And then and then we'll come back to what I 49 00:04:28,360 --> 00:04:32,000 was going to say before. So state management is a solution to manage state 50 00:04:32,199 --> 00:04:38,480 of your single page in single page applications. So basically, you have some 51 00:04:38,560 --> 00:04:45,199 data flow, you have data which changed along the time user interaction with application, 52 00:04:45,959 --> 00:04:49,759 and so state management helps to manage this data. So manage the state 53 00:04:49,800 --> 00:04:55,279 of your application, as theres lots of bits to it, like different sort 54 00:04:55,319 --> 00:04:59,759 of data. I mean, even URL in a browser might be considered as 55 00:04:59,800 --> 00:05:03,040 a something that is part of your state, as a dart that you want 56 00:05:03,079 --> 00:05:08,079 to bring to your you were going to manage with the state management solution. 57 00:05:08,199 --> 00:05:13,199 But yeah, so basically it's again, So state management is a solution which 58 00:05:13,240 --> 00:05:19,160 helps you to manage data and data flow in your seeing Good Place application. 59 00:05:19,639 --> 00:05:25,120 Just the way how I see it, I think I'm marvelously concise. I've 60 00:05:25,160 --> 00:05:29,120 used mg and jr X on a couple of different projects, and the only 61 00:05:29,120 --> 00:05:31,839 thing I know about MGXS is that the logo really reminds me of the Sega 62 00:05:31,839 --> 00:05:35,439 logo, which I really enjoy about it, but that's all I know. 63 00:05:35,560 --> 00:05:41,959 Can you can you tell us what what is mg excess and what makes it 64 00:05:42,079 --> 00:05:46,680 what makes it stand out from because you could probably argue that mgr x is 65 00:05:46,720 --> 00:05:49,399 the one that most people have heard of in the community. I guess, 66 00:05:49,680 --> 00:05:55,000 So what what makes mgxcess stand out and what makes it different? So first 67 00:05:55,040 --> 00:06:00,759 of all, you know the creator of jecs is still McDonald mcdenna, so 68 00:06:00,839 --> 00:06:03,399 probably some of you know him. He's been released back in two thousand, 69 00:06:04,639 --> 00:06:15,519 a team in two years ago by Japanda all the time beyond angular air with 70 00:06:15,600 --> 00:06:20,480 me and you panned ahead, so very well known for that if if no 71 00:06:20,519 --> 00:06:25,000 one else got the reference, so it must be really hard to write code 72 00:06:25,000 --> 00:06:30,399 and a giant planned ahead hm also sweaty Yeah true. So the injeccess is 73 00:06:30,439 --> 00:06:35,399 a simple step management solution with a less boarded plate. It has things like 74 00:06:35,720 --> 00:06:42,480 depends the injection and declarators as a fast citizens So basically by using j access 75 00:06:42,560 --> 00:06:47,160 you using normal angular thinking or you're doing things in an angular way, which 76 00:06:47,199 --> 00:06:53,560 is most of which every Angler developers is familiar with. It has a life 77 00:06:53,879 --> 00:06:58,600 action life cycles, and it has a great community. So there is a 78 00:06:58,639 --> 00:07:01,959 select channel when where any one can join and ask questions on discuss edits. 79 00:07:02,480 --> 00:07:10,680 So yeah, but simplicity is probably the number one feature for injeccess. I 80 00:07:10,720 --> 00:07:15,040 know that a lot of people's issue with n g x is is how much 81 00:07:15,439 --> 00:07:18,399 time it takes to get off the ground and with all the boiler plate. 82 00:07:18,879 --> 00:07:24,759 I haven't actually used more recent versions of end X. I understand that they 83 00:07:24,800 --> 00:07:30,639 have attempted to address that. So excess just comes out of the box with 84 00:07:30,800 --> 00:07:33,120 less boiler plate. Yep. So how do you get all of your stuff 85 00:07:33,160 --> 00:07:39,120 set up? Then? Like presumably you still using like actions and reducers and 86 00:07:39,160 --> 00:07:43,160 selectors and things, or is it like a completely different way of thinking of 87 00:07:43,240 --> 00:07:47,439 things. Yeah, So you think about injecis as a secure as pattern. 88 00:07:48,160 --> 00:07:54,879 So you have your comments and curies, so comments actually actions and curious they 89 00:07:54,920 --> 00:08:00,519 are selectors. So there's two basic concepts in injeccess you can think about. 90 00:08:01,240 --> 00:08:05,720 And so it's pretty much like you dispatch an annection from a component and you've 91 00:08:05,720 --> 00:08:11,439 got your piece of courts with this action executive right, and you can listen 92 00:08:13,279 --> 00:08:18,519 for life cycles or yeah, it's pretty much combination. Yeah, I mean 93 00:08:18,639 --> 00:08:24,720 it's very similar, Like there's a way of doing things in jer X so 94 00:08:24,959 --> 00:08:30,160 despatch in the action and yeah, listening for events. Okay, I mean 95 00:08:30,480 --> 00:08:33,320 I have to say it sounds it actually sounds quite similar to what we use 96 00:08:33,360 --> 00:08:37,240 on the project where I work, which is it we use like a homegrown 97 00:08:37,440 --> 00:08:41,960 solution, but it is much much simpler than jer x in that you're basically 98 00:08:43,000 --> 00:08:46,960 we're literally just dispatching and then just subscribing in other places. It's it really 99 00:08:48,039 --> 00:08:52,240 is just what we use is just building on top of behavior subjects. Really 100 00:08:52,279 --> 00:08:56,320 but just in a in a more like formalized way. Is that is that 101 00:08:56,399 --> 00:09:01,120 what ng access kind of tries to do as well? Or if I messed 102 00:09:01,120 --> 00:09:05,960 the point, sorry, Like what do you so you're saying you using services 103 00:09:05,039 --> 00:09:11,240 in yeah, yeah, yeah, we're using services and so we are we 104 00:09:11,320 --> 00:09:18,960 are we have basically objects containing behavior subjects and then so we we dispatch off 105 00:09:18,000 --> 00:09:22,919 to place data off the place data inside of behavior subjects, and then elsewhere 106 00:09:22,960 --> 00:09:26,519 we've got things listening. So, as I say, it's a homegrown solution, 107 00:09:26,600 --> 00:09:30,120 but it works quite well. I just wondered if it's like this was 108 00:09:30,159 --> 00:09:33,320 similar to injects as well. It seems like you're talking about the reactive service 109 00:09:35,080 --> 00:09:39,720 in my Yeah, so okay, like reactive services of wrapp around up of 110 00:09:39,720 --> 00:09:43,679 behavior of subjects. Right, So I mean that's basically is just a stepped 111 00:09:43,759 --> 00:09:48,639 number zero or state management zero in my in my view, so yeah, 112 00:09:48,799 --> 00:09:54,480 and then next level is a stick management solution like in jixus so which is 113 00:09:54,519 --> 00:10:00,200 different from using behavioral subject Okay, I fall at your feet and apologies as 114 00:10:00,240 --> 00:10:05,399 for my huge slip up there, please go on tell us more. Yeah, 115 00:10:05,120 --> 00:10:11,720 so there is like there is very easy for beginners and for like people 116 00:10:11,799 --> 00:10:20,759 who just first comers to Angular to avoid a learning curve and be productive not 117 00:10:20,919 --> 00:10:28,320 in a day number I don't know then, just let's be productive on the 118 00:10:30,000 --> 00:10:39,960 two one is just working out the tour of heroes something like that. So 119 00:10:41,240 --> 00:10:46,279 would you say that it's not a bad idea to learn this first then they 120 00:10:46,279 --> 00:10:50,840 don't need to have an understanding of everything that is built into ERG access to 121 00:10:50,919 --> 00:10:56,919 jump in. It depends, like it's very depends what you're trying to achieve. 122 00:10:56,960 --> 00:10:58,639 If you just want to learn that, Yeah, like you can learn 123 00:10:58,679 --> 00:11:05,919 into like on day one two. But if you know what you're doing, 124 00:11:05,200 --> 00:11:09,720 maybe you don't want to learn state management at day one. You want to 125 00:11:09,840 --> 00:11:16,000 just understand how you can actually build a simple solution first and then its rate 126 00:11:16,399 --> 00:11:20,480 so closer to them take ten. Maybe on day ten you think, oh, 127 00:11:20,559 --> 00:11:24,440 yeah, actually I want to try. Maybe it makes sense to bring 128 00:11:24,600 --> 00:11:28,320 state management, but maybe it never comes. Maybe never one to print stand 129 00:11:28,399 --> 00:11:33,679 management because maybe there's no sense at all. Maybe a solution is quite simple, 130 00:11:33,120 --> 00:11:37,879 which maybe like yeah, oh a team you're working also there is it 131 00:11:37,919 --> 00:11:43,320 depends like what's your team size? If your team maybe like look, there 132 00:11:43,399 --> 00:11:46,840 is talking about state measurement. It's also that it's like also like a state 133 00:11:46,879 --> 00:11:54,600 measurements a court style. So maybe this particular steate measgement solution doesn't allow aligned 134 00:11:54,679 --> 00:12:00,759 with your team cold style like using as I said in jexcess heavily using like 135 00:12:00,879 --> 00:12:05,480 dependency injection and decorators. As some people said, hey, it's actually cool. 136 00:12:07,080 --> 00:12:09,360 I love it, and other people say, oh no, we don't 137 00:12:09,399 --> 00:12:18,320 own decorators. The creators are evil, so it seems very harsh on the 138 00:12:18,360 --> 00:12:26,480 Thatch writis, so yeah, I love the creators. Yeah, I like 139 00:12:26,519 --> 00:12:28,360 I like the fact that they look so simple and they do all sorts of 140 00:12:28,720 --> 00:12:31,960 mysterious things under the hood, and I don't have to worry too much about 141 00:12:33,039 --> 00:12:37,519 was going on, And like people who coming from dot net background to job 142 00:12:37,559 --> 00:12:41,440 background. I can talk about dot net because I've done lots of years in 143 00:12:41,480 --> 00:12:46,960 dot net in my early career, so it's all, well, there's decorators 144 00:12:46,960 --> 00:12:52,639 everywhere in net so and once I saw the creators, then you can actually 145 00:12:52,879 --> 00:12:56,799 write the creators in your front end code, like, oh, yeah, 146 00:12:58,440 --> 00:13:03,320 that's cool. I mean, that's if one of the things you see when 147 00:13:03,399 --> 00:13:07,240 learning angler so uses lots of decorators. But yeah, once you see a 148 00:13:07,279 --> 00:13:15,559 solution library which also have decorators, I mean, because I mean it's not 149 00:13:15,679 --> 00:13:20,159 like, oh, let's like why would why Some people like decorators because they 150 00:13:20,200 --> 00:13:26,759 make your code declare very declarative, and it's very easy to read. This 151 00:13:26,879 --> 00:13:31,679 sort of code you can tell I mean, if unless your decorators have proper 152 00:13:31,759 --> 00:13:35,720 naming convention, which is most of people probably following now these days. So 153 00:13:35,799 --> 00:13:41,679 if the creators actually self explanatory and by reading the name, you can tell 154 00:13:41,720 --> 00:13:45,960 what this decorator is about. This sort of code is very easy to read 155 00:13:46,080 --> 00:13:52,320 and to explain to other people. And if you if you like a team 156 00:13:52,320 --> 00:13:56,679 of developers and to tell a number, so if there is a newcomer to 157 00:13:56,720 --> 00:14:01,799 your project, it's very easy for people to understand this sort of code because 158 00:14:01,799 --> 00:14:07,919 they're just read like in plain English. So for example, the creator action 159 00:14:09,720 --> 00:14:16,559 action, it means it's election. So if you despise this action is something 160 00:14:16,639 --> 00:14:20,480 will happened. Yeah, it's good. Yeah, you're you're absolutely right, 161 00:14:20,639 --> 00:14:24,200 You're absolutely right, of course, right. I have a question. It 162 00:14:24,200 --> 00:14:26,879 comes with the story because I always like to tell stories. I've told this 163 00:14:26,879 --> 00:14:31,960 story before, so apologies to anyone listening who is bored of my repeat stories. 164 00:14:31,480 --> 00:14:35,440 Word on a project a couple of years ago, it was an Angular 165 00:14:35,440 --> 00:14:39,879 project and we had a new fellow joined the team and he had come from 166 00:14:39,919 --> 00:14:43,399 a React background. He had not used Angler before. He picked it up 167 00:14:43,440 --> 00:14:48,120 remarkably quickly. It was very impressive. But literally the first thing he did 168 00:14:48,480 --> 00:14:52,600 was he took a look at the app and went, where's my state management 169 00:14:52,600 --> 00:14:56,360 solution? And then immediately implemented one and tried to raise a pr for it 170 00:14:56,559 --> 00:15:01,840 and like our kick back on it. We don't Why did you do that? 171 00:15:01,879 --> 00:15:05,840 Because we don't. Because the whole point is the difference between Angler and 172 00:15:05,879 --> 00:15:09,200 React. There are many differences. One of the differences is that like Angular 173 00:15:09,519 --> 00:15:13,159 kind of handles your state for you in a different way, right, so 174 00:15:13,200 --> 00:15:18,000 we don't need to immediately put this state management solution in and yet people are 175 00:15:18,720 --> 00:15:24,559 obviously using state management in anger application. So why why do I want to 176 00:15:24,679 --> 00:15:28,320 use a state management solution above a reactive service in my Angler app? Because 177 00:15:28,440 --> 00:15:33,200 it does kind of handle stuff for me. So actually it's a good point 178 00:15:33,200 --> 00:15:37,639 about the React developers. And I used to like, we can go oh 179 00:15:37,720 --> 00:15:41,279 no, not months ago, I was googling. I was finding some solution 180 00:15:41,440 --> 00:15:48,639 for something. I can't remember what was that for some reason, was I 181 00:15:48,720 --> 00:15:54,159 converting something. I was converting some format into another format once format of data 182 00:15:54,159 --> 00:15:58,200 into another format of data. And found this project in direct project and just 183 00:15:58,200 --> 00:16:03,559 for curiosity bring it up. It's like one or two components up one and 184 00:16:03,919 --> 00:16:11,000 I saw in a source code there is like a state manasion. I was 185 00:16:11,159 --> 00:16:15,399 like, okay, I was, isn't it to say? I was laughing? 186 00:16:15,600 --> 00:16:18,960 Yeah, I mean I don't want to say that, but yeah, 187 00:16:18,000 --> 00:16:23,519 I was like okay, So yeah, why you don't like when you like 188 00:16:23,679 --> 00:16:30,679 in application? Right? Is different? Like not every person bringing state management 189 00:16:32,039 --> 00:16:37,200 right away? And to answer to your question, why so if someone okay, 190 00:16:37,240 --> 00:16:41,120 it's like in your in your new particular station, say you're working on 191 00:16:41,159 --> 00:16:45,480 the project a couple of people. Then you're bringing some new developer with his 192 00:16:45,600 --> 00:16:52,360 own opinions about state management. Maybe like he comes from rag the ground where 193 00:16:52,440 --> 00:16:56,840 they're using reducks very heavily, and yeah, so he may made a PR 194 00:16:56,960 --> 00:17:03,319 to your project and you open in the PR and realizing like okay, and 195 00:17:03,680 --> 00:17:07,440 why, like maybe you want to ask the developer why you want to do 196 00:17:07,519 --> 00:17:15,079 this, or maybe you have say you have guidelines about your project. But 197 00:17:15,200 --> 00:17:19,359 yeah, so why you want to print state management? It needs like you 198 00:17:19,400 --> 00:17:23,519 don't want just to print in stead management because oh, like I bring in 199 00:17:23,559 --> 00:17:26,559 state management to every project. That's the way to go, right. It's 200 00:17:26,599 --> 00:17:32,440 not it's not an excuse to bring a state management. First of all, 201 00:17:32,680 --> 00:17:37,079 it's state management. Like every every state management is different. So first of 202 00:17:37,119 --> 00:17:41,920 all, the state management you bring to your project should match the code style 203 00:17:41,960 --> 00:17:45,559 of your team. So everyone needs to be great that Hey, you will 204 00:17:45,640 --> 00:17:52,359 love this how you write in a code. We like how the code looks 205 00:17:52,400 --> 00:17:56,720 like when you're using this particular state management. That's probably the first thing you 206 00:17:56,759 --> 00:18:00,960 need to agree. Second thing, your solution needs to be not like you're 207 00:18:00,960 --> 00:18:04,559 probably right in a complete application, so we're not You can hear about like 208 00:18:04,599 --> 00:18:10,720 two maybe five components. Maybe we're talking like about pretty much meat. I 209 00:18:10,759 --> 00:18:15,119 see, I'd say meat cluss need to big, mid, size, up 210 00:18:15,160 --> 00:18:22,920 and high. So that's probably another consideration of state management. So if you 211 00:18:23,200 --> 00:18:29,400 like, say you want a consistency in you are because if it's a big 212 00:18:29,440 --> 00:18:33,200 application, or say you have a number of applications in your organization. So 213 00:18:33,279 --> 00:18:38,559 people come and go and another day you can see another person joining your team 214 00:18:38,799 --> 00:18:45,200 with his own opinions and start doing stuff in your project. But you want 215 00:18:45,559 --> 00:18:49,440 you don't want new people to invent the bicycle, right, I come to 216 00:18:49,519 --> 00:18:56,200 the bicycle later today. But so so you don't want people to enter these 217 00:18:56,240 --> 00:19:03,200 bicycles. And that's why state management helped you to keep since consistent consistence that's 218 00:19:03,200 --> 00:19:07,440 consistent in your in your organization. So you do have to explain people, 219 00:19:08,359 --> 00:19:14,440 spend time to explain people about those consistency. You just give them your wealth. 220 00:19:14,680 --> 00:19:18,920 Hey that's A and j EXA's they please read it then like that's what 221 00:19:18,960 --> 00:19:22,279 we're using. So and also you don't have to come up with your own 222 00:19:22,960 --> 00:19:27,119 guidelines because it's already there. Opposite to that you say you're using, I'm 223 00:19:27,119 --> 00:19:32,759 talking about the project. So you're using interactive services or wrappers on top of 224 00:19:32,799 --> 00:19:36,599 behavior subject so you need to make sure that people who comes to your project 225 00:19:36,880 --> 00:19:41,279 actually stay consistent so they write in typical code. So what you need to 226 00:19:41,279 --> 00:19:47,920 do you probably need to spend some time to create documentation maybe customer so you 227 00:19:47,960 --> 00:19:52,599 need to put people who work in on the commentation and also bring this docommentation 228 00:19:52,799 --> 00:19:57,279 up to date. So this kind of additional exercise and additional resources you need 229 00:19:57,319 --> 00:20:02,599 to dedicate for a project. I'm talking to here about big project. Right. 230 00:20:02,640 --> 00:20:07,920 If it's small products, maybe no one writes the communication. Oh it's 231 00:20:07,039 --> 00:20:11,640 like a long two people working on the same project, right, But yeah, 232 00:20:11,640 --> 00:20:15,119 if you're talking about big organization and lots of developers involved, you have 233 00:20:15,160 --> 00:20:21,599 to have something where people can go and read. Otherwise you end up with 234 00:20:22,319 --> 00:20:27,480 having like prs like you. Like you mentioned, it's actually very interesting. 235 00:20:27,680 --> 00:20:32,000 It hasn't even occurred to me that one of the reasons why you might want 236 00:20:32,039 --> 00:20:36,880 to choose a state management solution is just just to make sure that everyone is 237 00:20:36,920 --> 00:20:41,119 doing things the same. That is interesting and uh, and you I'm thinking, 238 00:20:41,119 --> 00:20:45,000 I'm listening to what you're saying and thinking, oh, yeah, the 239 00:20:45,079 --> 00:20:48,440 thing that I work on some docs for how we actually do stuff would have 240 00:20:48,480 --> 00:20:52,440 been amazingly useful when I started. And then I'm also thinking, well, 241 00:20:52,640 --> 00:20:56,160 hope someone else has a chance to write those because I don't have time that 242 00:20:56,640 --> 00:21:02,680 is problem. So yeah, basically I guess this was the answer to your 243 00:21:02,759 --> 00:21:07,880 question in regards like why when you need to bring the state management. It 244 00:21:07,920 --> 00:21:11,960 was a great answer to my question. That's probably the best answer that I 245 00:21:11,000 --> 00:21:15,279 could possibly vote for, because I didn't even it didn't even occur to me 246 00:21:15,359 --> 00:21:18,799 that the answer might have been that. So I enjoyed it. Thank you. 247 00:21:18,839 --> 00:21:25,079 Cool so speaking about the reactive services by we here our subject and stuff 248 00:21:25,119 --> 00:21:30,200 like that. So I saw a picture of a cat go back. It's 249 00:21:30,240 --> 00:21:37,200 like a kid who controls the scenes. As you can see for everyone listening, 250 00:21:37,599 --> 00:21:41,960 Alexi is kindly providing us with a slide show for today's episode. And 251 00:21:41,880 --> 00:21:48,920 I am mesmerized at the moment by a cat sitting in a cafe looking like 252 00:21:48,000 --> 00:21:52,880 he gives zero fluffs. Very good, good. I wonder what you're going 253 00:21:52,920 --> 00:21:56,559 to say there for a second. I mean to be honest, isn't that 254 00:21:56,720 --> 00:21:59,599 just cats? I know my cat, My cat would do that, except 255 00:21:59,599 --> 00:22:02,200 people, I would say, smash the cup of coffee on the floor, 256 00:22:03,079 --> 00:22:08,480 who have like knowledgeable I've never really hung out with one. Yeah, cat 257 00:22:08,519 --> 00:22:14,319 looks like it's got attitude. So yeah, that's exactly the kind of cat. 258 00:22:14,519 --> 00:22:19,920 And the title of this light is elective Services, which helps you to 259 00:22:21,319 --> 00:22:26,240 solve component communication data flow in your application in quite elegant and simple way with 260 00:22:26,400 --> 00:22:33,039 our additional layer of complexity. So that's basically this attitude, this kettateitude, 261 00:22:33,119 --> 00:22:40,680 this kind of tells this sort of love it. I love it because I 262 00:22:40,720 --> 00:22:45,200 have this other slide like that. Oops, going back of this one, 263 00:22:45,720 --> 00:22:48,920 there's an opposite to this slide. I just feel stressed looking at that. 264 00:22:49,440 --> 00:22:56,119 I've been on projects like that. Yeah, so and yeah, at some 265 00:22:56,279 --> 00:22:59,960 point I thought like, hey, girl, do you really want to expose 266 00:23:00,079 --> 00:23:04,920 behavior subject into your component, into your services? So one don't again, 267 00:23:06,000 --> 00:23:11,599 like I like this idea of consistency and so he can you do something like 268 00:23:11,920 --> 00:23:21,480 to keep since consistent with behavior but not but by not using behavior subjects explicitly. 269 00:23:22,519 --> 00:23:27,319 And I create this library called eric service. So basically it's like state 270 00:23:27,359 --> 00:23:34,559 management zero so for lazy people. So basically it contains this upstore class with 271 00:23:34,640 --> 00:23:38,559 a number of methods, so which allows you to set the fault value, 272 00:23:38,920 --> 00:23:42,920 set new value, get current value, and subscribe to the current value. 273 00:23:44,240 --> 00:23:48,119 And so this way your code, your services code becomes a little bit simpler 274 00:23:48,519 --> 00:23:52,839 and more readable. So all but yeah, you don't have to use it. 275 00:23:53,039 --> 00:23:59,920 I have this if you want, I can quickly show you what I'm 276 00:24:00,000 --> 00:24:06,400 looking about here. So that's the normal behavior subject service is. You can 277 00:24:06,400 --> 00:24:11,359 see you can basically I'm defining a the hearoor subject and like basically using explicitly 278 00:24:11,400 --> 00:24:15,000 in this particular case. So I'm calling the next to set a new new 279 00:24:15,000 --> 00:24:19,799 piece of data. But this ERIC service it's looking a bit differently, So 280 00:24:19,839 --> 00:24:25,000 there is no behavior subject in my service. I'm just extended ERIC service. 281 00:24:25,440 --> 00:24:29,720 And what I do I just use functions set state in this particular case, 282 00:24:29,839 --> 00:24:32,680 right, so just to set a stage. So the code becomes a little 283 00:24:32,680 --> 00:24:37,640 bit less borely plaiting and more readable using this approach. In my world, 284 00:24:37,079 --> 00:24:44,519 maybe someone can say, yeah, I actually like like use behavior subjects implicitly. 285 00:24:45,279 --> 00:24:48,200 That's fine, that's fine, But yeah, I don't like behavior subjects 286 00:24:48,960 --> 00:24:52,319 in general. I think it can lead to a lot of spaghetti out. 287 00:24:52,559 --> 00:24:56,319 But I think I've been on projects that have used them so like you're passing 288 00:24:56,359 --> 00:25:03,359 them into components and and input and then updating the values that way and yep, 289 00:25:03,640 --> 00:25:08,000 great, you get it. And I think spaghetti will gets if you 290 00:25:08,480 --> 00:25:12,640 on the long running project. So it's not going it's not happening on day 291 00:25:12,799 --> 00:25:18,599 one, maybe on then they on day seven. See what I mean. 292 00:25:22,880 --> 00:25:27,319 You need a couple of iterations basically to get spaghetti the beaper subjects. It's 293 00:25:27,359 --> 00:25:34,480 true. So and in this particular use case, like do you see that 294 00:25:34,720 --> 00:25:38,920 state management might solve the problem if you replace the behavior subject to state management 295 00:25:38,920 --> 00:25:44,119 solution in the project that you mentioned? Oh the yeah, yes, state 296 00:25:44,160 --> 00:25:48,119 management would have helped a lot. I tried to suggest that, but I've 297 00:25:48,119 --> 00:25:52,640 also been on a project with NIXSS. We actually started with n g R 298 00:25:53,559 --> 00:25:59,039 and then people complained that that was too much, it would play They basically 299 00:25:59,400 --> 00:26:02,359 it was a larger team. The team didn't use it right. We kept 300 00:26:02,359 --> 00:26:04,599 on saying, you know, stop calling directly with service, don't switch to 301 00:26:06,240 --> 00:26:11,880 I actually did the implementation of switching it to ng excess and it was it 302 00:26:11,920 --> 00:26:15,680 was a lot smoother. We got people to buy into, other developers to 303 00:26:15,680 --> 00:26:18,279 buy in and start using it everywhere, which was awesome. I really like 304 00:26:18,720 --> 00:26:25,720 NG Access. There's also the cl I is super helpful when you, you 305 00:26:25,759 --> 00:26:30,039 know, get things going, the n G Excess c l I and there's 306 00:26:30,119 --> 00:26:37,640 a offline plug in but I've also used and that's really really cool because that 307 00:26:37,720 --> 00:26:41,359 comes it's kind of magical, and the form's plug in as well is really 308 00:26:41,400 --> 00:26:49,400 magical. I'm not sure how like NG Excess Labs or yeah add on, 309 00:26:51,519 --> 00:26:55,200 Yeah, like plugs, I'll put them in the chat for anyone who wants 310 00:26:55,240 --> 00:27:00,359 to. I also I am including in the show notes a linked to the 311 00:27:00,400 --> 00:27:04,359 episode that we did with Lexi on Angular Air because sometimes, I mean he 312 00:27:04,440 --> 00:27:10,480 blew my mind with the uh what is it is? It called the plug 313 00:27:10,519 --> 00:27:15,279 in with the RX service that you wrote, Oh yeah, and showing the 314 00:27:15,319 --> 00:27:18,720 difference between the code like before and after. It was like absolute magic. 315 00:27:18,799 --> 00:27:22,240 So for the visual learner who wants to see that, definitely check out that 316 00:27:22,920 --> 00:27:29,400 recording because I think sometimes you just have to see the code. So I 317 00:27:29,400 --> 00:27:34,440 want to give you props for that because I really really really enjoyed that episode. 318 00:27:36,920 --> 00:27:40,279 If you if you're going to promote your other podcast, I think you 319 00:27:40,400 --> 00:27:44,039 need to make sure that the next time you do Angular Air, you point 320 00:27:44,359 --> 00:27:48,759 we want to shout out too. I have something snickitty boys on the bud 321 00:27:48,839 --> 00:27:56,920 guest today. Oh you guys know you're my favorite? I mean what now 322 00:27:56,119 --> 00:28:03,880 we don't tell the others. Yeah, well Angular Air we are his favorite. 323 00:28:04,200 --> 00:28:10,559 Yeah, I imagine they'll hear it when this episode comes out, because 324 00:28:11,119 --> 00:28:17,359 yeah, absolutely So question now as that you are a part of You said, 325 00:28:17,400 --> 00:28:22,680 you're now a new member of the Ndixcess team. So can we anticipate 326 00:28:22,119 --> 00:28:26,839 the RX service that you wrote all of that functionality to just now be bundled 327 00:28:26,880 --> 00:28:33,319 in default behavior of ANGI excess. We did not, I mean we didn't. 328 00:28:33,640 --> 00:28:37,440 I don't think there is a need and it might create a little bit 329 00:28:37,519 --> 00:28:44,960 of yeah, exactly exactly because it's kind of different scene. I just love 330 00:28:45,039 --> 00:28:48,359 it so much and I'm like, it needs to be just how things work. 331 00:28:48,599 --> 00:28:53,640 Just maybe it's possible, but it needs to be discussed and it needs 332 00:28:53,680 --> 00:29:00,359 to be sold about it. But I don't know how and why needs to 333 00:29:00,400 --> 00:29:03,640 be there. Yeah, but yeah, it's might big good idea. Yeah, 334 00:29:04,599 --> 00:29:08,000 like if you want to use the full functionality, just use this little 335 00:29:08,000 --> 00:29:11,720 bit and then if you ready, just use everything else. Yeah, just 336 00:29:11,720 --> 00:29:18,720 call it NG excess light or diet yeah, Brooks, you are a new 337 00:29:18,759 --> 00:29:27,000 marketing manager, right, I was thinking about it and I bring this to 338 00:29:27,119 --> 00:29:33,240 the team. Just rise all right, Well, don't even mention it straight 339 00:29:33,279 --> 00:29:41,039 in time. Well that's what was the process to join the project? I 340 00:29:41,039 --> 00:29:44,039 mean, I assume you made some prs and I liked them and reached out 341 00:29:44,039 --> 00:29:47,559 to you. How did that work? Just curious? Yeah, like it's 342 00:29:47,559 --> 00:29:51,160 dependents like, well, I guess what how did it happen for you? 343 00:29:51,599 --> 00:29:55,640 I guess it's yeah, I used to be a part of the I joined 344 00:29:55,680 --> 00:30:00,160 the slack for quite a while and I done a couple of demos way back, 345 00:30:00,680 --> 00:30:04,720 a couple of proposals. There is actually a proposal which is still active 346 00:30:04,799 --> 00:30:08,559 and we're working on that. We just started working on that maybe months ago. 347 00:30:08,759 --> 00:30:12,519 But the proposal is maybe two years old, maybe one year or at 348 00:30:12,599 --> 00:30:18,000 least one year. It's actually two. It's about syschematic things because right now 349 00:30:18,200 --> 00:30:23,279 schematics is a separate package for NG excess, which is a bit weird. 350 00:30:23,640 --> 00:30:29,519 Usually you chematics lives and the same package. So if you want to install 351 00:30:30,000 --> 00:30:36,519 any package, you do ERGI with English right, Energie add package name right, 352 00:30:36,559 --> 00:30:41,400 and this will execute schematics and stuff like that and then you can actually 353 00:30:41,480 --> 00:30:45,240 if you want, you can use these chematics, like say you want to 354 00:30:45,279 --> 00:30:48,720 create an action or you want to create a selector, you say, just 355 00:30:48,759 --> 00:30:52,519 go a G like whatever action name or something like that, and you can 356 00:30:52,640 --> 00:30:57,880 it can scaffold the action for you. But in ang access, it's historically 357 00:30:59,240 --> 00:31:03,480 it's like a pre package, which probably not everyone knows about it, and 358 00:31:03,400 --> 00:31:08,519 it's kind of a little bit outdated. So currently be working on this story 359 00:31:08,880 --> 00:31:15,720 to make schematics works better for in JAXSAS and to be a part of main 360 00:31:15,759 --> 00:31:22,759 package which is at jecas, and then every plug in will have schematics in 361 00:31:22,799 --> 00:31:29,359 it. So you would install plugging just by saying NG at plugging name, 362 00:31:29,599 --> 00:31:34,279 and it will bring the plug in into your project and you'll do anything else 363 00:31:34,559 --> 00:31:41,880 needed to actually, so to minimize your development effort. So yeah, you 364 00:31:41,920 --> 00:31:45,559 need to be a little bit active. It's just a normal open source project. 365 00:31:45,920 --> 00:31:49,559 So like basically if you a little detective and you show your interest, 366 00:31:49,680 --> 00:31:55,680 which I just was, you know, I like JECSAS from first day I 367 00:31:55,680 --> 00:32:00,519 saw it. I remember this tweet fasting back in time. Actually was using 368 00:32:00,880 --> 00:32:06,079 n j X in my in this like two years ago. Yeah, at 369 00:32:06,079 --> 00:32:09,359 this project and then once I saw NJXS, I said, oh, yeah, 370 00:32:09,400 --> 00:32:15,920 it's exactly what I want so and signs signs then JXS is my favorite 371 00:32:15,000 --> 00:32:20,319 state management solution. I recommended everyone, and I yeah, been a part 372 00:32:20,359 --> 00:32:22,720 of the community for quite a while. And yeah, and some at some 373 00:32:22,799 --> 00:32:27,599 point on the slack I was asking, hey, like they want to join 374 00:32:28,160 --> 00:32:31,279 projects. I was like surprised they didn't expell that, and yeah, I 375 00:32:31,319 --> 00:32:36,799 had the conversation with Mark, he's a lead and yeah, signs then, 376 00:32:36,920 --> 00:32:39,680 like it's been like maybe two months ago, I think, so, Yeah, 377 00:32:39,960 --> 00:32:44,799 pretty happy to be part of it. So we have lots of things 378 00:32:44,880 --> 00:32:47,599 in the list, and yeah, we just want to make JCCESS is the 379 00:32:47,599 --> 00:32:53,880 best solution, the best state manajorment solution for ANGELA applications as our goal. 380 00:32:54,880 --> 00:32:58,200 Yeah, that's awesome. That's cool. I mean, like I said, 381 00:32:58,240 --> 00:33:01,440 I will go in gss N g r X project right now. I miss 382 00:33:01,480 --> 00:33:06,400 it, but yeah, very cool. And you from your perspective, like 383 00:33:06,480 --> 00:33:12,319 do you see like you like what do you see by working on JACCESS projects 384 00:33:12,599 --> 00:33:15,279 versus and jer X, Like what do you like or what you don't like? 385 00:33:15,519 --> 00:33:19,400 Is there any instance in juccess might be you don't like you want to 386 00:33:19,480 --> 00:33:25,839 be different. It's it's NGXS came a lot quicker and easier to me to 387 00:33:25,880 --> 00:33:30,559 pick up on and that's probably you know, less boiler plate, et cetera. 388 00:33:31,079 --> 00:33:36,720 The other thing that NXSS does, the documentation is really great. Like 389 00:33:36,799 --> 00:33:39,079 I I that's probably what helped me pick it up so quick. Was like 390 00:33:39,759 --> 00:33:43,839 going through the docks. It was like I went through them and all of 391 00:33:43,880 --> 00:33:45,759 a sudden, I was I was done, you know, I just dived 392 00:33:45,839 --> 00:33:50,559 right in and certain implementing it. And g RX has not been that smooth 393 00:33:50,920 --> 00:33:54,680 for me, but I'll get there. It's just time. So is that 394 00:33:54,720 --> 00:34:00,359 like with with your prior experience of using nj X that you like find nj 395 00:34:00,400 --> 00:34:07,200 excess docks helped. Was it easier because you'd been using a different state management 396 00:34:07,200 --> 00:34:09,440 solution or was it the like, no, I hadn't used this, Yeah, 397 00:34:09,480 --> 00:34:14,360 yeah, so I hadn't used the state management solution before then I used. 398 00:34:20,239 --> 00:34:23,840 Yeah. One thing I said about njr X is it it took me 399 00:34:24,960 --> 00:34:30,679 so long to get my head around it, Like just I did a course 400 00:34:30,480 --> 00:34:35,280 Todd Motto has on his Ultimate Courses platform. He has an ngr X course 401 00:34:35,360 --> 00:34:37,280 which is like seven and a half hours long. I'd done it twice. 402 00:34:38,320 --> 00:34:42,000 It's a great course, right, it was really good and it got me 403 00:34:42,079 --> 00:34:45,440 there, but it just just absolutely no concept really at the beginning of what 404 00:34:45,519 --> 00:34:49,760 on earth was going on? So super complex. So I really like the 405 00:34:49,800 --> 00:34:52,039 sound of one that is actually just you can literally just read the docs and 406 00:34:52,079 --> 00:34:57,719 know what's going on there. That's lovely. Yeah, in particular, there's 407 00:34:58,719 --> 00:35:02,599 I was looking at. I was going through the ng RX docs and there's 408 00:35:02,639 --> 00:35:06,639 some there's it. I'm pulling it up and I'm going to run in the 409 00:35:06,639 --> 00:35:12,639 show notes. This one right here, there's a diagram that really is simple 410 00:35:13,440 --> 00:35:16,480 and explains like basically the whole thing. I kept on referring back to this 411 00:35:17,000 --> 00:35:22,239 going through it and how it works. It's in the intro this this show, 412 00:35:22,440 --> 00:35:25,840 This podcast has been very visual for I know, I just brought up 413 00:35:25,840 --> 00:35:32,760 a diagram. Quick, someone describe this chart with a bunch of circles with 414 00:35:34,000 --> 00:35:37,320 arrows. Well, that part of it is, there's only three circles, 415 00:35:37,400 --> 00:35:43,480 right, and then your component your component, right, and so the component 416 00:35:43,760 --> 00:35:47,920 dispatches an action to the store and that updates the component again and that's kind 417 00:35:47,920 --> 00:35:52,679 of a loop. And the action also talks to the back end and if 418 00:35:52,719 --> 00:35:54,920 you have any plug in set as well. It's a very simplified. But 419 00:35:55,199 --> 00:36:00,800 that's kind of how it ends up working. No side des No is that 420 00:36:00,920 --> 00:36:04,760 good? Is that? Is that something you want? Is that? Is 421 00:36:04,760 --> 00:36:07,320 that a goal? You mean the goal? What do you mean by goal? 422 00:36:07,639 --> 00:36:12,320 Yeah? I mean perhaps the poor choice of words for me again going 423 00:36:12,360 --> 00:36:17,039 back to the complexity even r X, like the effects was just this whole 424 00:36:17,079 --> 00:36:21,880 other thing like that you have to learn. But I say, you say 425 00:36:21,920 --> 00:36:23,920 that we've got no side effects? So is that is that what you want? 426 00:36:24,000 --> 00:36:28,320 You want to go with a with an effectless state management? Yeah, 427 00:36:28,320 --> 00:36:34,840 it's like less complex or less concepts is a simpler the solution and the easier 428 00:36:34,840 --> 00:36:39,639 you can pick it up scripts already mentioned. So in j's quite simple because 429 00:36:39,679 --> 00:36:44,800 it has less a trust, it has less concepts you need. And it 430 00:36:44,880 --> 00:36:52,760 was the goal of Austin actually to make a solution stick measurement solution, which 431 00:36:52,800 --> 00:37:00,360 is simple. It was like he kind of saw that about injury is quite 432 00:37:00,360 --> 00:37:09,920 complex and what can I do in order to use the beauty of all these 433 00:37:10,119 --> 00:37:22,880 wonderful ideas like reduxy and security together to actually like to have estate management for 434 00:37:22,960 --> 00:37:29,920 my application? So without having all those spending all those time and learning neat 435 00:37:30,039 --> 00:37:35,960 and implementing because effects, it can go really really crazy sometimes. Yeah, 436 00:37:37,480 --> 00:37:40,920 I have seen that. Okay, that's interesting that how do you how do 437 00:37:42,000 --> 00:37:45,400 you handle because the whole point of the of the effect part of nger X 438 00:37:45,920 --> 00:37:51,760 is that as you are, as you're flowing through your you know, your 439 00:37:51,800 --> 00:37:58,159 action action reducer cycle. The point is is that, like you, you 440 00:37:58,239 --> 00:38:01,239 use the effect right to sort of off to the side and do something asynchronously 441 00:38:01,960 --> 00:38:07,519 while your cycle continues going around. So is it just literally that you just 442 00:38:07,559 --> 00:38:09,840 don't do that with mgxs, You just you have to stick inside of this 443 00:38:09,920 --> 00:38:13,880 cycle? Is that? Is that how it works? If you want, 444 00:38:14,079 --> 00:38:16,599 you can do something like that, but it's something not in the docks, 445 00:38:16,639 --> 00:38:23,400 I guess. So maybe for people who is en and Geric's big ground, 446 00:38:23,519 --> 00:38:29,199 they see, you know, once you get your head around it, you 447 00:38:29,280 --> 00:38:32,119 continue in sinking the bosset managements this way, and when you come to ng 448 00:38:32,280 --> 00:38:37,039 excess land you still want something like that. So you can do something like 449 00:38:37,079 --> 00:38:42,440 that if you want. I haven't done it in g excess because like for 450 00:38:42,519 --> 00:38:45,239 me, it's not necessary. But if you still sink it, you can 451 00:38:45,400 --> 00:38:49,199 do something like that. Yeah, that's cool. We're talking about belligerent developers 452 00:38:49,440 --> 00:38:52,639 who don't like to change. Now, that's fine. I mean, as 453 00:38:52,639 --> 00:38:55,519 I said, I find the effects to be quite just another added layer of 454 00:38:55,559 --> 00:39:00,760 complexity. I was just I was just interested in how how how you get 455 00:39:00,800 --> 00:39:02,400 on without them? But it sounds like you get on absolutely fine, So 456 00:39:02,480 --> 00:39:06,199 that's good. I have to say, like, just as the longer this 457 00:39:06,239 --> 00:39:09,480 episode goes on, the more I'm thinking that MGXSS just seems like something that 458 00:39:09,519 --> 00:39:13,880 I would like to try next time. Next time I'm in a position to 459 00:39:14,280 --> 00:39:16,440 use, you know, a state management solution, because that all I'm hearing 460 00:39:16,519 --> 00:39:21,840 is that it basically it's the same sort of thing you get with an njr 461 00:39:22,039 --> 00:39:25,000 X, but it is much simpler and much more pleasant to use. And 462 00:39:25,039 --> 00:39:29,559 I say, you know, by the time I'd used mgr X a bunch, 463 00:39:30,039 --> 00:39:31,960 like I get it now and it's fine, and I kind of like 464 00:39:32,000 --> 00:39:35,840 it, and I'm not too fussed by the boiler plate. But I'm never 465 00:39:35,880 --> 00:39:40,000 going to turn down something simpler because I like simplicity the more. And also 466 00:39:40,480 --> 00:39:46,599 I like you's saying like Injucess, it's like do more is less? I'd 467 00:39:46,599 --> 00:39:51,679 see, Yeah, is that is that the official catchphrase of the of the 468 00:39:51,679 --> 00:39:55,400 library. Not really, but yeah it might be. Yeah, I'll raise 469 00:39:55,440 --> 00:40:01,920 a pr to get it on the website. H Also, there is a 470 00:40:01,960 --> 00:40:07,239 thing called NGI Excess Labs. It's kind of a playground. It's a separate 471 00:40:08,239 --> 00:40:14,400 on it up that exists to test the new and prototype new ideas and puts 472 00:40:14,519 --> 00:40:20,519 for concepts, and that potentially may become a part of Jexa's core functionality. 473 00:40:21,079 --> 00:40:24,559 And there is lots of stuff in it, like and most of some of 474 00:40:24,599 --> 00:40:29,880 that it's actually production ready, so so like some of this is bulletproof, 475 00:40:30,199 --> 00:40:36,000 like for example, I know people using Jex's data plugging on the production and 476 00:40:36,559 --> 00:40:43,039 plugging for fire Base plugging as well. So if you want and a couple 477 00:40:43,039 --> 00:40:47,320 of things about in Jexa's data, it's actually like the same idea even less 478 00:40:47,400 --> 00:40:53,280 boil applies. So if you thought less boil apply was good, wait until 479 00:40:53,320 --> 00:41:00,760 you try even less boilerpl Yes, that's basically a DA here. It's like 480 00:41:00,880 --> 00:41:06,639 addition. Basically it's a plug and you installed on top of injects and you 481 00:41:06,679 --> 00:41:12,079 can use the benefits of this plug in. So you're not writing actions, 482 00:41:12,239 --> 00:41:15,639 you're not writing selectors. You just have your state. Okay, let me, 483 00:41:16,559 --> 00:41:24,559 are you right in anything unfortunately at phonage that yes, So that's the 484 00:41:24,639 --> 00:41:30,880 state I plementation just injeccess store implement normal implementation. So you have in normal 485 00:41:30,920 --> 00:41:36,119 implementation you have a state file. You have you might have separate file for 486 00:41:36,239 --> 00:41:40,840 selectors, and you have separate file for actions. But with injects data you 487 00:41:40,960 --> 00:41:49,320 have just one single file. Wow, what and how you consume that? 488 00:41:49,480 --> 00:41:55,440 So with the in normal energy access you consume your state like in components, 489 00:41:55,559 --> 00:42:00,039 you inject the store and you you might want to select that. So you 490 00:42:00,119 --> 00:42:06,360 using selectors and dispatching actions. That's a couple of lines, but with inject's 491 00:42:06,440 --> 00:42:09,679 data it's just a little bit different. There is that's all you need. 492 00:42:09,840 --> 00:42:14,239 You've got You've got literally nothing in that company. Yes, it's just exact 493 00:42:14,360 --> 00:42:19,719 injecting the state and that's all. And then that's crazy. And the template 494 00:42:19,800 --> 00:42:24,119 plot the template plots so basically on a template in a normal way. So 495 00:42:24,360 --> 00:42:29,880 you yeah, you have something in your component, like some functions in your 496 00:42:29,920 --> 00:42:35,599 component you want to call them, but in any dispatch in the action if 497 00:42:35,599 --> 00:42:39,159 you want to, if you want to mutate state. But here in inject's 498 00:42:39,280 --> 00:42:47,599 data you're referring directly to state, so you know, dispatching the action instead 499 00:42:47,679 --> 00:42:53,400 you just you just call the function directing the difference. How you literally just 500 00:42:53,440 --> 00:43:00,400 removed the dispatch you just yeah, Yeah, that's probably more closer to services, 501 00:43:00,519 --> 00:43:05,039 like the normal way of using services. Yeah, pretty neat. Is 502 00:43:05,079 --> 00:43:08,360 that your is that your projectors? Is that? Actually it's the also of 503 00:43:08,400 --> 00:43:14,280 this project is maxive enough And if anyone have any questions about this project or 504 00:43:14,480 --> 00:43:17,519 and it's not related to injeccess, you can join the select channel. It's 505 00:43:17,559 --> 00:43:23,079 a fictional channel, like there's like thousands of developers there and yeah, to 506 00:43:23,159 --> 00:43:29,760 discuss anything, to answer or plusk questions. So if something like this in 507 00:43:29,880 --> 00:43:34,440 g access data is in labs, does that mean it might one day be 508 00:43:34,880 --> 00:43:38,960 full time in ng access or will always live in under lads book. I 509 00:43:39,000 --> 00:43:45,079 think there was the discussions about that, and it's a little bit different approach. 510 00:43:45,920 --> 00:43:47,880 It's like you remember at least you said, like why don't you bring 511 00:43:47,960 --> 00:43:52,199 e rec service into ng in jexcess, it's kind of similar idea, like 512 00:43:52,760 --> 00:43:57,760 yeah, like it's just it's for now, it's as a part of labs, 513 00:43:57,840 --> 00:44:00,000 but yeah, who knows my in the future, Like you know, 514 00:44:00,159 --> 00:44:06,119 in ng REX there is a data like in data extension or whatever you call 515 00:44:06,159 --> 00:44:09,800 it, right, I think it's something similar in injury on anng X lent 516 00:44:10,239 --> 00:44:17,639 the ang X data and it leaves in angie rex repository. But it's a 517 00:44:17,679 --> 00:44:23,880 little bit different way of you of using ng rex right, And so some 518 00:44:23,920 --> 00:44:29,840 people choosing data to go and then they cut looks a little bit different. 519 00:44:30,440 --> 00:44:32,119 Or some people say no, we don't want to use it, and they're 520 00:44:32,159 --> 00:44:36,199 caught looking a little different. Right, Is it is the right way of 521 00:44:36,239 --> 00:44:39,280 saying that in anngr X lent or not. I'm not sure, but yeah, 522 00:44:39,440 --> 00:44:44,199 that's how it is in ngxcess because as you can see, your costyle 523 00:44:44,400 --> 00:44:49,119 change a lot very drastically. Yes, yeah, I can see that your 524 00:44:49,679 --> 00:44:53,199 your project in the open thing is called from services to ngxs. Is this 525 00:44:53,480 --> 00:44:57,599 is this part of the tutorial that you have and is this something that we 526 00:44:57,639 --> 00:45:00,519 can we can get out of it? Just a small snapshot that I'm looking 527 00:45:00,559 --> 00:45:06,440 at. I feel I feel sad for the folks listening who have no idea 528 00:45:06,480 --> 00:45:10,159 what we're just sort of staring open mouth that probably really frustrated, to be 529 00:45:10,239 --> 00:45:16,440 honest. Yes, the elephant in the room there, British if they're still 530 00:45:16,519 --> 00:45:22,280 listening. Everyone's everyone's still hanging on to here what your picks are this week, 531 00:45:22,320 --> 00:45:25,199 Brooks, they're worry I got a good one, A good one to 532 00:45:29,239 --> 00:45:34,639 But yeah, that's exactly the project is about. It's just like a tutorial. 533 00:45:35,320 --> 00:45:38,079 It's so it's a project on the top. So it's a public project 534 00:45:38,440 --> 00:45:44,719 and yeah, so here it's demonstratings away how are you going from here a 535 00:45:44,800 --> 00:45:50,880 sublic services erected services to intinexcess and then how actually to go for intexcess to 536 00:45:51,320 --> 00:45:54,880 anti excess data. So there is three three things. Maybe please have a 537 00:45:54,920 --> 00:46:00,800 link to your to the th REEPO in the in their notes because for the 538 00:46:00,840 --> 00:46:04,719 folks, for the for the one listener who is still hanging on because they 539 00:46:04,760 --> 00:46:07,239 want to hear Brokes Peck, go and check this out because what we're looking 540 00:46:07,280 --> 00:46:12,599 at looks it looks pretty pretty good. I also want to go to see 541 00:46:12,599 --> 00:46:16,360 it. Yeah, So basically that's that's in jeccess. If you have any 542 00:46:16,360 --> 00:46:22,320 more questions, maybe I missed something. We're working on releasing a new version. 543 00:46:22,039 --> 00:46:27,480 It's official, like the new version soon. But after this version, 544 00:46:27,880 --> 00:46:31,480 it's going to be another version which is probably breaking change version maybe not really 545 00:46:31,519 --> 00:46:36,000 but yeah, at another major versions on the next version is not major version, 546 00:46:36,039 --> 00:46:39,519 but at some point this year, thee next couple of months, we 547 00:46:39,559 --> 00:46:45,920 will release a new major version with features. What's the biggest feature that you're 548 00:46:46,239 --> 00:46:50,159 coming out in a new major version? So, first of all, it 549 00:46:50,360 --> 00:46:57,519 is schematics as first of all. Then we want to I mean there is 550 00:46:57,559 --> 00:47:01,360 not like there is sorts of good a polish going on and maybe if we 551 00:47:01,519 --> 00:47:06,840 want to use yeah, I can't, I can't. I can't tell you, 552 00:47:06,920 --> 00:47:10,400 like what the feature is going to be because as the new the new 553 00:47:10,440 --> 00:47:15,559 merger major version, it hasn't been finalized the list of things, and we 554 00:47:15,639 --> 00:47:21,800 want to pad you down. I want I want to that. Okay, 555 00:47:21,880 --> 00:47:30,119 it's going to be the better version of the current version, even even less 556 00:47:30,199 --> 00:47:36,400 boiler play. Yeah, that's not official. Don't don't say me if if 557 00:47:36,400 --> 00:47:39,519 there's more boiler plays than you're expecting. Yeah, like also like bulletplate is 558 00:47:39,559 --> 00:47:44,760 something new type right, and if there's something which can generate code for you, 559 00:47:45,119 --> 00:47:47,599 can you consider this less boilerplate? Yeah? Yeah, I think so, 560 00:47:47,800 --> 00:47:55,320 Yeah, I think so. Yes, A schematics yeah rightol prediction prediction 561 00:47:55,480 --> 00:48:02,320 mat yeah so yeah, what else? Yeah, we're being another episode. 562 00:48:02,639 --> 00:48:12,119 I can tell you all if you just do we do we want to do 563 00:48:12,199 --> 00:48:15,599 some pic. This is this is what everyone's been waiting for. No, 564 00:48:15,800 --> 00:48:19,440 actually that I do. I do a massive disservice because that was I just 565 00:48:19,519 --> 00:48:23,440 I've just digested a vast quantity of new knowledge there. So thank thank you 566 00:48:23,480 --> 00:48:29,000 Alexing for that. It was super super interesting and I feel like there's so 567 00:48:29,119 --> 00:48:34,239 much more to learn and I want to learn it. You give us all 568 00:48:34,280 --> 00:48:39,480 hope for the complexities of state management. Yeah, we've got even less boiler 569 00:48:39,519 --> 00:48:44,960 plate. What more do you need? I'm going straight to that goodness, 570 00:48:45,119 --> 00:48:51,639 I am another Another side of complexity is as a price, right, like 571 00:48:51,800 --> 00:48:57,559 the business has to pay to maintains a complexity. That's another side that I 572 00:48:57,559 --> 00:49:00,000 thought you were telling me there for a second that this is behind a pay 573 00:49:00,039 --> 00:49:04,639 Well, it just forgotten to mention, by the way, and the access 574 00:49:04,880 --> 00:49:13,199 the subscription. I had prime dollars. I had projects, not like not 575 00:49:13,239 --> 00:49:16,960 even talking about state management, just general projects. So I had a project 576 00:49:17,199 --> 00:49:22,559 or angular project and it's been abundant, no problems. There wasn't any problem 577 00:49:22,599 --> 00:49:27,880 with this project. It was working well like no performance should nothing all good. 578 00:49:28,360 --> 00:49:34,199 But the company, the developer left the company and they didn't find any 579 00:49:34,239 --> 00:49:42,559 more Angular developers, so they had to rewrite it with another framework. The 580 00:49:42,760 --> 00:49:46,719 nightmare right like, because the developers at the companies didn't didn't want to learn 581 00:49:46,760 --> 00:49:51,679 Angela, they didn't want to learn new framework, and so they didn't manage 582 00:49:51,719 --> 00:49:57,639 to motivate ang those developers to learn Angular and they didn't find then they didn't 583 00:49:57,639 --> 00:50:01,119 manage to find a new developer. Yeah, same thing with state management. 584 00:50:01,159 --> 00:50:07,719 So some people can implement the complexity, they can leave the company as a 585 00:50:07,840 --> 00:50:14,480 company have to actually find try to find the need developers and those developers might 586 00:50:14,880 --> 00:50:21,519 you might not even able to hire like students or meet beginners who can maintain 587 00:50:21,639 --> 00:50:28,400 this code. This code might be maintainable only by experts and express the very 588 00:50:28,440 --> 00:50:31,639 hard to find and they cost a lot. Is there are really good points 589 00:50:31,679 --> 00:50:37,400 and it is something that I talked to my husband often about is the bus 590 00:50:37,480 --> 00:50:42,639 factor because there's a lot of knowledge that only he or one of his other 591 00:50:42,679 --> 00:50:47,280 coworkers knows at their company on them team, and it's just anything that you 592 00:50:47,280 --> 00:50:52,679 can do to reduce that. So love that, well, gentlemen, was 593 00:50:52,760 --> 00:50:57,000 there any other comments. We'll get into the picks for today, anything else, 594 00:50:57,760 --> 00:51:00,159 let's do it. Well, my pick is a link. Any have 595 00:51:00,239 --> 00:51:08,440 you guys any anybody? Oh? This is the thing. YEA watch the 596 00:51:08,519 --> 00:51:13,800 live stream, got goose bumps, will be signing up to get one. 597 00:51:14,119 --> 00:51:19,159 Seriously though, if you haven't heard of it. It is device to that 598 00:51:19,280 --> 00:51:25,000 is implanted in your brain, creating symbiosis between our brains and AI so and 599 00:51:25,039 --> 00:51:30,360 there's lots of applications for it. But I'm pumped. Does it reduce any 600 00:51:30,760 --> 00:51:40,079 plate? How much? You should see the the other version of this basically 601 00:51:40,119 --> 00:51:44,920 like they I think in the live stream he he said, the other version 602 00:51:44,960 --> 00:51:49,360 of this that currently exists. It destroys quite a bit of brain matter. 603 00:51:49,559 --> 00:51:53,360 And it's the essentially like kicking your TV in order to get it to work. 604 00:51:53,760 --> 00:51:58,440 And it works sometimes right because it just sends like electric jolts into your 605 00:51:58,480 --> 00:52:01,559 brain for certain use case medical use cases. But this is like the the 606 00:52:01,599 --> 00:52:06,840 Finesse way of like you have to watch it if you haven't seen this story. 607 00:52:06,920 --> 00:52:10,480 It's just brilliant, very specific reference. But I feel like this is 608 00:52:10,519 --> 00:52:16,119 how the bar happened in Star Trek the next generation? Are you talking about 609 00:52:16,119 --> 00:52:21,760 the downfall? Community? Scary? Scary? It is? It is it 610 00:52:21,840 --> 00:52:29,480 also watching these electrodes like talk to the neurons in your brain. Like I 611 00:52:29,639 --> 00:52:35,679 was like, oh my god, it's the future like where it's just I 612 00:52:35,719 --> 00:52:38,400 know it's scary, but it's also like it has to happen next step. 613 00:52:38,480 --> 00:52:40,400 We got to go there, right, Like, I don't know. That's 614 00:52:40,480 --> 00:52:47,920 my personal opinion. I was going to follow on your pick. I saw 615 00:52:49,000 --> 00:52:52,599 I saw a tweet yesterday probably about this, and it was like, Bill 616 00:52:52,679 --> 00:52:57,000 Gates, we must have vaccines everyone, No, you're going to put micro 617 00:52:57,079 --> 00:53:00,440 chips in us eat on musk. I'm literally gonna put chip in your brain 618 00:53:00,519 --> 00:53:05,880 everyone. Ah, so revolutionary, it's so true. It's just how you 619 00:53:05,920 --> 00:53:08,480 sell it. Am I going quicks now? Or are you going out of 620 00:53:08,599 --> 00:53:12,239 order again? Yeah? Yeah, I'll go because I got I got a 621 00:53:12,280 --> 00:53:15,599 great one, all right. So for anyone with toddlers or young children, 622 00:53:16,079 --> 00:53:23,719 so you can't get in the bathtub, I use super super Bubble Night and 623 00:53:23,800 --> 00:53:28,119 I use with the kids out of the tub ahead of time, use a 624 00:53:28,159 --> 00:53:34,599 paintster on a drill and make the bubbles with the paintster and it gets huge 625 00:53:35,199 --> 00:53:37,920 and the kids love it. So I've been able to get them into the 626 00:53:37,960 --> 00:53:43,079 tub more successfully with this super bubble night. That's right. I linked a 627 00:53:43,159 --> 00:53:45,719 paintster that I use for it. It's a lot of fun. That's that's 628 00:53:45,760 --> 00:53:49,199 my pick. That's a great pick. I don't know if I could follow 629 00:53:49,239 --> 00:53:55,239 that. So is it my goal for peaks big? So that's my peak. 630 00:53:55,920 --> 00:54:00,519 It's a mug with a bicycle on it. Yeah, my pig is 631 00:54:00,519 --> 00:54:06,840 a bicycle. It was really helpful for me at these times being isolated. 632 00:54:07,360 --> 00:54:10,559 So it can keeps you isolated, but at the same time you can get 633 00:54:10,719 --> 00:54:15,760 away from your computer desk, don't bring commute computer with you, just sit 634 00:54:15,840 --> 00:54:20,480 on the bicycle and ride around. So that's what I do every month. 635 00:54:20,639 --> 00:54:24,280 I like for the last four months or three months, I'm doing more than 636 00:54:24,519 --> 00:54:30,360 three one hundred thousand in a month kilometers on my bicycle, which helps a 637 00:54:30,400 --> 00:54:37,199 lot to keep your feet and get away from desk from computer desk and stay 638 00:54:37,280 --> 00:54:40,800 isolated so you don't breathe and sneeze on other people. I can, I 639 00:54:40,840 --> 00:54:44,800 can only we can obviously any say from the from the chest up, I 640 00:54:44,800 --> 00:54:47,639 can't imagine you have legs the size of tree trucks after the three hundred thousand 641 00:54:47,679 --> 00:54:55,599 kilometers on your bike. Yes, sort of. Actually, this month. 642 00:54:55,679 --> 00:55:04,440 I done two hundred thousand eight nine. That's that's insane. Actually not this 643 00:55:04,599 --> 00:55:08,599 month's I mean August. It's already September, so it's zero. This month 644 00:55:08,719 --> 00:55:15,599 is you're speaking to us from the future. It's me from the future, 645 00:55:15,599 --> 00:55:25,360 but you're still in August. Oh, this is in a mask with your 646 00:55:25,440 --> 00:55:30,880 with your cyber pig. You we're literally talking to someone in the future. 647 00:55:35,960 --> 00:55:40,199 That's what as you call it. By the way, if anyone starts using 648 00:55:40,239 --> 00:55:45,320 that, I coined it. I want so do you want me to tell 649 00:55:45,400 --> 00:55:50,239 what the stocks price or anything like? Yeah, you're in the future, 650 00:55:50,360 --> 00:55:59,039 right exactly, take over the world. So the going price on September first 651 00:55:59,360 --> 00:56:07,320 is and it's another pick price. I haven't looked at the coin price for 652 00:56:07,440 --> 00:56:12,800 years. Okay, So what currency should they choose? US dollars? US 653 00:56:12,920 --> 00:56:16,280 dollars? Where is US dollars? You know I don't have US dollars in 654 00:56:16,280 --> 00:56:22,760 my list. Okay, I tell you in Singapore, Sincapore, Singapore Septempter 655 00:56:23,039 --> 00:56:29,119 nine, point of reference, Sincapore. Okay, comes out in September. 656 00:56:31,000 --> 00:56:35,159 Okay, hend on a second and need deserved. Okay, I tell you 657 00:56:35,360 --> 00:56:40,320 US dollars. It's eleven. It's eleven thousand, point seven hundred. Wow, 658 00:56:40,440 --> 00:56:45,119 this is the same with your end. Okay, it's eleven thousand and 659 00:56:45,159 --> 00:56:47,440 seven thirty five at my end, so yeah, yeah, okay, but 660 00:56:47,599 --> 00:56:51,719 down in the future, to be precise, it's a lot of size and 661 00:56:52,239 --> 00:56:58,519 seven hundred forty four dollars forty point okay, yeah, yeah, all right, 662 00:56:58,800 --> 00:57:12,079 so it goes up up if you buy Chris, what's your pick? 663 00:57:12,400 --> 00:57:16,840 I will go with a short pick. Today my toddler has a cold and 664 00:57:16,920 --> 00:57:22,599 this morning he had a temperature. So we did the sensible thing and booked 665 00:57:22,599 --> 00:57:28,840 a family trip to go and get coronavirus tests, which we we I appreciate 666 00:57:28,880 --> 00:57:31,119 this is different, going to be different in every country, but over here, 667 00:57:31,280 --> 00:57:36,320 like literally booked it and three hours later we were getting the test. 668 00:57:36,719 --> 00:57:39,480 It wasn't hugely pleasant to be like sticking that thing up my nose and in 669 00:57:39,519 --> 00:57:43,920 the back of your mouth and things, but it was also it was pretty 670 00:57:43,920 --> 00:57:46,719 painless and we got the kids done, and I think it's a sensible thing 671 00:57:46,800 --> 00:57:51,639 to do. So my pick is, if for any reason you think you 672 00:57:51,719 --> 00:57:54,320 might get a test, get a test, because then at least you know, 673 00:57:54,639 --> 00:57:59,719 do you know when you'll get the results? Did they tas forty hours 674 00:57:59,760 --> 00:58:07,440 get text apparently by text message, Wow, I hope it's negative, darling. 675 00:58:08,199 --> 00:58:10,519 Yeah, I mean, I mean he's got a cold. And just 676 00:58:12,000 --> 00:58:15,559 it seemed like a sensible thing because in the UK they're saying if you've got 677 00:58:15,599 --> 00:58:20,239 and I imagine probably will what they say if anyone in your house has like 678 00:58:20,280 --> 00:58:22,480 a temperature. It's like he's a toddler. Of course he has a temperature. 679 00:58:22,639 --> 00:58:28,559 He's apparently got a temperature. But its lock yourself away for two weeks, 680 00:58:28,559 --> 00:58:30,920 Like I'm not going to lock myself away for two weeks because the toddler 681 00:58:31,000 --> 00:58:34,440 has a cold, Like I'm just going to get the test that I can 682 00:58:34,480 --> 00:58:40,079 say is not coronavirus. I remember backings the months, like four months ago 683 00:58:40,360 --> 00:58:45,199 in order to convince doctor to make a test to a stick in a while. 684 00:58:45,599 --> 00:58:49,960 So this guy not in my office, like in my friend's office. 685 00:58:50,320 --> 00:58:57,000 So in April he came from Europe, somewhere from Europe with lots of was 686 00:58:57,000 --> 00:59:00,679 it Italy Probably he came from Italy, And basically it took a little bit 687 00:59:00,719 --> 00:59:05,840 of time to convince doctors that he might want to make a test. Who 688 00:59:05,960 --> 00:59:09,519 coronavarius test? Because I'm probably the station different. Now, if you want 689 00:59:09,559 --> 00:59:13,519 to make a test, they just hey, here you are. But for 690 00:59:13,639 --> 00:59:16,440 months ago, it was it was taking a little bit time to convince doctor 691 00:59:16,519 --> 00:59:21,519 as that you need to make a test. Yeah, but when this all 692 00:59:21,519 --> 00:59:23,000 started, we couldn't even get a test. I had in March, I 693 00:59:23,000 --> 00:59:27,880 had had a chest infection and I just wanted to I just wanted to get 694 00:59:27,920 --> 00:59:30,800 some antibiotics and like, because one of the things that you have with just 695 00:59:30,880 --> 00:59:35,960 infection is a cough. Literally just all adopts on the phone like no, 696 00:59:36,079 --> 00:59:37,239 you just have to self isolate for two weeks, Like no, I have 697 00:59:37,280 --> 00:59:42,199 a chest, I want some antibotics. Like no, get self islate, 698 00:59:42,280 --> 00:59:45,199 Like can I have a test? No? No, just self isolates. 699 00:59:45,239 --> 00:59:51,559 It's like, yeah, it's really come on because that was rubbish and the 700 00:59:51,639 --> 00:59:54,559 results are you saying for the eight hours or twenty four? Yeah? But 701 00:59:54,639 --> 00:59:58,679 I mean I was. I was the guy said that some people have been 702 00:59:58,760 --> 01:00:00,400 have been reported that can take twelve. It's it's public holiday in the UK 703 01:00:00,440 --> 01:00:05,119 today, so it's possible that the old testing might be a bit slower. 704 01:00:05,119 --> 01:00:08,239 But yeah, apparently forty eight hours to get a text. Yep, sorry 705 01:00:08,559 --> 01:00:10,519 that I was going to say. It would be cool if if it came 706 01:00:10,559 --> 01:00:14,760 through live on air unless it was positive, it would have not been cool. 707 01:00:15,559 --> 01:00:17,400 And I think, like my point here on the results, like may 708 01:00:17,639 --> 01:00:21,840 can move. One of my friends he made a test two weeks ago ago 709 01:00:22,800 --> 01:00:27,119 something that so it took like a couple of days to them to get back 710 01:00:27,159 --> 01:00:30,760 on the results results. Well it was negative, and he was surprised, 711 01:00:30,760 --> 01:00:35,440 like why it took so long. And my theory, if you're negative, 712 01:00:36,000 --> 01:00:40,119 so maybe taking like twenty four like whatever two days, but if you're positive, 713 01:00:40,559 --> 01:00:46,440 they probably come back to you like right, waitah, true, actually 714 01:00:46,519 --> 01:00:50,159 it's very true. But we've got to get these people off the street. 715 01:00:50,360 --> 01:00:52,840 Yeah yeah, yeah, yeah yeah right right, Well, Alessa, it's 716 01:00:52,840 --> 01:00:59,039 had to nip off, so I think that's probably a good sign that we 717 01:00:59,119 --> 01:01:01,280 are done. I just want to say thank you to Lexi for coming on 718 01:01:01,559 --> 01:01:07,039 and thank you. It was like super super interesting today and I really enjoyed 719 01:01:07,079 --> 01:01:10,679 all visuals. I'm sure those of us listening at home perhaps slightly less, 720 01:01:10,960 --> 01:01:14,000 but no, it it was fabulous, So thank you so much. And 721 01:01:14,039 --> 01:01:16,559 I also saw you minimized your desktop at one point and it's like four thirty 722 01:01:16,559 --> 01:01:21,480 in the morning there, which I hadn't realized. So also thank you for 723 01:01:21,840 --> 01:01:23,519 thank you for getting up in the middle of the night to speak to us. 724 01:01:24,000 --> 01:01:25,960 Yeah, I had to wake out, I had to get to bed 725 01:01:27,000 --> 01:01:31,079 at the eat, serious dedication. I slept a couple of hours. But 726 01:01:31,239 --> 01:01:37,719 yeah, yeah, it's not my first talk at as early morning. So 727 01:01:37,079 --> 01:01:43,199 I done my first early money talk back in maybe two months ago at Angel 728 01:01:43,239 --> 01:01:49,440 and New York. So at the first time, once you're speaking as early 729 01:01:49,480 --> 01:01:52,719 money first in your life, it's hard, but after that it's getting now. 730 01:01:53,039 --> 01:01:58,480 Yeah, yeah, it's fine, Yeah, brilliant. Right. Well, 731 01:01:58,760 --> 01:02:01,519 I think that all is left to do is to say thank you to 732 01:02:01,639 --> 01:02:05,639 everyone listening, and we will catch you next week.