1
00:00:00,181 --> 00:00:00,931
Carl: Hello everyone.

2
00:00:00,991 --> 00:00:04,171
Thank you for joining us for the
August edition of this Month in React.

3
00:00:04,201 --> 00:00:08,351
As we recap what's going on with React,
react native in the web we're coming to

4
00:00:08,351 --> 00:00:12,341
you live from Reactive Flux, the place
for professional developers using React.

5
00:00:12,841 --> 00:00:13,471
I'm Carl.

6
00:00:13,501 --> 00:00:16,231
I'm a staff product developer and
freelance community leader here at

7
00:00:16,231 --> 00:00:20,521
Reactive Flux, where I do community
programs like this event and write some

8
00:00:20,521 --> 00:00:21,841
code to help keep the community running.

9
00:00:22,341 --> 00:00:23,391
Mark: Hi, I'm Mark.

10
00:00:23,421 --> 00:00:25,161
I maintain Redux.

11
00:00:25,161 --> 00:00:27,351
I try to find time to maintain Redux.

12
00:00:27,351 --> 00:00:30,891
Life is busy these days and my day
job is working at Replay where we've

13
00:00:30,891 --> 00:00:34,431
built a time traveling debugger for
JavaScript and are also attempting to

14
00:00:34,431 --> 00:00:36,811
get in on the AI app generating craze.

15
00:00:37,381 --> 00:00:40,441
Carl: Mo is unfortunately out
this month, he seems to have food

16
00:00:40,441 --> 00:00:41,611
poisoning or something similar.

17
00:00:42,041 --> 00:00:44,591
So he's gonna take a break and
I'm gonna do my best on React

18
00:00:44,591 --> 00:00:46,841
Native news, which is only Okay.

19
00:00:47,291 --> 00:00:50,111
But yeah, let's start off
with some new releases.

20
00:00:50,161 --> 00:00:51,436
Mark, tell us about new TypeScript.

21
00:00:51,936 --> 00:00:54,546
Mark: The TypeScript release
train keeps on rolling.

22
00:00:54,576 --> 00:00:57,486
They've just put out TypeScript 5.9.

23
00:00:58,086 --> 00:00:59,856
Few points of interest out of this one.

24
00:00:59,906 --> 00:01:04,016
They've updated some of the options for
generating any new TypeScript project.

25
00:01:04,416 --> 00:01:08,872
They've simplified the initial TS
config, JSON that gets generated.

26
00:01:08,967 --> 00:01:15,087
They also have support for the upcoming
JavaScript import, defer syntax.

27
00:01:15,087 --> 00:01:16,137
This is a new thing.

28
00:01:16,637 --> 00:01:23,657
That is coming down the pipeline for
JavaScript engines where you can use

29
00:01:23,657 --> 00:01:30,077
the defer keyword in an import statement
and the JavaScript runtime will know

30
00:01:30,107 --> 00:01:35,057
that it needs to go read this file,
but it won't try to actually load and

31
00:01:35,057 --> 00:01:37,337
execute that JavaScript right away.

32
00:01:37,487 --> 00:01:40,277
Right now, when you do
imports, everything's imported

33
00:01:40,277 --> 00:01:41,717
and executed synchronously.

34
00:01:42,077 --> 00:01:46,867
This can have a lot of effect on startup
time, and so the import, defer keyword

35
00:01:46,867 --> 00:01:52,307
is meant to la effectively lazy load some
pieces of the JS system without having

36
00:01:52,307 --> 00:01:55,277
to use the the separate import statement.

37
00:01:55,777 --> 00:02:00,127
So TypeScript now at least has
support for that syntax, but in a

38
00:02:00,127 --> 00:02:03,817
sense it won't do anything until
JavaScript engines fully support

39
00:02:03,847 --> 00:02:06,457
actually doing something with that.

40
00:02:06,957 --> 00:02:11,097
One thing that I personally am
excited for is that TS 5.9 now has

41
00:02:11,097 --> 00:02:14,307
support for expandable hover previews.

42
00:02:14,847 --> 00:02:19,197
If you, if you ever work with TypeScript,
you have big type definitions, you

43
00:02:19,197 --> 00:02:23,787
know that TypeScript often cuts down
the amount of information it shows

44
00:02:23,787 --> 00:02:27,266
about a type in the hover preview
or, you know, the types are deeply

45
00:02:27,266 --> 00:02:30,776
nested and you, you don't already
know like what is inside this field.

46
00:02:31,326 --> 00:02:35,616
So ts 5.9 now has support for
actually being able to drill

47
00:02:35,616 --> 00:02:37,506
down into hover previews.

48
00:02:37,966 --> 00:02:43,186
you do need to have an updated version
of VS code to make use of that as well.

49
00:02:43,586 --> 00:02:46,706
But as someone who has spent too much
time fiddling with those settings, I'm

50
00:02:46,706 --> 00:02:48,056
actually very excited about that one.

51
00:02:48,566 --> 00:02:49,321
Carl: Yeah, that sounds great.

52
00:02:50,269 --> 00:02:52,359
Mark: And then along with
that, there are a couple bits

53
00:02:52,359 --> 00:02:53,739
about the future of TypeScript.

54
00:02:54,309 --> 00:02:56,109
So right now we're on 5.9.

55
00:02:56,599 --> 00:03:02,149
The TypeScript team has said that the
go port of the TypeScript compiler

56
00:03:02,569 --> 00:03:05,389
will become a TypeScript 7.0.

57
00:03:06,063 --> 00:03:10,693
They've put out some news and plans
on the roadmap for TypeScript 6.0.

58
00:03:11,023 --> 00:03:15,193
There's an issue in some discussion
about making the strict flag the

59
00:03:15,193 --> 00:03:21,013
default, or maybe not the entire strict
flag, but maybe graduating some of the

60
00:03:21,513 --> 00:03:25,713
specific settings, like strict null
checks to be turned on by default.

61
00:03:26,173 --> 00:03:28,543
As a maintainer, that
makes me very, very happy.

62
00:03:28,543 --> 00:03:32,353
I'm tired of seeing people post
issues against my library saying,

63
00:03:32,353 --> 00:03:33,703
your library doesn't work.

64
00:03:33,703 --> 00:03:34,093
Right.

65
00:03:34,423 --> 00:03:36,703
And the problem is they didn't
have TypeScript in strict

66
00:03:36,703 --> 00:03:38,053
mode in the first place.

67
00:03:38,623 --> 00:03:39,163
So.

68
00:03:39,663 --> 00:03:42,856
still to be worked out, but it's good
to see that they are trying to figure

69
00:03:42,856 --> 00:03:44,446
out the transition plan for all this.

70
00:03:44,946 --> 00:03:46,056
Carl: Definitely super cool.

71
00:03:46,556 --> 00:03:51,626
We've also got React native
releasing version uh, O 81.

72
00:03:51,804 --> 00:03:56,964
Obviously I am not anywhere near as deeply
versed in React native as Mo would be.

73
00:03:56,964 --> 00:04:01,294
So, uh, hopefully we'll have him
around to catch us up again later on.

74
00:04:01,324 --> 00:04:05,504
But we've talked a little bit
about what's coming on, what's in

75
00:04:05,504 --> 00:04:07,604
this release in previous months.

76
00:04:07,634 --> 00:04:09,614
Nothing here struck me as super new.

77
00:04:09,894 --> 00:04:13,414
They're deprecating, the safe area
view which they talked about as

78
00:04:13,414 --> 00:04:17,394
being originally an iOS specific.

79
00:04:17,994 --> 00:04:21,654
Component in order to support, you know,
the safe area because of the notch.

80
00:04:21,704 --> 00:04:25,514
But now Android has notches too, and
it doesn't work very well for that.

81
00:04:25,514 --> 00:04:29,922
So it's being deprecated and they're
leaning on the, Safe Area Context.

82
00:04:29,922 --> 00:04:32,652
They recommend that you migrate
to the React native safe Area

83
00:04:32,652 --> 00:04:34,452
context library for that.

84
00:04:34,912 --> 00:04:38,662
They are also defaulting to
Android 16 now in React Native.

85
00:04:38,712 --> 00:04:41,592
They had an, a curious call
out that seems strange to me.

86
00:04:41,692 --> 00:04:45,592
They say predictive back gesture
is now enabled by default for apps

87
00:04:45,592 --> 00:04:50,152
targeting Android 16 and just , the
phrase predictive back gesture.

88
00:04:50,652 --> 00:04:52,422
Is, I don't know, it
seems like a lot to me.

89
00:04:52,812 --> 00:04:55,602
I know gestures, you have to predict
them and whatever, and I guess

90
00:04:55,662 --> 00:04:58,812
everything is now gestures, but I have
my phone sent to use buttons still,

91
00:04:59,082 --> 00:05:01,962
so I don't know what they're talking
about, but that sounds complicated.

92
00:05:02,262 --> 00:05:05,742
It also talks like, you know, if you
have overridden your, the back behavior

93
00:05:05,742 --> 00:05:11,612
of your app, then you may need to
migrate or change how your app works.

94
00:05:11,612 --> 00:05:16,632
So man, if only you could reliably go
back in Native apps isn't the web great.

95
00:05:16,874 --> 00:05:20,684
They also are introducing pre-compiled
iOS builds, which they say cuts the

96
00:05:20,684 --> 00:05:25,874
compile time by up to You know, 10 x
so like one 10th the compiled time.

97
00:05:25,874 --> 00:05:29,369
It used to be in projects where
react native is a primary dependency.

98
00:05:29,439 --> 00:05:33,431
And they've got better error rendering
in the dev tools as well, which is great.

99
00:05:33,735 --> 00:05:37,095
it now shows the original message in
Stack trace of uncut JavaScript errors.

100
00:05:37,095 --> 00:05:40,035
So how, how lovely to know
where your errors come from,

101
00:05:40,464 --> 00:05:42,534
Mark: Next 15.5 came out.

102
00:05:42,714 --> 00:05:44,934
A couple things worth
noting from this one.

103
00:05:45,054 --> 00:05:49,914
They now have turbo pack
builds for production in beta.

104
00:05:50,364 --> 00:05:54,804
Turbo Pack had previously really only been
used for local development, and so they've

105
00:05:54,804 --> 00:05:59,004
been cranking away on trying to get it to
full compatibility for production builds.

106
00:05:59,154 --> 00:06:00,534
And it seems like that's getting close.

107
00:06:01,114 --> 00:06:04,444
They now have node support for middleware.

108
00:06:04,964 --> 00:06:07,506
They've got some TypeScript
improvements, like actually

109
00:06:07,506 --> 00:06:09,666
having full typing for routes.

110
00:06:09,666 --> 00:06:13,996
So it'll catch things like mistyped
link tags as well as trying to get

111
00:06:13,996 --> 00:06:16,366
rid of the old next lint command.

112
00:06:16,876 --> 00:06:21,196
Carl: Yeah, the middleware support for
no JS also seems like a pretty big step.

113
00:06:21,196 --> 00:06:24,646
You know, one of the main
complaints, a large complaint

114
00:06:24,646 --> 00:06:28,096
about next is how difficult it
is to run yourself not on Vercel.

115
00:06:28,706 --> 00:06:33,976
So supporting a more generic runtime
for your middleware seems really great.

116
00:06:33,976 --> 00:06:37,276
I haven't run into this with next
specifically, but I have run into.

117
00:06:37,494 --> 00:06:41,904
Compatibility issues between
edge runtimes and node JS code.

118
00:06:42,236 --> 00:06:45,896
it's such a constraint if you're trying
to run on, edge runtime, which is,

119
00:06:46,286 --> 00:06:51,866
you know, okay, so next Vercel is they
have their Edge Runtime, in title case.

120
00:06:51,916 --> 00:06:56,506
But also, you know, CloudFlare workers
are also a very similar kind of runtime

121
00:06:56,506 --> 00:06:58,996
that offer a similar set of constraints.

122
00:06:59,086 --> 00:07:04,276
And man, you just can't use a lot of
the node ecosystem when you're in one

123
00:07:04,276 --> 00:07:06,406
of those constrained environments.

124
00:07:06,406 --> 00:07:09,826
So this, this should open up compatibility
quite a lot it sounds like to me.

125
00:07:10,336 --> 00:07:15,766
Mark: Meanwhile, the Preact library, the,
the longstanding smaller replacement for

126
00:07:15,766 --> 00:07:19,436
React just put out a beta for version 11.

127
00:07:19,926 --> 00:07:23,976
Preact has always been dom
slash web only, not native.

128
00:07:24,376 --> 00:07:28,636
And the calling cards have been that
it's much smaller than full-blown

129
00:07:28,636 --> 00:07:33,796
react, but maintains most API
compatibility up to a certain point.

130
00:07:33,796 --> 00:07:36,946
I think they've stopped trying to,
maintain compatibility for some of

131
00:07:36,946 --> 00:07:39,256
the newer React APIs in 18 and 19.

132
00:07:39,866 --> 00:07:43,166
A couple of the big points this one
they finally dropped IE 11 support

133
00:07:43,566 --> 00:07:48,731
and they've improved hydration and
a number of other small tweaks.

134
00:07:48,991 --> 00:07:52,081
So it's always good to see that
them making progress as well.

135
00:07:52,523 --> 00:07:55,823
Carl: Every so often it's nice
to check in on what BUN and

136
00:07:55,823 --> 00:07:57,083
Dino and everything are doing.

137
00:07:57,133 --> 00:08:01,213
BUN has a 1.2 point 21 release out.

138
00:08:01,703 --> 00:08:06,293
A couple things that caught my eye
on it were the bun sql, you know,

139
00:08:06,293 --> 00:08:10,218
standard library tool now supports
MySQL, MariaDB, SQL Light, and

140
00:08:10,218 --> 00:08:12,498
Postgres, all from like one dependency.

141
00:08:12,498 --> 00:08:13,278
And that's pretty great.

142
00:08:13,338 --> 00:08:13,668
I don't know.

143
00:08:13,698 --> 00:08:16,628
Nice to have, nice to be
able to swap those out.

144
00:08:16,680 --> 00:08:19,170
I wonder what the experience of
actually trying to swap them out would

145
00:08:19,170 --> 00:08:22,710
be, because the different engines
have slightly different constraints.

146
00:08:23,132 --> 00:08:23,912
I appreciate that.

147
00:08:23,912 --> 00:08:24,392
That's cool.

148
00:08:24,392 --> 00:08:30,965
I, I love, especially for like SQL light
stuff, it just seems so simple as maybe

149
00:08:30,965 --> 00:08:34,395
overstating it, but it's really nice
to be able to just spin up a database

150
00:08:34,395 --> 00:08:35,685
without installing dependencies.

151
00:08:35,685 --> 00:08:37,184
So, uh, kudos to BUN for adding that.

152
00:08:37,684 --> 00:08:41,224
They've also added native
YAML support which is great.

153
00:08:41,224 --> 00:08:45,244
You know, it's lovely to not for
parsing confi common configuration file

154
00:08:45,244 --> 00:08:48,094
formats again, seems like something
that should be in the standard library.

155
00:08:48,514 --> 00:08:54,664
However, I am generally aware of YAML as
like a very challenging format to parse.

156
00:08:54,726 --> 00:09:00,033
There's a, a blog post that lives in
my brain about YAML from 2023 titled

157
00:09:00,033 --> 00:09:03,863
The YAML document from Hell Enumerates
some of the complexities one of my

158
00:09:03,863 --> 00:09:06,803
favorites being sex decimal numbers.

159
00:09:06,803 --> 00:09:15,373
And so a, a, apparently a common older
format quirk is that some, ranges of

160
00:09:15,373 --> 00:09:19,963
ports that you might try to map in, say
a Docker file like Port 22, mapped to

161
00:09:19,963 --> 00:09:24,223
port 22 is not parsed as 22, colon 22.

162
00:09:24,223 --> 00:09:27,583
It's parsed as a sexagesimal,
IE base 60, number.

163
00:09:28,083 --> 00:09:33,933
So then instead of the
string 22:22, you get 1,342.

164
00:09:34,453 --> 00:09:35,953
Which is not a valid port mapping.

165
00:09:36,163 --> 00:09:41,533
So like things like there are like
30 different ways to put Booleans

166
00:09:41,953 --> 00:09:43,993
to encode Boolean in a YAML file.

167
00:09:43,993 --> 00:09:47,293
And so like yes and no are
one of the valid formats.

168
00:09:47,653 --> 00:09:51,613
And so if you're trying to do a list of
countries using standard country codes,

169
00:09:51,613 --> 00:09:53,413
apparently Norway will be interpreted.

170
00:09:53,423 --> 00:09:54,043
Mark: Is NO,

171
00:09:56,236 --> 00:10:01,246
Carl: So like, just hearing about that,
those kind of like foot guns that exist in

172
00:10:01,246 --> 00:10:05,596
the format and apparently like variations
in parser behavior is an existing

173
00:10:05,596 --> 00:10:07,696
problem throughout the YAML ecosystem.

174
00:10:07,696 --> 00:10:08,942
So, great.

175
00:10:08,942 --> 00:10:09,032
I

176
00:10:09,287 --> 00:10:09,637
Mark: let's add another parser.

177
00:10:09,637 --> 00:10:10,297
Carl: Right what?

178
00:10:10,507 --> 00:10:10,807
Great.

179
00:10:10,807 --> 00:10:11,557
One more parser there.

180
00:10:11,887 --> 00:10:12,397
Wonderful.

181
00:10:12,397 --> 00:10:16,237
I can't wait to hear about what
weird, terrible, hellish bugs

182
00:10:16,597 --> 00:10:18,997
emerge from this new parser.

183
00:10:19,497 --> 00:10:20,097
Good luck to them.

184
00:10:20,457 --> 00:10:21,027
I hope it's good.

185
00:10:21,350 --> 00:10:25,380
Mark: Next up the folks over in the Tan
Stack Collective have just put out a beta

186
00:10:25,380 --> 00:10:28,170
of the new Tan Stack database library.

187
00:10:28,502 --> 00:10:30,002
it's a little interesting to describe.

188
00:10:30,002 --> 00:10:35,252
It's a layer that's supposed to sit
on top of your tan stack query setup,

189
00:10:35,822 --> 00:10:40,982
and it kind of acts as like a local
in client database and sync engine.

190
00:10:41,192 --> 00:10:45,452
So you can still use 10 set query
to do the fetching, but the database

191
00:10:45,452 --> 00:10:48,842
layer is supposed to provide a
normalized view of the data, supposed

192
00:10:48,842 --> 00:10:51,182
to have very fast in client updates.

193
00:10:51,462 --> 00:10:54,732
I believe this has been worked on
by Kyle Matthews, who you may know

194
00:10:54,732 --> 00:10:58,722
as the original creator of the
Gatsby framework back in the day.

195
00:10:59,122 --> 00:11:04,012
He's been working on electric sql, which
is itself a AYC engine layer, so he

196
00:11:04,012 --> 00:11:05,992
clearly now has some expertise over there.

197
00:11:06,592 --> 00:11:10,342
So, looks like a very potentially
interesting tool for fast

198
00:11:10,342 --> 00:11:11,842
client side data management.

199
00:11:12,342 --> 00:11:15,492
Carl: it seems like hand stack
throwing their hat in the ring on

200
00:11:15,492 --> 00:11:18,942
like sync engines at a slightly
different level of abstraction

201
00:11:18,942 --> 00:11:21,672
than like where React query sits.

202
00:11:21,702 --> 00:11:25,872
Further to the backend, further to
here's your internal store being

203
00:11:25,872 --> 00:11:28,332
managed, not just request caching.

204
00:11:28,762 --> 00:11:29,212
So that's cool.

205
00:11:29,242 --> 00:11:29,452
Yeah.

206
00:11:29,512 --> 00:11:29,872
Interesting.

207
00:11:30,422 --> 00:11:33,392
A very small shout out, a little
bit further away, but this is a

208
00:11:33,392 --> 00:11:37,022
tool that I evaluated for use in a
professional setting on a React project.

209
00:11:37,022 --> 00:11:38,822
So I'm gonna shout out
a new major version.

210
00:11:39,282 --> 00:11:42,012
Ghost version 6.0 has been released.

211
00:11:42,082 --> 00:11:46,472
Ghost is a, like CMS, an open
I believe open source CMS.

212
00:11:47,112 --> 00:11:49,062
And they generally seem nice.

213
00:11:49,062 --> 00:11:49,662
They seem great.

214
00:11:49,692 --> 00:11:54,672
I, you know, as contrasting
things like Contentful or Ghost

215
00:11:54,702 --> 00:11:57,672
or Substack or Medium or what have

216
00:11:57,672 --> 00:11:59,749
you, uh, Word, right?

217
00:12:00,239 --> 00:12:02,729
They sit in a good spot in the niche.

218
00:12:02,799 --> 00:12:05,919
They, so they're now, they're
announcing as part of this version

219
00:12:05,919 --> 00:12:09,349
six that they have added distribution.

220
00:12:09,349 --> 00:12:15,799
So now you can automatically publish your
posts from Ghost across social platforms.

221
00:12:15,829 --> 00:12:19,579
So like they, they call out Blue
Sky Flipboard Threads, MAs it on

222
00:12:19,669 --> 00:12:23,929
WordPress, interestingly and Ghost,
they can, so, okay, so you can publish

223
00:12:23,929 --> 00:12:27,199
the ghost and it will be distributed
elsewhere on, in Ghost, I don't

224
00:12:27,199 --> 00:12:28,129
know, I don't know what that means.

225
00:12:28,459 --> 00:12:31,619
Or any other social web platform
as well as like analytics.

226
00:12:31,919 --> 00:12:36,719
And they talk a lot about how much
revenue they have passed along

227
00:12:36,749 --> 00:12:39,179
to publishers on their platform.

228
00:12:39,189 --> 00:12:42,580
So they show their earnings
broken down into like.

229
00:12:43,120 --> 00:12:49,160
Hosting revenue and platform revenue,
and it's like $38 million for their

230
00:12:49,160 --> 00:12:53,930
own company and like a hundred million
dollars through, you know, distributed

231
00:12:53,930 --> 00:12:56,120
to people publishing on ghosts.

232
00:12:56,120 --> 00:12:56,720
So like that, I don't know.

233
00:12:56,720 --> 00:12:57,170
That's great.

234
00:12:57,170 --> 00:12:59,990
They, they shout out 4 0 4 Media, which
is a site that I'm familiar with and

235
00:12:59,990 --> 00:13:01,760
did not realize hosted on this platform.

236
00:13:02,090 --> 00:13:03,290
So, you know, love that.

237
00:13:03,290 --> 00:13:03,740
That's great.

238
00:13:03,800 --> 00:13:08,600
I love a, love a open source media
platform that's doing good work right now.

239
00:13:09,100 --> 00:13:09,460
Cool.

240
00:13:09,490 --> 00:13:13,434
Uh, That's all the new releases we
have for now,   into the main content.

241
00:13:14,124 --> 00:13:17,759
Mark: All right, so we have a
roundup of a number of topics

242
00:13:17,759 --> 00:13:21,689
related to changes in reacts APIs.

243
00:13:21,689 --> 00:13:24,599
So get your technical hats on for these.

244
00:13:24,842 --> 00:13:30,332
The first one is that Sebastian
Markbåge put up a PR to officially

245
00:13:30,362 --> 00:13:36,482
deprecate the throw a promise
technique for triggering suspense.

246
00:13:36,982 --> 00:13:40,252
So let's wind backwards and unpack a
little bit, like what is that in the

247
00:13:40,252 --> 00:13:41,902
first place and why does it even exist?

248
00:13:42,562 --> 00:13:43,132
So.

249
00:13:43,632 --> 00:13:47,718
Currently up through React 17 and 18.

250
00:13:48,348 --> 00:13:54,168
The suspense component came out in I
think like 16.6, but originally it was

251
00:13:54,168 --> 00:13:59,318
only used with React lazy for importing
and deferring loading of components.

252
00:13:59,938 --> 00:14:04,878
There wasn't an official like react
for data fetching method, but there

253
00:14:04,878 --> 00:14:07,488
was the unofficial experimental.

254
00:14:07,488 --> 00:14:12,318
This is never documented, but
the code exists and works.

255
00:14:12,858 --> 00:14:19,268
If you wanted to trigger suspense in
terms of like, you know, managing some

256
00:14:19,268 --> 00:14:25,238
data fetching yourself, the super secret
technique was that you would throw a

257
00:14:25,238 --> 00:14:27,368
promise from within your component.

258
00:14:27,868 --> 00:14:32,188
And the reason the React team
picked this was because we.

259
00:14:32,688 --> 00:14:37,518
It like, to a certain extent, it enabled
them to reuse the existing infrastructure

260
00:14:37,908 --> 00:14:42,738
from catching errors within a component
where, you know, it kind of conceptually,

261
00:14:43,156 --> 00:14:48,196
you have a catch block around the actual
component call and then react knows,

262
00:14:48,226 --> 00:14:52,546
here's where I'm rendering in the tree,
and then it can sort of bubble up the

263
00:14:52,546 --> 00:14:57,826
behavior to some ancestor component that
was supposed to catch it for errors.

264
00:14:57,826 --> 00:15:01,426
It's a, you know, actual error
handling with the component did catch.

265
00:15:01,996 --> 00:15:04,726
And for suspense it's, you
know, where's the nearest

266
00:15:04,726 --> 00:15:06,556
suspense component in the tree?

267
00:15:07,056 --> 00:15:11,466
And so this was never officially
documented, but, you know, library

268
00:15:11,466 --> 00:15:14,736
maintainers and people investigating
the code saw that it was there.

269
00:15:15,156 --> 00:15:19,896
And so it's been known and used by
the community and libraries for years.

270
00:15:19,926 --> 00:15:25,536
And so pretty much anything, any library
that had suspense support built in was

271
00:15:25,536 --> 00:15:28,116
internally just throwing a promise.

272
00:15:28,472 --> 00:15:36,962
So with React 19, we now have the use
hook built in, and that is the officially

273
00:15:36,962 --> 00:15:42,872
documented publicly, you know, described
way to actually trigger suspense.

274
00:15:43,372 --> 00:15:48,562
If you look at the use hook, I think
internally it does actually still end up

275
00:15:48,562 --> 00:15:52,672
throwing a promise last time I checked,
but it's now an implementation detail.

276
00:15:53,192 --> 00:15:55,772
And it does some other
things in there as well.

277
00:15:56,272 --> 00:16:00,562
So if you read a pr, they are
officially going to get rid of the

278
00:16:00,562 --> 00:16:05,242
throwing a suspense, throwing a promise
technique for a number of reasons.

279
00:16:05,272 --> 00:16:08,992
Some of it has to do with internal
implementation details and optimizations.

280
00:16:09,412 --> 00:16:13,372
Some of it has to do with, well,
we can have the lit rules look for

281
00:16:13,372 --> 00:16:18,502
uses of the use hook and flag any,
any time you try to put that in a

282
00:16:18,502 --> 00:16:20,212
place that it's not legal to do so.

283
00:16:20,762 --> 00:16:24,982
This did then lead to some discussion
on Blue Sky amongst a couple of the

284
00:16:24,982 --> 00:16:30,532
maintainers like Dominic Dorf, Meister
of React Query asking, well, if this

285
00:16:30,532 --> 00:16:36,642
comes out in like, you know, 19 3, 19 4,
something like that, how are we supposed

286
00:16:36,642 --> 00:16:43,332
to manage having our own libraries
work with both like React 18 and 19.1

287
00:16:43,392 --> 00:16:49,782
and 19.4 at the same time when there's
now three different variations of what

288
00:16:49,782 --> 00:16:52,122
is a legal way to trigger suspense.

289
00:16:52,502 --> 00:16:54,302
there was a bit of a
back and forth on that.

290
00:16:54,402 --> 00:16:59,682
One partial answer was, your library can
check if the use hook is exported from

291
00:16:59,682 --> 00:17:05,352
React and prefer that if it exists and
fall back the promise if it doesn't.

292
00:17:06,042 --> 00:17:10,062
One of the React team members, Ricky said,
well, you probably should just focus on

293
00:17:10,062 --> 00:17:12,552
supporting the latest version of React.

294
00:17:13,052 --> 00:17:16,832
I'll admit, I feel like that kind of
hand waves the problem a little bit.

295
00:17:17,202 --> 00:17:19,332
Carl: How great if everyone
could just rely on that.

296
00:17:19,337 --> 00:17:19,557
Yeah.

297
00:17:20,057 --> 00:17:23,327
Mark: yeah, because I mean that, that
probably also means putting out new

298
00:17:23,327 --> 00:17:27,707
major versions of our own libraries,
which is then an effort and also has

299
00:17:27,707 --> 00:17:29,327
a ripple effect on the ecosystem.

300
00:17:29,717 --> 00:17:32,807
I mean, I don't really want to
publish a new version, a new major

301
00:17:32,807 --> 00:17:37,097
version of, you know, some of the
Redux libraries just to support that.

302
00:17:37,597 --> 00:17:41,487
But it's good to see that there,
that we are actually making

303
00:17:41,487 --> 00:17:43,377
headway on that now that 19 is out.

304
00:17:43,927 --> 00:17:45,847
Another interesting point.

305
00:17:45,847 --> 00:17:51,882
So buried in a blue sky thread
Joseph from the React team said that.

306
00:17:52,382 --> 00:17:56,762
They're planning to not actually
implement an idea that they

307
00:17:56,762 --> 00:18:00,872
had discussed a few months ago
where they'd said, we are going.

308
00:18:01,052 --> 00:18:06,482
They were thinking about allowing you
to call use or use context inside of

309
00:18:06,482 --> 00:18:10,622
use memo as a way to optimize context.

310
00:18:11,242 --> 00:18:14,992
So backing up technical detail on
this one, the weakness of context

311
00:18:14,992 --> 00:18:19,492
has always been that when you update
the context value, every component

312
00:18:19,492 --> 00:18:20,842
that reads it will re-render.

313
00:18:21,342 --> 00:18:25,135
And then at that point, all the
children inside of that will re-render

314
00:18:25,135 --> 00:18:28,945
as well, just because react defaults
to when any component renders.

315
00:18:28,945 --> 00:18:33,145
It just keeps on going all the way down
the tree unless you optimize it to stop.

316
00:18:33,645 --> 00:18:37,725
And so the problem is if you have,
you know, fairly large objects with

317
00:18:37,725 --> 00:18:42,435
multiple fields as your context value,
some of your components probably only

318
00:18:42,435 --> 00:18:44,715
care about one or two of those fields.

319
00:18:45,405 --> 00:18:49,185
But as soon as you update that
object at all, every component that

320
00:18:49,185 --> 00:18:51,135
read the context will re-render.

321
00:18:51,735 --> 00:18:56,685
And so it ends up leading to, you know,
potentially lots of components rendering

322
00:18:56,685 --> 00:18:58,305
slower render performance, et cetera.

323
00:18:58,805 --> 00:19:05,085
So years ago, like, I don't know,
20 18, 20 19 there was a user land

324
00:19:05,325 --> 00:19:11,475
RFC suggestion that react should
add context selectors as an API.

325
00:19:11,895 --> 00:19:15,375
So, you know, kind of similar to
like a, a react redux use selector,

326
00:19:15,465 --> 00:19:17,865
but optimize for context instead.

327
00:19:18,475 --> 00:19:20,725
And so that proposal has
been around for a long time.

328
00:19:21,115 --> 00:19:25,075
Andrew Clark even briefly tried
implementing a proof of concept of

329
00:19:25,075 --> 00:19:29,485
a context selector's API in like
2020, and then it didn't go anywhere.

330
00:19:29,985 --> 00:19:35,265
So a few months ago, the React team
said we're, we're thinking about a. Use

331
00:19:35,265 --> 00:19:43,635
context in use memo as a alternative to
actually writing a selector for context.

332
00:19:44,135 --> 00:19:47,885
And apparently their thinking has evolved
and they're not going to do that at this

333
00:19:47,885 --> 00:19:57,720
point because the React compiler basically
gives you 95% of the performance benefits

334
00:19:58,150 --> 00:20:04,595
that a context selector's API would have
without them needing to design and ship a

335
00:20:04,595 --> 00:20:07,625
context selector's API, into React itself.

336
00:20:08,125 --> 00:20:13,645
If you think about it, the point of the
compiler is that it not only optimizes

337
00:20:13,645 --> 00:20:17,815
like your used memos and whatever,
it also optimizes the render output.

338
00:20:18,315 --> 00:20:22,755
And so if you have a component that
reads from a context, it will, it will

339
00:20:22,755 --> 00:20:25,395
render because the context value changed.

340
00:20:25,895 --> 00:20:31,295
But if none of the data that it needs
from the context has updated, it will

341
00:20:31,295 --> 00:20:33,425
end up skipping all of its children.

342
00:20:34,085 --> 00:20:38,045
And so that drastically cuts
down on how many components would

343
00:20:38,045 --> 00:20:40,175
render when the context updates.

344
00:20:40,805 --> 00:20:45,095
So there was actually some very, very
good discussion in the longstanding

345
00:20:45,095 --> 00:20:49,205
context, selectors RFC thread, just
within the last two or three days where

346
00:20:49,205 --> 00:20:53,615
a few people were agitating for react
should really add contact selectors.

347
00:20:53,615 --> 00:20:56,555
It'll get rid of all these other
state management libraries.

348
00:20:57,125 --> 00:21:01,085
And I left a couple comments trying to
explain how the compiler solves this

349
00:21:01,085 --> 00:21:06,640
problem and Joe Savona from the React
team then went on and wrote some very

350
00:21:06,640 --> 00:21:12,220
extensive, detailed comments talking about
how the React team has been doing research

351
00:21:12,250 --> 00:21:14,950
into these ideas of data flow analysis.

352
00:21:15,385 --> 00:21:19,975
And how do you manage large amounts
of state and how does it compare with

353
00:21:19,975 --> 00:21:25,195
react context and signals and, you know,
third party state management libraries.

354
00:21:25,705 --> 00:21:29,664
And so he confirmed that, they're not
planning to add a context selector's,

355
00:21:29,664 --> 00:21:35,193
API and instead their thought
process is actually now about this

356
00:21:35,193 --> 00:21:38,193
concept called concurrent stores.

357
00:21:38,693 --> 00:21:43,823
So as best as I understand it, the
idea is that right now a third party

358
00:21:43,823 --> 00:21:49,883
library like Redux or Zeus stand
relies on the use sink external store

359
00:21:49,883 --> 00:21:55,013
hook to be able to tell react that
there's a subscription data changed.

360
00:21:55,103 --> 00:21:57,643
This component needs to update, but.

361
00:21:58,333 --> 00:22:02,953
That has the limitation that it doesn't
play well with suspense and transitions

362
00:22:02,953 --> 00:22:06,793
because if something got updated in
the middle, react has to throw away

363
00:22:06,793 --> 00:22:09,223
work in progress and do a full render.

364
00:22:09,583 --> 00:22:12,673
It can't do all the, you know,
the performance optimizations

365
00:22:12,673 --> 00:22:14,503
and with transitions.

366
00:22:15,003 --> 00:22:21,573
So it sounds like this concurrent
store idea is supposed to be like an

367
00:22:21,573 --> 00:22:27,093
improved, better version of use sync
external store where you can still

368
00:22:27,093 --> 00:22:29,013
have some data living externally.

369
00:22:29,583 --> 00:22:34,893
You can still have selectors saying like,
only these components need to update.

370
00:22:35,393 --> 00:22:39,953
But the concurrent store would
wrap the updates in a concurrent

371
00:22:39,953 --> 00:22:41,453
transition compatible way.

372
00:22:41,953 --> 00:22:45,403
So he said that they're really trying
to put some focus in API design

373
00:22:45,673 --> 00:22:51,133
onto figuring out what a concurrent
store, API ought to look like.

374
00:22:51,718 --> 00:22:56,668
And it sounds like they've got some,
some amount of progress on that design

375
00:22:56,668 --> 00:22:58,138
to talk about in the near future.

376
00:22:58,638 --> 00:23:02,388
They did put up a pull request
a couple months ago with the

377
00:23:02,388 --> 00:23:05,358
skeleton for concurrent stores.

378
00:23:05,668 --> 00:23:11,018
It's just like defining some, some
data types and adding some tests.

379
00:23:11,018 --> 00:23:12,968
There's no implementation code yet.

380
00:23:13,468 --> 00:23:18,408
However a third party developer that I
saw has actually looked at all the tests

381
00:23:18,408 --> 00:23:22,728
and then gone off and tried to implement
a third party hacky polyfill version

382
00:23:23,118 --> 00:23:28,038
of what it looks like the concurrent
stores are supposed to be and publish

383
00:23:28,038 --> 00:23:30,978
that as a React concurrent store package.

384
00:23:31,398 --> 00:23:35,628
I'm very excited about this and I have
not had time to actually try it out yet.

385
00:23:36,128 --> 00:23:41,378
So the takeaways are a. Most
developers probably won't need to

386
00:23:41,378 --> 00:23:43,928
use some of these things directly.

387
00:23:44,048 --> 00:23:48,748
A lot of this is going to be more
library maintainer concerns but

388
00:23:48,748 --> 00:23:52,588
it's very good to see that the React
team is actively thinking about how,

389
00:23:52,738 --> 00:23:54,958
how can we make React apps faster?

390
00:23:55,438 --> 00:23:58,288
What are the best ways
to manage complex state?

391
00:23:58,828 --> 00:24:03,598
How can we better integrate with
third party libraries and try to

392
00:24:03,598 --> 00:24:08,038
make all the react features like
transitions work well in those cases?

393
00:24:08,538 --> 00:24:10,331
So there's your info dump for the day.

394
00:24:10,831 --> 00:24:11,396
Carl: Love that.

395
00:24:11,596 --> 00:24:14,626
I had said some stuff just before we
started recording, just before we started

396
00:24:14,626 --> 00:24:18,676
the event about, I've been playing
with effect effect ts lately, which

397
00:24:18,676 --> 00:24:20,476
we, we've mentioned once or twice now.

398
00:24:20,476 --> 00:24:24,523
And again and when you're talking about
these concurrent stores and you know,

399
00:24:24,523 --> 00:24:29,803
like I'm reading the post from Joe
Savona talking about context selectors.

400
00:24:30,173 --> 00:24:33,833
One of the things that I think effect
solves well is dependency injection.

401
00:24:34,099 --> 00:24:36,439
it's focused on the backend, that
actually says in the documentation

402
00:24:36,439 --> 00:24:38,839
like, effect is not meant for front end.

403
00:24:38,869 --> 00:24:41,847
They're, it may seem good, but
it's not what it's meant for.

404
00:24:41,847 --> 00:24:43,797
And they're interested in exploring
that, but they haven't yet.

405
00:24:44,277 --> 00:24:46,707
But I think the execution
model is pretty similar.

406
00:24:46,707 --> 00:24:50,817
It's like, it's almost like
componentized backend a little bit.

407
00:24:51,217 --> 00:24:57,427
But with type safe dependency injection
and error generation and, and using

408
00:24:57,517 --> 00:25:01,657
effect pretty extensively for the last
three or four weeks has really made me.

409
00:25:02,157 --> 00:25:04,827
Itch for some of those benefits in React.

410
00:25:05,043 --> 00:25:08,783
I'd be curious to see if they can,
well, I've got a little bit more

411
00:25:09,203 --> 00:25:11,783
connections to make on that later
on, so I guess I'll end it there.

412
00:25:11,991 --> 00:25:15,381
I don't know, just about dependency
injection in effect and type safety and

413
00:25:15,381 --> 00:25:20,651
whatever in the context of selecting data
on the front end, I think is interesting.

414
00:25:20,651 --> 00:25:24,521
I think there's still a lot of API
design exploration to do there.

415
00:25:25,021 --> 00:25:27,447
Mark: I definitely recommend taking
a few minutes to read some of

416
00:25:27,447 --> 00:25:29,517
Joe's comments in that context.

417
00:25:29,547 --> 00:25:34,377
Selector's, RFC thread, if you got some
time, and then I, I expect there be,

418
00:25:34,377 --> 00:25:38,697
and to be at least some announcements,
possibly about concurrent stores

419
00:25:38,697 --> 00:25:40,917
coming up at React Conf in October.

420
00:25:41,188 --> 00:25:41,728
Carl: Interesting.

421
00:25:42,228 --> 00:25:46,818
Mark: Then the last item out of the
React related changes they merged

422
00:25:46,818 --> 00:25:52,698
a PR to add what looks like a new
suspense timeline to the dev tools.

423
00:25:53,038 --> 00:25:57,328
They've got a demo video in there, and
so it looks like it's actually now a, a

424
00:25:57,328 --> 00:26:00,808
third extra tab in the Chrome dev tools.

425
00:26:00,898 --> 00:26:04,498
So you've got the component tree,
you've got the performance tab, and

426
00:26:04,498 --> 00:26:06,688
then there's a suspense timeline tab.

427
00:26:07,188 --> 00:26:12,758
And it looks like what it does is a
mixture of , a rough rec out, like

428
00:26:12,758 --> 00:26:17,498
rectangle outline of the shapes of your
components, but not showing like any of

429
00:26:17,498 --> 00:26:21,908
the HTML, just like , here's the structure
of what your component tree looks like

430
00:26:21,908 --> 00:26:27,428
visually, and some highlighting for which
ones have suspended, and then possibly

431
00:26:27,428 --> 00:26:32,048
some further details in a sidebar about
which components suspended and when.

432
00:26:32,538 --> 00:26:33,108
So.

433
00:26:33,588 --> 00:26:37,338
as a dev tools type person, I'm
always very, very excited to see new

434
00:26:37,338 --> 00:26:39,198
dev tools capabilities being added.

435
00:26:39,654 --> 00:26:41,364
Carl: Okay, let's go into.

436
00:26:41,864 --> 00:26:44,844
We talked a little bit
about Lee Rob leaving Vercel

437
00:26:45,044 --> 00:26:46,904
recently and going to Cursor.

438
00:26:47,354 --> 00:26:51,974
He put out a really great blog post
called Reflections on the React Community.

439
00:26:52,344 --> 00:26:56,994
This sort of summarizing his,
his time at Next and in React.

440
00:26:57,154 --> 00:26:57,904
Yeah, I don't know.

441
00:26:58,084 --> 00:26:59,014
Mark, do you wanna start?

442
00:26:59,069 --> 00:27:01,529
I don't know if I have anything
specific to start here.

443
00:27:01,529 --> 00:27:06,769
It's a really good overall hot, you
know, 30,000 foot view of his time.

444
00:27:07,269 --> 00:27:11,649
Mark: So Lee Robinson was the primary
developer relations person for

445
00:27:11,649 --> 00:27:13,959
Vercel for about five plus years.

446
00:27:14,409 --> 00:27:17,169
And even in my own head like.

447
00:27:17,669 --> 00:27:22,239
when I hear the word devel Lee is pretty
much the first person that comes to mind.

448
00:27:22,739 --> 00:27:25,674
And Lee was always in
a very tough position.

449
00:27:26,094 --> 00:27:31,134
You know, CEL is, you know, a somewhat
divisive company in some ways.

450
00:27:31,494 --> 00:27:33,504
You know, it, it puts out
some wonderful technology.

451
00:27:33,534 --> 00:27:37,044
They've genuinely done a lot to
advance the React ecosystem makes,

452
00:27:37,194 --> 00:27:40,344
make apps, you know, easier to
host, they build next, et cetera.

453
00:27:40,704 --> 00:27:45,064
But, you know, they've also been
accused of, you know, the React

454
00:27:45,064 --> 00:27:48,904
team and pushing reacts direction
and making changes just for profit.

455
00:27:49,564 --> 00:27:52,924
And you know, as I've discussed
in some previous episodes and

456
00:27:52,924 --> 00:27:57,964
blog posts, like a lot of that is
undeserved criticism or, you know,

457
00:27:57,964 --> 00:28:00,544
misinterpretation of the background.

458
00:28:01,144 --> 00:28:08,404
And so, as you know, the visible face
of Vercel and the next team we was.

459
00:28:08,904 --> 00:28:13,914
Frequently the target of a lot of those
criticisms, even though, you know, none

460
00:28:13,914 --> 00:28:19,314
of it was, you know, like he wasn't
the one developing the tool set or, you

461
00:28:19,314 --> 00:28:21,084
know, making the businesses decisions.

462
00:28:21,584 --> 00:28:24,254
And one of the things I've always
appreciated about Lee is that,

463
00:28:24,754 --> 00:28:30,214
you know, he was always very, very
active in discussions on, you know,

464
00:28:30,214 --> 00:28:31,864
Reddit and Twitter and Hacker News.

465
00:28:32,194 --> 00:28:36,154
You know, like not just in like the
next sub Reddit, but you know, the

466
00:28:36,154 --> 00:28:38,074
React Reddit hacker news discussions.

467
00:28:38,314 --> 00:28:43,684
Like anytime a discretion thread
would happen, he would pop up and,

468
00:28:43,744 --> 00:28:48,004
you know, respond to comments,
offer feedback, and, you know, yeah.

469
00:28:48,004 --> 00:28:49,024
Because of his position.

470
00:28:49,024 --> 00:28:53,434
Like occasionally people would
interpret it as being like a corporate

471
00:28:53,434 --> 00:28:58,144
ish response, but he was always
very, very active in being in there.

472
00:28:58,624 --> 00:29:00,784
And unfortunately that meant
he was also the, you took the

473
00:29:00,784 --> 00:29:02,824
brunt of a lot of the criticism.

474
00:29:03,324 --> 00:29:08,484
So a lot of his blog post, you
know, talks about, you know, react

475
00:29:08,484 --> 00:29:13,254
has, react has become stable,
it's grown, the community's big.

476
00:29:13,554 --> 00:29:18,204
Working with any community is
really, really hard and it can be

477
00:29:18,204 --> 00:29:20,304
very stressful and very frustrating.

478
00:29:20,644 --> 00:29:23,854
He talks a bit about some of the
difference between, you know, a, you

479
00:29:23,854 --> 00:29:28,234
know, more broadly like projects like
React versus Rails you know, dealing

480
00:29:28,234 --> 00:29:32,224
with some of the community management
acts, aspects, how you get feedback.

481
00:29:32,724 --> 00:29:37,060
He even talks some about,
incentives like the React team in

482
00:29:37,060 --> 00:29:40,240
some ways builds react for meta.

483
00:29:40,670 --> 00:29:43,910
And sometimes that means that, you
know, issues slip through the cracks.

484
00:29:43,910 --> 00:29:47,360
You know, like Meta isn't
trained to make money off React.

485
00:29:47,360 --> 00:29:49,430
Well, in some ways Vercel is.

486
00:29:49,930 --> 00:29:53,200
And he also talks about, you know,
some of the, the server component

487
00:29:53,200 --> 00:29:57,050
development process, how that was
marketed how it's been interpreted.

488
00:29:57,550 --> 00:29:59,320
And he talks about burnout.

489
00:29:59,710 --> 00:30:04,090
And boy can I understand and sympathize
with this one on multiple levels.

490
00:30:04,522 --> 00:30:08,362
responding to issues and comments,
even when they're positive,

491
00:30:08,632 --> 00:30:09,952
takes a lot of time and effort.

492
00:30:10,522 --> 00:30:15,262
And when a lot of those comrades are,
you know, angry and critiquing and

493
00:30:15,262 --> 00:30:19,451
throwing around conspiracy theories,
that wears away at you a lot.

494
00:30:19,951 --> 00:30:23,791
So I have a huge amount of respect
for Lee and everything he's done

495
00:30:23,791 --> 00:30:27,481
for Vercel and next in the React
community over the last several years.

496
00:30:28,051 --> 00:30:33,421
And so I appreciated him doing the writeup
and I could totally identify with a lot

497
00:30:33,421 --> 00:30:34,711
of the points he was making in here.

498
00:30:35,211 --> 00:30:36,366
Carl: Yeah, definitely.

499
00:30:36,696 --> 00:30:40,616
And it's funny, I, you know, nobody,
nobody's ever paid me to do reactive

500
00:30:40,616 --> 00:30:44,816
flux things, and it's a very different
type of like community management.

501
00:30:45,236 --> 00:30:48,676
But I definitely, a lot of
what he said resonated with me.

502
00:30:48,766 --> 00:30:51,466
But from that perspective, and
also just like, I don't know.

503
00:30:51,966 --> 00:30:56,076
The burnout and, you know,
thanklessness of wrangling a large

504
00:30:56,076 --> 00:30:58,263
group of people is is pretty real.

505
00:30:58,573 --> 00:30:59,953
Mark: So it's a post worth reading.

506
00:31:00,348 --> 00:31:03,553
And Lee, if you ever hear this, thank
you for all your time and effort.

507
00:31:04,113 --> 00:31:04,443
Carl: Yeah.

508
00:31:04,443 --> 00:31:05,883
Thank you for all your time and effort.

509
00:31:05,883 --> 00:31:06,483
It's been a lot.

510
00:31:06,513 --> 00:31:06,963
It's been great.

511
00:31:06,996 --> 00:31:11,063
what you said about like Lee really
being like you think Lee, Robb is

512
00:31:11,063 --> 00:31:15,566
definitely a canonical dev rel, like
showed the world how dev rel happens.

513
00:31:15,566 --> 00:31:16,046
I think

514
00:31:16,496 --> 00:31:17,936
really, uh, personified it.

515
00:31:18,433 --> 00:31:22,353
Maybe in two remix doing
its own component model.

516
00:31:22,548 --> 00:31:25,488
Mark: we've been doing sort of a
running observation of what in the

517
00:31:25,488 --> 00:31:31,388
world are Michael Jackson and Ryan
Florence doing over in their corner.

518
00:31:31,778 --> 00:31:36,458
They, they continue to drop
cryptic hints on Twitter about the

519
00:31:36,458 --> 00:31:38,438
directions of remix version three.

520
00:31:38,798 --> 00:31:42,796
And while this isn't, trying to keep
this from being the, just repeat what

521
00:31:42,796 --> 00:31:48,376
they say on Twitter podcast, but, you
know, so far all we have to go by is

522
00:31:48,376 --> 00:31:49,816
the cryptic hints that they're dropping.

523
00:31:50,416 --> 00:31:56,056
And so we've gone from, you know, just
Remix v3 is its own thing to, it's

524
00:31:56,056 --> 00:32:01,486
going to use Preact to, well, actually,
I guess now it's not using Preact.

525
00:32:01,986 --> 00:32:07,511
Carl: Yeah, so I, I, I guess they want
to explore a similar kind of problem

526
00:32:07,511 --> 00:32:12,541
space as react and React are, I mean,
I, you know, that's the signals that

527
00:32:12,541 --> 00:32:17,071
they're putting out here is that like,
well, these existing tools do not solve

528
00:32:17,071 --> 00:32:19,681
the problem well enough, we believe.

529
00:32:19,681 --> 00:32:21,481
And so we're going to explore that.

530
00:32:21,911 --> 00:32:26,381
And, you know, I, fair enough, I, I think
there is more room to explore there.

531
00:32:26,451 --> 00:32:31,001
I know some discussion in reactive
flux on this, you know, on this

532
00:32:31,001 --> 00:32:33,771
link earlier Ricky had said like,
you know, good luck to them.

533
00:32:33,771 --> 00:32:38,550
I think they may find some of the
same constraints as React has,

534
00:32:38,550 --> 00:32:39,750
and I think that's pretty likely.

535
00:32:39,750 --> 00:32:44,339
But, you know, also there's a term coming
to mind uh, path dependence, which is,

536
00:32:44,339 --> 00:32:48,089
you know, like what the options available
to you going forward are dependent

537
00:32:48,089 --> 00:32:49,649
on the choices you made in the past.

538
00:32:49,919 --> 00:32:55,379
And so, like, you know, react is pretty
far down, it's set of chosen decisions.

539
00:32:55,479 --> 00:32:59,379
So I think there is some value in
backing out and saying like, well,

540
00:32:59,379 --> 00:33:01,029
hey, maybe we're in a local maximum.

541
00:33:01,029 --> 00:33:03,849
Let's explore some other
possible paths here.

542
00:33:04,359 --> 00:33:08,199
And yeah, so let me pick up where I
sat down earlier talking about effect.

543
00:33:08,359 --> 00:33:08,689
Right.

544
00:33:08,689 --> 00:33:13,489
So like, it, it feels to me like a
componentized model for the backend.

545
00:33:13,999 --> 00:33:18,129
And it's really interesting because
each, you know, backend component

546
00:33:18,309 --> 00:33:21,519
that you write, which I'm, they call
'EM Effects, but you know, this is a

547
00:33:21,519 --> 00:33:23,679
React chat, so I'm going to translate.

548
00:33:24,079 --> 00:33:28,379
So you write like a backend component
and it has a type safe it uses

549
00:33:28,379 --> 00:33:33,629
TypeScript generics to describe
its outputs, its possible errors

550
00:33:33,629 --> 00:33:37,849
emitted and what dependencies it
requires to be passed in effects.

551
00:33:37,999 --> 00:33:42,159
These backend components can like,
make their own dependencies available,

552
00:33:42,249 --> 00:33:45,459
you know, or they can say, you
need to provide this at runtime.

553
00:33:45,969 --> 00:33:52,139
And so that's pretty, that feels very
similar in use to me in like ideology

554
00:33:52,349 --> 00:33:54,599
to me as what React is trying to do.

555
00:33:54,723 --> 00:33:56,433
Mark: your props and your output.

556
00:33:56,933 --> 00:33:57,293
Carl: Right.

557
00:33:57,353 --> 00:33:58,853
Props, return value, boom.

558
00:33:59,003 --> 00:34:02,603
Like, okay, every return value is
JSX and it doesn't really matter

559
00:34:02,633 --> 00:34:05,003
specifically what, but you know.

560
00:34:05,503 --> 00:34:05,803
Yeah.

561
00:34:05,803 --> 00:34:11,837
So it, it, it's really interesting having
error safety as well as dependency type

562
00:34:11,837 --> 00:34:13,427
safety because like props are one thing.

563
00:34:13,847 --> 00:34:16,967
But you know that there's
no way to describe that.

564
00:34:16,997 --> 00:34:22,037
This component being rendered
relies on being nested

565
00:34:22,037 --> 00:34:24,587
underneath a context provider.

566
00:34:24,617 --> 00:34:27,527
Like you can do a runtime check for
that, but you can't do a a compiled

567
00:34:27,527 --> 00:34:29,447
time type safety check for that.

568
00:34:29,627 --> 00:34:33,017
And that's the kind of thing
that effect is enabling.

569
00:34:33,067 --> 00:34:34,807
It's that kind of dependency injection.

570
00:34:34,807 --> 00:34:38,437
Like what environment does this
expect to be run in, not just what

571
00:34:38,437 --> 00:34:40,567
inputs does it expect to be provided.

572
00:34:41,057 --> 00:34:45,857
I. So like using that in a backend
context, you know, in this, going all

573
00:34:45,857 --> 00:34:49,307
in on this in a backend space where
it's intended to be used has really

574
00:34:49,307 --> 00:34:53,057
made me reflect on the experience
of using React and what kind of,

575
00:34:53,087 --> 00:34:54,407
what some of its pain points are.

576
00:34:54,767 --> 00:35:01,287
And so I guess like the React core
team has gone all in on the transition

577
00:35:01,287 --> 00:35:04,227
boundary between the client and
the server with server components.

578
00:35:04,227 --> 00:35:07,317
Like they wanna really make that
smooth and instead of this request

579
00:35:07,317 --> 00:35:11,457
response model, just have it be
more fluid and you know, whatever.

580
00:35:11,917 --> 00:35:15,007
Yeah, streaming all that which is
great and that's a very interesting

581
00:35:15,217 --> 00:35:19,657
direction to explore, but it does
not address all of those kinds of

582
00:35:19,657 --> 00:35:22,567
things of how do we make a robust.

583
00:35:23,047 --> 00:35:28,447
Reliable application that can be
statically verified, will run as expected.

584
00:35:28,507 --> 00:35:32,557
And that is more of where
effect is coming at the problem

585
00:35:32,557 --> 00:35:34,087
space of code authoring from.

586
00:35:34,537 --> 00:35:38,167
And yeah, I think the, like both
of those are really interesting

587
00:35:38,167 --> 00:35:41,187
viable problem spaces to explore.

588
00:35:41,697 --> 00:35:47,187
And if Remix is saying, we think the
path that React is exploring is not the

589
00:35:47,187 --> 00:35:50,997
ideal user experience, maybe they're
gonna go more in something like this.

590
00:35:51,027 --> 00:35:55,887
And if they do, this is wild, pure,
rampant speculation on my part right now.

591
00:35:55,947 --> 00:36:00,057
But if they, you know, I can
see a possible world where one

592
00:36:00,062 --> 00:36:03,687
thing that might interest them
is the same kind of guarantees

593
00:36:03,687 --> 00:36:05,697
that effect is trying to provide.

594
00:36:06,027 --> 00:36:06,927
And that would be valuable.

595
00:36:06,927 --> 00:36:09,477
Like, so I, I, yeah, I'll still
be paying attention to this.

596
00:36:09,807 --> 00:36:12,896
I do have a greater degree of
skepticism it's a huge expansion of

597
00:36:12,896 --> 00:36:14,816
what scope of problem they're exploring.

598
00:36:15,206 --> 00:36:16,796
So that's challenging.

599
00:36:17,186 --> 00:36:18,821
But you know, they've taken
on big challenges before.

600
00:36:19,321 --> 00:36:20,581
Shipped things.

601
00:36:21,061 --> 00:36:23,251
So yeah, we'll be paying
attention and see what they see.

602
00:36:23,251 --> 00:36:23,821
What they come out with.

603
00:36:24,321 --> 00:36:26,901
Mark: Yeah, so basically where
things stand at the moment are

604
00:36:27,021 --> 00:36:28,491
lots of cryptic hints on Twitter.

605
00:36:28,581 --> 00:36:29,691
It's not gonna be a React.

606
00:36:29,811 --> 00:36:31,311
It's a different component model.

607
00:36:31,741 --> 00:36:33,691
They want to make it LLM friendly.

608
00:36:33,751 --> 00:36:38,011
We still haven't seen any good
examples, but I'm assuming they will

609
00:36:38,011 --> 00:36:42,601
do a big announcement at the Remix
Jam conference, which I think is in

610
00:36:42,911 --> 00:36:43,331
October.

611
00:36:43,586 --> 00:36:43,876
Carl: Yeah.

612
00:36:44,021 --> 00:36:46,151
Oh, they had just done, just
recently announced that.

613
00:36:46,349 --> 00:36:50,879
Mark: And then along with the rampant
speculation bit I saw a blog post just

614
00:36:50,879 --> 00:36:55,389
earlier, earlier today, but it was from
a month ago called Remix Three and the

615
00:36:55,389 --> 00:37:00,939
End of React Centric Architectures, which
also does a bit of, you know, speculating,

616
00:37:00,939 --> 00:37:06,189
hypothesizing on the ways various
frameworks have chosen to build things and

617
00:37:06,189 --> 00:37:09,669
says, you know, maybe it's a good thing
that Remix three is supposedly going back

618
00:37:09,669 --> 00:37:12,999
to a more web native framework approach.

619
00:37:13,499 --> 00:37:16,109
Carl: Yeah, and they're doing
Remix Jam right after React

620
00:37:16,109 --> 00:37:17,909
Conf in Toronto, so, yeah.

621
00:37:17,909 --> 00:37:20,879
We'll, we'll shot that out at the, in
the conferences section at the end too.

622
00:37:21,379 --> 00:37:21,739
Yeah.

623
00:37:22,279 --> 00:37:23,149
Okay, moving on.

624
00:37:23,149 --> 00:37:26,476
our last main content subject
for the month,  there's

625
00:37:26,476 --> 00:37:28,456
another security vulnerability.

626
00:37:28,456 --> 00:37:31,246
I feel like we, you know, we, we, we
talk about these somewhat regularly

627
00:37:31,246 --> 00:37:37,786
it feels like, but some pretty popular
NX packages were compromised on NPM.

628
00:37:37,886 --> 00:37:39,116
So NX is a,

629
00:37:39,326 --> 00:37:41,966
Mark: Monorepo management and build tool

630
00:37:42,506 --> 00:37:42,986
Carl: yes.

631
00:37:43,016 --> 00:37:44,876
It's a competitor to turbo repo.

632
00:37:44,876 --> 00:37:45,956
I, I, I think I would

633
00:37:46,016 --> 00:37:47,096
Mark: to, to some extent.

634
00:37:47,096 --> 00:37:47,396
Yeah.

635
00:37:47,651 --> 00:37:53,441
Carl: it got wholesale compromised as in
like everyone who installed it had a post

636
00:37:53,441 --> 00:38:01,217
install script run that swiped a bunch of
configuration files like .env and .npmrc,

637
00:38:01,544 --> 00:38:04,544
anywhere you can think that credentials
might be stored in your project

638
00:38:04,544 --> 00:38:06,854
workspace or elsewhere on your system.

639
00:38:07,064 --> 00:38:10,574
This script looked for and
then uploaded to GitHub.

640
00:38:10,914 --> 00:38:12,864
So that's really bad.

641
00:38:12,894 --> 00:38:16,254
This is a, this is a, this is a
theoretical exploit that I've been

642
00:38:16,254 --> 00:38:17,994
hearing about for the last 10 years.

643
00:38:17,994 --> 00:38:23,094
Like the vulnerabilities possible by
NPM post install has been a subject

644
00:38:23,094 --> 00:38:24,834
that comes up every couple of years.

645
00:38:25,284 --> 00:38:27,144
And, oh boy, this is a bad one.

646
00:38:27,394 --> 00:38:33,164
The, this blog post discussing the
vulnerability said that when they

647
00:38:33,164 --> 00:38:34,544
were, they were monitoring GitHub.

648
00:38:34,784 --> 00:38:38,294
'cause the way the script worked is
it would, if it found your GitHub

649
00:38:38,294 --> 00:38:42,804
credentials, if it found a valid SSH
key for GitHub or I guess actually

650
00:38:42,804 --> 00:38:44,544
an API token, not an SSH token.

651
00:38:44,604 --> 00:38:50,634
But if it found a GitHub API token, then
it would silently upload a new repo.

652
00:38:51,144 --> 00:38:54,474
So it, it, which is interesting
because it was a public repo on

653
00:38:54,474 --> 00:38:56,484
GitHub created by this malware.

654
00:38:56,754 --> 00:39:01,224
So there was some kind of public
metric that could be gathered

655
00:39:01,224 --> 00:39:02,934
for its scope of impact.

656
00:39:02,934 --> 00:39:08,264
And so there this blog post says that
they saw at one point, 1,400 of these

657
00:39:08,264 --> 00:39:11,234
repos created by this malware script.

658
00:39:11,234 --> 00:39:15,254
So like, that's quite a number
of people who got all of their

659
00:39:15,704 --> 00:39:17,504
secrets swiped off their system.

660
00:39:18,004 --> 00:39:22,294
One interesting thing that this
malware did is if it found an LLM

661
00:39:22,294 --> 00:39:27,904
tool on your system, it would write a
prompt to that LLM asking it to find

662
00:39:27,904 --> 00:39:29,554
all of the secrets on your system.

663
00:39:29,854 --> 00:39:33,994
So like if you, if you've got Claude,
like suddenly Claude is maliciously

664
00:39:33,994 --> 00:39:37,174
gathering all of your tokens from
your entire system that it can,

665
00:39:37,174 --> 00:39:38,434
you know, whatever it can access.

666
00:39:38,644 --> 00:39:40,474
Like, holy shit, that's bad.

667
00:39:40,974 --> 00:39:43,184
That's not, yeah, that's,
that's pretty bad.

668
00:39:43,611 --> 00:39:46,701
you know, last month we discussed
a, another vulnerability where

669
00:39:46,701 --> 00:39:50,001
the eslint-plugin-prettier
package maintainers were targeted.

670
00:39:50,311 --> 00:39:54,331
So I guess this, this could be, this
could be the same attackers perhaps,

671
00:39:54,331 --> 00:39:56,731
and they were just more successful
in that, you know, instead of.

672
00:39:57,231 --> 00:40:00,651
Getting busted while trying
to steal credentials for a

673
00:40:00,651 --> 00:40:02,571
major packages maintainers.

674
00:40:02,811 --> 00:40:03,831
They actually got it.

675
00:40:03,861 --> 00:40:07,401
And so now they have successfully
executed on this broader attack that

676
00:40:07,401 --> 00:40:08,811
they were maybe trying to do earlier.

677
00:40:09,311 --> 00:40:09,581
Woo.

678
00:40:09,941 --> 00:40:10,541
That's bad.

679
00:40:10,781 --> 00:40:13,291
And it sucks 'cause like what
do you, how do you even respond?

680
00:40:13,321 --> 00:40:16,171
What do, how can you keep
yourself safe if just

681
00:40:16,171 --> 00:40:21,486
Mark: Monitor your, monitor your
dependencies, actually look at lock files.

682
00:40:21,566 --> 00:40:25,526
I, I can say that there are some
good tools out there that will

683
00:40:25,526 --> 00:40:30,566
watch PRS for, you know, like what
packages are getting updated in this

684
00:40:30,566 --> 00:40:35,846
PR and, you know, warn you if any of
them have known PO known problems.

685
00:40:36,126 --> 00:40:38,886
That's definitely a valuable thing
to include in the CI process.

686
00:40:39,386 --> 00:40:39,676
Carl: Yeah.

687
00:40:39,821 --> 00:40:40,361
True.

688
00:40:40,861 --> 00:40:43,921
But man, one of the, one of the
challenging parts about this

689
00:40:44,221 --> 00:40:45,996
particular vulnerability is the.

690
00:40:46,496 --> 00:40:49,256
I, I remember half of the discussion
that I saw earlier, and I can't

691
00:40:49,256 --> 00:40:52,786
remember where I found it, so I can't
quickly refresh my memory, but there,

692
00:40:52,861 --> 00:40:59,586
a, a popular tool uses NX at latest
on like, you know, project Bootstrap.

693
00:40:59,946 --> 00:41:04,656
So like, you know, if you're just casually
idly using whatever project generator

694
00:41:04,656 --> 00:41:08,186
this was to start something new oops.

695
00:41:08,216 --> 00:41:10,226
You got the latest NX
that was compromised.

696
00:41:10,226 --> 00:41:12,326
So like that's not even,
yeah, I don't know.

697
00:41:12,326 --> 00:41:12,776
Just like

698
00:41:13,094 --> 00:41:16,424
Mark: the comment was actually in the,
the tech reads and news link and it was

699
00:41:16,424 --> 00:41:17,504
the NX vs.

700
00:41:17,504 --> 00:41:18,644
Code extension.

701
00:41:19,184 --> 00:41:19,474
Carl: Okay.

702
00:41:19,474 --> 00:41:19,754
Okay.

703
00:41:19,929 --> 00:41:22,089
That's a li that's at least
a little bit different vs.

704
00:41:22,089 --> 00:41:27,659
Code extension is not as popularly
used as a, you know, project

705
00:41:27,659 --> 00:41:30,659
bootstrap tool, but yeah, not great.

706
00:41:31,159 --> 00:41:31,449
Okay.

707
00:41:31,949 --> 00:41:32,819
Into the lightning round.

708
00:41:33,092 --> 00:41:33,527
Mark: Go for it.

709
00:41:33,888 --> 00:41:39,498
Carl: I saw this post from, it was a
blog post summarizing a podcast from

710
00:41:39,508 --> 00:41:42,038
react Native Radio from Infinite Red.

711
00:41:42,038 --> 00:41:42,578
Great Folks.

712
00:41:43,504 --> 00:41:48,454
They spoke with the maintainers of
React strict Dom and React native

713
00:41:48,454 --> 00:41:50,374
for web comparing and contrasting.

714
00:41:50,654 --> 00:41:54,404
We had discussed React strict dom
a about a year and a half ago.

715
00:41:54,404 --> 00:41:56,114
It was like February of 2024.

716
00:41:56,564 --> 00:41:59,114
And a, a lot of what we did
was compare and contrast it

717
00:41:59,114 --> 00:42:01,044
against React native for web.

718
00:42:01,584 --> 00:42:06,594
So this was like very precisely the
type of conversation we had except

719
00:42:06,594 --> 00:42:10,344
with the maintainers who aren't
just speculating and guessing and

720
00:42:10,374 --> 00:42:13,434
inferring, but like they, no, they
made this like, they know how it works.

721
00:42:13,434 --> 00:42:14,484
They know what the trade-offs are.

722
00:42:14,884 --> 00:42:18,544
So it's got some really great
architectural diagrams explaining the

723
00:42:18,544 --> 00:42:20,344
distinction and what the difference is.

724
00:42:20,654 --> 00:42:24,194
It lines up pretty well with what I
recall us discussing and they have

725
00:42:24,194 --> 00:42:28,574
a really good little flow chart for
making decisions about you know, TLDR

726
00:42:28,574 --> 00:42:30,194
should you adopt React strict dom.

727
00:42:30,694 --> 00:42:33,904
And they did a nice little handy visual,
which I'm gonna go to the Happy Path

728
00:42:34,414 --> 00:42:37,914
through the Happy Path on, which is
do you already have React native app?

729
00:42:37,974 --> 00:42:38,394
No.

730
00:42:38,859 --> 00:42:40,329
Will you need web support eventually?

731
00:42:40,359 --> 00:42:40,809
Yes.

732
00:42:40,959 --> 00:42:41,919
Use extract Dom.

733
00:42:41,919 --> 00:42:48,879
So like basically they're saying this
is a great low level set of abstractions

734
00:42:48,909 --> 00:42:54,669
that will make it more feasible
to reuse your code in more places.

735
00:42:54,739 --> 00:42:57,079
You know, like the benefit has
always theoretically been that

736
00:42:57,079 --> 00:43:01,519
you could reuse much of the code
between React native and web.

737
00:43:01,859 --> 00:43:04,079
But I've tried to do that a
couple of times and the practical

738
00:43:04,079 --> 00:43:06,149
realities are challenging.

739
00:43:06,179 --> 00:43:10,609
Like, you know, just you need to
use doing abstractions so that, that

740
00:43:10,609 --> 00:43:12,589
work in both places is really hard.

741
00:43:12,829 --> 00:43:16,249
So this acknowledge React
native sorry, react strict.

742
00:43:16,249 --> 00:43:19,729
Dom sort of acknowledges that and says,
rather than trying to make a brand

743
00:43:19,729 --> 00:43:25,899
new abstraction on top of both React
Native and react dom, we are going to

744
00:43:25,899 --> 00:43:29,739
lean more heavily on the web platform
as an existing stable abstraction.

745
00:43:30,219 --> 00:43:30,789
Which is cool.

746
00:43:30,849 --> 00:43:31,239
I like it.

747
00:43:31,239 --> 00:43:31,719
It seems cool.

748
00:43:31,749 --> 00:43:32,799
This is a really great blog post.

749
00:43:33,369 --> 00:43:33,999
Definitely recommend.

750
00:43:34,499 --> 00:43:38,069
Mark: The V8 JavaScript engine
developers put up a post where they

751
00:43:38,069 --> 00:43:42,299
said they've spent a lot of time
trying to optimize js, ON stringy.

752
00:43:42,799 --> 00:43:46,849
Think about how many times your code
stringys stuff, whether it's sending

753
00:43:46,849 --> 00:43:52,099
back an H TT P response or you know,
serializing things into an extension.

754
00:43:52,559 --> 00:43:54,689
they go, they go into a bunch
of technical detail about how

755
00:43:54,689 --> 00:43:56,039
they've tried to make this faster.

756
00:43:56,238 --> 00:44:01,348
Carl: specifically that problem parsing
Jason, Jason Parse performance is exact,

757
00:44:01,558 --> 00:44:05,068
like that was the reason for React
native doing the new architecture, which

758
00:44:05,068 --> 00:44:09,778
they've spent like much of the last
year communicating and executing on.

759
00:44:09,778 --> 00:44:13,978
So yeah, the massive problem
for the entire ecosystem,

760
00:44:14,478 --> 00:44:18,003
Mark: You know, like other than actually
executing the JavaScript code faster,

761
00:44:18,003 --> 00:44:19,893
like string finding stuff has to be

762
00:44:19,893 --> 00:44:22,353
one of the most common things
your JavaScript code does.

763
00:44:23,013 --> 00:44:26,523
So I believe this is supposed to
be out in, I think it was like V

764
00:44:26,523 --> 00:44:34,723
eight like 13.8 I think it said
which is available in Chrome 1 38.

765
00:44:35,233 --> 00:44:40,183
And I don't know what node version will
contain that, that version of V eight.

766
00:44:40,483 --> 00:44:41,953
But faster is good.

767
00:44:42,453 --> 00:44:44,913
Carl: Yeah, faster is so good,
especially for stringifying.

768
00:44:44,913 --> 00:44:45,483
Yeah, man.

769
00:44:45,723 --> 00:44:50,292
Just the number of plate serializing
and des serializing is one of

770
00:44:50,292 --> 00:44:54,582
the largest costs, you know,
performance costs like everywhere.

771
00:44:54,582 --> 00:44:56,052
So yeah, it'll love that.

772
00:44:56,102 --> 00:44:56,622
That's great.

773
00:44:56,938 --> 00:45:02,258
Node 22 point 18 flags TypeScript
type stripping support.

774
00:45:02,645 --> 00:45:04,685
node has had experimental support for.

775
00:45:05,185 --> 00:45:08,665
Interpreting TypeScript code
and stripping out the types.

776
00:45:08,740 --> 00:45:11,770
doesn't actually check them or
anything, but it allows you to

777
00:45:11,770 --> 00:45:17,320
take a project authored natively in
TypeScript and run it with node without

778
00:45:17,320 --> 00:45:21,670
a compilation step, without building
it through the TypeScript compiler.

779
00:45:21,730 --> 00:45:24,640
Mark: Or, or using a tool
like TS Node to execute it.

780
00:45:24,640 --> 00:45:25,000
Carl: Yes.

781
00:45:25,160 --> 00:45:25,460
Yeah.

782
00:45:25,485 --> 00:45:25,835
Right.

783
00:45:25,910 --> 00:45:26,570
More directly.

784
00:45:26,570 --> 00:45:28,160
This is a replacement for TS node.

785
00:45:28,500 --> 00:45:28,980
And that's great.

786
00:45:28,980 --> 00:45:30,060
It's no longer experimental.

787
00:45:30,090 --> 00:45:31,530
It's, they're now saying it works.

788
00:45:31,530 --> 00:45:33,540
it's officially blessed, it's released.

789
00:45:33,880 --> 00:45:34,570
Love that.

790
00:45:34,990 --> 00:45:41,260
Definitely the ecosystem has moved more
from, you know, a long time ago it was

791
00:45:41,260 --> 00:45:45,070
very focused on you compile the code and
then you take those built artifacts and

792
00:45:45,070 --> 00:45:48,460
you run them, and if the type checker
fails, you don't get a built artifact

793
00:45:49,030 --> 00:45:53,197
and you know, the metagame here has
shifted a little bit more into the.

794
00:45:53,752 --> 00:45:59,182
Type checking is one very valuable
part of verifying your code

795
00:45:59,182 --> 00:46:04,852
statically, but it is not necessarily
where the compilation step lives.

796
00:46:04,882 --> 00:46:08,952
So, many more projects in my experience
have moved towards sort of a parallel

797
00:46:08,952 --> 00:46:13,002
model where you have a build step
and there is type checking in the

798
00:46:13,002 --> 00:46:16,932
project, but it just kind of runs
separately from that build step.

799
00:46:17,032 --> 00:46:20,622
So this is, this is a great tool
enabling that kind of pattern.

800
00:46:20,622 --> 00:46:22,032
And it's released, it's done.

801
00:46:22,032 --> 00:46:22,542
Yay.

802
00:46:23,042 --> 00:46:26,192
Mark: A couple RSC and
project related updates.

803
00:46:26,222 --> 00:46:32,292
We've talked previously about how,
vet itself has been missing some

804
00:46:32,292 --> 00:46:37,902
pieces in that would enable like full
RSC support for vet based frameworks

805
00:46:38,382 --> 00:46:43,052
and that there has been a work in
progress PR to try to add better

806
00:46:43,052 --> 00:46:46,382
RSC primitives into vet somehow.

807
00:46:46,802 --> 00:46:53,702
So the Waku RSE framework is now making
use of vet's work in progress plugin

808
00:46:53,942 --> 00:46:57,662
rather than whatever layers they had
built for themselves internally already.

809
00:46:58,232 --> 00:47:00,362
So it's good to see that
that's coming together.

810
00:47:00,822 --> 00:47:05,532
And then I saw an announcement for a
new framework called rari, which is

811
00:47:05,592 --> 00:47:10,842
sort of an acronym for something, some,
something faster rendering somehow.

812
00:47:11,202 --> 00:47:15,192
But it looks like a, it's supposed
to be an RSC based framework that

813
00:47:15,192 --> 00:47:17,412
has a custom low level layer.

814
00:47:17,912 --> 00:47:18,902
Built with rust.

815
00:47:18,902 --> 00:47:22,262
And of course, as we all know,
rust makes everything faster.

816
00:47:22,722 --> 00:47:26,292
But it sounds like someone looked
at some benchmarks of, you know,

817
00:47:26,292 --> 00:47:30,672
like next RSC performance and said,
I think I can do better myself.

818
00:47:30,912 --> 00:47:34,272
And has built their own full stack
framework that has RSC support

819
00:47:34,662 --> 00:47:37,452
using a custom low level rust layer.

820
00:47:37,952 --> 00:47:38,242
Carl: Neat.

821
00:47:38,387 --> 00:47:38,897
Cool.

822
00:47:38,987 --> 00:47:42,287
Yeah, they do claim four, four times
faster component rendering under load

823
00:47:42,287 --> 00:47:44,687
four milliseconds versus 17 milliseconds.

824
00:47:45,187 --> 00:47:46,057
And that's cool.

825
00:47:46,327 --> 00:47:50,461
I don't know that if your problematic
performance is 17 milliseconds, that's

826
00:47:50,941 --> 00:47:52,291
maybe not the worst problem to have.

827
00:47:52,963 --> 00:47:57,733
Mark: Then separate from all that the
always wonderful Dominic Dome TK Dodo

828
00:47:57,793 --> 00:47:59,563
has put up a couple great blog posts.

829
00:47:59,933 --> 00:48:04,163
One is the latest in the series of posts
on how to use React Query correctly

830
00:48:04,223 --> 00:48:09,143
in this case, how to use the ability
to select values out of a query.

831
00:48:09,173 --> 00:48:11,483
So maybe like you have a,
a list items query and you

832
00:48:11,483 --> 00:48:12,713
only want to grab one of 'em.

833
00:48:13,203 --> 00:48:16,713
And then you also put up a post talking
about how a lot of time you don't

834
00:48:16,713 --> 00:48:19,053
actually need the used callback hook.

835
00:48:19,543 --> 00:48:22,873
There's a lot of cases that used
callback is actually kinda useless.

836
00:48:23,503 --> 00:48:25,513
So excellent reading as always.

837
00:48:26,013 --> 00:48:28,823
Carl: Can you tell I've been using
effect and it's just been living

838
00:48:28,823 --> 00:48:30,143
in my brain for a lot of the time.

839
00:48:30,723 --> 00:48:34,453
I, as part of reading it, I found
this blog post that they wrote

840
00:48:34,783 --> 00:48:36,173
pretty recently beginning of July.

841
00:48:36,673 --> 00:48:41,053
Where they had done, they had actually
forked the TypeScript compiler

842
00:48:41,053 --> 00:48:45,123
wholesale and tried to do what they
called TypeScript plus TS plus.

843
00:48:45,673 --> 00:48:51,453
And I guess part of the idea, as you,
as I've been using effect, I can feel

844
00:48:51,453 --> 00:48:58,383
very strongly the desire for JavaScript
to support a couple of different tools

845
00:48:58,383 --> 00:49:03,123
that I, I I, I had remembered seeing as
proposals many, many years ago and waited

846
00:49:03,333 --> 00:49:08,333
many, many years for them to land mo
specifically the pipeline operator for

847
00:49:08,333 --> 00:49:14,883
composing functional, you know, programs
together and pattern matching, which

848
00:49:14,933 --> 00:49:19,013
resembles a switch case, but lets you
match on like properties and attributes

849
00:49:19,013 --> 00:49:22,553
and, you know, things like that in a
different way, in a more flexible way.

850
00:49:23,033 --> 00:49:23,513
So.

851
00:49:24,013 --> 00:49:29,743
They tried to fork the compiler to
make errors a little bit better.

852
00:49:29,773 --> 00:49:32,773
Basically, like they're really
pushing the bounds of everything you

853
00:49:32,773 --> 00:49:34,933
can do in TypeScript and JavaScript.

854
00:49:35,413 --> 00:49:41,163
So the, as part of that, they explored
fully forking, TypeScript and this, so

855
00:49:41,163 --> 00:49:46,113
this is a great postmortem of their design
goals and what they were trying to achieve

856
00:49:46,113 --> 00:49:48,393
and why they have backed off of that.

857
00:49:48,813 --> 00:49:52,753
Yeah, how far we went and what went
wrong, what we learned it's pretty good.

858
00:49:52,813 --> 00:49:55,093
Definitely very interesting like this.

859
00:49:55,093 --> 00:50:00,097
Just reading more about effect, I can
just like, it just the amount of the

860
00:50:00,097 --> 00:50:04,687
number of different places where they're
pushing the envelope and like iterating

861
00:50:04,687 --> 00:50:09,637
on the state of the art in web on the
backend is just really palpable to me.

862
00:50:09,637 --> 00:50:11,797
So, definitely an interesting read here.

863
00:50:12,297 --> 00:50:14,487
Mark: I, I, I thought
it was a good blog post.

864
00:50:14,537 --> 00:50:17,687
Honestly, I also partly appreciate
it just because they said we spent

865
00:50:17,717 --> 00:50:21,137
like an entire year trying to build
this thing and it didn't pan out.

866
00:50:21,587 --> 00:50:26,147
Here's what we tried and what we learned
and what went wrong in the process.

867
00:50:26,262 --> 00:50:28,907
I, I, appreciate good art,
good write-ups, like that.

868
00:50:29,372 --> 00:50:30,422
Carl: Yeah, right.

869
00:50:30,422 --> 00:50:34,502
I feel like this is good to read as
an engineer because it's just a really

870
00:50:34,502 --> 00:50:38,762
good postmortem where you can really
understand their thought process of why

871
00:50:38,762 --> 00:50:42,452
they tried to do this, what benefits
they were hoping to get, and what

872
00:50:42,962 --> 00:50:46,442
challenges they ran into that made
them say, okay, this is not achievable.

873
00:50:46,752 --> 00:50:47,982
Just really good, really good read.

874
00:50:48,482 --> 00:50:51,917
Mark: I saw a good short post from
Jordan Eldridge, who I believe created

875
00:50:51,917 --> 00:50:55,757
the web amp recreation of Winamp.

876
00:50:56,217 --> 00:51:00,957
Where gave some, gave some thoughts on
what happens when you do a React used

877
00:51:00,957 --> 00:51:08,187
transition and you apply some other state
updates while the transition is going on.

878
00:51:08,647 --> 00:51:11,857
Short but useful, especially
since transitions are a newer

879
00:51:11,857 --> 00:51:13,327
part of the react rendering model.

880
00:51:13,768 --> 00:51:19,368
And then I also saw a post called A Clock
That Doesn't Snap, which talks about

881
00:51:19,398 --> 00:51:24,678
some of the dealing with inconsistency
problems between server rented values like

882
00:51:24,678 --> 00:51:29,538
dates, and then what happens when you try
to actually hydrate that on the client.

883
00:51:30,018 --> 00:51:34,758
And a couple different techniques for
trying to make it not be inconsistent.

884
00:51:35,258 --> 00:51:35,768
Carl: Interesting.

885
00:51:36,278 --> 00:51:38,918
Mark: There was an article on React Cache.

886
00:51:38,948 --> 00:51:45,098
It's about consistency, so React added
the cache, API for use on the server,

887
00:51:45,518 --> 00:51:48,278
and it's, it's a sort of memo function.

888
00:51:48,398 --> 00:51:53,828
The idea is that you can get, like
if you need to make one fetch call

889
00:51:53,828 --> 00:51:58,058
in multiple places while doing server
side rendering, you can try to ensure

890
00:51:58,058 --> 00:52:02,528
that it only happens once during that
particular render pass on the server.

891
00:52:03,098 --> 00:52:06,518
And so the post goes into some
detail on what the cache method

892
00:52:06,518 --> 00:52:10,708
is, why you want, would want to use
it, and how it, you know, actually

893
00:52:10,708 --> 00:52:15,028
using that cashed value during the
render can produce more consistent

894
00:52:15,028 --> 00:52:17,038
results during the render process.

895
00:52:17,368 --> 00:52:20,758
And then goes into a little bit more
about like some of the conceptual

896
00:52:20,758 --> 00:52:26,294
behavior of React components and
what is pure versus impure anyway.

897
00:52:26,807 --> 00:52:32,617
saw an article that gave some battle
hardened details on the complete guide

898
00:52:32,617 --> 00:52:35,407
to self-hosting Next JS at scale.

899
00:52:35,947 --> 00:52:39,197
So next is commonly used with Vercel.

900
00:52:39,217 --> 00:52:43,417
You can deploy it yourself, but
you sometimes have to fill in some

901
00:52:43,417 --> 00:52:44,977
of the missing hosting pieces.

902
00:52:45,457 --> 00:52:48,637
And so this was a good post that
gave and that talked about, you

903
00:52:48,637 --> 00:52:52,957
know, what are, what happens
when you try to use Next Cache?

904
00:52:53,107 --> 00:52:55,627
And it by default cache is values locally.

905
00:52:55,627 --> 00:52:58,087
But if you've got multiple copies
of the server rendering, now

906
00:52:58,087 --> 00:53:00,847
you can have inconsistencies
between different instances.

907
00:53:01,297 --> 00:53:05,527
So how would you break that out into
using a Redis server or something?

908
00:53:05,527 --> 00:53:09,907
Instead, how can you handle image
optimization and CDN configuration?

909
00:53:10,407 --> 00:53:12,657
So if you're trying to do any
self host, you know, next, this

910
00:53:12,657 --> 00:53:14,112
looks like a very useful guide.

911
00:53:14,612 --> 00:53:15,092
Carl: Love that.

912
00:53:15,362 --> 00:53:18,692
Such a good, deep technical
writeup of, I mean, right.

913
00:53:19,202 --> 00:53:23,192
Self-hosting next is such a big
problem that people discuss regularly

914
00:53:23,192 --> 00:53:26,242
that I, I just love seeing, you
know, a proper writeup about it.

915
00:53:26,742 --> 00:53:31,122
Mark: Then finally we have a post from
Aurora Scharf who spent a lot of time

916
00:53:31,122 --> 00:53:35,472
researching and writing about server
components and various usage patterns,

917
00:53:35,922 --> 00:53:41,382
and she has an excellent post on server
and client component composition in

918
00:53:41,382 --> 00:53:45,882
practice, which gives some examples
of how you can intermingle server and

919
00:53:46,092 --> 00:53:49,842
client components to do some of the
work on the server, some of the work

920
00:53:49,842 --> 00:53:53,112
on the client figure, and figure out
where the boundaries ought to be.

921
00:53:53,482 --> 00:53:53,932
Carl: Yeah.

922
00:53:53,932 --> 00:53:57,342
figuring out where the boundaries
are should lie in things

923
00:53:57,342 --> 00:53:58,927
that's uh, very challenging.

924
00:53:59,606 --> 00:54:02,616
Mark: And I think that's actually all
we've got for this month, which is good

925
00:54:02,616 --> 00:54:04,026
'cause we're right about at at time.

926
00:54:04,378 --> 00:54:04,708
Carl: Cool.

927
00:54:04,708 --> 00:54:06,505
Let's wrap up here with some conferences.

928
00:54:06,977 --> 00:54:11,159
We got React, Universe coming up in
just about a week in September 2nd

929
00:54:11,159 --> 00:54:13,769
through fourth in Wroclaw, Poland.

930
00:54:14,169 --> 00:54:17,299
There's also Ways Conf
September 16th and 17th.

931
00:54:17,602 --> 00:54:18,652
Krakow Great.

932
00:54:18,652 --> 00:54:19,312
Also in Poland.

933
00:54:19,342 --> 00:54:21,322
So yeah, Poland heavy uh, September.

934
00:54:21,742 --> 00:54:26,302
Then right after that, Cascadia Js,
September 18th and 19th in Seattle.

935
00:54:26,842 --> 00:54:31,562
Coincident with Squiggle Con September
18th in Boston, which I will be at

936
00:54:32,507 --> 00:54:37,397
Then in October we've got React Alicante,
October 2nd through fourth in Spain.

937
00:54:37,719 --> 00:54:38,919
Mark: I will be speaking at that one.

938
00:54:39,241 --> 00:54:45,391
I was not going to be there originally,
but I will be flying back from Spain and

939
00:54:45,391 --> 00:54:47,911
showing up at React Conf in Las Vegas.

940
00:54:48,411 --> 00:54:49,401
That's gonna be a trip.

941
00:54:49,901 --> 00:54:50,351
Carl: Yeah.

942
00:54:50,531 --> 00:54:51,281
Oh, wild.

943
00:54:51,396 --> 00:54:51,686
Yeah.

944
00:54:51,791 --> 00:54:55,301
'cause we've got, you know,
react conf in Las Vegas right.

945
00:54:55,301 --> 00:54:56,621
Then October 7th and eighth,

946
00:54:56,931 --> 00:55:00,735
then, like we mentioned earlier, we've
got Remix Jam October 10th in Toronto.

947
00:55:00,735 --> 00:55:04,853
So if you really, like, you could
fly out to Vegas and then fly across

948
00:55:04,853 --> 00:55:07,283
the, well, I was gonna say across the
country, but it's a different country.

949
00:55:07,283 --> 00:55:09,803
You can fly across the
continent to Toronto.

950
00:55:10,303 --> 00:55:10,633
Cool.

951
00:55:10,963 --> 00:55:11,893
That's all we got for you today.

952
00:55:12,202 --> 00:55:13,255
Thanks so much for joining us.

953
00:55:13,825 --> 00:55:16,525
We will be back on the last Wednesday
of the month here in the live

954
00:55:16,525 --> 00:55:19,225
stage or back in your podcast feed
just as soon as we can after that.

955
00:55:19,725 --> 00:55:20,715
Mark: Thank you all for listening.

956
00:55:20,715 --> 00:55:24,225
Hopefully the list of links has
been useful and informative.

957
00:55:24,535 --> 00:55:29,365
If you are going to be at either
Squiggle Con, react Delicate, react

958
00:55:29,965 --> 00:55:32,245
Ante, or React conf please say hi.

959
00:55:32,245 --> 00:55:36,715
I will be running around possibly wearing
my Simpsons picture as a name tag.

960
00:55:37,080 --> 00:55:37,440
Carl: great.

961
00:55:37,560 --> 00:55:38,100
Love that.

962
00:55:38,490 --> 00:55:38,995
Yeah, same.

963
00:55:38,995 --> 00:55:39,395
Likewise.

964
00:55:39,395 --> 00:55:44,370
If you see me in Boston or in Las Vegas
say, Hey,  We gather sources from this

965
00:55:44,370 --> 00:55:48,809
week in React Bites, dev the React JS
subreddit, and here in Reactive Flux

966
00:55:48,809 --> 00:55:50,789
from the uh, tech News and Reads channel.

967
00:55:51,219 --> 00:55:53,739
If you see anything that you think
we should discuss definitely send it

968
00:55:53,739 --> 00:55:56,109
over to us at hello@reactiveflux.com.

969
00:55:56,509 --> 00:55:59,119
if this is a show you get value from
and wanna support, best way you can

970
00:55:59,119 --> 00:56:01,699
do so is by submitting a review on
wherever you listen and tell your

971
00:56:01,699 --> 00:56:02,629
friends and coworkers about it.

972
00:56:02,844 --> 00:56:03,474
Thanks so much.

973
00:56:03,517 --> 00:56:03,937
you next month.

974
00:56:04,137 --> 00:56:04,617
Mark: Take care.