S9 E9 | Into Server-Side Rendering | Brygida Fiejdasz - The Angular Plus Show

Episode Transcript
Available transcripts are automatically generated. Complete accuracy is not guaranteed.
Speaker 1 (00:08):
Welcome to the Angular plus Show. We're app developers of
all kinds share their insights and experiences. Let's get started.

Speaker 2 (00:21):
Hello and welcome back to another episode of the Angular
Plus Show. My name is Laara Newsome. I'll be one
of your hosts today. With me, I have yan How's
it going pretty good?

Speaker 3 (00:31):
It's finally getting nice out, which is weird in the Midwestern,
but it's nice it is.

Speaker 2 (00:35):
We were in that brief window where it's NATSI humid.
There really aren't bugs, it doesn't get like too hot
during the day. The air conditioner doesn't really have to
be on yet, although I do know some people that
already have their air conditioners. Boy, they just like to
spend money, I guess.

Speaker 3 (00:50):
But that's one of the good things in this country.
So leave me that jo of like.

Speaker 2 (00:56):
Having this air conditioner all the time. Yeah, I know,
my friend, Like, I would get rid of the entire
internet if it meant I could keep air conditioning, Like
it is like the one thing that makes my life livable.
It's my one creature comfort that I'm like, oh, how
would I live without it? Also with me, I have
chow chow.

Speaker 3 (01:17):
How are you good?

Speaker 4 (01:18):
How are you all?

Speaker 5 (01:20):
I'm a same as us Nicholas here enjoying the little window,
tiny window of perfect Midwest weather.

Speaker 2 (01:29):
Yeah yeah, so we're like for the listener, u Yan
and Chow and I make sort of a triangle right
in the middle of the United States. So I'm going
to move.

Speaker 3 (01:42):
Oh, I'm going to move to Atlanta.

Speaker 2 (01:45):
Oh okay, just that batter triangle. It'll just be like
a triangle with instead of like a nice Auceles triangle.

Speaker 3 (01:52):
So I'm shocked that you will not have.

Speaker 2 (01:57):
As much of a window of nice weather as my suspicion.
I think you're going to get a lot more humidity
and it's going to come faster.

Speaker 3 (02:03):
But is all right.

Speaker 2 (02:06):
Our guest that we have with us today is Brigita
ye Dash. Oh gosh, I messed that up, but almost
so close. I was so close. I just yes at
the end because I yeah, yeah. I know he loves

(02:28):
making me say his name, and I don't like to
because I feel so judged. I don't even like talking
to the duo lingual lady, so.

Speaker 3 (02:37):
You can judge by me. But is like the most passive, aggressive,
soft drownd oh, I know.

Speaker 2 (02:45):
That's where I like, I hate talking to her. Because
I'm like, oh no, she's gonna judge me again, Grinta,
Welcome to the show. Hello, So would you tell the
listeners a little bit about yourself?

Speaker 6 (02:59):
Okay, so first of all, I'm from Poland, and in Poland,
now it's cold. I don't know why, because last week
it was around Okay, it will be in Celsius degree,
so pleased, I.

Speaker 3 (03:15):
Can tell Okay, I can delate too too.

Speaker 2 (03:19):
I'm the only idiot here. I know that fifteen point
five is about sixty, so.

Speaker 6 (03:24):
Okay, so it was around twenty three, twenty.

Speaker 3 (03:28):
Five, that's perfect, seventy four yeah, yeah, and.

Speaker 6 (03:34):
Now it's around I don't know, twelve, so it's super cold.
So I'm front and developer, as you know probably.

Speaker 2 (03:44):
Yeah, I mean we invited you that. Maybe you know
a little bit about.

Speaker 6 (03:48):
Yeah, ellen, but you know, I started like a full
seck developer, so I had also the back end, I know,
the back and part mostly the dot net dot net one.
And that's why Angular is my super besty friend.

Speaker 2 (04:09):
I think there's like a pipeline that just goes straight
from dot net into Angular.

Speaker 6 (04:13):
Yeah. Yeah, that's true because before Angular, I was just
you know, trying to learn playing JavaScript. It was like, please,
don't why I can assign everything to everything and get strange,
strange results, and why I don't have types and so

(04:36):
on and so on, And when I just went for
a workshop connected with Angular, it was like, wow, it's
my world.

Speaker 2 (04:48):
So yeah, I that was definitely my experience as well,
just coming from a type safe world and then coming
into JavaScript, which I like as an artist. I loved
the wild us the JavaScript, but as to accomplished tasks
at work, it was frustrating.

Speaker 6 (05:06):
So yeah, and I think that what m and in
my company two years years ago, I think, and we
organized some kind of small boot camp for people that
who want to start in IT world and it was
connected with front end. So we were teaching them and

(05:30):
they've got first exercise connected with JavaScript, and it was awful.
They didn't know what's going on there, why the application
is not working, and so on and so on. And
now I know that first they should start with typescript.

(05:51):
When they know a little bit how it works, they
can jump to JavaScript. But nope, not before. It's too
hard for people that that that are outside from IT
T world. It's it's crazy, really crazy for them. Okay,
but let's go to me, let's work again. Uh yeah,

(06:17):
I'm working in Avenga. I'm they're also some kind of
the lead of all front end developers in Poland. Okay,
so I'm also some kind of a manager. But I
don't like people. It's really hard to manage people.

Speaker 2 (06:38):
It's like, honestly, I'm so afraid that someday I'm going
to have to have people report to me and then
I'll have to like give them feedback and like.

Speaker 6 (06:47):
But you know, feedbacks are not you have to think
about feedback the nice, nice way. People mostly are good developers.
They are, I believe the feedback.

Speaker 2 (07:02):
It's the ones where you're like, dude, you're just I
don't know what to tell you, Like you're I need
you to do it different. Then I get anxious.

Speaker 6 (07:15):
Okay, so I think you figure it out. Yeah that's
so hard.

Speaker 2 (07:22):
I feel like, you know, I figured out how to
write code. I guess I could figure out how to
tell people that they need to stop doing something right?

Speaker 6 (07:28):
Would you just use CHATEGYPT or whatever?

Speaker 2 (07:32):
Please help me give feedback to this affect?

Speaker 5 (07:36):
How do I how do I say ABC in a
professional way?

Speaker 3 (07:45):
Now?

Speaker 5 (07:46):
One the one little tip for you, Lara good feedbacks
are not necessarily nice feedbacks, not always, so you'll be afraid.

Speaker 2 (07:57):
Yeah, I've learned. You're supposed to ask permission to get
the best results for feedback. If you aren't in a
position where you're supposed to be giving somebody feedback, you're
supposed to say, do you mind if I give you
some feedback about your talk? And if they say I
don't want to hear it right now, you're like cool, bye,
or they say yes please, and then you give them

(08:18):
their feedback. But I don't know so many rules.

Speaker 3 (08:23):
That's exhausting.

Speaker 6 (08:25):
At work, it's a little bit different.

Speaker 2 (08:29):
Yeah, Yeah, there's a lot more at stake too, and
people can get really anxious. And there's people like me.
If you say, hey, Laura, I want a meeting with
you and I'm going to give you some feedback, my
immediate response is going to be like, oh no, I'm
getting fired.

Speaker 3 (08:43):
No welcome to call for in America.

Speaker 6 (08:52):
Maybe somebody wants to give you a really really good feedback.

Speaker 2 (08:57):
What happens, But you know, it's like the like catastrophizing.

Speaker 3 (09:03):
Okay, and now I'm curious to people really schedule a meeting
to give you a nice feedback. Usually when I give
nice feedback, I would just send a sack message here,
I really appreciate what you did there. I usually just
schedule a meeting with someone if I have negative feedback,
I know.

Speaker 2 (09:18):
Right, I did get some good fee. Like it wasn't
good feedback. I actually got a raise and it was.

Speaker 3 (09:24):
Like that.

Speaker 2 (09:27):
A meeting on your calendar. And I was immediately like,
oh no, but it was just to go over the
rais with me, and that was really fantastic. But my
managers have learned when they work with me, they need
to say things like can I put I put a
meeting on your calendar? It's nothing bad.

Speaker 6 (09:43):
Yeah, but this is important to say it's nothing. It
is because.

Speaker 2 (09:49):
People like me, they're like what does this mean? What's happening?
And yeah, and then you spend hours just sweating.

Speaker 6 (09:56):
Yeah. I'm also like you if I get For example,
sometimes manager managers rights to me and do you have
fifteen minutes for small talk? And it's like, what's happening?

Speaker 4 (10:13):
Right?

Speaker 2 (10:15):
It's always on my team? Where are you moving me to?
What dumb project do you want me to work on?

Speaker 3 (10:26):
We have a very different work experience.

Speaker 7 (10:28):
Sorry, you know, mostly it's it isn't nothing bad, it's
just something normal, normal thing.

Speaker 6 (10:43):
But in my mind it's like, what's happening, what's going on?
I don't want to know now why it is?

Speaker 2 (10:52):
It's because I'm suspicious, all right. So you you're technical
leader on your team, you manage a people, and are
your teams writing Angular?

Speaker 6 (11:06):
Of course, yes, of course, but you know I also
have the React people. But it's some kind of uh,
you know, I want to one day, I want to
learn React. I try that. It was like, no, it's

(11:30):
not for me. I love Angila, Please I want to
go back.

Speaker 2 (11:36):
Yeah, I've definitely written some I've written some React. You know,
I'll work and if you pay me money, all write
whatever you're doing, right, I'm not too picky, but I
do prefer to write Angular. But yeah, React is in
some ways it's there's overlapping similarities and then there's also

(11:58):
like it's wildly different a lot of ways as well.

Speaker 6 (12:01):
Yeah, and for me it's messy. Sure, really for me
it's messy, but I know that for a lot of
people it's pretty simple. For me.

Speaker 2 (12:14):
Nope, yeah, yeah, And I think that's the feedback I've
heard too.

Speaker 3 (12:19):
So I was like crying writing and React on a
daily basis, right.

Speaker 5 (12:21):
Now, Yeah, you're right, I use I use React on
a daily basis at work.

Speaker 6 (12:31):
Yeah, all right.

Speaker 5 (12:34):
In my opinion, it's okay, Like for as long as
I work with it. The only thing is that the
overhead of keeping track of rerenders and React is a
little bit too much mhm. But other than that, I
think you can write best selfway anyway, and you can
write good software with it.

Speaker 6 (12:53):
Of course, it's only depends on your preferences if you
just like to write code Angular or Reaco something else.

Speaker 2 (13:03):
Yeah, okay, so you're you've got your teams, you're writing Angular.
Are you Are you in a position where you're able
to keep what version are you able to use at work?

Speaker 6 (13:16):
Oh? It's a hard question because we have a lot
of application. There's the lowest on.

Speaker 2 (13:25):
Sex and then there's the one that's on eleven.

Speaker 6 (13:28):
Yeah, eleven. Yeah, it's the lowest one.

Speaker 2 (13:34):
That's that's pretty good. I mean, we I have some
that I was told I owned that had It was
like it was some Angular JS with some four and
six mixed then, so it was it was something.

Speaker 6 (13:47):
But you know, this eleven version is with us because
we still don't have time to remove all you my
library of our client, and we can't upgrade because this
library probably written in Angular nine or something like that.

(14:15):
So this is a huge problem. Okay, it's one one
app rest is mostly version eighteen. I think, yeah, nice,
it's it's quite nice. I can use signals and a
lot of other cool stuff. But still I'm thinking, why

(14:36):
why I don't have a link signal? Why I need it?
Where is it?

Speaker 2 (14:42):
Yeah, it's like every new version is like it gives
you something else to be like, oh, but I want
to be able to use this in my I mean,
and sometimes it's on the minor versions too, like you'll
find you'll find something. You'll be like, oh, this is
exactly what I need to solve this problem. It's the
next minor version from where I'm at.

Speaker 6 (14:58):
Yeah.

Speaker 2 (14:59):
Yeah, my cat is over here purring into the microphone.
So if you listen anything weird, that's what that is.

Speaker 6 (15:09):
So.

Speaker 2 (15:10):
Uh. One thing I've noticed is that you are an
organizer of n g KTO.

Speaker 6 (15:15):
Yeah, so it's a meetup in Kato, Visa in Silesia.
Uh and you know, organizing Angular meetups. It was also
one of my dreams. I always wanted to do this.
I didn't didn't know how to do this because you know,

(15:40):
I contact some GDG people in Si Cilicia, but something
went wrong, right, and I just I was waiting for
for the answer if if, if we can meet or no,
do some thing together. But I'm not so patient, and

(16:07):
I just to ask my company if they could help
me and tell them. And the Kato's here and I'm
organizing it with my my friends. She's also from Katowitza
And yeah, in May we will have next a next meeting. Yeah,

(16:33):
maybe somebody is from from poland please came. It's on
twenty second, I think of n Yeah, I think yes,
so please go and.

Speaker 2 (16:46):
Make my second Now do you do?

Speaker 4 (16:48):
Uh?

Speaker 2 (16:49):
It looks like, let's see, I got your meet up
page of nice but yeah, so okay, So when you
organize the meetup, how do you go about getting guests
to present?

Speaker 6 (17:05):
It's super easy, really instead, yes, for me, it's super easy.
A lot of people want to be guests on our meetup.
So you know, before I started it, I had some
list of people that I want to invite, so I

(17:32):
just use it. And now a lot of people are
asking if they can say something on our meetup and
so on and so on and I also have I
hope so in September or maybe November, we will have

(17:53):
a few special guests, not from Poland. But for now
it's secrets. Okay, But you know Reiner was on our
second meetups, so I also was really grateful that he

(18:16):
he joined us and give a talk.

Speaker 8 (18:19):
Come from Austria, yes, gotcha, Yeah, but his sermon name
is also hard and I don't want to crown out
for me.

Speaker 9 (18:31):
No, doesn't count Austria because it's almost I'm not gonna
say it's the same country, but it's similar.

Speaker 3 (18:42):
Better, not like you would say Florida is the same
like same country.

Speaker 2 (18:47):
I know, yes, and they will say something different in Florida,
but like the base of the like the bases close enough.
But I'm going to stop getting myself in trouble with Mike,
is okay? So is the meetup in person or is

(19:08):
it online?

Speaker 6 (19:09):
In person? Of course? You know, it's important, important for
us to build some kind of the community because you know,
before pandemic, I think we had had a meet up
angular Silesia. It was in Lewitza, it's around. It will

(19:29):
be also in kilometers.

Speaker 2 (19:31):
That's I used to run. I know how this works.

Speaker 6 (19:35):
Right, So it's around thirty kilometers from a Katoviza. So
we have that some mid JS meetups, the community was
quite quite big, and after pandemic, you know, probably as
everywhere it was, it was hard to organize something new

(20:02):
and so on and so on. Try to organize it.
And I think that we have a quite nice audience
because it's around thirty people more or less. I know
that other meetups have more, but I think that for

(20:23):
us is a quite nice number because on the one
side it is quite a big number of people and
on the second is still nice atmosphere and all people
could talk to each other. So I think it's nice.

(20:45):
And you know, we we don't want to do it online.
Now we are trying to record it, but it's still
like you know, I use my phone. I have microphone
because I using it for recording my shorts and so

(21:06):
on and so on, so I have it, and on
the last meetup we just try, okay, we will do
it use your phone and mike and we will see
what happened. And now the recordings are waiting for me
because you know, I us there's something with them and

(21:27):
probably maybe I hope next month they will be published
on Angikato YouTube channel. And I hope also the next
meetings will be recording. We will see, we will see
what's happened.

Speaker 2 (21:45):
I feel like getting your your technical power is down
like that is you know, it's I think that that
was something that a lot of people had to learn
really fast during the pandemic because we never did stuff.
I mean stuff didn't happen that much online. Some things
did but not very much, and it was having to
figure it out really.

Speaker 6 (22:06):
Fast and how to do this? Yeah yeah, yeah, I
know all conference all conferences online and that was like
whoa well.

Speaker 2 (22:15):
And I think we all saw how like some of
them had technical problems like certain platforms to perform well,
Like there were definitely issues that way. But you know,
I think to go back to the in person number,
like thirty is great. That's a great number because you
can actually like really get to know some of the
people that are there, start to build relationships, and honestly,

(22:37):
it is those relationships that keep the community strong. It
feels so good to walk into a conference and and
seal friends.

Speaker 6 (22:48):
Yes, I like it so much really now when I
know more and more and more people and I could
go for for example, last time I was on engine
Bend and it was super cool that I can can
go there see a lot of people that I know,

(23:09):
talk to them and feel more or less like with
my friends, my friend group, you know, yes for life. Yeah,
before it was like you know, you are only one. Yeah.
It was my first Angular conference was in Jipoland and

(23:36):
I was alone there and you know, I was just
walking there and go from one cent to another, drink something,
go to the and the cinema room. It was awesome. Yeah,

(23:58):
but I feel a little but lonely there.

Speaker 10 (24:02):
Sure sure there when it was twenty nineteen, I think, yeah, And.

Speaker 6 (24:11):
She didn't say Hi, I didn't know you.

Speaker 3 (24:17):
I was on stage.

Speaker 6 (24:22):
I'm shy. I'm really shy.

Speaker 2 (24:24):
I feel that like and and I think it takes.
I've had very few people at conferences that come up
and just start a conversation with me. And I am
extremely approachable. I mean, like I go when I'm at stores, No,
I am when I'm at stores. Everyone thinks I work
at the store because I think I have Can I

(24:46):
help you face? But you know, it's like we're you know,
I think it's it's weird being at conferences. I know
that when I go to like a p conference, like
a dot net conference. Sometimes I go incognito mode and
I just pretend like I don't really know anyone.

Speaker 6 (25:10):
Sometimes also cool.

Speaker 2 (25:13):
Sometimes it's nice to just be like, eh, I might
just disappear for the rest of the day, totally fine.
And that is hard to do at an Angular conference
because like the minute you start to try to disappear
to go back to your room, everyone's like, hey, Hi,
good to see you. It's like, this is great, but also.

Speaker 6 (25:35):
I need to go to the toilet.

Speaker 2 (25:36):
Yeah, exactly, I need some alone time. I'm not gonna elaborate,
but yeah, no, that's a that's a really great number.
So yeah, definitely, if you're one of our listeners and
you can get get to where the meetup is happening,
it's a great opportunity. I have people write me all
the time how do I get involved in the Angular community,

(25:57):
And I'm like, if you can go to a meetup,
go to a meet up.

Speaker 6 (26:01):
Yeah, it's a perfect opportunity.

Speaker 2 (26:03):
It really is, It really is. And so how long
have you been doing that meetup?

Speaker 11 (26:10):
I started last year in septemberdition to organizing this meetup,
you also do speaking, yes, So what has been So
what have you been talking about the last like the
last few talks.

Speaker 2 (26:27):
What has been your favorite topic to talk on?

Speaker 6 (26:30):
My favorite topic is of course SSR.

Speaker 2 (26:35):
Yeah, and that's something happening in Angular around that.

Speaker 6 (26:38):
Right, It's happening a lot of things. But you know,
SSR now is it. I didn't want to say something
new because it's not you it's a hot topic. And
now if you want to use SSR, now you can

(27:02):
use it in you know, not a proper in a
proper ways. It's working. It's just working.

Speaker 2 (27:10):
Yeah, yeah, it's no longer doing that like not that
destructive hydration.

Speaker 6 (27:14):
That yeah, destructive hydration, that's it. It's not hydration, destructive qrydration.

Speaker 2 (27:20):
Yeah. Yeah, so it's yeah, like I know that SSR
has been around for a while, but uh yeah, it
hasn't really been a great experience in Angular until they
managed that the destructive hydration problem. So for the listener,

(27:42):
if you don't know what destructive hydration is used to
be that when Angular could server side render, render that
application on the server, send it to your browser, and
then your browser has to rerender it to attach all
the javascripts, and it would just destroy the dom and
put it back in, so the the users saw page flicker.

Speaker 6 (28:03):
And we don't like it.

Speaker 2 (28:05):
Yeah, And because also you know, if you if you're
coming from the dot net world, if you're coming from
like ASP or some of these older dynamic server rendering
UH languages or frameworks, you that's like the full post back, right,
that's old school application and people see it like you

(28:27):
can trick yourself and say, nobody notices that the page flickered,
but they definitely did, because it's not an experience that
modern users of the Internet expectancy. So your topic of
choice has been SSR. Can you tell me so for
a listener who's thinking, maybe I need SSR at work,

(28:47):
because I think that every manager out there, not every
manager obviously, but like a lot of managers who maybe
aren't maybe shouldn't be the ones making technical decisions, we'll
say things like we need to do SSR.

Speaker 6 (29:03):
And I think, no, please.

Speaker 4 (29:08):
Please.

Speaker 2 (29:09):
What are some of the guidelines you would UH give
people when trying to decide if SSR is right for
their application.

Speaker 6 (29:17):
First of all, you have to think if your application
is used outside of your company network, Yes, it's first point.
If it is, you can think about SSR. But but ah.

(29:38):
You have to also think if you have some problems
with initial initial load, if it's too slow, you can
consider it, of course, because SSR is pretty pretty gool
too for better initial load, because you know you you've

(30:00):
got just uh uh this HTML render on the server
and then the hydration uh kicks in and you got
all Java script and so on and so on, so
bundles smaller. Also if you have this uh pre uh

(30:20):
maybe not pre render because it depends what you choose,
is just so far or or s SG, but you
have have this h h mile oh sorry, uh hml
rendered on the server. Also, co web vitals are better

(30:45):
because you know it's it's just you just get it. Uh.
So all these metrics should be better. And if if
you cared about se O, of course it will be
a very very good score. But it's always but right,

(31:11):
you know.

Speaker 12 (31:12):
I I say that as a sorry is not for
all applications, and you have to consider it because it's
not simple concept.

Speaker 6 (31:26):
I know that a lot of people just struggling. For example,
it's the most common question why I've got an error
a local storage is not defined? It's like, hm, why
because you're on the server. In answer, you don't have

(31:48):
local storage. So I think that people should just go
deeper in this concept. Know how it works, Know that
what is the server site rendering SSG, what's going on
the browser when it's hydrated? How how it could be

(32:10):
hydrated because now we have also incremental hydration. So and
we have a lot of problems with hydration because you know,
if you are using some kind of third party LOPS,
which is using them manipulation, it's problem. It's it's it's

(32:34):
a really huge problem. And you can check for for
other library which is okay from the SSR point of view.
You can use skip hydration, but it's a huge you know,

(33:00):
it's like for a minute, because if you skip hydration,
you uh, this part of the dom will be destroyed
and we render as you said before, So it's not
a good solution. I think.

Speaker 2 (33:19):
Temporary solution, yeah, until you can fix the problem and
then yeah.

Speaker 3 (33:24):
Yes, good morning. You know that moment when your coffee
hasn't kicked in yet, but your lag is already blowing
up with Hey did you hear about that new framework
that just dropped? Yeah, me too. That's why I created
the Weekly Death Spur, the newsletter that catches you up
on all the web depth chaos while you're still on
your first cup. Oh look, another anger feature was just

(33:47):
released and what's this typescripts doing something again? Look also
through the poor request and change slot gramma. So you
don't have to five minutes my newsletter on Wednesday morning,
and you'll be the most informed person in your standard.
That's better the wiki desper because your brain deserves a

(34:10):
gentle onboarding to the weeks tech matness. Sign up at
weekly brew dot Depth and get your dose of deaf
news with your morning caffeine. No clickback, just the updates
that actually matter your Wednesday morning soltwill thank.

Speaker 6 (34:23):
You for example. You can also think about deafer use
the defer, but it depends if you need this I
don't know, charge or whatever right away, because if you
use deafer it will be rendered on the client side.
Of course, you can't use the deafer with hydrate drinker,

(34:49):
and of course you should use deafer with placeholder, and
if you don't use it, you probably have to deal
with some layout shifts and so on and so on.
So it's always a problem. But what is also nice,

(35:12):
I don't know it's nice. And we have death tools
Angular death tools, and there you can check which of
your components are hydrated, and if something is broken, you've
got there an error that this or that component had

(35:34):
had a problem with hydration and you could probably fix it.
What else?

Speaker 10 (35:41):
I think there's a lot of different catchy I think
the dept tools are really great because like, if it's
server rendered, it looks fine.

Speaker 2 (35:54):
Because it renders the way it looks. It doesn't render
how it behaves. And so you might be thinking that
you're clicking a button and your button's broken. It's like, well,
your button's broken because it's not actually hooked up to
the JavaScript. So yeah, it didn't hydrate properly.

Speaker 6 (36:10):
What's one more thing with you know this hydration, but
it's mostly the with incremental hydration or with the fur block.
When I was just playing with incremental hydration and probably

(36:32):
it was Angular nineteen and I had problem because I
was checking if, for example, my component was hydration after
I don't know, could it be on Hoover but it wasn't.
It was hydrated right away, and I was why I

(36:56):
don't have this lazy loaded change and why is hydrated?
What's going on? And I spent I didn't know quite
some time to figure it out. And you know, in
I think in Angular nineteen, we've got this a hot

(37:18):
Modo replacement by but it was by default, and I
just think, oh, maybe it's this, and I used the
comment you know ng as a Dutch snow HMR and
it's worked, really and you know it should be obvious.

(37:44):
Why yeah, it doesn't work if I had not module replacement.
But still in my mind it wasn't, so I really don't.
I didn't realize that the hot model replacement is there

(38:06):
and I'm using it and so on. And I know
that a lot of people had the same problem, and
I also create a short about it, and I think
it's my most popular short. Nice and people people just

(38:28):
needs some small information that you know, you can just
turn it off and everything is working. I think that
also Jessica and Mark had the same problem and when
they had a Q and A session and they also
realized that after you know, a few minutes and oh yeah,

(38:52):
that's it.

Speaker 2 (38:54):
Yeah. And I love what you said though, that you
made a video short about it, because that is one
of the ways that like chances are, if you run
into an error or a problem, you are not the
only person who has experienced it. Yeah, now with literally
everyone who experiences it never writes about what they found
and how they fixed it. I mean it's stack overflowed, right, Like,

(39:17):
this is why stuff like stack overflow exists. It's because
none of our problems are really it is very rare
to an encounter a problem in software engineering that no
one has solved before. I'm not saying there aren't problems.
I mean how I feel like you probably have a list, Chia.
I was like, well, there was this one, and then
there was this one, and then there was also I

(39:38):
tried to do this one thing that no one's ever
tried to do. But you know, like in your everyday job,
you know, unless you're trying to really push the boundaries
of what the framework can do, like most of the
problems somebody has already run into. And so it's really
great to share that back with the community.

Speaker 6 (39:58):
And yeah, yeah, and you know, because I think that
this as ASR topic Angular, it wasn't so popular before,
you know, it had this Angular universal but now as
a SR is a part of the framework and it's changed,

(40:20):
you know, and now the community using a SSR in Angular.
Of course, I don't think it's so so big, and
also in you know, commercial projects. I know a few
people who are using a SSR, but they are they

(40:44):
were using as an SR before version seventeen, so they
were using also Angular Universal because they need it. And
I think that a lot of people who who who
is now application Angular application, probably they don't need a SR. Yeah,

(41:12):
if it's works now, they probably don't need it. But
it's now Angular finally opens the door for some new
type of application where we can just think, Okay, now

(41:34):
we can use Angular, not next, Jase, I hope, So
I guess.

Speaker 2 (41:41):
Yeah, And you know I think too, like I think
to your point, like it is hard. So it's not
like there's no overhead when you use SSR, like you
have to then maintain the server that's rendering the application.

Speaker 6 (41:57):
Of course, and it's costs l such.

Speaker 2 (42:00):
Money exactly exactly. And you know, if you work, you know,
like I know at Cisco we have we can't just
spin up servers and point them and let people have them.
And you know, like there's all these processes involved with
setting up our infrastructure correctly following the guidelines, meeting all

(42:20):
our security standards, and so it's not simply simply spin
it up and then let people use it. It's like
it's a it's a process to get there as it
should be right.

Speaker 6 (42:33):
You know, like yeah, of course, especially like if you're dealing.

Speaker 2 (42:36):
With financial records, like please please be very careful. But
you know, and and so I think there's also so
if you were if you were working on a project
and somebody said, we have performance issues, we want you
to use SSR, what are some of the things you
would look at before you decided that SSR was the

(42:59):
right ways.

Speaker 6 (43:02):
Probably first of all, I will think about our complexity
of our project, if we could do something back before
using FOSR. I think it's sometimes I think we can
compare it with micro services because a lot of people say,

(43:25):
don't use micro services at least if you're right, you know,
if you're super super super superheded that you can use it,
but before just try everything before it. Yeah, you know,

(43:46):
I think that as a star is a cool feature,
but you have to know how it works, and you
have to have money for the server. Yeah, it's everything.
It's really for me, it's really complex because you know,

(44:07):
you can investigate the project. You can for example, I
can do it, but my people also have to know it.
If not the time of debugging application, fixing bugs and
so on and so on, the time will be longer. Yeah,

(44:29):
and and pro probably.

Speaker 2 (44:32):
I like that point that, like you have to also
think about your teams that are maintaining the code, because
you know, for a very basic application, it's very easy
to turn on SSR or a new one, right, Yeah,
get SSR. You can spin it up right out of
the box. It works fine. Right, but but like the

(44:55):
minute you start, like do you use D three? Guess
what that does? Drip relations.

Speaker 6 (45:01):
So that's the problem.

Speaker 2 (45:02):
You're going to have to initialize that in one of
the render hooks, right, Like you're going to have to
figure like you're gonna have to know how to set
everything up because, like you were saying, you can't do
browser things on the server.

Speaker 6 (45:16):
Yeah, and you mentioned this new hook after next render.

Speaker 2 (45:21):
Yeah.

Speaker 6 (45:21):
Also we have some kinds of some changes because first
it was after next render and after render.

Speaker 4 (45:29):
And we have also I think there was a new
meal living running Anglo API documentation is after render.

Speaker 5 (45:40):
Effect they're considering dropping the after render or rename it
after next render is like Angie on in it but
after next render only runs on Clan side, so they
do not run on suicide, whereas Angie on in it
will run on both side.

Speaker 2 (45:59):
Yeah, so the the after render is where you would
put initializing code that has to run on the browser.

Speaker 5 (46:08):
Like, actually no, so after render runs great?

Speaker 3 (46:12):
Well, actually.

Speaker 5 (46:15):
I planned the Angler team for naming for the bad
naming conventions, but like after render means it's after every Yeah,
after the next render is I didn't run.

Speaker 2 (46:32):
I ran into that because I was doing a course
that covered it slightly, and I ran because I'm like,
after render runs every time. So you want to be real,
real careful about what you put in there because it's
like do check or something or.

Speaker 3 (46:47):
Check Yeah, yeah, yeah, I have two questions. Okay, okay,
go find No, no, no, you had such a great moment,
so please go ahead. Okay.

Speaker 5 (46:58):
So my question is, so we all all know that
Angler team is right now is focusing more on ssr UH,
and some of us might actually know what they're working on.
What they're focusing on right now. For example, they try
to bring in like more Nitro for for for listeners
that who don't know. Nitro is a technology that allows

(47:19):
you to run your servi side JavaScript code on different platforms.
So not just no jest, but it's like also cloud
Furna and all the stuff, which is great, But to
me personally, Angler SSR is still very limiting compared to
the other solutions in the ecosystem. So I want to

(47:42):
ask you what would you like to see in the
Angler SSR solution. For example, like in the future when
they when they announce the next SSR future and I
go and I a new application Angle application with SSR,
what should I be able to do? For example, if

(48:03):
I initialize a new Remix application right now, this is
my that's my completely full stack application, so I can
build my route components in there, SSR route ASSR routing.
I can also build my API routes alongside with that
using the same server to serve the application. Anglass I does.

Speaker 4 (48:24):
Not have that.

Speaker 5 (48:25):
So that's my wish for anglans.

Speaker 6 (48:27):
It's a great wish. It's a great wish, I know,
you know, I just they think in uh just as
a star topic in Angular. And it's also I know
it's quite new for me, so I'm discovering it. But

(48:51):
your wish it's perfect for me. And I know that
this is not now, it's not idea, but still it's
better and better, and that's why I think it's a
good good time to learn it. How it works step
by step. It's some kind of like with US signals.

(49:14):
What signals are simplier for me? Yeah, you have to
learn step by step everything and if it's important for
you maybe someday. I also was like all all these people,
Yeah it's new feature. I want to use it. And

(49:34):
I also was considering first maybe I could use as
a star in my project London. I think no, it's.

Speaker 2 (49:43):
Yeah, it's so hard to get like we tried in
Are the project I was on, and we just ran
into so many, so many roadblocks. It's public facing, and
really what it boiled down to you was our bigger
issue isn't how fast the browser renderers. We had a
couple of performance issues we worked on and we got
our bundle sizes down. But as our APIs or APIs

(50:04):
are slow, RPIs are slow, it doesn't matter how fast
your server renders your code. It's just going to sit
in way for that data to show up.

Speaker 6 (50:11):
So yeah, that's true. Also in my work it's the same.

Speaker 3 (50:16):
Yeah, that's not.

Speaker 2 (50:18):
To dig on my ape like the data that they
got to.

Speaker 3 (50:20):
Get us is tomorrow you have a meeting on your calendar, Like, it's.

Speaker 2 (50:26):
Not your fault. No, Like there's there's reasons and a
lot of us inherited that code from previous teams. Oh yeah,
you do the best you can with what you get,
and so I just want to acknowledge that.

Speaker 6 (50:40):
But but yeah, sometimes you don't have pagination, or you
have pagination, but in your pagination you have landhouse and eelements, so.

Speaker 2 (50:52):
Right or at points that all handle it slightly different.

Speaker 3 (50:57):
That's what That's what I ran into at work.

Speaker 2 (51:00):
Yeah, yeah, definitely you.

Speaker 3 (51:03):
Had some uh trut to answer your question single flight
mutations from ten stax start or solid start. Wait what
single what single flight mutations?

Speaker 12 (51:16):
Uh?

Speaker 5 (51:16):
Single file mutation? You mean like putting the civil codes
of a psyche code and.

Speaker 3 (51:21):
It's basically on top of your API routes. But mutations
with the way that there are structured. I think even
in Remax there are basically two requests to handle the
update process as well, so like back to the UI, Yeah,
I think I think it's basically like a post and

(51:43):
then a get and solid are I think, Okay, I
think that's how Remix does that.

Speaker 5 (51:53):
No, in in in remix, you you would do your
mutation and is the default behavior is that when a
mutation happens on a route, the hierarchy of that route,
like all the ancestor up to that route will get revalidated.

Speaker 3 (52:12):
Well but okay, but that's a react issue.

Speaker 5 (52:17):
I mean, yeah, it's how remix works.

Speaker 3 (52:20):
So I'm not sure about this single file mutation. But
I had a very similar question on that because I
was wondering. I mean, we had a mediocre this is
our story for like what eight years. Do you think
spending the time and effort and at the end of
the day money to implement an SSR story is the

(52:42):
best use of the younger team's time.

Speaker 6 (52:49):
You know, For me, this feature was waiting into waiting
a lot of years for for some action. So I think, yes,
it's it's a good choice to improve it and do

(53:09):
it in the proper way.

Speaker 3 (53:13):
I disagree. I I disagree. I think spending time to
implement VT and vets would be such a better use
of time and resources.

Speaker 8 (53:24):
You can help it, help them, fair, they can ask
for zero for that.

Speaker 3 (53:30):
I don't care. Fair fair.

Speaker 5 (53:32):
I can see that.

Speaker 2 (53:34):
I like the I like the like this the routing
where you can now at the route level declare whether
it's server or static.

Speaker 3 (53:45):
Or I agree it's important. But if you're eight years
and like front end years didn't care for.

Speaker 6 (53:52):
It, but you know you can than never.

Speaker 3 (54:00):
That is all true, But then that's some single API
I said, I'm not flashed out yet, like forms for instance,
or oh yeah, or double imports. I don't know. I
don't think it's about I think it's important, but I
think it was important seven years ago.

Speaker 6 (54:16):
Yeah, it was waitin but this space, you know, I
think there was like a queue.

Speaker 2 (54:25):
But I think seven years ago, like like IVY was important,
and like I think that is a lot of stuff
that had to get fixed years ago, but now we
are reaping the benefits of.

Speaker 3 (54:38):
That is true. I post IVY it I would have
liked to see now. I think I would have even
liked to see it before IVY.

Speaker 2 (54:46):
Sure, sure, I mean we were also at this point
right where like we had server rendered everything forever and
everyone was like no everything in the browser, and so
there was sort of a boomerang. Like I feel like
it's one of those things where it kind of bounces

(55:07):
back and forth where we're like everything happens on the server.
That's inefficient. Let's do everything on the browser. Oh, it
turns out that's not a good idea either.

Speaker 6 (55:14):
So I.

Speaker 3 (55:16):
I mean, in general, I agree, but like all the
other front and frameworks had it. Sure, sure, like next
has been around for I don't know how long NEXTUS
has been around for.

Speaker 5 (55:29):
Well, my hot tech sorry now that you brought that up.
Actually my hot tech is Angle team should collaborate with
Brandons agree with that.

Speaker 2 (55:40):
Yeah, yeah, I think, but it's nice to have the
doors open in it so it enables people to do
more with it. Like, yeah, I don't know, it's it
feels kind of like like, Okay, I shop at all
the and sometimes I just can't get some things there.
And maybe that's the choice you make when you pick
a framework. And so now they're like, we need to

(56:03):
book out our SSR section, and so you're like, I
think I'll buy some partial hydration and but yeah, that
is a complaint I've heard often actually and more than
once on this podcast, not even just from you.

Speaker 3 (56:14):
Yahn, sorry that they didn't implement SSR, that they implemented it,
or that they're not collaborating with brenton. What is this
complaint in this context?

Speaker 2 (56:24):
There were a lot of statements that were made right then,
basically that Angular was late to the game with SSR
in a lot of ways, it hurt adoption.

Speaker 5 (56:33):
Yes, yes, would you recommend like starting a new project,
I would say, like a like a regular web application
project where SSR might be needed but maybe not initially.
Would you still recommend starting with SSR, uh with not
with with with.

Speaker 3 (56:54):
No hold on?

Speaker 5 (56:55):
Hold on with the possibility of using the civil civil
route configuration where you set everything to clean side first.

Speaker 6 (57:02):
Now it's quite cool because you can say, okay, it
should be clients side render or SSG or SSR, you
can peak. It gives you fine, very nice flexibility. So yes,

(57:23):
but yeah, but it's you. I think that your team
should know how it works. Yes, it's it's really important
and probably you know that when people don't know the framework,

(57:46):
library whatever, So it's it's messy. It's really messy when
they're trying to learn something. And sometimes it could be
like like you know, they they did a lot of

(58:09):
crappy things and then they figure it out how we
have to rewrite everything because we have we have some
problem that we don't know how to resolve. Now, so
I I always think that you know, it depends you

(58:30):
have to think about a lot of a lot of things.
You could get some bonuses, but also you can get
a lot of people.

Speaker 2 (58:45):
Is there sure? Yeah, I feel like when you're starting
a project, like I like what you're saying, Chow, Like,
it's kind of like you can add NX from the
beginning too, and like either you use parts of it
or you.

Speaker 6 (59:00):
Don't like but still you need to have a server.

Speaker 2 (59:04):
Yeah, yeah, you still need to have the server. But
at the same time too, it's not okay, it's not
too terribly bad to put it in later. The problem
is that if you've got bad habits, or you're doing
direct dom manipulation, or there's things that you're doing like
accessing storage, like those things are gonna make it harder

(59:27):
to just turn it back on again. If you've got
an app that just like follows some certain set of
rules like turning it on, turning it off is easy.
Like I've I've put SSR into apps and it works
fine because they're usually cute little demo apps that don't
really do very much. So but yeah, I think definitely
knowing your project A is this even a candidate for

(59:49):
SSR right, Like, will I ever need SSR on this?
Like you said, is it client facing? If it's not,
it's probably not worth it. If it like sits behind
uh some process that takes a while, it's probably not
going to help. Like if your login process takes a while,
it's not gonna help. That's faster, you know. Could you

(01:00:14):
pre render if you're out like maybe like maybe that's
the way you go, like, oh this this is just
always static content. I can just pre render this and
those which should go really fast.

Speaker 3 (01:00:23):
I don't know.

Speaker 2 (01:00:23):
I think it's it's an interesting question. Would child you
do that?

Speaker 5 (01:00:28):
I would, Yeah, just from the deployment standpoint alone, so
you don't have to okay, so you.

Speaker 2 (01:00:35):
Don't have to change your point That makes sense. That
makes sense because then your resources are there from the
beginning and you're not having to figure it out. So
that makes sense.

Speaker 6 (01:00:44):
Yeah, And probably your point of view is also a
good that if you turn it on and do something,
if you have a server sight render, you will get
an error about hydration if you just uh, just some
dumb manipulation and so on and so on.

Speaker 3 (01:01:05):
So yeah, and I and I do think.

Speaker 5 (01:01:08):
Turning on s s R from the beginning kind of
promote good practices in terms of like leaning onto dependency
injections more like, hey, and so, I don't write Angler
on the day, day to day basis anymore, but I
do maintain libraries and Angler is that I uh I

(01:01:30):
encourage everyone to uh to. So if they contribute like
a new function or something like that that uses depicit
dependency jection and that relies on the document, I always
call out, hey, use the document token. Use the document token.

Speaker 2 (01:01:46):
Yeah, yeah, that makes sense. Very cool.

Speaker 3 (01:01:51):
On that note, though, would you, if you anyway go
the SSR round when would you DIFFERENTI okay, I should
go with something like analog, or I should stick with
plane anger SSR.

Speaker 5 (01:02:08):
That depends on whether or not I have an assisting
back end. If I don't, I might lean toward more
analog chass that I can define my back like API
rouse alongside with my application. I don't have to worry
about the proxy andes all this stuff. But if I
have like a separate back ends, then yes, probably just

(01:02:29):
Angler SSR.

Speaker 6 (01:02:32):
But yeah, but I.

Speaker 5 (01:02:33):
Do hope Angler SSR like he's improved more and more.

Speaker 2 (01:02:39):
But yeah, yeah, I mean I think we've gotten quite
a bit in the last few releases, it feels like
you're like looking back at like sixteen seventeen, we got
just sort of hummeled with stuff almost like like yay,
it's a lot, like everything's great, but also like it's
a lot to take in and learn. It feels like

(01:03:00):
now they're kind of getting a lot of what they're
kind of going back internal and there aren't as many
new like public things that are happening where it's like
a feature I have to learn how to use. They're
kind of working more on some.

Speaker 6 (01:03:12):
Of the Again, now a lot of things will be
just stable in version twenty. So yeah, for me, it
was also hard to you know, you have a lot
of new things and when when you can use it

(01:03:33):
play with it because at work, okay, I have now
version eighteen, but in version eighteen we have for example
Eric's resource and so on and so on, and now
I can just play with it in my pet projects

(01:03:55):
and sometimes also when I'm creating a content or for
YouTube channel, I need to have the time to just
check it out, it works, what I can do with it.
And normally if you have a lot of new features, yeah,
you don't have time to check everything and learn everything,

(01:04:19):
and sometimes I feel that. Ah, I like with this
new hook after next effect. Yeah, yes, I just heard
about it, not heard, I read about it because because
one of my colleagues just post a post.

Speaker 12 (01:04:43):
Yeah, so it's now.

Speaker 6 (01:04:48):
It's a lot of new things to learn, uh, and
I just want to use it. But but still I
don't have time for it. And probably a lot of
developers don't have time. I feel that most of them
just playing with new things in their projects at work.

(01:05:13):
And if they don't have Version high teen, they couldn't
do this. You know, probably you also have your own
life after.

Speaker 5 (01:05:25):
Work is doing what is that?

Speaker 6 (01:05:31):
I'm with?

Speaker 2 (01:05:31):
Cats keep yelling at my house. I don't know what's
wrong with them, but.

Speaker 6 (01:05:39):
They are waiting for you like mine.

Speaker 2 (01:05:43):
Yeah, it's usually my cats actually have teenagers, so they
don't really need me very much. It's the cats that
need me the most. I like what you're saying. I
think there is a lot of pressure on engineers to
learn everything, literally everything, all the time, and it is
like drinking from a fire hose, there is so much.
The way I handle it is I learned what I learned,

(01:06:04):
what I need to learn when I need to learn it.

Speaker 6 (01:06:06):
Mm hmm.

Speaker 2 (01:06:07):
You like, oh, I'm gonna do SSR, Like, is SSR
the right choice for work? This week, I'm going to
become an SSR expert because I need to go figure
it out. I need to find out if it is
the right choice for work.

Speaker 6 (01:06:18):
You know, and you know, most or less, if you
are joint using some feature in your daily basis, you
forgot it. And it's like, that's why I have my
shorts and I go there, Okay, you know a.

Speaker 2 (01:06:33):
Lot of them are just for me really, because I'm like,
what did I do?

Speaker 3 (01:06:38):
So I'll probably get kicked out of the GD program after.

Speaker 5 (01:06:41):
This podcast episode because I'm gonna I'm gonna I'm gonna
blame on them again.

Speaker 3 (01:06:46):
I'm gonna blame on the Angler team again.

Speaker 5 (01:06:48):
So I'm gonna right on top of the content creating
like content or surrounding new stuff, new Angler stuff, and
specifically SSR. He's that with the current state of the
Angler SSR, it is really really hard for content creators
to just focus on Angler without bringing in another technology.

Speaker 4 (01:07:11):
Right.

Speaker 3 (01:07:12):
So again, for example, if.

Speaker 5 (01:07:14):
I want to build a I want to make like
a tutorial with Angler SSR full SAC application, there is
no way for me to just use angler for that
full Slack application, I have to bring in a different thing,
which is an additional burden for the content creator itself
and also the burden for the viewers now they have

(01:07:35):
to worry about, Hey, do I need like a different
server for my endpoints and all of that stuff.

Speaker 2 (01:07:41):
Yeah, I absolutely agree with you. It is. It's also
really really difficult to create a sample application that comes
even close to replicating any of the real problems you're
actually going to encounter, Like it is almost impossible, like
to you know, I can do very very trite examples

(01:08:06):
where I'm like, and here is this. It's very simple,
it works like this, and it's like it's not very complex,
and literally only I have coded it, so it's like
I know what all my patterns are and and it's
really hard to replicate those problems. I think that's why
it's so important for people. So if you are working
on a large product and you are using SSR and

(01:08:27):
you run into something and you have to solve the problem,
that is like where we need the community more than
ever to say this happened to me, this is how
I fixed it. You know, this might happen to you,
and because somebody else out there is probably having that
exact same problem. But yeah, and then content it's so hard.
The one thing I will say, though, is for companies

(01:08:49):
that lag a few versions behind, they get the benefit
of hindsight. So you can say, on version sixteen, I
know which parts of the signals API made it into
stable release, so I know if I make it to
version sixteen, I can use this and this without having
to worry about it not being stable. Later, John's shaking

(01:09:11):
his head now at me.

Speaker 3 (01:09:13):
No, I generally agree. On the other hand, if you
use experimental or death preview APIs for your production weld,
it's your own fault.

Speaker 2 (01:09:22):
No, no, it is. That's what I'm saying though, Like
if you if you're like, I really want to get
to version eighteen, but right now I made it to
version sixteen, and I'd like to use signals like use
the right ones, use the composables like.

Speaker 3 (01:09:33):
I get that. But the sentiment is the same of
people bitching when they use deprecated API and be like, oh,
I cannot upgrade. The anger upgraded story is so bad.
I'm like, no, you're just dumb.

Speaker 2 (01:09:46):
Like the people when they're following an online recipe and
they're like, I made this carrot cake, but carrots have
too much sugar, so I put kal in it and
it tasted terrible, the.

Speaker 3 (01:09:54):
Worst besides the fact that cops us a useless metric
for recipes. But that's another story.

Speaker 5 (01:10:01):
Let's just let's just all wait for signals to get
to native JavaScript, right.

Speaker 3 (01:10:09):
So everyone that I talked to on that, they're like, well,
the signal proposal is just for frameworks, so I should
developer care about that. So why why do you think
it will change anything for you? Do you really think
you're going to use native signals when signal two point
zeros r a solid as RV, Like, well, we have
no acing signals to the lure exactly.

Speaker 6 (01:10:32):
Yep.

Speaker 3 (01:10:34):
Sorry, very tangent, unlike us entirely.

Speaker 2 (01:10:42):
All right, Well, so as you guessed, we could go
on for hours. Eventually my boss will ping me and
ask me where I am.

Speaker 3 (01:10:52):
It's a meeting on your calendar. I've got some feedback
for you, Laura.

Speaker 13 (01:10:55):
Oh no, I'll be like what you'll see on the
this video chat is that I go white as a ghost,
and then like I get real quiet, and I stop
talking and I do a lot of like I'm on
my phone because.

Speaker 3 (01:11:12):
Yeah, you guys. You guys saw me ton off my camera?

Speaker 6 (01:11:15):
Are you?

Speaker 3 (01:11:15):
Yeah? If something happened, how I need to talk?

Speaker 6 (01:11:23):
What is this? Wait?

Speaker 3 (01:11:25):
Victis the intimidated me until to stay?

Speaker 2 (01:11:28):
So Alex was still on my team. Alex and Krusko
used to like, he's he gives feedback, like he will
give you feedback and it is valuable and I'm I
am so thankful for him doing that. But I always
was like so worried that it would just be like
you're terrible at everything you do. It was never that,

(01:11:49):
but that's always like that's the imposter syndrome. It's still there.
It still creeps around in the back of my mind
and tells me that like I'm doing something wrong. But
and I totally am. Two years from now, I'm going
to look at my own code and be like, why
are you?

Speaker 6 (01:12:05):
But it's normal. It's totally normal.

Speaker 5 (01:12:09):
Yeah, this is exactly what we talked about in the
last episode.

Speaker 2 (01:12:12):
So, yeah, I heard. It was a lengthy conversation.

Speaker 3 (01:12:21):
It was fun. I enjoyed it.

Speaker 6 (01:12:23):
Yeah.

Speaker 2 (01:12:24):
Yeah, that's what we love about community.

Speaker 6 (01:12:26):
Right.

Speaker 2 (01:12:29):
Well, we're going to thank you so much for joining
us today. Was there any final thoughts you had about
SSR or ngicado or any of the activities you do.
I don't know, activities isn't the right word.

Speaker 6 (01:12:44):
Okay, So first of all, thank you for the invitation.
It was really really nice time. Lara. Are you there? Oh?

Speaker 14 (01:12:52):
Oh okay, see let me let me screenshot this one.

Speaker 6 (01:13:05):
Okay, cheese okay, So once more again, thank you so much.
It was a pleasure and for me it was a
really really nice evening withn't.

Speaker 3 (01:13:18):
You and likewise likewise mm hmm.

Speaker 6 (01:13:24):
And what I want to say, I want to invite
all of you if you are in Poland please join
our meetup in Tikato. Uh. And of course if you
want to be a speaker and please let me know,
just write me on LinkedIn whatever, any social media it

(01:13:47):
could be instagramd Facebook, whatever. So I'm waiting waiting for it.
And if you want to use as a sign in
regular please just think about it. If it's a good
idea for your project, if you really want to do this.

Speaker 2 (01:14:08):
You know, I want to maintain this later.

Speaker 6 (01:14:13):
No, I think that a lot of people just should
think if I really need it. If yes, please go
go and coach. Yeah. Ok thanks, thank you once more again.

Speaker 2 (01:14:31):
Absolutely thank you so much for being able to join us.
It's always lovely to hear from developers all over the
entire world. It's so great to have you on as
a guest for our listener. NG comp tickets are on
sale now. It's October seventeenth and eighteenth in Baltimore area,

(01:14:56):
somewhere near Baltimore. Maryland is the state that that is,
and so definitely look up those tickets online. It's a
great place to actually talk to people in person. If
you see me there, I will have may I help
you face? Or I won't. I might have I'm freaked

(01:15:17):
out face. So but you can always say hi to me,
and Yan will yell at you if you don't say
hi to him.

Speaker 3 (01:15:22):
That's sure. I'm known for publicly yelling at people if
they don't say hiating.

Speaker 2 (01:15:30):
And why people don't say hi. It's sort of a
feedback loop, but it is what it is now. But
to our lizard, thank you for joining us today. If
you enjoy the podcast, please subscribe. That's how we keep
paying the editors to bleep out the f words and

(01:15:51):
we'll catch you next time.

Speaker 15 (01:15:54):
Hey, this is pressed to mine. I'm one of the
n G champions riders in our daily battle to crush
out code, we run into problems, and sometimes those problems
aren't easily solved. NGCOMF broadcasts articles and tutorials from angie
champions like myself that help make other developers' lives just
a little bit easier. To access these articles, visit medium
dot com, forward slash, ngcomm.

Speaker 1 (01:16:16):
Thank you for listening to the Angular Plus Show in
Ngicoff podcast. We would like to thank our sponsors, the
NGCOMF organizers Joe Eames and Aaron Frost, our producer Genebourne,
and our podcast editor and engineer Patrick Kays. You can
find him at spoonful ofmedia dot com.

All Episodes

S9 E9 | Into Server-Side Rendering | Brygida Fiejdasz

Episode Transcript

Popular Podcasts

New Heights with Jason & Travis Kelce

Dateline NBC

24/7 News: The Latest

.css-15opob5{left:0;position:absolute;top:0.8rem;} All Episodes

.css-14f5ked{margin:0;word-break:break-word;display:-webkit-box;-webkit-box-orient:vertical;box-orient:vertical;-webkit-line-clamp:2;overflow:hidden;}S9 E9 | Into Server-Side Rendering | Brygida Fiejdasz