Hello, Welcome to Adventures and Angler, the podcast where we keep you updated
on all things Angular related. This show is produced by two companies, Top
and Doves and Void. Top and Doves is where we create Top and Doves,
so get top and pay and recognition while working on interesting problems and making
meaningful community contributions. An Onvoid, which provides remote design and software development services
on a performance basis, so clients only pay for delivered tasts. In today's
episode, we will talk about the Angular renaissance. This is how they're mentioning
this new movie. Angler was recently rebranded and we also got a new version
Anglar version seventeen. So we have a lot of things to talk about.
We're going to introduce you all on what is new, just taking it from
the top and Yeah. So my name is Lucas Paganini. I am the
CEO of Void and your host and the podcast. Joining me in today's episode
is Charles Maxwood. Hey, folks, it's been a little bit yeah,
and Subrett Mishra Hello, everyone. All right, Okay, so let's get
into it. So, so Brett, let's talk about the rebrand. What
do you think about the new Angular logo? Yeah, I think When I
saw the logo first, I thought like someone just caated I got it in
my LinkedIn that angular it's dedicated. I thought someone just cut it from the
side and is trying it to animate it as some grady and and something.
But I saw that. Okay. Now Anglar is also coming up with the
new new document side and which looks pretty cool, like if you go,
they have an Apple style branding and then so scrolling effect and now it's that
think Anglarre going is a good way of catching the market again, hope like
with all these changes, all this optimization with Angler seventeen, let's hope for
the best. And I like the I like the old one actual a little
more, but the new one also quite good. The old branding an old
logo, old Angler and logo, a simple material design. Now it's a
Signee logo. But yeah, I thought my opinion would be unpopular. I
like the old logo a lot better than a new one. Whatever. Yeah,
I mean, I am still a bit divided. The new logo looks
really cool, but I just feel like it looks like a lot of other
startup logos that are trying to look cool. And the old logo had this
classic look to it. It was just it was just classic, you know,
the red shield with an A. But at the same time, I
completely agree that they needed a rebrand, and like, I'm not gonna lie.
This week, I think it was Monday, I opened up LinkedIn and
I saw those pools on LinkedIn and somebody was making this question, if you
were to start a new project right now, it's a personal project, you
have full autonomy over the technical decisions. What would you use for the framework
in the front end? And the options were nothing. It was React and
the third option was Angular JS And I was like, dude, really twenty
three like you Yeah, It's like people are still are still like not getting
that Angular and anglar j us are completely different things. So even though it
sounds like we should be over this problem by now, I actually think this
rebranding and distancing ourselves from all that can make people identify Angler as if you
were anglergyass, I think it's for the best. So yeah, I'm on
board with the change. Yeah, the idea of doing a rebrand is different
from having a logo that looks like a second year art student made it.
That that's I'm just saying, Oh, shots fired, No, I really
don't like it, but not my decision. So I like, someone just
slept and opened this is fine. Cut it, cut it, cut it
here and right? How much it five minutes done? Grady, it's awesome.
Yeah, but what one thing I was searching about posting it might my
channel was trying to download the logo, but it's not. It's a gradient.
It says SPG. Now, so either either like if you have animated
logo, you you have TOPG the thing though, but yeah, rebranding is
required and opening Photoshop or something. Yeah, you can get away with that.
That's not a major issue for me. Yeah, okay, so what's
you besides the colors. Yeah, let's get into the other stuff. Let's
see if anything pleases you. Check. I don't have any opinions. Let's
get into the new docs. So we are not gonna rely on Angular dot
i O anymore. We have a new website with a new domain and now
everything is over Angular dot do. So a couple of pros and cons,
just so that we can summarize it. Seems that now we have interactive tutorials,
which is cool. And they said that they revised the entire thing.
I'm saying those things in that way, instead of giving certainty just because I
myself haven't taken the time to actually read to the entire new documentation, I
just scheme to the website and it looks good. It looks really good.
Yeah, it looks it looks better than the old website. And what I
really like is that when they were announcing this new website, they said that
they revisited the entire documentation to make it way easier for people to get started
on Angler, and they also made sure that every lesson was contained in itself.
So for example, if you want to learn just how dependence injection works,
you can read only the lesson about the pend this injection. You don't
need to read anything that came before. So they made it in a way
in which it requires a minimum amount of context from the lessons that are in
other sections. So that's really good for people that just want to like a
quick handbook to consult how a particular part of the framework works. I think
that's a major leap forward. I really really really like that. And one
cons is that right now this new website is doing beta and it doesn't have
all the features that the other website had. For example, translations. There
are no other languages. Everything is just in English, and there's no way
for people to go to GitHub and add other languages to it. In their
defense, in the old website, it was also not super easy, like
people would have to clone the website repository to create versions in other languages,
so it wasn't super easy, and Minko said that they are trying to make
it easier this time, so they I'm thinking that they're going to do everything
in the same repository and just kind of have the different languages sitting up there
as markedown files. Probably would probably that would be much better, but unfortunately
we don't have support for that yet. And I totally understand, like they're
just releasing the website. They don't want to make it too rigid because like
structural decisions like this make it harder for you to make changes to the website
later on. But at the same time, I'm not sure if I agree,
just because like they just released it, so everybody is excited, so
I feel like this would they have enough momentum that asking for people to create
translations would probably work really well right now, just because everybody's talking about it,
so that would be a good moment for them to ask people to create
translations, but nobody can't do that yet. So yeah, that's one cost.
But everything else that I've seen so far are just pros. Yeah.
I think one thing I liked a lot is that they have now they have
a playground option and in that if you go to the contact flow, and
it is so that how far Anglar came. Now within only one file you
can host your application like only main dot ts and that's all. So now
a'mular that is going in a like a modelarized way, or you can say,
like how minimalistic way. Now new people coming to Angular, they don't
have to learn about modules a lot of things. They can start building it
and on in process they will learn a lot a lot of things. Yeah,
I think they're using stacklets for that, aren't they. Ah, But
uh, it's it's pretty slick, yeah, because it's yeah, it's building
and injecting dependencies for like polyphills and stuff. But yeah, I I really
like that piece. And like you said, it's all simplified too, yep.
And here we can write it everything builder application, then down download it,
then put it so that's off. Sen is also there, so yeah,
you always didn't they not have to start from the scratch YEP. I
also like that there's a key command for search and then it does dark mode.
My computer's on dark mode, so it went to dark mode automatically.
But I'm starting to like websites in light mode better even now. I like
my computer and dark mode. Don't ask me why, but it just a
lot of that makes it a lot simpler. Just you know, the the
command K for search, and then any other key commands that you know you
expect to work in other systems tend to work here, and so that is
pretty approachable to your point, Lucas. With the translations, yeah, every
translation is a bit of work. I was gonna joke and say they should
just put it Google Translate right right, But the reality is is, yeah,
you you want it to be correct, and Google Translate isn't always so
yeah. What would be interesting too, is if they got bona fide translations
going, and then they could maintain their momentum by saying, hey, now
we have a French version, right, just let everybody know, Hey,
we've got the French version. Now, we got the Spanish version, now
we've got the Japanese version. Now you're right, because then every community is
going to be going, yeah, you got to us. So that's a
good point. Yes, so they can to do that. That's a good
point. Yeah. And well, in terms of the website itself, before
we actually get into Angular version seventeen, another thing that I also liked is
that at the bottom of the side menu they also added a section for it.
Well, there are a lot of new sections, a lot of new
lessons, but there's this new section called extended Ecosystem, and I thought that
was so smart because there's more to the extended native ecosystem of Angular than just
Angular Material. But unfortunately a lot of people think they're like, oh,
there's Angular, there's Angular Material, and everything else is just third party.
So now they are adding all those other extended libraries to this Angular dot dev
documentation, which makes it really clear that they are supported by Google itself.
So we have Angular fire which is to work with Firebase. We also have
one for Google Maps, another for Google Pay, the YouTube player, and
then we have the traditional ones like the Angler CDK and Angler material, as
well as some other stuff for service workers and PWAs. So I really like
that. It's like a it's a nice call to action for people to go
beyond what's just on the core angular dogs and learn more about those other things
that they might want to use in their applications too. Right, I think
one thing I would like to like to maybe in some future some may be
Angler or React. They will also integrate some AI with it, and people
that go to the dog and say I need this application, and then they
prepared application and give it to them. That reminds me of when I first
got started freelancing. So I was doing Reviy on rails and Twitter when it
came out was written in Ruby on rails. They've moved a lot of their
stack off into other pieces depending on anyway. So I would get emails from
people that said, hey, can you write me a script that will be
a Twitter app? Oh man? I love talking to people that want to
build to tack business and have no idea how it is to code. Well.
The other thing that gets me though, is just like, look,
is there any other part of business anywhere where if I could crank you out
of Twitter clone in two days, then it would be worth anything because anybody
wanting to compete with you can do the exact same thing. Right, The
profitable businesses are the ones that are out there. Yeah, they make it
easy for you to do a thing, but it's not trivial to copy what
they did exactly exactly. Yeah, I don't know why, but okay,
So in terms of the last new thing is a new version of Angler.
So we have Angular version seventeen now, and that was actually released today.
So the website was released Monday, but Angler seventeen was released today a few
hours ago. But we already know what's in it because they said the in
the launch of the new brand Monday. And let's go over what's new.
So first, we have much a much more improved build performance because now Yes
Build and Vite are no longer just experimental. They're actually stable bundlers. Cool.
Yeah, and if you replace Webpack with Yes Build or vite, you're
gonna get I don't even know it by a head, but it's like maybe
ninety percent faster. It's like something egregious like that, just like much,
much, much faster. I think it's funny because people I've heard some people
bagging on Webpack, you know now that we have an es builder of Eat.
But the reality is is that Webpack kind of opened the gate to this
whole thing, so you have to give them a ton of credit and then
recognize that, yeah, we want faster builds and so we're going to use
a different tool now because they are better tools. But yeah, props to
the Webpack folks for solving some of these problems early. Definitely, definitely they
as you said, they opened up the gates. And the only reason why
other competitors can differentiate themselves just because they are faster is because Webpack already differentiated
itself by having all the features, so everybody else can just say we have
the features and we are fast the plug ins. Yeah, exactly exactly,
but it's really nice that we have that. This is definitely going to improve
the overall developer experience, which by the way, I was already feeling that
it was much better. I was. I was getting like less than one
second hot reload when developing on the latest versions of Anglers. So now that
we have the other build modules, I'm guessing that this will be even less
noticeable. So yeahs yeah, exactly exactly, And I mean, sorry,
go ahead, you know I'm saying that with this week they have also like
have a eighty seven percent rendering sixty seven percent client set rendering, so after
you build, also when you're rendering with some ankle universala something that that is
also quite fast. Now yeah, I feel like the most noticeable performance improvement
now it's going to be in continuous integration, because if you're just developing locally,
I don't feel like the speed right now is a problem. But when
you actually send your code and you open up your PR and then you have
to wait for your continuous integration system to build and run all the checks and
tests, then that still takes up a while. If you have Like at
Void, we generally use NX to organize all of our Angular code basis,
and then we can break it into smaller pieces and we can use caching for
all the individual pieces. So when we send something to CI, it builds
up much faster because it's only building smaller parts of the application instead of having
to rebuild the entire thing all the time. But still it's still not blazingly
fast. Like I would say, it takes a minute and a half to
two minutes on average for our Angular libraries to build on continuous integration, even
with part of them being cashed. So if there's no cash, I would
say that it takes like two minutes to two and a half on average.
So I really like the idea of eating things up on CI. I think
it's going to give us a much faster feedback loop. Because sometimes I gotta
be honest, Sometimes I send coach to CI and I go make some coffee.
It's like that x KCD where they're fencing and the boss walks by,
like, what are you guys doing? Oh, it's the Yeah, yeah,
okay. I think now it's pretty good. Yeah. Like I think
we just have to have a look on like how Angular is growing. I
think be pour Anglar nine or something till Angle and nine people are saying Angular
building, we have a very high high amount of any cell bundle size and
that is reduced then Ivy game, then then slowly stand alone everything. Now
with Anglar seventeen we have control flow. So now Angler is also making how
flexible you want to write a code. It's in your way, how how
you can divide your code to a different function and use them as you like
it. It's I think it's removing the rigidity from Angular and giving more flexibility
to the developer. And that's that that's a very good way which anglized.
I think seventeen is the might be a very big religion in terms of Angular
ecosystem. Yeah, let's talk more about that. So build in control flow.
It's not really a new feature itself, but it's it's a way for
you to clean up your code a lot, and it's also going to make
it much more easier for beginners to get into Angular. So now you don't
need and let me be clear, it's not that you can't. You can
still use NGF and four and switch, but you don't need to use that
because right now we have building functionalities for the So you have a building at
if statement. You also have l's if and l's already built in into the
Angler template language, so you don't need to import the common module and use
NGF, NG four, eng switch. You can get rid of those unnecessary
elements or engine containers that you are using just to provide country flow. And
they are also faster. So they are also faster. But I think the
main benefit is not really the speed, is really the syntax. It's just
much clearer to read and understand how the component is being rendered and in which
steps things are being rendered, and now what is actually new not just like
a synthactic change. But an actual new feature is deferable views, and it
goes on top of the new built in control flows. So it's using the
same syntax as if for and switch statements, but it's a different thing.
Like we don't have a way like an energy deferable view, you know,
like there's no that right now on Angler sixteen. But we do have this
at the fur command right now, which is going to allow you to tell
your template that parts of it should only be rendered after a given a synchronous
condition happens. And this a synchronous condition can be one of the presets that
they have, like once the component is on the viewpoort, once it loads,
like you have a bunch of triggers, but you can also have your
custom triggers, so you can say when this property is equal to true,
or when this array is not empty. You know, you can have things
like that to indicate that the request that you made to the backhand was successful,
the data was retrieved and now you're ready to show it. So you
can put the parts of your component that depend on this data already being available
inside a defer condition, and then you can give it the condition of when
that part of the deferable view is supposed to be rendered, and it's going
to be rendered when that happened. And it also has a lot of other
utilities, right, So red like you now have a very declarative way of
saying like what should be showed to the user when the data is being loaded?
Or you can even add what's it called, like that template that you
show when you don't have data, but it feels like you have the components
there I forgot the name of it. Placeholders. Yeah, you can also
show these placeholder components and it's so declarative it's really really easy to understand what's
going on. You even have a section to tell what happens if there's an
error. So that sounds really promising. I really liked this the first statement.
Yeah, I think by using up viewport and by different sell loading,
by different loading, it's also like I think going in a way of which
Angler has in future in mind that change detection will work as a view basis,
like currently it's working as a component basis, so only on your component
if you flag, if your component is flagged, it will be registered for
change detection. Then the whole flow is down that now you can convert that
to So in future, what will happen. They'll convert each suppose a fur
loop or a statement to a view and that view only be redent and not
the whole component. So I think this is a new way, starting way,
and that is only possible with standalone based component and signals and everything.
So I think in few a lot of things yet to come in eighteen nineteen,
yeah, yeah, and everything else. I think we can put it
in a box of developer experience. So I'm going to just list some of
the other things that we have, but honestly, there's just so much here
that we're probably going to have to do other episodes to get deeper into it
and actually show examples, and we focused on each of them, but just
so that we actually have a complete podcast where we list all the new things
for you. The other things that we have are like improvements to service side
rendering, so there are performance improvements to service I render and they're also like
quality of life improvements. For example, right now, before Anglar seventeen,
if you wanted to start a code base from scratch and add Angular Universal to
it, you needed to do just that. You needed to start the code
base, and then at Angular Universal, there was no way for you to
just already start with Anglar Universal setup. It wasn't super hard to set up
Angular Universal, but it was that extra step, right, And now you
can have that already in the CLI, so you can start a new project
and use dash dash assr and it's going to already start with Angular Universal.
Also, they renamed it so it's no longer called Angular Universal. It's called
Angular SSR, which is much more Yeah, it's much easier to I liked
the idea of Angular Universal because when it originally came up, the idea was
to have Angular running in all sorts of environments, So it wasn't like just
for service ARE rendering. It was supposed to provide all the necessary structure to
make Angular run in any environment that you want, so which is why it
was called universal. But the truth is, over time we really only used
it to do service I rendering, so it just makes sense to call it
Service I rendering. And if you're going to support other platforms, you can
have modules or packages that have the names of that of those platforms specifically.
So for example, if Angler ever releases a native way to build hybrid apps,
I know that we already have Ionic, but if Angler decides to release
a native version instead of using Universal and putting all those platforms into the scope
of Universal, they can have like an at Angular Slash Mobile for example,
which is also going to be much easier to understand. So I like this
movement of calling it angular SSR. Then we also had some other improvements to
the bugging, so now we have dependency injection Debugging in Depth DULs. So
the Angular dept DoLS now has a dedicated page for dependency injection, and you
can understand where your instance is coming from, and also if you were not
able to to if Angler wasn't able to provide an instance of what you wanted,
like how it traversed up to the root node and all the steps that
it went to get there, so you can see if the module that you're
providing this dependency is not in this hierarchical tree, and you can understand why
you're not able to inject the dependency that you want to inject. So that
also helps the ton And yeah, like a lot of other quality improvement,
one that I really liked, I really like, but I want Suprett's opinion
on this one. So let's see suberred. Have you taken a look into
the how do they call it? I think it's transform input value transforms.
So it's basically like you have you know, when you have a buttom and
you want to have like this disabled parameter, but you don't want people to
actually have to set up a value to it. It's like just the mere
presence of the disabled attribute should already tell the component that it is disabled.
But the thing is for you to support that that synax. We needed to
convert the existence of this attribute into a bullion to indicate if disabled was true
or false. Uh, And that added up other boilerplate to the co base.
And now we can do all that with a single, natively supported way
to transform the input. But I wanted your opinion, so Brette, like,
do you think the way they did it is Yeah, I'm just wondering
about the signature of the function itself and the way in which we build those
transformers. Have you had a chance to take a look at that. I
have used that though in angles sixteen. If you passed a transform attribute to
the to input and past and that the corresponding component and that you can just
report it now. But yeah, it's the required actually how people should do
it, because I so a lot of sides they just put it digble and
they go and change remove that part. It re enables it and you can
go and fast forward. So the first thing is to not do that,
like you should not have an option to have a user can edit in the
STML and then just passed the passityjable. Second way is yeah, I think
the input way is good in terms of passing the state from parent to child.
And now I think but I guess it's not on the seventeen right,
so I it started at the sixteen, I guess, or just came seventeen
because I remember using it sixteen. It actually came like officially came on version
seventeen. Okay, experiment sixteen, Yeah, yeah, maybe that was it.
I really only only saw it on Angler seventeen, so I don't think
we had that on sixteen. Well, we did have six thing with Anglar
signals, which now if I recall correctly, they are officially stable. Right.
Oh cool, yeah, yeah, all right, I've got to take
off if you guys want to keep talking and Lucas if you have the end
stream button in the top right corner you can keep going. Otherwise I've got
to wrap us up. Okay, we can keep going. I have it,
Okay, you have it all right, Well this was fun, really
cool, looking forward to good new things to come. Sorry, folks,
I gotta bail. My kids have a My daughter made the honor roll and
so they're having a thing at the school. So anyway, go ahead and
keep talking and we'll catch y'all later. Okay, thanks for Johnny. Thanks.
Yeah, I guess about the transform. I guess they faery member transform
off to bullian or transform like now we can pass it will check your input
type on the on the sub. Suppose you're you're passing a string and somehow
you are passing a number to the to the input. That also transfer will
help that. Okay, it's a bullion. It's not a number. I
think earlier alily to us not you'll get it only on run time, not
on compiled time. That's also another another but I think it's it's game with
sixteen. Maybe I'm wrong with I have used experimental, but I have used
it sixteen. Okay, okay, what else read? Do you think there's
anything here that because we're definitely going to have to do all the episodes getting
deeper. You have to use it like like a hands on develop some change
some app with Hangulas seventeen and try to try to do it. I think
n g r X also maybe it release with new seventeen. Maybe maybe they
have already released out or maybe tomorrow or day after tomorrow. They will really
just super quick with a version, so how it integrates with them and all
the things. A lot of new things to do, and as every six
month we are getting a new versions. So this is maybe fop for you
guys who was watching us or listening to us like it's just a new version,
doesn't things like okay, every six month, I have to learn new
things. It's not like it's just addition up a slight small approach. So
if you just keep listening to to podcast or start doing a project yourself,
like slowly, you will learn everything. You don't have to put so much
better on yourself that I have and read the dogs just to know what at
all in end seventeen to focus on your product and we'll learn that. I
decided definitely, definitely, I think that it was a beautiful disclaimer for us
to start wrapping things up. Is like don't get afraid of it is not
a new framework. It's still Angular, but a new logo though, Like,
yeah, it's a new logo, but there are not too many major
changes. The thing is, it's been a while that Angular itself its new
right Ever since Angular thirteen fourteen fifteen, it already had this feeling that it
was a much more modern framework. Somehow, there was like this big leap
from versions, Like when we were upgrading from Vision like seven to eight to
nine to ten to eleven, it didn't felt like we had many like big
changes that would change the way in which we actually code Angle. There were
a lot of improvements, definitely, but it didn't felt like it was really
catching up with the other stuff that was appearing in other frameworks. But since
Angular thirteen we really started to get momentum. So the fact that they rebranded
it now doesn't mean that Angular seventeen is like a new thing, but I
would say that ever since Angular thirteen it just feels like a new framework.
So yeah, like, if you are on Angolar eight and want to upget
to Anglar seventeen, then you might spend some time and go through everything and
try to check late it's not breaking something. But if you're on Angler fourteen,
fifteen or sixteen, I don't think it will break anything. It just
need to run engy update and it to work. Definitely, definitely is going
to be a breeze. And yeah, going to the promotions, I'm actually
going to use this as a segue because if you are in the situation you
need to upgrade your code base, then I feel free to reached out at
Onvoid dot com is U n Void dot com because we definitely can help you
out with that. And we work on a performance basis, so that means
that you're only going to pay for our work when we actually deliver the work
to you, So there's no risk you're not going to pay per hour.
For example, Oh if we take longer than we anticipate it, that's our
problem, that's not the client's problem. So the client is always in a
much safer position when they're working with us. So if you're at all interested
in either outsourcing a project or augmenting your staff, you can check out Void
dot com. We are currently available for new projects, but I'm not sure
for how long we're going to stay that way because we really have a maximum
of projects in which we do concurrently because we understood that if we do more
than that, it starts affecting our output and we don't want that. We
want to be known as a company that delivers outstanding quality and not a company
that has like thousands of clients. So yeah, if you're interested in that,
go check out Onvoid dot com and we can schedule a meeting. How
about you, Sugred, What would you like to promote? Yeah, I
think nowadays I have a little bit pause. It's not too I think it's
on the blaming on me though, like a little pause by from posting some
videos. Sorry you guys for that. And I think nowadays I either I
need to put a very long video or maybe starts. And that's what trending
right now. YouTube is not promoting it after I guess after chat GPT people
are searching less on programming stuff, so they are getting the answer from charge.
We saw a decline in stack overflow traffic. We saw a decline in
Google search or maybe searching too particular things. But yeah, but it's it's
how it is. So so I will try to I think I'll try to
have like the first podcast too. I will try to add some more podcasts
and try to build with it, and I'm planning to schedule them and launch
them. So yeah, if you, if you would like to go to
my channel. My channel name is fun of Heuristic there we with there.
We have plenty of videos on Angular, a lot of stuff like Angular,
Peter Blu, a service worker working with location, and a lot of things.
So you just go and check that and please keep the comment if you
If you don't like it, scrolled me say that I don't like it,
so I'll try to make it better, but please check it. Yeah,
I sent a link to your YouTube channel here on the on the comment section,
and we got to get used to that, right. It's weird having
a comment section. I wasn't used to that when we were just recording the
podcast, but now that everything is live, it's it's nice to have that.
And I'm also putting it on Avoids website there, so if anyone wants
to wants to check out. But yeah, again, just to reiterate,
like, really, guys, if you like the content that we produce here,
you're definitely going to like Subrett's channel. His content is really good and
there's just so much that we can do with a podcast. Because even though
we have this video version on YouTube right now, we always try to be
mindful of all of you that are just on audio, so we try to
avoid really showing code and depending on visual things to get our message across.
But Subred has none of those limitations in his YouTube channel, so it's much
easier for him to explain some of the concepts that might be harder for us
to do here just because we are in an audio only format. So highly
recommend check out his content, and it's definitely not just for beginners. He
has a ton of very advanced stuff. He has things that I check out
eventually and I learn new things, and like, I'm not trying to say
that that I'm a complete expert in everything, but I would say that I'm
pretty advanced. But still there are a lot of things that I learned from
Subred. So I highly recommend. Thanks Mat, thanks for the nice verse.
No problem, It's easy to recommend when the content is good. All
right, let's start wrapping things up, So thank you everyone from for sticking
with us. We really appreciate all of you with us for so long.
We are approaching the episode number four hundred, Like, oh yeah, that's
so much content, so much. Yeah, I think I joined around two
hundred or three hundred. I joined the podcast around three hundred, I guess,
so I had I was a guest and then then I joined the podcast.
So I think it's a long journey. I think that's all care you
go to Chucks like he's doing it for twelve years, the podcast King.
Yeah, everyone should learn something from from him. You can. You can
discuss with him the day in and day out, like, just discuss with
him about podcasting and he will be definitely definitely. But at the same time,
like, I'm a super fan of Chuck's commitment to this because it is
a very long, a very big effort to keep this up for that long.
But also a big shout out to everyone that actually listens to us,
because we wouldn't really be here if there wasn't an audience. So thank you
so much, and consider this an early thank you as we approach episode four
hundred. All right, thanks everyone, I'll see you in the next one.
See you guys, Bye bye.