РАСШИФРОВКА 🔗
1
00:00:00,056 --> 00:00:00,506
Carl: Hello.
2
00:00:00,546 --> 00:00:04,486
Thank you for joining us for the July
edition of This Month in React, as we
3
00:00:04,486 --> 00:00:08,076
recap what's been going on with React
Native and other things across the web.
4
00:00:08,515 --> 00:00:11,126
We are coming to you live
from Reactiflux, the place for
5
00:00:11,136 --> 00:00:12,585
professional developers using React.
6
00:00:12,976 --> 00:00:13,886
And I'm Carl.
7
00:00:13,936 --> 00:00:16,595
I'm a staff product developer and
freelance community leader here at
8
00:00:16,595 --> 00:00:20,185
Reactiflux, where I run community programs
like these events and build tools like
9
00:00:20,799 --> 00:00:22,129
help keep the community operating.
10
00:00:22,489 --> 00:00:23,429
Mark: Hi, I'm Mark.
11
00:00:23,449 --> 00:00:26,809
My day job is replay.io, where
we've built time travel debugging,
12
00:00:26,819 --> 00:00:31,109
are working on autonomous QA, and I
get to do all kinds of awesome time
13
00:00:31,109 --> 00:00:33,259
travel-powered React analysis tools.
14
00:00:33,619 --> 00:00:37,999
And outside of that, I am still
doing Redux stuff, and I'm actually
15
00:00:38,009 --> 00:00:41,139
finding the energy to do a fair amount
of that right now, which is cool.
16
00:00:41,579 --> 00:00:41,929
Carl: Nice.
17
00:00:41,989 --> 00:00:42,419
Heck yeah.
18
00:00:42,839 --> 00:00:46,989
Hell yeah for finding the energy
to invest in a project you love.
19
00:00:47,459 --> 00:00:47,759
Mark: Yep.
20
00:00:47,939 --> 00:00:50,719
I'm also actually back at home
after, like, two and a half months
21
00:00:50,719 --> 00:00:52,719
of almost nonstop conference travel.
22
00:00:53,049 --> 00:00:55,889
Carl: We were saying in prep, we
have kind of a grab bag this month.
23
00:00:55,899 --> 00:00:59,119
There's not, like, one big thing
to discuss, but yeah, we're
24
00:00:59,119 --> 00:01:00,089
gonna get into a couple things.
25
00:01:00,119 --> 00:01:03,209
Uh, obviously there's been more
security stuff and new releases of
26
00:01:03,209 --> 00:01:07,119
major projects, like TypeScript 7,
which we've discussed, like, four
27
00:01:07,119 --> 00:01:08,659
times already, but y- it's here.
28
00:01:08,669 --> 00:01:08,999
Yay.
29
00:01:09,459 --> 00:01:13,399
We also are gonna get into some
open source governance questions.
30
00:01:13,409 --> 00:01:15,859
There's been some developments
on the React Foundation.
31
00:01:15,919 --> 00:01:20,539
And l- kind of out of left field at
the same time, Poimandres a cooperative
32
00:01:20,539 --> 00:01:23,219
doing open source around Three.js.
33
00:01:23,299 --> 00:01:25,299
It also published some governance work.
34
00:01:25,629 --> 00:01:26,999
So yeah, we're gonna get into it.
35
00:01:27,109 --> 00:01:29,109
But first, the first new release.
36
00:01:29,529 --> 00:01:33,359
Vite+ from Voidzero is in beta now.
37
00:01:33,739 --> 00:01:34,729
Mark: It's not paid anymore.
38
00:01:34,739 --> 00:01:34,779
Oh, okay.
39
00:01:34,789 --> 00:01:35,529
They dropped that.
40
00:01:35,529 --> 00:01:40,099
I think they dropped the paid part
even before they got bought out.
41
00:01:40,269 --> 00:01:41,399
They initially said it was paid.
42
00:01:41,779 --> 00:01:44,779
Then they said, "No, no, we'll, we'll
make Vite+ free. We're gonna build
43
00:01:44,779 --> 00:01:49,949
our own server runtime layer on top
of Cloudflare," and then Cloudflare
44
00:01:49,949 --> 00:01:51,269
just bought the entire company.
45
00:01:51,957 --> 00:01:55,007
So- Great … Plus itself, as far
as I know, is going to be entirely
46
00:01:55,007 --> 00:01:56,547
free at this point multiply.
47
00:01:57,147 --> 00:02:01,537
But it's just the Void Zero company
had been paying a bunch of people to
48
00:02:01,537 --> 00:02:08,247
build out OXC, you know, that whole
layer of parser tooling, partly to use
49
00:02:08,257 --> 00:02:12,507
in the Rolldown Rust-based bundler.
50
00:02:13,027 --> 00:02:16,527
The latest version of Vite uses
Rolldown, but then there's all these
51
00:02:16,557 --> 00:02:19,907
other Rust-based tools related to that.
52
00:02:20,277 --> 00:02:25,017
And so Vite Plus is a combination
of we have pre-configured all these
53
00:02:25,017 --> 00:02:30,147
different tools into one super package,
as well as added some additional
54
00:02:30,147 --> 00:02:31,817
layers of functionality on top of that.
55
00:02:32,117 --> 00:02:35,677
So it's essentially supposed to be
an entire JS development suite in
56
00:02:35,677 --> 00:02:39,757
a box, sort of akin to what Rome
was promising a few years ago.
57
00:02:40,197 --> 00:02:40,597
Carl: Cool.
58
00:02:40,687 --> 00:02:41,067
Love that.
59
00:02:41,117 --> 00:02:44,737
Mark: Meanwhile, as mentioned, we have
talked about this repeatedly, so I
60
00:02:44,737 --> 00:02:49,747
don't have to go into a lot of details,
but TypeScript 7 is finally live.
61
00:02:50,237 --> 00:02:50,797
Hooray.
62
00:02:51,117 --> 00:02:55,297
This is the Go implemented native
implementation of the TypeScript
63
00:02:55,317 --> 00:03:00,247
compiler that is supposed to be
up to 10X faster, so the actual…
64
00:03:00,247 --> 00:03:05,737
If you install the actual TypeScript
package at latest now, it is actually
65
00:03:05,747 --> 00:03:07,827
built with Go under the hood.
66
00:03:08,267 --> 00:03:12,167
The biggest caveats here at the moment, as
we've again talked about, the programmatic
67
00:03:12,167 --> 00:03:20,317
TypeScript API essentially does not exist
in version seven, because the API had
68
00:03:20,317 --> 00:03:26,199
been partly official, partly unofficial
before that And lots of different tools
69
00:03:26,209 --> 00:03:28,059
had various dependencies and needs.
70
00:03:28,409 --> 00:03:32,219
A lot of them had hacked together
solutions in the past, and so the
71
00:03:32,369 --> 00:03:35,109
TypeScript team said, "Okay, we
know the compiler itself's working.
Load full transcript
72
00:03:35,109 --> 00:03:36,329
We're gonna get that out the door.
73
00:03:36,879 --> 00:03:43,649
We want to take our time and carefully
consider what a better and proper public
74
00:03:43,679 --> 00:03:48,709
API would look like to support all the
different use cases people have come up
75
00:03:48,709 --> 00:03:53,889
with, and we'll get that out the door in,
like, a version 7.1 or 7.2." so there is
76
00:03:53,889 --> 00:03:55,829
some, there is an update on that front.
77
00:03:56,099 --> 00:04:00,919
They've put up a PR for something
they're calling content mappers, and
78
00:04:00,919 --> 00:04:05,729
the way I'm understanding this is that
for other languages like, say, View or
79
00:04:05,729 --> 00:04:10,349
Angular that have templates, you want
to be able to type check the templates.
80
00:04:11,059 --> 00:04:15,109
The TypeScript compiler handles
JSX, which means React kind of
81
00:04:15,109 --> 00:04:16,649
got special treatment there.
82
00:04:17,029 --> 00:04:21,679
But how can other languages
actually get similar behavior
83
00:04:21,689 --> 00:04:25,009
for non-TypeScript syntax?
84
00:04:25,419 --> 00:04:31,239
And so this content mappers proposal
from the TS team is a way that
85
00:04:31,239 --> 00:04:35,769
they're hoping they can address
essentially a plug-and-play conversion
86
00:04:35,799 --> 00:04:39,809
of other syntax into something
TypeScript itself can type check.
87
00:04:40,369 --> 00:04:44,599
So there, there may be other API
integration things that they're looking
88
00:04:44,599 --> 00:04:48,569
at as well, but this feels like it's
a, a good step in that direction.
89
00:04:49,239 --> 00:04:52,549
And in the meantime, a bunch
of teams are doing things with
90
00:04:52,549 --> 00:04:57,129
integrating with TS Go in hacky
ways you're not supposed to anyway.
91
00:04:57,579 --> 00:05:01,539
Johnson Chu, who I think built the
Alien Signals library, and I think
92
00:05:01,549 --> 00:05:07,119
also works on the Vue Volar language
extension, if I've got my connections
93
00:05:07,119 --> 00:05:11,719
right, put together a package called
the TypeScript Native Bridge, which
94
00:05:11,719 --> 00:05:16,039
is supposed to help polyfill some of
the, I think, the language server-type
95
00:05:16,109 --> 00:05:17,779
integrations so that they're faster.
96
00:05:18,299 --> 00:05:22,189
And then the OXC folks have been doing
their own hacky native TypeScript
97
00:05:22,709 --> 00:05:28,829
integration to try to enable typed
lint rules within the OXC linter.
98
00:05:29,259 --> 00:05:34,319
And so the typed linting support
has just gone stable as well.
99
00:05:35,049 --> 00:05:39,469
So, lot of improvements around
TypeScript compiling and checking
100
00:05:39,479 --> 00:05:41,849
in the entire tooling ecosystem.
101
00:05:42,019 --> 00:05:42,429
Carl: Interesting.
102
00:05:42,429 --> 00:05:45,149
Yeah, type-aware linting
would be a really big win.
103
00:05:45,559 --> 00:05:48,909
I've wanted that a number of times,
and we've never really gotten there.
104
00:05:49,029 --> 00:05:53,889
Mark: TS ESLint has them, but it requires
a lot of slower integration and running
105
00:05:53,929 --> 00:05:56,359
full-blown standard TS type checking.
106
00:05:56,915 --> 00:05:57,275
Carl: Cool.
107
00:05:57,585 --> 00:05:59,935
Can you talk about this
install time security, Mark?
108
00:06:00,115 --> 00:06:05,435
Mark: Due to the entire series of supply
chain attacks that we've seen happen over
109
00:06:05,435 --> 00:06:11,105
the last year, one of the biggest issues
has been that packages are allowed to
110
00:06:11,115 --> 00:06:13,735
run scripts after install by default.
111
00:06:13,935 --> 00:06:16,675
And so you're just arbitrarily
executing remote code on your
112
00:06:16,675 --> 00:06:18,415
machine with your privileges.
113
00:06:18,995 --> 00:06:23,775
And so several other package
managers like pnpm had switched
114
00:06:23,785 --> 00:06:26,445
to disallowing that by default.
115
00:06:27,005 --> 00:06:33,455
And so npm 11 still allowed that,
but they started adding the options
116
00:06:33,475 --> 00:06:36,915
to disable running scripts by
default and preparing things.
117
00:06:37,325 --> 00:06:43,165
So npm 12 actually does flip the
switch on a lot of those options.
118
00:06:43,585 --> 00:06:48,085
So npm 12 no longer runs
post-install scripts by default.
119
00:06:48,475 --> 00:06:55,605
By default, it does not allow a Git
repo URL as a valid dependency, and
120
00:06:55,605 --> 00:06:59,645
it has a couple other options that it
turns off by default to enable security.
121
00:07:00,161 --> 00:07:04,331
I also saw that GitHub is changing
Dependabot, so it now has a cool
122
00:07:04,331 --> 00:07:08,251
down by default, so it won't
install new deps until, like, two
123
00:07:08,251 --> 00:07:10,161
or three days after they came out.
124
00:07:10,811 --> 00:07:15,601
So we are very, very belatedly, as
an ecosystem, finally learning some
125
00:07:15,601 --> 00:07:20,751
lessons we probably should have learned
many years ago, and changing some of
126
00:07:20,751 --> 00:07:24,921
the default behaviors of our tools to
try to cut down on the blast radius
127
00:07:24,951 --> 00:07:26,791
of some of these malware releases.
128
00:07:27,151 --> 00:07:27,571
Carl: Yeah.
129
00:07:27,621 --> 00:07:31,351
And we've covered some of that
in recent episodes, so I, let's
130
00:07:31,351 --> 00:07:32,871
not rehash it entirely again.
131
00:07:33,541 --> 00:07:37,241
Mm. Yeah, definitely some,
uh, long overdue changes here.
132
00:07:37,411 --> 00:07:37,631
Mark: Yep.
133
00:07:37,881 --> 00:07:42,661
Carl: As well as, I guess, in w-
security tweaks for server components
134
00:07:42,711 --> 00:07:44,371
that were just released this week.
135
00:07:44,491 --> 00:07:44,721
Mark: Yep.
136
00:07:44,751 --> 00:07:47,871
Looks like another denial of
service attack possibility.
137
00:07:48,311 -->
00:07:48,581
Carl: Okay.
138
00:07:48,581 --> 00:07:51,971
Mark: So just bad, bad… So
not remote code execution, but
139
00:07:51,981 --> 00:07:53,911
bad input freezes the server.
140
00:07:54,051 --> 00:07:54,391
Carl: Okay.
141
00:07:54,531 --> 00:07:55,201
Can't have that.
142
00:07:55,421 --> 00:07:57,531
That's a denial of service vector.
143
00:07:57,911 --> 00:08:00,601
Okay, well that's the, like,
brand-new releases we have.
144
00:08:00,621 --> 00:08:03,341
There's some other new stuff, but a
little bit, like, less, you know…
145
00:08:03,411 --> 00:08:05,801
N- we're not gonna start with it, but
we're gonna do that towards the end.
146
00:08:06,251 --> 00:08:07,181
Main content.
147
00:08:07,611 --> 00:08:12,011
We are gonna start with the React
org updates, and we're gonna frame
148
00:08:12,011 --> 00:08:15,841
this against the backdrop of, like,
open source governance generally.
149
00:08:16,501 --> 00:08:21,231
There have been some changes
announced by the, uh, you know,
150
00:08:21,231 --> 00:08:22,941
React Foundation within the Discord.
151
00:08:22,941 --> 00:08:25,791
There's been, you know, there's
been a, a couple of visible
152
00:08:25,791 --> 00:08:31,851
changes to the website and PRs to
the actual governance repository.
153
00:08:32,277 --> 00:08:35,217
Mark: I specifically had been
griping, I think in the last two
154
00:08:35,217 --> 00:08:40,757
months, that I have no idea who's
even on the React team anymore.
155
00:08:41,097 --> 00:08:44,807
And I don't know whether they literally
heard me or whether this was just,
156
00:08:44,867 --> 00:08:46,397
you know, kind of coincidental timing.
157
00:08:46,677 --> 00:08:51,587
But they did a significant update to the
existing React team page on the website.
158
00:08:51,947 --> 00:08:55,397
They updated it both with, you
know, current people involved
159
00:08:55,407 --> 00:08:58,557
in moving some folks to more
of, like, an emeritus status.
160
00:08:58,887 --> 00:09:05,417
But the team page now actually
reflects a new team structure that is
161
00:09:05,417 --> 00:09:11,677
coming out of this React foundation
itself, where there's, like, a set of
162
00:09:11,827 --> 00:09:15,717
different working groups for topics
like, you know, server components
163
00:09:15,727 --> 00:09:17,417
and compiler and, and other things.
164
00:09:17,707 --> 00:09:21,237
But then there's, like, a leadership
council that appears to be essentially,
165
00:09:21,237 --> 00:09:25,057
like, a, a representative from
each of those groups, as well
166
00:09:25,057 --> 00:09:26,387
as possibly a couple others.
167
00:09:26,887 --> 00:09:31,817
So I still don't, still don't have
a lot of details on the actual
168
00:09:32,197 --> 00:09:36,807
responsibilities, but we're seeing some
visible evidence that they're working
169
00:09:36,817 --> 00:09:39,327
on the organization process here.
170
00:09:39,677 --> 00:09:40,177
Carl: Interesting.
171
00:09:40,237 --> 00:09:43,340
Cool Curious, the reason I'm in the
Discord is 'cause, 'cause somebody reached
172
00:09:43,340 --> 00:09:45,600
out asking if I wanted to help with
community, and so now seeing a bunch of
173
00:09:45,630 --> 00:09:49,010
people listed as on the Docs and Community
Working Group and nobody reached out to
174
00:09:49,010 --> 00:09:51,010
me makes me feel like I got left out.
175
00:09:51,480 --> 00:09:52,080
But that's okay.
176
00:09:52,380 --> 00:09:54,880
I'm an independent actor, unaffiliated.
177
00:09:55,200 --> 00:10:01,440
Mark: The list of working groups is, uh,
server, DOM, fiber, docs and community,
178
00:10:01,490 --> 00:10:04,450
compiler, DevX, and React Native.
179
00:10:04,860 --> 00:10:05,120
Carl: Yep.
180
00:10:05,230 --> 00:10:09,090
I am s- slightly surprised to see
React Native generally put into its
181
00:10:09,090 --> 00:10:12,880
own single group, because they're
a- at least as large as React.
182
00:10:12,900 --> 00:10:15,940
I would say technically, you know,
problem space they operate within
183
00:10:15,940 --> 00:10:18,610
is larger than React itself.
184
00:10:18,620 --> 00:10:22,100
So I'm slightly surprised to see
it positioned as a single working
185
00:10:22,100 --> 00:10:23,999
group under the umbrella of React.
186
00:10:24,190 --> 00:10:26,220
But I guess, you know, there's
other organizations that are more
187
00:10:26,220 --> 00:10:29,659
meaningfully invested in React
Native, so, uh, maybe this is more
188
00:10:29,659 --> 00:10:30,910
of, you know, division of labor.
189
00:10:30,910 --> 00:10:33,720
This is the pipeline more
than the umbrella, per se.
190
00:10:33,870 --> 00:10:36,850
Mark: It's also worth noting that
there, there's like seven or eight
191
00:10:36,850 --> 00:10:40,009
people on the leadership council,
which I guess, you know, matches
192
00:10:40,009 --> 00:10:41,719
roughly the number of working groups.
193
00:10:42,100 --> 00:10:48,020
And then the working group members section
is at least a good 20-plus people long
194
00:10:48,449 --> 00:10:54,269
for current people, and then there's a set
of advisors and a set of emeritus people.
195
00:10:54,570 --> 00:10:58,359
So there, there's a good 30 to
35 names listed on this page.
196
00:10:58,390 --> 00:11:01,560
Like, it's not just, you
know, two to three people.
197
00:11:01,899 --> 00:11:04,220
Carl: It's quite a long list,
and it is much more specific.
198
00:11:04,269 --> 00:11:04,539
I don't know.
199
00:11:04,539 --> 00:11:07,480
We just complained about this, and
it's really nice to see a, like,
200
00:11:07,670 --> 00:11:10,339
full refresh that looks reliable.
201
00:11:10,609 --> 00:11:11,190
That's nice.
202
00:11:11,740 --> 00:11:13,670
I was reading a little bit of the charter.
203
00:11:13,820 --> 00:11:14,639
It is pretty interesting.
204
00:11:14,640 --> 00:11:18,229
It looks like they're quite earnestly
trying to make this, like, you know, open
205
00:11:18,229 -->
00:11:23,859
participation, and I've thought a lot
about governance questions and stuff like
206
00:11:23,859 --> 00:11:28,609
cooperatives and, like, how do you do…
If you have multiple people with opinions
207
00:11:28,609 --> 00:11:33,660
about what to do with a project, a shared
good, I don't know, it's really hard, it's
208
00:11:33,660 --> 00:11:37,400
really hard to do that right in a way that
allows people to feel represented and like
209
00:11:37,400 --> 00:11:39,960
they have agency in the overall system.
210
00:11:39,960 --> 00:11:42,909
So I appreciate the challenge
of what they are trying to do.
211
00:11:42,909 --> 00:11:46,929
It is difficult to set up a general
organization that lets many people
212
00:11:46,930 --> 00:11:48,849
in many walks of life feel heard.
213
00:11:49,290 --> 00:11:51,769
I like the, the way they scoped it
as, you know, "the mission and scope
214
00:11:51,769 --> 00:11:54,630
of the project is to develop and
maintain React and associated open
215
00:11:54,630 --> 00:11:58,380
source software. The leadership council
will be responsible for technical
216
00:11:58,380 --> 00:12:00,189
oversight of the open source project."
217
00:12:00,199 --> 00:12:03,999
You know, like, this is… I can
tell that from reading this, that
218
00:12:03,999 --> 00:12:09,860
the way that they are discussing
responsibilities and constraints and
219
00:12:09,900 --> 00:12:13,590
decision-making and work delegation,
like they are very meaningfully
220
00:12:13,590 --> 00:12:19,066
trying to make this open participation
And with a high bar of quality.
221
00:12:19,306 --> 00:12:19,636
Yeah.
222
00:12:19,966 --> 00:12:22,276
This is, you know, primary
source kind of stuff.
223
00:12:22,276 --> 00:12:26,116
This is-- The commit on this
charter.md document is two days
224
00:12:26,116 --> 00:12:27,556
old, so this is, like, brand new.
225
00:12:27,586 --> 00:12:31,826
No one has really been…
This is a- as yet untested.
226
00:12:31,836 --> 00:12:34,956
The processes described here are
not currently fully implemented.
227
00:12:35,316 --> 00:12:37,376
But yeah, what I see here
looks quite good to me.
228
00:12:37,676 --> 00:12:38,136
I like it.
229
00:12:38,356 --> 00:12:40,416
Mark: And to be clear, like,
the, the repo's public.
230
00:12:40,416 --> 00:12:42,406
I mean, I can look at this
information right now.
231
00:12:42,406 --> 00:12:47,256
I don't-- The- there hasn't been,
like, a formal team announcement of the
232
00:12:47,256 --> 00:12:51,255
leadership council and the charter per
se, but clearly they're trying to put all
233
00:12:51,255 --> 00:12:56,176
the pieces together to be able to say,
"This is the way we're gonna do things."
234
00:12:56,546 --> 00:12:57,106
Carl: Yes.
235
00:12:57,316 --> 00:13:01,066
Okay, I don't see-- I heard rumor of a,
uh, pending blog post, but I, I don't
236
00:13:01,066 --> 00:13:05,236
see it yet, so… But yeah, I expect that
there should be some broader announcement
237
00:13:05,246 --> 00:13:08,396
of what this is and what it means and
what their intentions are coming soon.
238
00:13:08,996 --> 00:13:11,196
But what I see here looks quite good.
239
00:13:11,206 --> 00:13:11,666
I like it.
240
00:13:11,695 --> 00:13:13,456
It seems like a good effort.
241
00:13:13,715 --> 00:13:16,425
Mark: Like I said, I, I griped a
little bit about the lack of visible
242
00:13:16,436 --> 00:13:20,625
progress in the last few months, but
clearly what we're seeing here, and
243
00:13:20,626 --> 00:13:23,645
even what I'd heard about the amount of
effort that was needed to just create
244
00:13:23,666 --> 00:13:25,136
the foundation in the first place.
245
00:13:25,136 --> 00:13:29,946
Like, there is a lot of effort going on
behind the scenes, clearly, and there's
246
00:13:29,946 --> 00:13:34,066
a lot of good faith intention behind
what they're trying to accomplish.
247
00:13:34,075 --> 00:13:35,546
Like, this is not just for show.
248
00:13:36,126 --> 00:13:36,516
Carl: Yes.
249
00:13:36,595 --> 00:13:36,995
Agreed.
250
00:13:37,635 --> 00:13:41,370
Mark: One of the longstanding complaints
about- You know, the community with
251
00:13:41,370 --> 00:13:45,420
React and React with the community has
been, they do most of their coding work
252
00:13:45,420 --> 00:13:48,950
in public, but there's also some that
happens behind the scenes in private.
253
00:13:49,430 --> 00:13:53,230
And historically, they've had the
problem that any time they push
254
00:13:53,270 --> 00:13:55,880
a draft PR, people jump on it.
255
00:13:55,880 --> 00:13:59,100
It's like, "Oh, React is working on this
new feature," and they start writing
256
00:13:59,100 --> 00:14:01,320
blog posts and tutorials and everything.
257
00:14:01,680 --> 00:14:06,900
And so that has actually made the React
team less likely to show their work in
258
00:14:06,900 --> 00:14:11,479
public, because a lot of times it is an
experiment or a prototype, and there's no
259
00:14:11,480 --> 00:14:14,120
guarantee that this will even ship at all.
260
00:14:14,680 --> 00:14:19,199
So there's been discussion on both sides
that it would be really helpful if they
261
00:14:19,199 --> 00:14:25,840
tried to follow a TC39 stages model, where
it's very clear that we are working on
262
00:14:25,850 --> 00:14:32,790
concept X. It is a stage one prototype, a
stage two, like, we think this is likely.
263
00:14:33,150 --> 00:14:35,189
Stage three, this is probably gonna ship.
264
00:14:35,199 --> 00:14:36,590
Stage four, it's ready.
265
00:14:36,680 --> 00:14:37,389
That kind of thing.
266
00:14:37,770 --> 00:14:42,709
And so Rick posted a comment on Reddit
saying that they've been trained
267
00:14:42,720 --> 00:14:47,870
to follow that model themselves
internally and had some success with it.
268
00:14:47,870 --> 00:14:52,209
But essentially, they're trying to prove
to themselves that they can actually work
269
00:14:52,419 --> 00:14:59,109
using that approach before they fully
publicly commit to doing that and making
270
00:14:59,110 --> 00:15:00,959
the scale, the stages and progress public.
271
00:15:01,199 --> 00:15:04,569
Carl: Yeah, and we've talked a couple
times in past episodes about the
272
00:15:04,580 --> 00:15:08,099
general challenges, like the tensions
there of them earnestly wanting to
273
00:15:08,099 --> 00:15:12,020
work in public and having repeatedly
tripped over the same problem every
274
00:15:12,020 --> 00:15:15,939
time they've tried to of, you work in
public and then you get just a bunch
275
00:15:15,940 --> 00:15:18,600
of yahoos talking over you as you're…
276
00:15:18,610 --> 00:15:22,339
You know, the, the people who don't,
people who haven't seen the work that went
277
00:15:22,349 --> 00:15:27,299
into the current state that is actually
now public and end up just re-litigating
278
00:15:27,309 --> 00:15:28,840
all the same issues or, you know.
279
00:15:28,840 --> 00:15:31,939
So there, there are a lot of very
real challenges there, and I earnestly
280
00:15:31,940 --> 00:15:36,160
appreciate the continued exploration of
how to make that actually functional and
281
00:15:36,160 --> 00:15:38,529
work well for as many people as possible.
282
00:15:39,008 --> 00:15:40,698
Mark: One other small but related item.
283
00:15:40,728 --> 00:15:44,688
You know, there are a bunch of React
folks at Vercel at this point, and
284
00:15:44,698 --> 00:15:51,658
Guillermo just announced that Pete Hunt
and Nick Schrock have both joined Vercel.
285
00:15:52,078 --> 00:15:57,038
Pete Hunt was one of the first advocates
for React at Facebook at the time.
286
00:15:57,338 --> 00:16:02,288
He did one of the more famous talks that
helped get React off the ground in public.
287
00:16:02,688 --> 00:16:05,368
He had spent the last few years,
I think, working at a company
288
00:16:05,368 --> 00:16:10,568
called Dagster that just got
acquired, and so this is presumably
289
00:16:10,568 --> 00:16:11,848
his chance to move on from that.
290
00:16:12,068 --> 00:16:15,208
But the announcement is that
he'll be leading the frameworks
291
00:16:15,228 --> 00:16:18,148
group in Next.js itself.
292
00:16:18,737 --> 00:16:24,118
And then Nick Schrock was instrumental
in the development of GraphQL as a spec
293
00:16:24,287 --> 00:16:30,707
at Meta, and he is gonna be working on
Agent DX or something along those lines.
294
00:16:31,057 --> 00:16:35,288
So Ver- Vercel continues to scoop
up more and more of the folks
295
00:16:35,288 --> 00:16:39,037
who were involved with React at
Meta at some point in the past.
296
00:16:39,387 --> 00:16:44,387
Carl: Yeah, I'm curious to see about
the interplay between Agent DX and
297
00:16:44,397 --> 00:16:49,847
the GraphQL, because increasingly
so, what an agent needs to do with an
298
00:16:49,857 --> 00:16:56,371
arbitrary server is get the data it
wants And that's what GraphQL's good at.
299
00:16:56,581 --> 00:16:57,121
Hey.
300
00:16:57,591 --> 00:16:59,011
Yeah, I'm skeptical of MCP.
301
00:16:59,101 --> 00:17:00,241
MCP is gonna die.
302
00:17:00,631 --> 00:17:01,601
Actually, no, it's not gonna die.
303
00:17:01,601 --> 00:17:05,611
It's gonna, it's gonna live forever
the way that, like, SOAP does.
304
00:17:05,621 --> 00:17:05,641
Yeah.
305
00:17:06,111 --> 00:17:11,061
It's gonna be an early exploration of
a, an A- API, and I think it's going
306
00:17:11,061 --> 00:17:12,791
to be widely hated in five years.
307
00:17:13,341 --> 00:17:14,041
Calling it now.
308
00:17:14,041 --> 00:17:15,651
There's my mark on the yardstick.
309
00:17:16,071 --> 00:17:20,851
Related to the org updates and open
source governance more than that
310
00:17:21,101 --> 00:17:25,131
last update, though, Polymanders
has published their charter as well.
311
00:17:25,181 --> 00:17:28,571
It's been around for, I would
say, at least eight years,
312
00:17:28,731 --> 00:17:29,891
maybe 10 years at this point.
313
00:17:30,321 --> 00:17:34,961
Oriented around Three.js and 3D
rendering on the web, I think
314
00:17:34,961 --> 00:17:36,661
is a fair characterization.
315
00:17:36,671 --> 00:17:40,751
Mark: A, a number of, number of folks
there have prior experience in game
316
00:17:40,751 --> 00:17:42,521
development one way or the other.
317
00:17:42,721 --> 00:17:48,321
Sort of a set of artists
collaborating to build related
318
00:17:48,351 --> 00:17:49,861
things together kind of a vibe.
319
00:17:50,201 --> 00:17:50,851
Carl: Yes.
320
00:17:50,871 --> 00:17:51,321
Yes.
321
00:17:51,331 --> 00:17:51,591
Right.
322
00:17:51,591 --> 00:17:54,431
We all have a shared interest,
a shared passion in this.
323
00:17:54,541 --> 00:17:59,571
You know, I open their website and it's
full of WebGL demos with, you know,
324
00:17:59,591 --> 00:18:05,441
parallax and physics and refraction
and, you know, translucent interact…
325
00:18:05,461 --> 00:18:08,591
You know, so it's, that's generally
what they're anchored around.
326
00:18:08,641 --> 00:18:13,941
It's a bunch of artists doing art on
the web in different ways, playing
327
00:18:13,941 --> 00:18:15,881
with visual technology on the web.
328
00:18:16,281 --> 00:18:18,081
And I- when I say playing,
I don't mean to diminish.
329
00:18:18,081 --> 00:18:21,131
I mean earnest play in
the sense of exploration.
330
00:18:21,291 --> 00:18:26,211
Mark: It's also worth noting that
was originally developed by one of
331
00:18:26,211 --> 00:18:31,321
the, one of the earlier folks in that
org, and I b- and I think Z- possibly
332
00:18:31,321 --> 00:18:37,341
Zeustin and Jotai and Vultio are
still owned by that org on GitHub.
333
00:18:37,421 --> 00:18:37,711
Carl: Yeah.
334
00:18:37,711 --> 00:18:42,021
Zeusstand, React Three Fiber,
React Spring, Jotai, Volto, Drei.
335
00:18:42,081 --> 00:18:45,231
Mark: Some very solid well-known
libraries in the React ecosystem.
336
00:18:45,291 --> 00:18:45,811
Carl: Yes.
337
00:18:45,941 --> 00:18:46,351
Yeah.
338
00:18:46,591 --> 00:18:48,871
Tons and tons of well-known projects.
339
00:18:48,991 --> 00:18:51,711
Yeah, so like, I hope that
didn't sound diminishing because
340
00:18:51,711 --> 00:18:52,801
I do not mean to diminish.
341
00:18:52,841 --> 00:18:54,891
These are talented, respected.
342
00:18:55,001 --> 00:18:58,861
But yeah, so they, they… As a
point of comparison, these other
343
00:18:58,891 --> 00:19:02,761
technical, highly technical, highly
skilled folks have also published a
344
00:19:02,761 --> 00:19:07,621
charter, and I think the React one is
a little bit more clearly articulated.
345
00:19:07,661 --> 00:19:08,681
I appreciate this charter.
346
00:19:08,681 --> 00:19:12,091
It is, you know, it discusses the
core principles and what it means to
347
00:19:12,101 --> 00:19:15,691
be a member and how decision-making
works and how they adopt projects.
348
00:19:16,041 --> 00:19:18,651
But, you know, it's like the
membership is one paragraph and
349
00:19:18,651 --> 00:19:21,061
says, "What are the working roles?
There's no strict definition of a
350
00:19:21,061 --> 00:19:23,021
working role." So it's more vague.
351
00:19:23,061 --> 00:19:25,461
There's less buttoned down there.
352
00:19:25,501 --> 00:19:26,041
Which makes sense.
353
00:19:26,041 --> 00:19:29,151
You know, this is an open source
collective of artists who are very
354
00:19:29,151 --> 00:19:32,541
talented, and they're very talented
in more along technical things.
355
00:19:32,541 --> 00:19:36,541
Like whereas people coming from Meta are
much more experienced in the corporate
356
00:19:36,591 --> 00:19:40,741
aspect of precision of language and
clarity of, you know, communication
357
00:19:40,761 --> 00:19:46,301
and definitions in documentation like
operating agreements and charters.
358
00:19:46,311 --> 00:19:50,511
So i-it's, I'm positioning these
in reference to each other, mostly
359
00:19:50,511 --> 00:19:52,841
because of the coincidence of
timing of them having both come
360
00:19:52,841 --> 00:19:55,591
out at the same time, and because
I think that's a really interesting
361
00:19:55,591 --> 00:19:57,001
and valuable comparison to draw.
362
00:19:57,131 --> 00:20:02,301
What does it look like when a corporation
helps found a foundation versus what
363
00:20:02,301 --> 00:20:05,931
does it look like when artists as part
of a collective do the same thing?
364
00:20:06,201 --> 00:20:10,441
These are contrasting ideologies creating
something, and these are two examples.
365
00:20:10,751 --> 00:20:12,401
I think it is fascinating to look at both.
366
00:20:12,871 --> 00:20:15,791
Mark: So let's say they wanna work
on a, uh, React Three Fiber version
367
00:20:15,821 --> 00:20:20,691
10 to be able to make use of WebGPU
and make it more AI agent friendly.
368
00:20:20,871 --> 00:20:24,911
They'd like to work on their
own design system for common
369
00:20:24,921 --> 00:20:26,621
look and feel and behavior.
370
00:20:26,941 --> 00:20:31,311
And then they also want to
work on better quality text
371
00:20:31,311 --> 00:20:33,541
rendering in WebGL, apparently.
372
00:20:33,931 --> 00:20:34,201
Carl: Okay.
373
00:20:34,231 --> 00:20:34,601
Cool.
374
00:20:34,661 --> 00:20:35,411
I appreciate that.
375
00:20:35,431 --> 00:20:39,471
Yeah, text rendering is really hard
because it's actually insane when you
376
00:20:39,471 --> 00:20:43,881
start drilling into the details of how
glyphs are rendered on your screen.
377
00:20:43,921 --> 00:20:47,571
F- 'cause like for instance, if you're on
a low DPI monitor, they will do all sorts
378
00:20:47,571 --> 00:20:51,621
of crazy sub-pixel rendering in order
to make it look, you know, 20% crisper.
379
00:20:52,111 --> 00:20:55,231
Which ironically actually Apple gets
flack for now because all of their
380
00:20:55,231 --> 00:20:58,481
displays are high DPI, and so they
don't do those anymore, and then it's
381
00:20:58,491 --> 00:21:01,531
really hard to get crisp icons on OSX.
382
00:21:01,591 --> 00:21:05,171
Mark: Yeah, anytime a text rendering
article pops up on Hacker News, I
383
00:21:05,171 --> 00:21:07,801
end up reading it, 'cause there,
there's some deep stuff there.
384
00:21:08,051 --> 00:21:08,511
Carl: Yes.
385
00:21:08,671 --> 00:21:13,571
If you see text rendering or Unicode
in a blog post title, like I highly
386
00:21:13,571 --> 00:21:16,261
recommend checking it out, because you
probably take it for granted, and it's
387
00:21:16,271 --> 00:21:18,331
probably like insanely complicated.
388
00:21:18,461 --> 00:21:21,881
Text rendering in WebGL is likely
going to be a fascinating project
389
00:21:21,911 --> 00:21:26,711
that deserves its own full initiative
from a, uh, collective of expert
390
00:21:26,861 --> 00:21:29,541
engineers with visual experience.
391
00:21:30,457 --> 00:21:30,727
Cool.
392
00:21:30,727 --> 00:21:32,107
Okay, let's move on a little bit.
393
00:21:32,207 --> 00:21:36,507
Recently, we've been covering more
and more React-alike projects.
394
00:21:36,577 --> 00:21:39,427
I'm gonna coin it, I'm calling
it, these are React-alikes.
395
00:21:40,007 --> 00:21:42,687
Yeah, we've got a new one,
Octane, from Dominic Ganaway.
396
00:21:43,427 --> 00:21:43,677
Mark: Yeah.
397
00:21:43,677 --> 00:21:46,777
Okay, so there's, there's a
whole causational chain here.
398
00:21:47,137 --> 00:21:52,837
So Dominic started off by creating
a library called Inferno back in
399
00:21:52,837 --> 00:21:59,277
2014 or 2015, and the idea was React
similar, but much, much faster.
400
00:21:59,357 --> 00:22:06,007
Whereas Preact was, say, like React, but
only for the web and as small as possible.
401
00:22:06,467 --> 00:22:11,127
So, like, there was like a Inferno-React
compat library that tried to fill in
402
00:22:11,137 --> 00:22:14,967
some of the differences in behavior,
but the whole point of Inferno was let's
403
00:22:14,967 -->
00:22:16,907
make something very small and very fast.
404
00:22:17,297 --> 00:22:21,467
Dominic joined the actual React
team and was there for a few years.
405
00:22:21,797 --> 00:22:23,057
He left Meta.
406
00:22:23,857 --> 00:22:30,337
He, I believe, worked with Rich Harris in
some of the Svelte 5 stuff for a while.
407
00:22:30,947 --> 00:22:35,537
And we actually covered Dominic just
in the last couple months because he
408
00:22:35,537 --> 00:22:41,977
recently released a- another different
framework called Ripple, which tried
409
00:22:41,977 --> 00:22:48,007
to pull together a few different ideas,
and he also released a JSX improvement
410
00:22:48,097 --> 00:22:53,217
language called TSRX, and then
iterated on its design a couple times.
411
00:22:53,847 --> 00:23:01,427
So he's back, and he has another new
framework called Octane, and the sales
412
00:23:01,427 --> 00:23:04,417
pitch for this one is very intriguing.
413
00:23:04,747 --> 00:23:09,967
It's essentially what if we took
React's syntax and pretty much almost
414
00:23:09,967 --> 00:23:14,867
all the semantics, but we have a
compiler, and thanks to the compiler,
415
00:23:14,887 --> 00:23:20,927
we can eliminate the virtual DOM, we
can get rid of the rules of hooks, and
416
00:23:20,927 --> 00:23:25,707
actually have, like, conditional hooks,
and we don't need a dependency array.
417
00:23:25,737 --> 00:23:29,917
And so there's actually a, a very strong
connecting line through all these things.
418
00:23:29,927 --> 00:23:34,157
It's like what if React,
but better in certain ways.
419
00:23:34,477 --> 00:23:36,207
Svelte was all compiled.
420
00:23:36,507 --> 00:23:39,527
TSRX is a compiler syntax layer.
421
00:23:39,937 --> 00:23:43,747
So there's a lot of different previous
threads of work that are getting
422
00:23:43,747 --> 00:23:44,887
pulled together in this project.
423
00:23:45,077 --> 00:23:49,257
Now, I took a look at the
commit history for this project.
424
00:23:49,877 --> 00:23:55,417
It looks like he only started working
on this, like, a month or a month
425
00:23:55,417 --> 00:23:57,817
or and a half ago, thereabouts.
426
00:23:58,197 --> 00:24:03,307
You can pretty s- quickly see the commit
messages going from, you know, first test,
427
00:24:03,547 --> 00:24:10,597
try this, oops, broke, fix, whatever, to,
like, very quickly building up the pieces
428
00:24:11,533 --> 00:24:16,933
And he's officially launched it in some
sort of like, well, I don't know what
429
00:24:16,933 --> 00:24:21,723
the actual version number is, but like he
feels it's ready enough for people to try.
430
00:24:22,113 --> 00:24:25,343
The implementation has
obviously been AI built.
431
00:24:25,923 --> 00:24:27,193
Here's where it gets interesting.
432
00:24:27,203 --> 00:24:32,703
So he just joined OpenAI to
work on their own web front end.
433
00:24:33,073 --> 00:24:37,451
I believe he'd been using
Claude To do the implementation.
434
00:24:37,991 --> 00:24:42,711
But in some discussion on Twitter, he
said, like, "I am actually seriously
435
00:24:42,711 --> 00:24:49,521
pushing Octane forward because
OpenAI heavily relies on React in
436
00:24:49,521 --> 00:24:53,781
their web stack, and we need to
essentially, like, find ways to make
437
00:24:53,781 --> 00:24:55,201
that faster and more optimized."
438
00:24:55,611 --> 00:25:00,551
So there's both the personal history of,
"I am very familiar with React and its
439
00:25:00,551 --> 00:25:06,081
ecosystem, and I'm trying to push it to
the next level, and now I have a day job
440
00:25:06,091 --> 00:25:11,251
that will fund me to do that, and also g-
they get to benefit from them." One other
441
00:25:11,251 --> 00:25:13,241
interesting technical point out of this.
442
00:25:13,691 --> 00:25:19,551
So it's React syntax and almost React
semantics, but it's totally different
443
00:25:19,551 --> 00:25:23,981
packages, which would normally
mean that there's no ecosystem out
444
00:25:23,981 --> 00:25:28,051
of the box because there are no
packages that import from Octane.
445
00:25:28,051 --> 00:25:30,481
There are packages that import from React.
446
00:25:31,091 --> 00:25:37,291
So if you look at the Octane repo, there
is an entire subfolder where he has
447
00:25:37,391 --> 00:25:43,921
programmatically built adapter layers
for commonly used React libraries to
448
00:25:43,921 --> 00:25:49,611
make them work with Octane, ranging
from component libraries to, in our
449
00:25:49,611 --> 00:25:51,741
case, React Redux and Redux Toolkit.
450
00:25:51,941 --> 00:25:56,611
Essentially, look at the actual
source code, create a port or thin
451
00:25:56,621 --> 00:26:03,021
adapter layer that imports from Octane
instead, and I assume they work?
452
00:26:03,331 --> 00:26:08,281
So it's brand new and no one's using
it yet, but this looks very genuinely
453
00:26:08,291 --> 00:26:10,301
fascinating on multiple levels.
454
00:26:10,711 --> 00:26:14,391
Carl: The thing I'm observing on the
homepage in the announcement, you
455
00:26:14,391 --> 00:26:20,261
know, code snippet, it looks extremely
familiar, except for there's no return
456
00:26:20,491 --> 00:26:22,121
in this function, which is strange.
457
00:26:22,241 --> 00:26:23,521
Mark: That'd be the TSRX.
458
00:26:23,561 --> 00:26:23,971
Carl: Right.
459
00:26:24,021 --> 00:26:28,671
Mark: In fact, n- notice if you look
carefully, there is a, there's an @ symbol
460
00:26:28,681 --> 00:26:30,541
right before the opening curly brace.
461
00:26:30,831 --> 00:26:34,651
That's apparently the TSRX symbol
that this just auto-returns.
462
00:26:34,841 --> 00:26:35,821
Carl: See, I don't like that.
463
00:26:35,821 --> 00:26:39,211
Th- th- those feel like personal
preference decisions that
464
00:26:39,211 --> 00:26:40,441
don't actually really matter.
465
00:26:40,471 --> 00:26:42,661
It reminds me of, like, CoffeeScript.
466
00:26:42,761 --> 00:26:44,371
That was so mixed.
467
00:26:44,641 --> 00:26:46,891
It was so perfect.
468
00:26:46,931 --> 00:26:51,881
They had the single versus the
double arrow function, which would
469
00:26:51,911 --> 00:26:54,121
change the behavior of binding this.
470
00:26:54,181 --> 00:26:59,471
You know, a hyphen greater than did normal
function binding, and equals greater than
471
00:26:59,661 --> 00:27:01,641
bound this automatically to the function.
472
00:27:01,881 --> 00:27:05,081
And people loved that so much that we
pulled it into this language, and that's
473
00:27:05,081 --> 00:27:06,511
where we got arrow functions from.
474
00:27:06,731 --> 00:27:12,241
And I don't think that this at symbol
justifies it to the same degree.
475
00:27:12,261 --> 00:27:17,071
Like, I don't think implicit return…
Like, JSX had an implicit return, too.
476
00:27:17,071 --> 00:27:18,861
You know, it was like you
add braces or you don't.
477
00:27:18,951 --> 00:27:24,951
And so adding a new symbol to
the language in order to change
478
00:27:24,951 --> 00:27:28,341
the behavior of something that we
already have a, a variable on, I
479
00:27:28,411 --> 00:27:31,001
think is gonna be a distraction.
480
00:27:31,001 --> 00:27:33,741
I think that's a, I think that's
an API failure, I would say.
481
00:27:34,261 --> 00:27:37,431
Like, the rest, plenty of these, you
know, the rest of these all seem…
482
00:27:37,681 --> 00:27:41,081
It bothers me that it's so close
to being familiar, while m- making
483
00:27:41,081 --> 00:27:43,601
a, a dramatic departure like that.
484
00:27:43,611 --> 00:27:45,251
Implicit return is a big difference.
485
00:27:45,511 --> 00:27:49,331
Mark: It's worth noting that it
does support both existing JSX
486
00:27:49,341 --> 00:27:53,741
syntax and the new modified TSRX
syntax, so it is pick and choose.
487
00:27:54,231 --> 00:27:54,891
Carl: Skeptical.
488
00:27:54,931 --> 00:27:55,561
It's interesting.
489
00:27:55,571 --> 00:27:59,921
Overall, I think this is a really good
idea and a good direction to explore.
490
00:28:00,101 --> 00:28:04,151
I'm reacting strongly to that small note
because I think this is good to explore,
491
00:28:04,151 --> 00:28:07,611
and that feels like a, that feels like a
unintentional self-injury that will make
492
00:28:07,611 --> 00:28:11,071
it more difficult for this to succeed,
I think is why I'm calling it out.
493
00:28:11,561 --> 00:28:12,521
But yeah, I think that's really cool.
494
00:28:12,531 --> 00:28:15,681
Like, you know, boom, they
got a use effect in an if.
495
00:28:15,741 --> 00:28:16,861
Can't do that in React.
496
00:28:17,431 --> 00:28:20,991
So conveniences like that seem
really cool, and I'm excited to
497
00:28:21,021 --> 00:28:24,501
see if this works, and I hope
that it doesn't introduce foot
498
00:28:24,501 --> 00:28:26,991
guns that make it less successful.
499
00:28:27,351 --> 00:28:27,581
Mark: Yep.
500
00:28:27,741 --> 00:28:30,871
That ties into the next bit conveniently
because
we organized it that way.
501
00:28:31,251 --> 00:28:35,771
I think partly in, in response to
the release of Octane and some other
502
00:28:35,771 --> 00:28:39,841
related discussions, Ryan Carniato had
a couple tweets that relate to this.
503
00:28:40,061 --> 00:28:42,891
So, like, you know, one of Solid's
selling points has been that it
504
00:28:42,901 --> 00:28:45,201
mostly looks like it re- like React.
505
00:28:45,201 --> 00:28:46,751
It uses JSX syntax.
506
00:28:47,051 --> 00:28:49,011
It is JavaScript inside.
507
00:28:49,161 --> 00:28:52,251
Okay, the state and the effects are
different, and the getters are different.
508
00:28:52,251 --> 00:28:55,951
But, like, it looks like React
much more than Angular would be.
509
00:28:56,551 --> 00:29:01,501
So Ryan had a couple tweets where he was
commenting that, you know, at this point,
510
00:29:01,511 --> 00:29:07,851
he feels like the… React is commonly
used largely because of complacency.
511
00:29:08,111 --> 00:29:12,671
It's the modern no one got fired
for choosing IBM kind of a thing.
512
00:29:12,981 --> 00:29:18,091
And then he also had a, a tweet
commenting on, like, do people just
513
00:29:18,131 --> 00:29:23,701
not feel that there's going to be
any more innovation in front end?
514
00:29:24,591 --> 00:29:27,741
So I mean, like, he's been talking about
a number of these points for a while,
515
00:29:27,751 --> 00:29:32,731
so, like, there's not necessarily,
like, new changing details there.
516
00:29:33,181 --> 00:29:38,061
That, we've talked about this before,
you know, AI is sort of encoding React as
517
00:29:38,061 --> 00:29:44,371
the default, and we're also still stuck
in writing, like, 2019 era React and
518
00:29:44,371 --> 00:29:47,001
not even using a lot of the newer APIs.
519
00:29:47,541 --> 00:29:47,831
Carl: Yeah.
520
00:29:47,881 --> 00:29:49,281
I do appreciate this chat shout-out.
521
00:29:49,281 --> 00:29:52,691
"Directly contradicts the meme of
a new framework every week." Like-
522
00:29:52,901 --> 00:29:53,171
Mark: Yep
523
00:29:53,311 --> 00:29:53,781
…
Carl: all right.
524
00:29:53,841 --> 00:29:55,121
Yeah, can't have it both ways.
525
00:29:55,121 --> 00:29:59,841
We're literally, the JS ecosystem is
criticized for all things at every moment.
526
00:30:01,903 --> 00:30:02,903
Mark: I mean, why not both?
527
00:30:02,923 --> 00:30:05,203
We can have a new framework
and nobody uses it.
528
00:30:05,543 --> 00:30:05,853
Carl: Yeah.
529
00:30:06,413 --> 00:30:06,953
True.
530
00:30:07,293 --> 00:30:08,543
Entirely real.
531
00:30:08,913 --> 00:30:12,143
Mark: I mean, the number of times
I've seen new "React state management
532
00:30:12,153 --> 00:30:14,603
library" posted on r/reactjs, man.
533
00:30:14,783 --> 00:30:16,813
Carl: Yeah, you know, actually, I'm
gonna tie that back to what you just
534
00:30:16,813 --> 00:30:19,723
said of not moving past 2019 era React.
535
00:30:20,043 --> 00:30:23,893
People are still doing 2019 era
open source announcements of,
536
00:30:23,933 --> 00:30:25,873
"Hey, I made a new library."
537
00:30:26,263 --> 00:30:28,693
And like, yeah, that worked 10 years ago.
538
00:30:28,893 --> 00:30:29,813
I don't think it works anymore.
539
00:30:30,487 --> 00:30:30,827
But yeah.
540
00:30:31,197 --> 00:30:32,747
Mark: One last little point on that note.
541
00:30:32,767 --> 00:30:38,507
We've talked before about both Solid
2.0 being in beta and having some new,
542
00:30:38,507 --> 00:30:44,747
uh, async features with the asynchroness
baked directly into the signals graph.
543
00:30:45,097 --> 00:30:48,997
And someone put up a good, you know,
w- very well-written tutorial-like
544
00:30:49,007 --> 00:30:53,787
post illustrating both just
the overall usage and talking
545
00:30:53,797 --> 00:30:55,287
about some of the nuances there.
546
00:30:55,677 --> 00:31:01,227
And then someone else explicitly
ported the example app into Remix
547
00:31:01,237 --> 00:31:06,807
Version 3 as a intro to how you
would do things with Remix 3 as well.
548
00:31:07,257 --> 00:31:07,537
Carl: Cool.
549
00:31:08,007 --> 00:31:08,417
Nice.
550
00:31:08,417 --> 00:31:08,897
Love that.
551
00:31:09,157 --> 00:31:13,527
Anytime somebody does a direct port
of one app to a different framework,
552
00:31:13,577 --> 00:31:16,057
especially in demos like this, I love it.
553
00:31:16,097 --> 00:31:18,777
I listen to a lot of economics, and
there's a big thing, uh, in that
554
00:31:18,777 --> 00:31:20,997
field about natural experiments.
555
00:31:21,417 --> 00:31:25,237
Like, you know, y- some decision is
made, and boom, now you have a randomized
556
00:31:25,387 --> 00:31:29,357
population that you can determine
the outcome of that decision on.
557
00:31:29,677 --> 00:31:32,557
This feels like this, uh,
open source equivalent.
558
00:31:32,567 --> 00:31:35,817
Somebody made a demo app, somebody
else ported it to an different
559
00:31:35,827 --> 00:31:39,007
framework, and now we have a very pure
comparison of those two frameworks.
560
00:31:40,277 --> 00:31:43,267
I have always thought it would be
incredibly valuable if we had a,
561
00:31:43,277 --> 00:31:47,187
like, representative, like, "No,
this is the best possible to-do
562
00:31:47,187 --> 00:31:50,077
app in nine different frameworks."
563
00:31:50,207 --> 00:31:54,077
Mark: That was the whole to-do
MVC website back in the day.
564
00:31:54,427 --> 00:31:55,517
Carl: But then, like, they all suck.
565
00:31:55,547 --> 00:31:58,687
I feel like none of them achieved…
Individually, none of them were
566
00:31:58,697 --> 00:32:01,447
actually good enough to wear that
mantle, and so it was like, wait,
567
00:32:01,457 --> 00:32:03,217
actually, these are not, this is not…
568
00:32:03,267 --> 00:32:05,357
Or, I don't know, maybe that's
just a reality of the fact that you
569
00:32:05,357 --> 00:32:08,767
cannot actually have a single the
best anything because there are
nine
570
00:32:08,767 --> 00:32:12,397
different approaches to doing tables
in React, and so you cannot make a
571
00:32:12,397 --> 00:32:14,887
single definitive React to-do list.
572
00:32:15,307 --> 00:32:19,927
But, oh, man, I… So anyway, that's
why I love that somebody has ported one
573
00:32:19,927 --> 00:32:21,877
demo app from one framework to another.
574
00:32:21,927 --> 00:32:22,697
This is really good.
575
00:32:22,977 --> 00:32:23,307
Mark: All right.
576
00:32:23,317 --> 00:32:26,837
So there, there's a long-running
JS frameworks benchmark that's been
577
00:32:26,837 --> 00:32:31,947
out there that measures things like
loading performance or swapping
578
00:32:31,997 --> 00:32:33,967
items in a long list, et cetera.
579
00:32:34,207 --> 00:32:37,857
That has been, like, the holy grail
that every new framework tries to
580
00:32:37,877 --> 00:32:39,637
add and measure itself against.
581
00:32:40,047 --> 00:32:45,297
NullVoxPopuli, who is part of the
Ember community, has put together a
582
00:32:45,307 --> 00:32:50,867
sort of similar benchmark, but trying
to solely measure the reactivity
583
00:32:50,897 --> 00:32:53,237
and re-rendering portion of it.
584
00:32:53,597 --> 00:32:54,527
I only glanced at it.
585
00:32:54,527 --> 00:32:59,157
I don't fully understand the nuances
and the differences of how, like,
586
00:32:59,187 --> 00:33:04,477
what is being measured differently
than the, the JS framework benchmark.
587
00:33:04,807 --> 00:33:07,557
But I've, I've watched this person long
enough to know they have a pretty good
588
00:33:07,557 --> 00:33:10,837
idea what they're talking about, and so
they're trying to measure more about,
589
00:33:10,837 --> 00:33:16,577
like, the, the state update sequence, I
think, than necessarily just, like, DOM
590
00:33:16,587 --> 00:33:19,117
loading time or something to that effect.
591
00:33:19,377 --> 00:33:19,597
Carl: Yeah.
592
00:33:19,597 --> 00:33:23,513
So I mean, this table has-
Incrementing render effect.
593
00:33:23,523 --> 00:33:28,723
So I guess that means the length of
time it took to render and then produce
594
00:33:28,723 --> 00:33:32,153
an effect that would increment and
then thereby trigger a re-render,
595
00:33:32,173 --> 00:33:33,773
an infinite loop, it sounds like.
596
00:33:34,183 --> 00:33:38,573
And it's saying React took 8.7 times
longer than the baseline to just do that.
597
00:33:38,573 --> 00:33:38,833
Which is,
598
00:33:39,043 --> 00:33:40,373
Mark: which is Angular apparently.
599
00:33:40,913 --> 00:33:41,613
Carl: Yes.
600
00:33:41,743 --> 00:33:45,223
Or the baseline there was solid,
but yes, most of these Angular
601
00:33:45,223 --> 00:33:46,443
is the, is the benchmark.
602
00:33:47,091 --> 00:33:47,861
Okay, this is interesting.
603
00:33:48,011 --> 00:33:52,991
So this, these are a lot of… This does
look like a pretty solid stress test.
604
00:33:53,311 --> 00:33:57,901
You know, like 1,000 item list, one
update on 25% of items at random.
605
00:33:58,281 --> 00:33:59,551
Like, that's pretty good.
606
00:33:59,771 --> 00:34:03,501
You know, that reminds me of like a
stock ticker, you know, a table of stock
607
00:34:03,501 --> 00:34:05,721
results with real-time prices updating.
608
00:34:06,061 --> 00:34:06,581
Mark: Interesting.
609
00:34:06,581 --> 00:34:09,881
I actually just dealt with that
scenario in the React Redux
610
00:34:09,881 --> 00:34:11,311
prototype branch that I'm working on.
611
00:34:11,331 --> 00:34:13,981
I'm going to have to go steal some
ideas from this, for this one too.
612
00:34:14,401 --> 00:34:15,151
Carl: Ah, there you go.
613
00:34:15,191 --> 00:34:15,561
Yeah.
614
00:34:15,571 --> 00:34:18,601
I had to render sparklines
once, and do you know how many
615
00:34:18,611 --> 00:34:19,981
DOM nodes are in a sparkline?
616
00:34:20,661 --> 00:34:23,721
Do you know what happens if you render
one sparkline for 30 table results?
617
00:34:23,731 --> 00:34:26,701
So I, yeah, the optimization that has to
go into that is kinda crazy sometimes.
618
00:34:26,841 --> 00:34:27,331
But yeah, cool.
619
00:34:27,341 --> 00:34:30,181
This looks like a very good benchmark.
620
00:34:30,381 --> 00:34:35,121
And yeah, it is in fact saying that
Angular has the best performance
621
00:34:35,701 --> 00:34:37,821
as rendered by time spent-
622
00:34:38,241 --> 00:34:42,101
Mark: Doing the data update work, I think
623
00:34:42,531 --> 00:34:46,791
Carl: the values here are not
super-duper helpful, I would say.
624
00:34:47,111 --> 00:34:50,331
The options here are values raw,
so I don't k- I, like, I don't
625
00:34:50,331 --> 00:34:51,941
know if that's raw on milliseconds.
626
00:34:51,941 --> 00:34:56,011
I don't know what unit's it in, or
a score, which is also not helpful,
627
00:34:56,431 --> 00:34:58,641
or multiplicative relative time.
628
00:34:58,641 --> 00:34:59,881
So anyway, this is really interesting.
629
00:34:59,881 --> 00:35:02,061
I think this has potential
to be very helpful.
630
00:35:02,251 --> 00:35:04,051
Benchmarks are great,
and we have a new one.
631
00:35:04,541 --> 00:35:09,691
Mark: And then one other benchmark, Aiden
Bai, who has been on a tear releasing
632
00:35:09,701 --> 00:35:14,061
various kinds of React-related analysis
tools, right up my alley, put out a
633
00:35:14,121 --> 00:35:21,651
React bench to try to measure how well
different AI models write React code.
634
00:35:22,081 --> 00:35:26,651
He put together some kind of a scoring
metric for common mistakes and patterns,
635
00:35:27,121 --> 00:35:34,411
and is measuring how well they actually
write good code versus bad code.
636
00:35:34,551 --> 00:35:38,231
I'm assuming that a fetch in
a use effect is scored as bad.
637
00:35:38,711 --> 00:35:45,111
And for the record, apparently GPT 5.6 is
leading at a 53% score on the benchmark.
638
00:35:45,381 --> 00:35:45,771
Carl: Cool.
639
00:35:45,881 --> 00:35:46,411
Interesting.
640
00:35:46,531 --> 00:35:50,571
I love this because this is such
a, like "code crafts person"
641
00:35:50,581 --> 00:35:53,321
versus "fuck it, ship it" attitude.
642
00:35:53,821 --> 00:35:56,331
This is something I felt like I had
to get over in my professional career,
643
00:35:56,341 --> 00:35:59,121
'cause I jumped around employers so
many times, and I was so close to the
644
00:35:59,121 --> 00:36:00,761
React ecosystem, it's like, "Oh, cool.
645
00:36:00,761 --> 00:36:01,891
I know all the best practices.
646
00:36:01,891 --> 00:36:04,811
I know how to do it right." And then you
join a company, it's like, "Oh, you're
647
00:36:04,811 --> 00:36:06,311
just putting a component in state?
648
00:36:06,431 --> 00:36:10,761
Got it." Yeah, I bet the, I bet all
of these models are trained on some
649
00:36:10,761 --> 00:36:14,751
pretty garbage code, because most of the
code in the world is complete garbage.
650
00:36:15,131 --> 00:36:18,271
And I think that's very clearly
demonstrated by the highest
651
00:36:18,281 --> 00:36:20,531
score on this being 53%.
652
00:36:20,981 --> 00:36:23,161
Mark: I'm gonna have to go dig
into that benchmark to see what
653
00:36:23,161 --> 00:36:24,521
they're actually scoring things on.
654
00:36:24,691 --> 00:36:28,141
Carl: The time I saw a component being
put into state was during a take-home
655
00:36:28,141 --> 00:36:31,241
test… No, during a whiteboard
interview for a new company, and I
656
00:36:31,241 --> 00:36:34,051
terminated the interview because I was
like, "If you're doing this, then I do
657
00:36:34,051 --> 00:36:35,581
not wanna work here. I am so sorry."
658
00:36:37,513 --> 00:36:40,033
Mark: All right, so that,
that ties into our next item.
659
00:36:40,093 --> 00:36:46,363
Alex Russell wrote a, as usual,
incendiary blog post blasting the
660
00:36:46,363 --> 00:36:48,763
React ecosystem and its practices.
661
00:36:49,313 --> 00:36:54,823
And as always, it's a very
well-written post, and I actually
662
00:36:54,833 --> 00:36:59,673
agree with and understand a lot
of the points he's trying to make.
663
00:36:59,993 --> 00:37:05,033
I disagree with the conclusions and
the way he's messaging a lot of them.
664
00:37:05,443 --> 00:37:05,683
Carl: Yeah.
665
00:37:05,783 --> 00:37:10,943
Mark: So his first argument is React
has built-in state management, but
666
00:37:10,943 --> 00:37:15,623
the existence of dozens and dozens
of state management libraries must
667
00:37:15,633 --> 00:37:20,873
mean that either React isn't a state
management system or React is an
668
00:37:20,923 --> 00:37:23,993
insufficient state management system.
669
00:37:24,493 --> 00:37:28,513
And I think we would all agree it's,
it is a state management system,
670
00:37:28,513 --> 00:37:31,493
but it's very insufficient, the
fact that it's all tree-shaped.
671
00:37:32,253 --> 00:37:35,143
So that's why we have all these
external state management libs.
672
00:37:35,563 --> 00:37:40,853
He then goes on to, to blast the fact
that there's the plethora of external
673
00:37:40,853 --> 00:37:45,243
state management libraries and that
they're all big and complicated and
674
00:37:45,243 --> 00:37:47,143
basically just pub/sub event emitters.
675
00:37:47,653 --> 00:37:52,243
But where-- He then takes it in a
very surprising direction, which is
676
00:37:52,273 --> 00:37:57,363
essentially that all these different state
management libraries, quote, and I will
677
00:37:57,393 --> 00:38:02,363
paraphrase, "Don't actually manage state."
678
00:38:02,923 --> 00:38:06,413
They store a value at a point in time.
679
00:38:07,063 --> 00:38:13,243
They are pub/sub and trigger updates,
but they don't have any sense of what
680
00:38:13,263 --> 00:38:22,453
was the state over time or how do you
intelligently merge in changes over time.
681
00:38:23,483 --> 00:38:31,473
And so he then points to sync engines
and CRDTs as essentially this is what I
682
00:38:31,493 --> 00:38:35,353
think is the right way to manage state.
683
00:38:36,113 --> 00:38:39,773
Of course, half his argument is all
these libraries are large and then
684
00:38:39,783 --> 00:38:44,313
people do bad things for SSR and
hydration and send down massive JSON
685
00:38:44,313 --> 00:38:45,383
blobs, and that leads to bad perf.
686
00:38:45,833 --> 00:38:52,383
But he's also primarily arguing that the
entire way the React ecosystem uses the
687
00:38:52,383 --> 00:38:57,873
word state management is wrong, and that
almost everybody would be better off
688
00:38:57,903 --> 00:39:06,663
using some kind of a sync engine or, or
CRDT to both auto-merge changes as well
689
00:39:06,663 --> 00:39:10,943
as manage the time aspect of changes.
690
00:39:12,417 --> 00:39:14,097
I hear what he's saying.
691
00:39:14,117 --> 00:39:16,947
I disagree on a number of levels.
692
00:39:16,967 --> 00:39:20,777
When I wrote my Redux versus Context post
a few years ago, I actually explicitly
693
00:39:20,777 --> 00:39:24,687
said that to me, a state management
tool is, well, essentially pub/sub.
694
00:39:24,947 --> 00:39:28,677
You store a value, you have a way
to update it, you have a way to read
695
00:39:28,677 --> 00:39:31,597
it, and a way to trigger updates.
696
00:39:32,057 --> 00:39:34,047
All these libraries fit that category.
697
00:39:34,137 --> 00:39:39,417
He's the one trying to put the extra
dimension of time on top of that.
698
00:39:39,947 --> 00:39:43,657
I agree sync engines and CRDTs are
useful, and that probably a lot
699
00:39:43,657 --> 00:39:45,207
more people ought to look at them.
700
00:39:45,867 --> 00:39:52,287
But I feel like saying these are a blanket
solution that almost everybody should go
701
00:39:52,287 --> 00:39:56,117
with if, you know, assuming you're doing
more than just server-side rendering,
702
00:39:56,547 --> 00:39:59,637
feels like it's a pretty big step.
703
00:39:59,987 --> 00:40:03,857
And so I had a bit of a debate with him
on Blue Sky about this, kind of trying to
704
00:40:03,857 --> 00:40:08,717
probe and get him to expand on a few of
the thoughts, and he eventually did say
705
00:40:08,717 --> 00:40:11,967
that like, "Yeah, I'm basically saying
that everyone needs to have a major
706
00:40:11,967 --> 00:40:18,497
mental shift in how they approach thinking
about state whatsoever In applications."
707
00:40:18,907 --> 00:40:22,077
Which I get what you're saying,
and number one, that's not going
708
00:40:22,077 --> 00:40:25,137
to happen, and number two, I don't
agree that it needs to happen.
709
00:40:25,617 --> 00:40:26,007
Carl: Yeah.
710
00:40:26,017 --> 00:40:31,537
The, specifically that thought, that
expressed thought of, "the problem here is
711
00:40:31,537 --> 00:40:35,927
that everyone else is thinking about this
wrong and everyone needs to learn this
712
00:40:35,927 --> 00:40:38,987
new thing in order to do it correctly."
713
00:40:39,387 --> 00:40:43,917
Categorically, I'm gonna say that i- if
that's your defense, it's ineffective.
714
00:40:43,917 --> 00:40:49,957
Like, no one has, no idea has
ever been adopted to that extent.
715
00:40:49,997 --> 00:40:52,897
Like, the best you get
is something like React.
716
00:40:53,427 --> 00:40:59,177
React is one of the most widely successful
used technologies like that, and we're
717
00:40:59,177 --> 00:41:01,157
discussing how badly abused it is.
718
00:41:01,167 --> 00:41:04,387
So like, no, you are never going to
get everyone to do any particular
719
00:41:04,387 --> 00:41:05,947
thing in a particular manner.
720
00:41:06,307 --> 00:41:07,327
I also empathize.
721
00:41:07,357 --> 00:41:12,417
Like, most state, quote-unquote,
in React apps is actually cache.
722
00:41:12,737 --> 00:41:16,797
You know, and we've discussed how,
like, most state should just be
723
00:41:16,797 --> 00:41:19,457
like React Query, because actually
you're just caching network state.
724
00:41:19,467 --> 00:41:20,857
This is not your local state.
725
00:41:20,877 --> 00:41:25,247
Mark: Use Nuxt, put more of it in the
URL so it, it survives a page refresh.
726
00:41:25,357 --> 00:41:28,737
You know, use, use uncontrolled
form inputs, that sort of thing.
727
00:41:29,147 --> 00:41:29,567
Carl: Right.
728
00:41:29,757 --> 00:41:30,027
Right.
729
00:41:30,027 --> 00:41:35,537
And so sure, it is probably technically,
from a technical perspective, it is
730
00:41:35,537 --> 00:41:38,347
correct that we are misusing state.
731
00:41:38,577 --> 00:41:42,337
State is a precisely def-
defined technical term, and
732
00:41:42,747 --> 00:41:43,947
we are probably misusing it.
733
00:41:43,957 --> 00:41:45,047
We are certainly misusing it.
734
00:41:45,357 --> 00:41:47,097
But like, I don't know, what
are you gonna do about it?
735
00:41:48,837 --> 00:41:51,247
Mark: I tried to hint at this in
the Blue Sky thread, and you didn't
736
00:41:51,257 --> 00:41:54,577
really bite on my train of thought
and went in a
different direction.
737
00:41:54,587 --> 00:41:59,167
But like, I'm a big fan of going
back to how did we get here, what
738
00:41:59,167 --> 00:42:01,037
problems were people trying to solve?
739
00:42:01,157 --> 00:42:04,827
Problem A leads to problem B leads
to problem C. Each stage builds
740
00:42:04,827 --> 00:42:08,167
a new tool to try to address
the previous problems we had.
741
00:42:08,867 --> 00:42:13,237
We went from, you know, you can't do
JavaScript in the browser to you can
742
00:42:13,237 --> 00:42:18,507
do a bunch of JavaScript in the browser
to, okay, y- we've got jQuery to make
743
00:42:18,507 --> 00:42:23,127
it easier to work across browsers, but
you're just toggling a class in the DOM.
744
00:42:23,527 --> 00:42:26,717
You're hoping that the DOM is
what you think it is at that point
745
00:42:26,717 --> 00:42:28,397
in time, otherwise it breaks.
746
00:42:28,807 --> 00:42:31,847
It's hard to scale all
these jQuery click handlers.
747
00:42:31,847 --> 00:42:35,307
What if we tried using actual
variables to keep track of this data?
748
00:42:36,067 --> 00:42:39,497
How do we start to write larger
scale structures and architectures?
749
00:42:39,917 --> 00:42:41,857
Keeping track of all this logic's hard.
750
00:42:41,867 --> 00:42:44,367
What if we just declared what
we want it to look like and let
751
00:42:44,367 --> 00:42:45,687
the framework take care of it?
752
00:42:46,237 --> 00:42:48,677
Okay, we're having trouble
keeping that data in sync
753
00:42:48,677 --> 00:42:50,107
across large parts of our apps.
754
00:42:50,457 --> 00:42:57,725
So I'm not saying that the current
React or front-end ecosystems are Great.
755
00:42:58,445 --> 00:43:03,415
I'm not saying that they are, like,
you know, absolutely the best possible
756
00:43:03,425 --> 00:43:07,615
theoretical way we could have landed
on doing things, but I do think it's
757
00:43:07,615 --> 00:43:13,365
important to say, "This is how we
got here, and this is the real world
758
00:43:13,465 --> 00:43:19,855
current state of things. What can we
practically do to improve things?"
759
00:43:20,215 --> 00:43:23,665
And so I would be very happy to have
conversations with Alex about, like,
760
00:43:23,665 --> 00:43:27,295
"Okay, here's how the React ecosystem
got here. I'm sure you know this already,
761
00:43:27,325 --> 00:43:31,585
but, like, this is where we are. Here
are some influ- here's are some ways
762
00:43:31,585 --> 00:43:35,965
we could try to nudge things and push
people towards mentally modeling."
763
00:43:36,615 --> 00:43:40,085
But just starting off by saying, "React
claims to have state management and
764
00:43:40,085 --> 00:43:43,085
it doesn't fit my definition, and
therefore it's wrong, and everyone
765
00:43:43,085 --> 00:43:46,305
else has weighed these things on top
that aren't my definition, therefore
766
00:43:46,305 --> 00:43:50,655
they're bad, and also bad at perf." I
get that he- a little bit of this is
767
00:43:50,655 --> 00:43:54,005
him venting, and I think part of it
was the, "I've had these discussions,
768
00:43:54,005 --> 00:43:57,075
let me write down my thoughts so I can
refer to them." okay, cool, agreed.
769
00:43:57,705 --> 00:44:02,105
But it feels a little bit like shouting
into the void, and it's not going
770
00:44:02,105 --> 00:44:04,605
to improve the situation at all.
771
00:44:05,035 --> 00:44:05,335
Carl: Right.
772
00:44:05,685 --> 00:44:06,095
Yeah.
773
00:44:06,175 --> 00:44:09,845
Like, there are two little trigger
phrases here that make me go, "Er."
774
00:44:10,345 --> 00:44:11,595
And one is the first sentence.
775
00:44:11,625 --> 00:44:14,485
"It is by no means the gravest
linguistic crime of the React
776
00:44:14,495 --> 00:44:15,685
epoch, blah, blah, blah."
777
00:44:15,685 --> 00:44:19,535
But, like, okay, so, like,
literally this starts off announcing
778
00:44:19,545 --> 00:44:20,875
that a gripe on semantics.
779
00:44:20,885 --> 00:44:25,155
Th- this is framed as a linguistic
crime, so it's just definition
780
00:44:25,155 --> 00:44:26,245
and what are we talking about.
781
00:44:26,715 --> 00:44:31,205
And then at some point it's like
his stated resolution here is, "Devs
782
00:44:31,285 --> 00:44:33,565
should…" And like, boom, done.
783
00:44:33,565 --> 00:44:34,335
You lost me.
784
00:44:34,665 --> 00:44:36,435
Devs is not precisely defined.
785
00:44:36,445 --> 00:44:37,385
Who are you talking about?
786
00:44:37,555 --> 00:44:38,625
Who needs to make a change?
787
00:44:38,645 --> 00:44:39,735
And you just say should.
788
00:44:39,775 --> 00:44:42,245
Like, devs should do something.
789
00:44:42,255 --> 00:44:42,895
Like, I don't know.
790
00:44:42,905 --> 00:44:46,665
Any- anytime somebody uses a general
statement about a large population
791
00:44:46,665 --> 00:44:50,395
to say, "Everyone in this group
should do X," like, you're wrong.
792
00:44:50,425 --> 00:44:53,075
It does not matter who you're
talking about or what your idea is.
793
00:44:53,365 --> 00:44:54,445
That is never correct.
794
00:44:54,995 --> 00:44:56,125
So right.
795
00:44:56,125 --> 00:45:00,975
I, like, I broadly agree with
the perspective here as I-
796
00:45:01,075 --> 00:45:02,885
correctly identifying a problem.
797
00:45:02,985 --> 00:45:05,615
Mark: As my mom used to say to us
many times growing up, "You stated
798
00:45:05,615 --> 00:45:07,115
the problem, now state the solution."
799
00:45:07,625 --> 00:45:08,055
Carl: Right.
800
00:45:08,235 --> 00:45:08,695
It's a problem.
801
00:45:08,715 --> 00:45:09,545
The solution is hard.
802
00:45:09,555 --> 00:45:13,475
Like, there are lots of very smart people
working very earnestly on this problem.
803
00:45:13,735 --> 00:45:19,595
You know, we as an industry are
exploring the cutting edge of UI and
804
00:45:19,595 --> 00:45:22,475
what does it mean to interact, you know,
human computer interaction used to be
805
00:45:22,515 --> 00:45:24,825
considered a field of academic research.
806
00:45:24,835 --> 00:45:30,465
And, like, all of us are HCI experts
with no credentials and no…
807
00:45:30,495 --> 00:45:33,345
Like, you know, there's no scientific
rigor behind the experiments we do.
808
00:45:33,365 --> 00:45:37,671
Our company, our companies just say,
like, "Oh, I think this should be-" A
809
00:45:37,671 --> 00:45:41,211
dropdown instead of a type ahead select.
810
00:45:41,741 --> 00:45:43,671
And like, you know, okay, why?
811
00:45:43,931 --> 00:45:45,501
Oh, well, you know, that's
what the design, that's what
812
00:45:45,501 --> 00:45:46,291
the design spec calls for.
813
00:45:46,381 --> 00:45:47,511
Okay, well, why?
814
00:45:48,001 --> 00:45:49,401
Well, that's what the designer wrote down.
815
00:45:49,401 --> 00:45:52,021
Well, okay, does that, how
would people interact with that?
816
00:45:52,021 --> 00:45:55,761
This is a human computer interaction
question, and there is a body of research.
817
00:45:56,181 --> 00:46:01,181
We are earnestly exploring all of this
without the support of traditional, like,
818
00:46:01,561 --> 00:46:06,831
in years past, in decades past, people
doing this type of exploration of a, a
819
00:46:06,831 --> 00:46:11,241
problem space might have the support of
things like academic journals with peer
820
00:46:11,241 --> 00:46:16,671
review, and then ultimately, if it's
published in this journal, then you can
821
00:46:16,671 --> 00:46:20,701
trust that it went through this review
process and, you know, that by being
822
00:46:20,701 --> 00:46:26,091
present in its current form, it represents
a consensus from this perspective.
823
00:46:26,131 --> 00:46:27,101
And like, we don't have that.
824
00:46:27,111 --> 00:46:28,231
We have blog posts.
825
00:46:28,661 --> 00:46:31,211
Like, you know, we have
vibes of popularity.
826
00:46:31,211 --> 00:46:35,561
So like, we're exploring a really
challenging problem space without
827
00:46:35,581 --> 00:46:39,441
very much ability to capture the
results of those explorations, and
828
00:46:39,441 --> 00:46:40,791
that's a very hard space to be in.
829
00:46:41,081 --> 00:46:45,071
But that to say, I think there's a lot
of really interesting stuff happening
830
00:46:45,071 --> 00:46:47,381
with sync engines, Electric SQL.
831
00:46:47,591 --> 00:46:50,721
I've, I remember hearing about
a long time ago, the… Oh, God,
832
00:46:50,721 --> 00:46:51,611
I can't remember some of them.
833
00:46:51,611 --> 00:46:55,541
There were a lot of really good
sync engineed and local first-
834
00:46:55,551 --> 00:47:00,041
Mark: Electric, Zero, Replicache, maybe
that, maybe those are the same company.
835
00:47:00,101 --> 00:47:02,081
Howard Sync is out there, I think.
836
00:47:02,241 --> 00:47:02,581
Carl: Yeah.
837
00:47:02,631 --> 00:47:03,881
Thank you for filling in the gap.
838
00:47:03,881 --> 00:47:06,511
I have lots of the ideology and
less of the, uh, proper
nouns.
839
00:47:07,091 --> 00:47:08,541
But so yeah, yes, correct.
840
00:47:08,581 --> 00:47:09,871
This is a problem.
841
00:47:09,941 --> 00:47:12,461
People do misuse date, quote, unquote.
842
00:47:12,661 --> 00:47:18,671
But yeah, the way you change that is
by effectively broadcasting a message
843
00:47:18,701 --> 00:47:24,271
that allows people to observe that their
previous practices were incorrect and
844
00:47:24,281 --> 00:47:26,871
guides them into more correct practices.
845
00:47:27,441 --> 00:47:30,261
Mark: Update the docs, add a
linter, build it in by default.
846
00:47:30,781 --> 00:47:31,151
Carl: Right.
847
00:47:31,251 --> 00:47:33,831
None of those include an angry blog post.
848
00:47:34,101 --> 00:47:38,741
I relate to that as someone who wishes to
write angry blog posts, but I don't think
849
00:47:38,741 --> 00:47:40,401
it's an effective solution to the problem
850
00:47:41,143 --> 00:47:45,263
Mark: Aurora Scharf, who has been doing
a lot of fantastic conference talks
851
00:47:45,263 --> 00:47:49,733
and blogs on using Next.js and using
Suspense in the last couple years,
852
00:47:50,113 --> 00:47:55,343
joined Vercel and i- in a dev role,
role, and has been, I guess, part
853
00:47:55,373 --> 00:47:56,943
of or working with the React team.
854
00:47:56,943 --> 00:47:59,013
I think she's actually
listed on the team page.
855
00:47:59,523 --> 00:48:03,373
And so she actually just did a
significant update to the Suspense
856
00:48:03,433 --> 00:48:08,863
docs page to add a lot of details on
what are all the cases that actually
857
00:48:08,873 --> 00:48:13,433
trigger a Suspense boundary, as well
as some of the, the other use cases.
858
00:48:13,763 --> 00:48:18,753
So again, great to see a lot of the,
the usage and technical details being
859
00:48:18,763 --> 00:48:20,603
fleshed out in the official docs.
860
00:48:20,923 --> 00:48:22,353
Always something I'm asking for.
861
00:48:22,413 --> 00:48:22,703
Yay.
862
00:48:22,803 --> 00:48:27,303
Uh, and then she also wrote on her
own blog a, a post on some various
863
00:48:27,313 --> 00:48:30,713
Suspense-related usage patterns
that she's been playing around with.
864
00:48:31,053 --> 00:48:31,363
Cool.
865
00:48:31,553 --> 00:48:36,983
On the flip side, the TanStack folks have
added initial server component support
866
00:48:37,013 --> 00:48:39,253
in its own form to TanStack Start.
867
00:48:39,253 --> 00:48:40,813
We've talked about that
in previous months.
868
00:48:41,163 --> 00:48:46,953
And I believe they had been using that in
the actual TanStack.com website, primarily
869
00:48:46,973 --> 00:48:51,413
to move heavy markdown rendering to the
server so you weren't shipping the, the
870
00:48:51,413 --> 00:48:54,843
markdown rendering logic to the client
and having to wait for that to happen.
871
00:48:55,293 --> 00:48:57,203
And apparently they've removed that.
872
00:48:57,253 --> 00:49:01,183
They put up a post saying they actually
pulled out the server component usage.
873
00:49:01,393 --> 00:49:04,503
It worked, but it, they weren't getting
a lot of benefit out of it, and it was
874
00:49:04,503 --> 00:49:06,443
actually hurting perf in some ways.
875
00:49:06,753 --> 00:49:09,403
And instead, they have
restructured things.
876
00:49:09,403 --> 00:49:14,053
They've actually shipped a couple of very
tiny libraries to do markdown parsing,
877
00:49:14,463 --> 00:49:17,663
and then separately, syntax highlighting.
878
00:49:18,113 --> 00:49:22,833
And so essentially going back to a
somewhat more SPA-ish approach, but
879
00:49:22,863 --> 00:49:26,473
minimizing the amount of work done so
they still get fairly fast loading times.
880
00:49:26,793 --> 00:49:27,103
Carl: Nice.
881
00:49:27,363 --> 00:49:31,803
Let me tell you, doing syntax highlighting
on a documentation site is fucking crazy.
882
00:49:31,973 --> 00:49:36,153
I underweighted that as a problem
circa 2018, and it almost killed
883
00:49:36,153 --> 00:49:40,483
the entire project, because we had
wanted a single API reference page
884
00:49:40,793 --> 00:49:44,593
constructed from dozens of markdown
documents, so we could maintain it as
885
00:49:44,603 --> 00:49:48,303
individual docs, but have it presented
in a single, large, searchable page.
886
00:49:48,643 --> 00:49:52,643
And holy shit, we were shipping 12
megabytes of HTML across the wire
887
00:49:52,653 --> 00:49:54,003
because of syntax highlighting.
888
00:49:54,393 --> 00:49:58,393
We took syntax highlighting out, and it
dropped to, like, you know, 600 kilobytes.
889
00:49:58,603 --> 00:50:01,403
Which is still insane, and, like, part
of the reason it almost killed the
890
00:50:01,403 --> 00:50:04,273
project, because we just were trying
to put too much docs on one webpage.
891
00:50:05,203 --> 00:50:09,831
But- Yeah, man, like when you start
highlighting individual, every individual
892
00:50:09,831 --> 00:50:15,961
character and wrapping it in glyphs, in a
span which has a class name, and, uh, so
893
00:50:15,981 --> 00:50:22,581
it's, it is insane how much markup bloat
gets added just by syntax highlighting.
894
00:50:22,581 --> 00:50:25,891
So moving that from rendered on
the server, shipped to the client,
895
00:50:25,911 --> 00:50:30,031
into data is passed from server
to client and then rendered on, on
896
00:50:30,031 --> 00:50:32,071
the client makes total sense to me.
897
00:50:32,171 --> 00:50:36,401
But that's why this is the cutting edge
of UI, 'cause like that sounds so obvious.
898
00:50:36,431 --> 00:50:39,611
Of course you just want a rendered page
to come directly from the browser and
899
00:50:39,671 --> 00:50:43,591
oops, that rendered page is 20 times
larger than it could be if you just
900
00:50:43,591 --> 00:50:45,621
sent the raw data needed to render it.
901
00:50:45,631 --> 00:50:50,401
So that's why it's so impossible to
answer the question abstractly of
902
00:50:50,401 -->
00:50:53,871
whether or not server components are
right for you, 'cause I don't know.
903
00:50:54,151 --> 00:50:54,581
Do you know?
904
00:50:56,609 --> 00:50:58,139
Anyway, that's a fun project.
905
00:50:58,209 --> 00:50:59,279
This is a really good case study.
906
00:50:59,629 --> 00:51:00,059
I love it.
907
00:51:00,359 --> 00:51:02,849
Mark, tell us, I'm giving
you an opening to talk about
908
00:51:02,859 --> 00:51:04,549
your performance prototyping.
909
00:51:04,949 --> 00:51:07,249
Mark: So I'm pretty sure I alluded
to this two months ago, and then
910
00:51:07,249 --> 00:51:09,299
I linked the draft PR last month.
911
00:51:09,579 --> 00:51:13,579
But for the last few years, I've been
kicking around the idea that surely there
912
00:51:13,579 --> 00:51:20,369
is some way that I can magically use some
combination of signals and proxies inside
913
00:51:20,369 --> 00:51:26,409
of React Redux to speed up performance
updates in large scale applications.
914
00:51:26,419 --> 00:51:31,339
So cases where you have thousands of
connected components, and right now
915
00:51:31,339 --> 00:51:37,169
we have to run all end subscribers
and selectors on every dispatched
916
00:51:37,169 --> 00:51:41,939
action just for each selector to
grab its state and diff the result
917
00:51:41,969 --> 00:51:43,939
and see if it needs to update.
918
00:51:44,299 --> 00:51:47,369
That's fine when you've got
500 or 1,000 components.
919
00:51:47,379 --> 00:51:52,329
When you've got 5,000, 10,000, whatever,
that's just the overhead of calling
920
00:51:52,329 --> 00:51:54,249
those subscribers is expensive.
921
00:51:54,929 --> 00:51:58,739
So I played around with a couple
proof of concepts in previous years.
922
00:51:58,739 --> 00:52:01,459
They were like, you know, like
one-off, I'm gonna hack on something,
923
00:52:01,789 --> 00:52:02,999
and didn't get any further.
924
00:52:03,819 --> 00:52:08,439
So I finally came back to that , and I
did a whole bunch of research on other
925
00:52:08,449 --> 00:52:11,189
signals libraries, proxy-using libraries.
926
00:52:11,199 --> 00:52:12,029
What do they do?
927
00:52:12,039 --> 00:52:12,699
How do they work?
928
00:52:12,719 --> 00:52:13,479
What are they good at?
929
00:52:13,479 --> 00:52:14,229
Where do they break?
930
00:52:14,679 --> 00:52:16,059
All very AI powered.
931
00:52:16,119 --> 00:52:24,289
And I have a working branch that adds a
useSignalSelector hook to React Redux that
932
00:52:24,319 --> 00:52:27,579
is using the Alien Signals library inside.
933
00:52:27,959 --> 00:52:32,809
And essentially what it does is it wraps
your selector so that the data is in a
934
00:52:32,809 --> 00:52:40,009
proxy, tracks what fields got accessed,
and then essentially precomputes, "Hey,
935
00:52:40,009 --> 00:52:44,469
this was the state that got updated.
Do we think that selector actually
936
00:52:44,469 --> 00:52:50,669
needs to run? Nah, skip it." With
the idea being that in most
cases,
937
00:52:50,729 --> 00:52:56,629
only a relative handful of selectors
actually need to rerun most of the time.
938
00:52:57,399 --> 00:53:02,639
So if we can just pre-skip most of them,
that ends up being a performance win.
939
00:53:03,119 --> 00:53:05,089
So I have a draft PR.
940
00:53:05,489 --> 00:53:10,369
It works, and it appears to
be a significant performance
941
00:53:10,369 --> 00:53:12,539
win almost across the board.
942
00:53:13,141 --> 00:53:16,331
In terms of the number of updates,
in terms of the total amount of
943
00:53:16,331 --> 00:53:18,541
scripting time that executes.
944
00:53:19,201 --> 00:53:23,291
It's a little bit slower in the mounting
phase because it takes more work to set
945
00:53:23,291 --> 00:53:25,531
up the signal and the tracking time.
946
00:53:25,911 --> 00:53:28,561
There's definitely going to
be some bigger bundle size.
947
00:53:28,821 --> 00:53:31,611
I don't know how big, like 5 to 10K maybe.
948
00:53:32,061 --> 00:53:35,741
And there's also a few weird
cases, like doing certain identity
949
00:53:35,901 --> 00:53:39,051
comparisons won't work because you're
comparing the proxy reference and
950
00:53:39,051 --> 00:53:40,941
not something inside the proxy.
951
00:53:41,041 --> 00:53:45,691
But it feels good enough, and I've
got solid enough test coverage that
952
00:53:45,691 --> 00:53:50,591
I actually feel very good that, like,
this is a, this is the direction that
953
00:53:50,591 --> 00:53:52,291
I would probably end up shipping.
954
00:53:52,771 --> 00:53:59,541
There's a lot of work to figure out
around real-world testing and, you know,
955
00:53:59,541 --> 00:54:03,801
like all, all the, all the non-fun stuff
around actually shipping real software.
956
00:54:04,321 --> 00:54:07,261
Uh, but the idea is it would
be a separate set of exports.
957
00:54:07,301 --> 00:54:10,581
You would intentionally
choose to use this.
958
00:54:10,851 --> 00:54:14,841
So like most apps would still have
useSelector by default, but if you have
959
00:54:14,841 --> 00:54:21,261
a large-scale app and performance is a
problem, then-- And you, you could choose
960
00:54:21,261 --> 00:54:26,151
to import this and make slightly different
trade-offs in performance and bundle size.
961
00:54:26,531 --> 00:54:29,941
So I feel pretty good about that,
and I'm, I'm still finding time to
962
00:54:29,941 --> 00:54:31,381
try to push that direction forward.
963
00:54:32,041 --> 00:54:37,241
I'm also thinking about what a notional
Redux Toolkit 3.0 would look like.
964
00:54:37,781 --> 00:54:41,591
Uh, a couple years ago when I
shipped 2.0, and I said at the time
965
00:54:41,771 --> 00:54:46,331
that I was deferring touching RTK
Query at all because there's some
966
00:54:46,371 --> 00:54:49,361
unknown number of breaking changes
we would probably wanna make.
967
00:54:49,371 --> 00:54:50,731
I don't even know what those are.
968
00:54:51,131 --> 00:54:52,881
We'll just kick that can down
the road.
969
00:54:53,221 --> 00:54:55,411
Well, we've successfully kicked
the can down the road almost
970
00:54:55,411 --> 00:54:56,831
three years at this point.
971
00:54:57,521 --> 00:55:02,131
Uh, the ecosystem is actually
going ESM-only at this point.
972
00:55:02,141 --> 00:55:06,881
So presumably, if and when we
do a 3.0, it would be ESM-only.
973
00:55:07,451 --> 00:55:12,201
Um, but I've had a bunch of things on
my mind in terms of rough spots in our
974
00:55:12,211 --> 00:55:17,511
API and the way the internals have just
evolved over time, but in a kind of
975
00:55:17,511 --> 00:55:22,081
haphazard way because people keep asking
us to add options or capabilities, and
976
00:55:22,081 --> 00:55:27,501
we just added them without ever really,
like, doing a coherent design upfront.
977
00:55:28,071 --> 00:55:30,911
And so there's, there's a bunch
of pain points I've known about.
978
00:55:30,921 --> 00:55:33,091
There's a bunch of things
I would like to improve.
979
00:55:33,871 --> 00:55:37,531
But they were all, you
know, if, maybe, someday.
980
00:55:38,249 --> 00:55:43,079
And so actually just in the last 48
hours, I did a whole bunch of AI-powered
981
00:55:43,079 --> 00:55:46,389
research tasks saying, "Here's all
the things I would like to have, the
982
00:55:46,429 --> 00:55:52,109
properties and qualities I'd like to
have in a 3.0, um, some new options
983
00:55:52,109 --> 00:55:56,269
I'd like to add that we can't do right
now because they break with TypeScript.
984
00:55:56,739 --> 00:56:02,449
Could we possibly come up with some kind
of an API design that looks basically the
985
00:56:02,449 --> 00:56:07,803
same But is just different enough to clean
things up and unlock the constraints.
986
00:56:08,403 --> 00:56:11,573
And, uh, as of last night,
I've got a local prototype that
987
00:56:12,153 --> 00:56:15,283
Claude claims actually, like,
does most of what I wanna do.
988
00:56:15,943 --> 00:56:20,873
So, like, noth- nothing's happening
anytime soon over here, but, like, I
989
00:56:20,873 --> 00:56:24,193
actually have had the time and effort
to do this because the AI can do the
990
00:56:24,193 --> 00:56:27,723
dirty work, and frankly, I didn't
have the time or effort or mental
991
00:56:27,723 --> 00:56:29,353
capacity to do that work myself.
992
00:56:29,673 --> 00:56:33,303
And so being able to tell it, "Here's
what I want. Can you just, like, run for
993
00:56:33,303 --> 00:56:37,363
a while and, and come back to me and tell
me if this works?" has actually made this
994
00:56:37,363 --> 00:56:40,093
possible, which is actually pretty cool.
995
00:56:40,633 --> 00:56:45,513
So nothing's, like, nothing's gonna
ship anytime soon, but I actually
996
00:56:45,513 --> 00:56:46,853
like the direction this is going.
997
00:56:47,343 --> 00:56:47,963
Carl: That's super fun.
998
00:56:48,333 --> 00:56:52,483
I love having problems within a box
that is clearly defined enough to
999
00:56:52,483
--> 00:56:54,893
where AI can do it in that kind of way.
1000
00:56:54,913 --> 00:56:58,693
A lot of the problems I've been exploring
are primarily in my head, and so
1001
00:56:58,693 --> 00:57:02,903
getting them out of my head and into
a state that AI can check against is
1002
00:57:03,013 --> 00:57:04,393
its own task, and so it's a problem.
1003
00:57:04,773 --> 00:57:07,413
Mark: Part of me feels a little
bad that some of my contribution
1004
00:57:07,413 --> 00:57:10,963
here was just saying the equivalent
of, "I don't like that answer.
1005
00:57:11,073 --> 00:57:11,763
Try again.
1006
00:57:12,003 --> 00:57:16,043
Think harder." But also, like, I had
to come up with, "Here's the list of
1007
00:57:16,053 --> 00:57:21,043
constraints that I want to satisfy and
the problems I want to solve, and here's
1008
00:57:21,043 --> 00:57:23,223
the list of the prior research we did.
1009
00:57:23,733 --> 00:57:28,843
Now go think hard on these things." Like,
I am actually driving the work here.
1010
00:57:28,923 --> 00:57:29,183
Carl: Right.
1011
00:57:29,193 --> 00:57:33,953
Having that body of knowledge and
research is critical, and is real
1012
00:57:33,953 --> 00:57:35,743
work, and should not be discounted.
1013
00:57:36,403 --> 00:57:36,763
Cool.
1014
00:57:36,803 --> 00:57:39,833
Into a couple of final
details before we wrap up.
1015
00:57:40,173 --> 00:57:42,203
This is a fun aside.
1016
00:57:42,533 --> 00:57:45,093
Making referential stability a type.
1017
00:57:45,303 --> 00:57:48,083
So React relies pretty heavily
on referential stability, which
1018
00:57:48,083 --> 00:57:50,123
is triple equals equality.
1019
00:57:50,393 --> 00:57:54,053
If you have two objects or arrays
that are equal to each other, it
1020
00:57:54,053 --> 00:57:55,523
is literally the same reference.
1021
00:57:55,543 --> 00:57:56,513
It is the same pointer.
1022
00:57:56,513 --> 00:57:59,193
It's in this, the same part of memory.
1023
00:57:59,703 --> 00:58:04,483
And someone made a type that
represents that, which is crazy.
1024
00:58:04,723 --> 00:58:06,053
I don't understand how they did that.
1025
00:58:06,343 --> 00:58:10,933
I saw our resident TypeScript wizard
here, who is the person-- I think
1026
00:58:10,933 --> 00:58:13,943
they're the only person who's answered
any types question I've had in the
1027
00:58:13,943 --> 00:58:17,173
last, like, decade, possibly literally.
1028
00:58:18,073 --> 00:58:21,403
My favorite types wizard said,
"Oh, cool. I tried to do this
1029
00:58:21,433 --> 00:58:23,213
and gave up." Which I just love.
1030
00:58:23,223 --> 00:58:24,393
Like, yeah, this is a hard problem.
1031
00:58:24,393 --> 00:58:25,083
It's really cool.
1032
00:58:25,103 --> 00:58:26,353
It would be really nice to have.
1033
00:58:26,663 --> 00:58:30,543
Somebody seems to have put together
a real effort at it, and I love that.
1034
00:58:30,573 --> 00:58:30,983
It's cool.
1035
00:58:31,023 --> 00:58:33,943
Mark: Yeah,
what they bork
on both Preact and GraphQL.
1036
00:58:33,993 --> 00:58:35,723
They're one of the Preact maintainers.
1037
00:58:35,893 --> 00:58:36,293
Carl: Oh, cool.
1038
00:58:36,323 --> 00:58:36,823
I love that.
1039
00:58:36,993 --> 00:58:37,263
Wow.
1040
00:58:37,263 --> 00:58:38,203
Real-- I don't know.
1041
00:58:38,203 --> 00:58:38,963
They got real chops.
1042
00:58:39,183 --> 00:58:43,437
Yeah, core team of Preact,
Urql, and- Gql.tada.
1043
00:58:43,437 --> 00:58:47,557
So yeah, okay, they've got some real
experience with wrangling complex data.
1044
00:58:48,134 --> 00:58:48,614
That's awesome.
1045
00:58:48,884 --> 00:58:52,774
Mark: There's been an interesting
set of different projects around
1046
00:58:52,794 --> 00:58:56,904
trying to compile TypeScript
code to true native code.
1047
00:58:57,294 --> 00:59:00,664
One that's been out there for a
while is called AssemblyScript, and
1048
00:59:00,664 --> 00:59:05,684
it's essentially a, a restricted
subset of TypeScript, not full-blown
1049
00:59:05,684 --> 00:59:07,204
true JavaScript semantics.
1050
00:59:07,484 --> 00:59:11,934
But there's three different projects
I've seen recently that are attempts
1051
00:59:11,934 --> 00:59:17,344
to compile just straight-up TypeScript
code to native code in some form.
1052
00:59:17,694 --> 00:59:21,204
One's called Porffor, which is
a… It's a single-person project.
1053
00:59:21,504 --> 00:59:26,264
He's been posting about this for a
while and doing a lot of performance
1054
00:59:26,264 --> 00:59:30,044
optimizations on the output lately, and
even making the compiler self-hosting.
1055
00:59:30,384 --> 00:59:35,954
So he announced that Pro4 is about ready
to hit alpha stage in the next few weeks.
1056
00:59:36,384 --> 00:59:38,974
So that, that's a pretty massive
technical achievement there.
1057
00:59:39,354 --> 00:59:45,554
A second one called Perry that I,
I don't know who's working on this,
1058
00:59:45,564 --> 00:59:47,414
but I saw it pop up pretty recently.
1059
00:59:47,804 --> 00:59:51,204
So they're also trying to compile
TypeScript to native code, and they
1060
00:59:51,204 --> 00:59:56,164
recently put up an article about
taking the entire, like, 13-megabyte
1061
00:59:56,164 --> 01:00:02,034
Claude code bundle that ships on
disk and compiling that to native.
1062
01:00:02,314 --> 01:00:06,664
And part of it's the compilation process,
and part of it is all the semantics
1063
01:00:06,994 --> 01:00:12,994
and non-JS bits that it expects, like
relying on the, the message channel,
1064
01:00:12,994 --> 01:00:17,234
message port interface to, to send
messages back and forth over a microtask.
1065
01:00:17,474 --> 01:00:23,424
And then Vercel just announced something
called ScriptC, and this is apparently
1066
01:00:23,434 --> 01:00:28,344
in their Vercel Labs area, which is where
they put all their vibe-coded projects.
1067
01:00:28,364 --> 01:00:31,814
And, uh, boy was this one vibe-coded,
I think someone on Hacker News
1068
01:00:31,814 --> 01:00:35,214
points out that the first commit
is 800,000 lines a week ago.
1069
01:00:36,074 --> 01:00:39,944
Yeah, so who knows what the
actual quality is there, but
1070
01:00:39,974 --> 01:00:40,954
they're playing around with that.
1071
01:00:41,544 --> 01:00:47,482
So Bunch of different people trying
to solve the same problem of, it's
1072
01:00:47,482 --> 01:00:52,172
both the publishing aspect and the
runtime execution speed aspect.
1073
01:00:52,672 --> 01:00:53,002
Carl: Cool.
1074
01:00:53,282 --> 01:00:53,792
Interesting.
1075
01:00:54,022 --> 01:00:57,882
Well, I would love it if we had some
more native compiled… what attention
1076
01:00:57,882 --> 01:01:02,112
we experience, because native
compiling is also the thing getting
1077
01:01:02,172 --> 01:01:04,942
suppressed by NPM for security reasons.
1078
01:01:05,772 --> 01:01:10,672
So yeah, what, what attention the
ecosystem is under right now of moving
1079
01:01:10,672 --> 01:01:17,792
away from compiled dependencies,
but also being very hungry for the
1080
01:01:17,792 --> 01:01:21,142
kind of performance improvements
that native code is capable of.
1081
01:01:21,162 --> 01:01:25,372
Mark: I mean, I think in general,
packages that have a native dependency
1082
01:01:25,842 --> 01:01:30,012
used to rely on a postinstall script
to check your local environment and
1083
01:01:30,012 --> 01:01:32,462
then go manually download the binary.
1084
01:01:32,812 --> 01:01:36,702
And at this point, most of them, like ES
Build, have switched over to we're just
1085
01:01:36,702 --> 01:01:41,782
gonna publish a se- a separate package
for each possible native architecture.
1086
01:01:42,292 --> 01:01:46,142
And then the package managers have
gotten smart enough to say, "Oh, well,
1087
01:01:46,412 --> 01:01:52,812
each of those packages lists a certain
native environment that it needs. Let's
1088
01:01:52,812 --> 01:01:56,982
only actually install the one that
matches your current environment."
1089
01:01:57,192 --> 01:01:57,532
Carl: Fair.
1090
01:01:57,942 --> 01:01:58,452
Interesting.
1091
01:01:59,202 --> 01:02:01,262
Complex, nuanced, subtle.
1092
01:02:01,452 --> 01:02:02,002
Mark: Programming.
1093
01:02:02,572 --> 01:02:03,072
Carl: Programming.
1094
01:02:03,162 --> 01:02:03,722
Facts.
1095
01:02:04,122 --> 01:02:04,852
Cool, okay.
1096
01:02:04,882 --> 01:02:08,902
Our last link for you today is,
I don't know, it's kind of sad.
1097
01:02:09,022 --> 01:02:10,922
Goodbye Forever, Probably.
1098
01:02:11,342 --> 01:02:12,272
Mark: It's very personal.
1099
01:02:12,562 --> 01:02:13,342
Carl: Very personal.
1100
01:02:13,362 --> 01:02:19,032
This is by Salma Alam-Naylor,
who goes by White Panther online.
1101
01:02:19,082 --> 01:02:23,232
They were a very talented developer
relations person for quite a while.
1102
01:02:23,272 --> 01:02:25,372
I feel like they sprung up out
of nowhere, or at least I didn't
1103
01:02:25,372 --> 01:02:26,552
see them before they were huge.
1104
01:02:26,902 --> 01:02:30,142
And I always thought they were
very, very, just very skilled at it.
1105
01:02:30,152 --> 01:02:33,382
I thought they did a really good
job of being technically at the
1106
01:02:33,382 --> 01:02:37,942
cutting edge, while being, like,
personable and entertaining.
1107
01:02:37,972 --> 01:02:39,282
And, like, that's really hard.
1108
01:02:39,292 --> 01:02:41,302
All three of those is really hard to do.
1109
01:02:41,882 --> 01:02:46,482
But, so anyway, she put out this blog
post called Goodbye Forever, Probably:
1110
01:02:46,492 --> 01:02:49,592
Why I'm Leaving Developer Relations and
Why I'm Not Telling You What's Next.
1111
01:02:50,052 --> 01:02:52,422
And oh man, I gotta say, a
lot of this resonated with me.
1112
01:02:52,462 --> 01:02:56,472
I've actually never had a job
described as developer relations.
1113
01:02:56,852 --> 01:02:59,712
I'm just a developer who blogged
and has engaged with the community,
1114
01:02:59,942 --> 01:03:04,572
which then later turned into
the job of developer relations.
1115
01:03:04,662 --> 01:03:07,382
This whole thing I relate to so much.
1116
01:03:07,382 --> 01:03:10,612
Like, the number of times I've sat and
seriously contemplated if I wanted to
1117
01:03:10,612 --> 01:03:17,278
keep doing what I was doing is, like-
At least five, possibly more than 10.
1118
01:03:17,378 --> 01:03:18,158
I think about it often.
1119
01:03:18,978 --> 01:03:19,948
And I've always stuck it out.
1120
01:03:20,038 --> 01:03:20,878
I don't know, here I am.
1121
01:03:20,908 --> 01:03:23,678
Probably because nobody's paying
me and because I have full agency
1122
01:03:23,678 --> 01:03:26,248
over everything I do, which has
its own different trade-offs.
1123
01:03:26,678 --> 01:03:27,618
And yeah, I don't know.
1124
01:03:27,628 --> 01:03:31,568
This is just a really good articulation
of how hard it is to be publicly
1125
01:03:31,578 --> 01:03:34,168
visible in tech and to get paid for it.
1126
01:03:34,478 --> 01:03:40,888
And I think that if you are someone
who consumes tech content, this is
1127
01:03:40,888 --> 01:03:43,378
a really good read to see what it's
like on the other side of the page.
1128
01:03:43,638 --> 01:03:43,808
Mark: Yeah.
1129
01:03:43,838 --> 01:03:46,308
So, um, makes a, an, a
bunch of different points.
1130
01:03:46,318 --> 01:03:51,688
A lot of it is around dev rel as
a job role, that it's, it is by
1131
01:03:51,688 --> 01:03:53,308
its nature really hard to measure.
1132
01:03:53,408 --> 01:03:56,898
You know, how are you… Like, what
metrics are you being measured on?
1133
01:03:56,908 --> 01:03:59,058
How are you trying to
contribute to the company?
1134
01:03:59,438 --> 01:04:01,728
How do you even know if
you're having success?
1135
01:04:01,738 --> 01:04:02,488
What is your role?
1136
01:04:02,488 --> 01:04:04,588
Are you going to conferences,
writing blog posts, writing
1137
01:04:04,588 --> 01:04:06,118
documentation, that sort of thing.
1138
01:04:06,468 --> 01:04:10,688
But specifically she also talks about
being heavily overworked at multiple
1139
01:04:10,688 --> 01:04:13,428
companies, and that contributing things.
1140
01:04:13,998 --> 01:04:15,948
She'd spent a lot, a
lot of time streaming.
1141
01:04:15,988 --> 01:04:18,958
That was a really big part of
her online persona, both in
1142
01:04:18,958 --> 01:04:20,548
and out of the day job role.
1143
01:04:20,598 --> 01:04:22,778
So that, that sucks up a
lot of time and effort.
1144
01:04:23,128 --> 01:04:27,728
But then also talking about
AI killing teaching content.
1145
01:04:28,108 --> 01:04:32,988
When she linked this post publicly on
Blue Sky, there was a massive number
1146
01:04:32,988 --> 01:04:36,718
of responses, and I know somewhere
down in the replies, Josh Comeau
1147
01:04:36,718 --> 01:04:42,168
said that he's looking at taking a
break from building courses as well.
1148
01:04:42,258 --> 01:04:48,848
So when you put in massive amounts of time
and effort to carefully craft a teaching
1149
01:04:48,848 --> 01:04:53,778
course, and then either y- you don't
get much payoff because people aren't
1150
01:04:53,788 --> 01:04:58,876
buying it or the content essentially
just ends up getting swiped Yeah.
1151
01:04:59,046 --> 01:05:00,376
Like, why put in the time?
1152
01:05:00,846 --> 01:05:01,076
Carl: Yep.
1153
01:05:01,206 --> 01:05:04,486
I was thinking about Josh and this as
well, 'cause Salma says here, "I've too
1154
01:05:04,486 --> 01:05:08,006
often overworked myself in desperate
attempt to justify my existence. This
1155
01:05:08,006 --> 01:05:10,886
has more than once caused me to suffer
from health problems, including joint
1156
01:05:10,906 --> 01:05:15,296
and nerve pain. At its worst, I couldn't
even use my hands due to the pain."
1157
01:05:15,506 --> 01:05:16,646
That happened to Josh.
1158
01:05:16,936 --> 01:05:21,226
Like, both Josh and Salma had to learn
to code with their voice because of
1159
01:05:21,426 --> 01:05:23,816
hand injuries as a result of overwork.
1160
01:05:23,836 --> 01:05:29,976
So, like, these are two extremely
successful people who have, as in
1161
01:05:29,976 --> 01:05:34,036
pursuing their success, ground their
bodies into a state of non-function.
1162
01:05:34,376 --> 01:05:36,016
So, like, that's the industry we're in.
1163
01:05:36,026 --> 01:05:36,396
I don't know.
1164
01:05:36,416 --> 01:05:37,976
This is what working in tech does.
1165
01:05:38,006 --> 01:05:39,586
This is what succeeding in tech does.
1166
01:05:39,636 --> 01:05:40,306
It's hard.
1167
01:05:40,416 --> 01:05:44,636
One of the decisions I made in
producing this podcast was I
1168
01:05:44,636 --> 01:05:46,816
am not targeting entry level.
1169
01:05:46,966 --> 01:05:48,096
This is not educational.
1170
01:05:48,116 --> 01:05:50,896
This is not catch up, this
is stay on the cutting
edge.
1171
01:05:51,486 --> 01:05:54,316
And part of that was because
of looking at the economics and
1172
01:05:54,316 --> 01:05:55,756
realizing that, like, you know what?
1173
01:05:55,776 --> 01:05:59,266
If you're targeting entry
level people, the market you're
1174
01:05:59,306 --> 01:06:00,986
chasing doesn't have the income.
1175
01:06:01,036 --> 01:06:02,126
They don't have money.
1176
01:06:02,126 --> 01:06:03,966
They're trying to get into tech.
1177
01:06:04,166 --> 01:06:09,176
Part of the reason I have never targeted
entry level humans in tech, trying to
1178
01:06:09,176 --> 01:06:12,506
get into tech, is because I felt the
economics of it was pretty fucked up.
1179
01:06:12,526 --> 01:06:15,486
It was, you're taking money from
people who aspire to get into
1180
01:06:15,486 --> 01:06:19,576
tech to get the high salaries,
and that's playing off people's
1181
01:06:19,576 --> 01:06:21,876
desperation to succeed and do well.
1182
01:06:22,156 --> 01:06:25,446
And, like, ultimately, like sure, while
the money was flowing, while it was
1183
01:06:25,446 --> 01:06:29,996
easy to get into tech, while you could
self-teach and then get a full-time
1184
01:06:29,996 --> 01:06:32,626
job that pays you six figures, like
fuck yeah, that was a great deal.
1185
01:06:32,636 --> 01:06:33,166
That was great.
1186
01:06:33,176 --> 01:06:33,876
That was phenomenal.
1187
01:06:33,946 --> 01:06:35,146
It was a good part of the world to be in.
1188
01:06:35,736 --> 01:06:36,706
And now you can't.
1189
01:06:36,806 --> 01:06:41,186
And so I think we're gonna watch
a lot of educators' careers dry up
1190
01:06:41,196 --> 01:06:46,626
because for all the good they did
for the people, the market they're
1191
01:06:46,696 --> 01:06:49,296
serving to doesn't have the money.
1192
01:06:49,606 --> 01:06:50,956
They're trying to get the money.
1193
01:06:51,316 --> 01:06:53,046
I think we're gonna see
more of this, unfortunately.
1194
01:06:53,506 --> 01:06:56,236
It's gonna get blamed on AI, and,
but there is a portion of that.
1195
01:06:56,236 --> 01:06:59,766
People don't seek-- People are
self-educating less often and
1196
01:06:59,766 --> 01:07:03,506
relying on AI to learn more of those
nuts and bolts details for them.
1197
01:07:03,726 --> 01:07:04,406
That's true.
1198
01:07:04,886 --> 01:07:09,536
But I do think there's another
real problem of incentives.
1199
01:07:09,606 --> 01:07:13,606
You know, this reminds me too of
GitHub just announced, their sponsors
1200
01:07:13,626 --> 01:07:17,276
program, the GitHub sponsors program,
you know, they waved the banner.
1201
01:07:17,276 --> 01:07:21,026
They, you know, did the proud
marketing announcement that $100
1202
01:07:21,026 --> 01:07:25,126
million has flowed through the
program since its inception in 2018.
1203
01:07:25,386 --> 01:07:29,606
So since 2018, 2019 I think it
was actually, 'cause the number
1204
01:07:29,606 --> 01:07:30,506
in my head is seven years.
1205
01:07:30,966 --> 01:07:35,646
But so over the past seven years of
GitHub having a sponsorship program, $100
1206
01:07:35,646 --> 01:07:37,866
million has flowed through it in total.
1207
01:07:38,386 --> 01:07:40,216
Mark: 14 million a year.
1208
01:07:40,576 --> 01:07:40,956
Carl: Yeah.
1209
01:07:41,096 --> 01:07:46,236
I did 30 seconds of back of the napkin
research and math, and the number
1210
01:07:46,236 --> 01:07:50,986
I came up with for venture capital
dollars that flowed just in SF over
1211
01:07:50,986 --> 01:07:54,006
the same time period is 200 billion.
1212
01:07:54,848 --> 01:07:59,058
So while content creators are chasing
their piece of $100 million, the
1213
01:08:00,448 --> 01:08:04,538
businesses are chasing 200 times that.
1214
01:08:05,058 --> 01:08:08,228
Thousands of times the
sums of money involved.
1215
01:08:08,228 --> 01:08:12,438
So like, I- it's, for all the commentary
about, you know, who's doing what in
1216
01:08:12,438 --> 01:08:17,228
education and content and making money,
like at the end of the day, like there's a
1217
01:08:17,228 --> 01:08:22,308
stereotype of a certain political subgroup
that all just passes around the same $20.
1218
01:08:22,448 --> 01:08:24,308
You get it, and you give it to someone
else, and they give it to someone
1219
01:08:24,308 --> 01:08:25,368
else, and they give it to someone else.
1220
01:08:25,618 --> 01:08:28,928
And like that's how I see
programs like GitHub sponsors.
1221
01:08:29,108 --> 01:08:32,718
It's not a sustainable ecosystem
'cause you're all just passing the
1222
01:08:32,718 --> 01:08:34,318
same $20 around at the end of the day.
1223
01:08:34,348 --> 01:08:35,658
The money's coming from somewhere else.
1224
01:08:36,158 --> 01:08:38,968
So that's my… Sorry, that's my
political rant at the end of this.
1225
01:08:39,088 --> 01:08:39,708
It's rough.
1226
01:08:39,848 --> 01:08:40,688
It's rough out there.
1227
01:08:41,298 --> 01:08:42,668
Mark, did you add these conferences?
1228
01:08:42,768 --> 01:08:43,478
Should we read them?
1229
01:08:43,998 --> 01:08:46,198
Mark: Yeah, I put them in here,
uh, because I will actually be
1230
01:08:46,238 --> 01:08:49,338
speaking at both of them, and
they're, they're also coming up.
1231
01:08:49,518 --> 01:08:52,858
So listing the two conferences off the
top of my head that I know I'll be at.
1232
01:08:53,198 --> 01:08:57,638
ZurichJS in Zurich,
Switzerland on September 11th.
1233
01:08:57,918 --> 01:09:01,468
The primary organizer, Faris
Aziz, great person, first year
1234
01:09:01,468 --> 01:09:02,488
putting on the conference.
1235
01:09:02,848 --> 01:09:06,348
I have a sense of how much time
and effort he has put into trying
1236
01:09:06,348 --> 01:09:07,828
to organize this conference.
1237
01:09:08,098 --> 01:09:12,698
Fantastic person, ton of effort, and
I'm really looking forward to that one.
1238
01:09:12,758 --> 01:09:14,278
Great list of speakers as well.
1239
01:09:14,528 --> 01:09:19,328
And then, uh, React Alicante is in
Spain September 25th and 26th, o-
1240
01:09:19,338 --> 01:09:20,938
out on the Mediterranean coastline.
1241
01:09:21,288 --> 01:09:23,478
This will be my third
straight year speaking there.
1242
01:09:23,498 --> 01:09:27,248
Again, wonderful conference, great
community vibe, highly recommended.
1243
01:09:27,378 --> 01:09:30,488
So if any of you happen to be in
Europe or can make your way over to
1244
01:09:30,488 --> 01:09:32,148
Europe, definitely check those out.
1245
01:09:32,368 --> 01:09:33,008
Carl: Heck yeah.
1246
01:09:33,078 --> 01:09:34,618
Well, that's everything we got for you.
1247
01:09:34,668 --> 01:09:35,758
Thank you for listening.
1248
01:09:35,848 --> 01:09:39,998
We'll be back here on the live stage on
the last Wednesday of August, or back in
1249
01:09:39,998 --> 01:09:41,678
your podcast feed just as soon as we can.
1250
01:09:41,778 --> 01:09:44,798
Man, maybe, hopefully I'll get it
in by the end of the month in July.
1251
01:09:44,808 --> 01:09:45,868
I've been bad at that lately.
1252
01:09:46,308 --> 01:09:46,998
Sorry everybody.
1253
01:09:47,388 --> 01:09:50,168
Yeah, thank you so much for
listening, especially to those of
1254
01:09:50,168 --> 01:09:53,728
you who made it all the way through
the end to hear this gratitude.
1255
01:09:53,828 --> 01:09:56,998
Mark: We started the day by saying
we've got a grab bag of stuff.
1256
01:09:57,188 --> 01:09:59,208
Yeah, we never run out
of stuff to talk about.
1257
01:09:59,258 --> 01:10:00,968
We cut out 15 items.
1258
01:10:01,058 --> 01:10:05,558
Carl: Yeah, we did cut out legitimately 15
items and still went 30 minutes over time.
1259
01:10:06,328 --> 01:10:06,508
Yep.
1260
01:10:06,868 --> 01:10:07,368
That's us.
1261
01:10:07,878 --> 01:10:08,548
Thanks so much.
1262
01:10:08,558 --> 01:10:11,268
If there's feedback you wanna send,
if there's tips you wanna give, please
1263
01:10:11,308 --> 01:10:12,138
email them to hello@reactiflux.com.
1264
01:10:14,358 --> 01:10:16,268
I read every email that comes through.
1265
01:10:16,358 --> 01:10:17,058
It's a low number.
1266
01:10:17,058 --> 01:10:17,708
It's very easy.
1267
01:10:18,198 --> 01:10:20,248
If this is a show that you get
value from and wanna support, the
1268
01:10:20,248 --> 01:10:23,508
best way to do so is by submitting
a review wherever you listen and by
1269
01:10:23,538 --> 01:10:24,908
sending this episode to your friends.
1270
01:10:25,008 --> 01:10:25,528
Thanks so much.
1271
01:10:25,648 --> 01:10:26,118
See you next month.