TRANSKRIPT 🔗
WEBVTT
1
00:00:05.160 --> 00:00:08.919
Hey, folks, welcome back to another episode of JavaScript Jabber.
2
00:00:09.480 --> 00:00:12.759
This week on your panel's It's just Me this week
3
00:00:12.960 --> 00:00:18.960
Charles max Wood. I'm also here with Aral Rocca Gomez.
4
00:00:20.719 --> 00:00:22.719
Do you want to just introduce yourself, let people know
5
00:00:22.760 --> 00:00:26.199
who you are and what maybe you're famous for that
6
00:00:26.280 --> 00:00:26.839
kind of a thing.
7
00:00:29.559 --> 00:00:33.799
Yeah, sure, Hello, Well, yeah, I'm at all. I'm from Barcelona.
8
00:00:35.920 --> 00:00:38.280
I love to contribute the open source, so I have
9
00:00:38.640 --> 00:00:41.520
a lot of libraries and I try to contrude as
10
00:00:41.560 --> 00:00:42.840
much as possible to open source.
11
00:00:42.960 --> 00:00:49.479
And the last seeing a Davy, it's a framework, Risa. Yeah,
12
00:00:49.600 --> 00:00:51.479
that's the topic of awesome.
13
00:00:51.759 --> 00:00:54.399
Yeah, I got in, had started having a look and
14
00:00:54.439 --> 00:01:00.320
it looks like it kind of does everything. So before
15
00:01:00.320 --> 00:01:03.399
we get too far in, I did want to ask
16
00:01:05.879 --> 00:01:07.159
why build another framework?
17
00:01:07.359 --> 00:01:07.519
Right?
18
00:01:07.680 --> 00:01:10.680
It seems like the running joke for a long time
19
00:01:10.879 --> 00:01:14.840
was another day another framework kind of thing, So yeah,
20
00:01:15.319 --> 00:01:19.400
why why create something new as opposed to just saying, oh,
21
00:01:19.400 --> 00:01:20.920
here's how you're doing reakay whatever.
22
00:01:21.000 --> 00:01:25.120
Yeah, it's yeah, it's a little bit different than the
23
00:01:25.159 --> 00:01:25.680
other ones.
24
00:01:25.959 --> 00:01:29.640
It's a it's a fully started framework, but it's not
25
00:01:30.159 --> 00:01:34.560
like solid the start jes or or as spal kids
26
00:01:35.000 --> 00:01:39.879
because all these frameworks, and really it's a top framework
27
00:01:39.920 --> 00:01:40.840
from some front.
28
00:01:40.879 --> 00:01:46.640
The library like noj is using React a library, and.
29
00:01:48.599 --> 00:01:51.879
That's the same for next, but it's using bw aspal
30
00:01:51.959 --> 00:01:56.120
Kit is using the spread et cetera. And in Brizil
31
00:01:56.200 --> 00:01:59.079
we implement it in the other way. So we started
32
00:01:59.239 --> 00:02:03.879
building the framework without any JavaScript from ten library and
33
00:02:04.359 --> 00:02:08.719
the main goal at the beginning was to be possible
34
00:02:08.800 --> 00:02:15.520
to create web applications without Java, skip playing code and
35
00:02:15.000 --> 00:02:19.159
bringing all the power on the server. And here we
36
00:02:19.360 --> 00:02:23.680
mix ideas from actually the makes that it's a great library,
37
00:02:24.439 --> 00:02:30.759
and also ideas from server actions, but implemented in a
38
00:02:30.759 --> 00:02:35.199
different way.
Load full transcript
And this was the first approach, but then
39
00:02:36.400 --> 00:02:40.680
we realized that well, really be playing interactions also makes
40
00:02:40.719 --> 00:02:44.680
sense in order to implement that. And one of the
41
00:02:44.680 --> 00:02:47.719
things that we like in presides to use the web
42
00:02:47.719 --> 00:02:50.759
platform as much as possible. And also we are transferring
43
00:02:50.840 --> 00:02:56.680
hypermedia and the best thing to support this front and
44
00:02:56.759 --> 00:03:02.840
part was to implement web components and but two in
45
00:03:02.879 --> 00:03:05.680
a different way because we wanted that the developers can
46
00:03:05.759 --> 00:03:08.919
write the components in an easy way, in the similar
47
00:03:09.240 --> 00:03:13.400
way that they are breeding the server components with.
48
00:03:13.560 --> 00:03:13.759
Yeah.
49
00:03:13.800 --> 00:03:19.840
Yes, and also we are using signals for these were components.
50
00:03:20.560 --> 00:03:27.319
So it is another idea of framework, so it's a
51
00:03:27.319 --> 00:03:31.400
little bit different, but the main goal is that, for example,
52
00:03:31.960 --> 00:03:36.560
if you have any commerce and almost everything are server interactions,
53
00:03:37.000 --> 00:03:40.039
you can build it without any component. That is the
54
00:03:40.719 --> 00:03:46.000
most powerful, more powerful thing, and then you have two
55
00:03:46.039 --> 00:03:46.599
kill whites.
56
00:03:46.840 --> 00:03:48.840
That is the size of the RPC.
57
00:03:48.759 --> 00:03:53.759
Of right, So let's go ahead and start with where
58
00:03:53.800 --> 00:03:57.560
you started, because you you mentioned that it was you know,
59
00:03:57.599 --> 00:04:01.199
it had kind of the server what was it, server
60
00:04:01.280 --> 00:04:06.159
actions and those kinds of things, and then yeah, you
61
00:04:06.199 --> 00:04:09.759
brought in some of the ideas from HTMX. By the way, folks,
62
00:04:10.080 --> 00:04:12.960
it's breeze a b r I s A. You can
63
00:04:13.000 --> 00:04:15.280
find it at Breeza br I s A dot build.
64
00:04:16.800 --> 00:04:23.160
But yeah, so, yeah, you want to explain how the
65
00:04:23.199 --> 00:04:27.759
server actions work and how the HTMX ideas kind of
66
00:04:27.759 --> 00:04:29.720
come in, and then we can move up from there
67
00:04:29.839 --> 00:04:30.639
to the front end.
68
00:04:33.839 --> 00:04:36.279
Yeah sure, Yeah.
69
00:04:36.480 --> 00:04:39.279
In Briza, all the events on the server are server
70
00:04:39.360 --> 00:04:44.079
actions and they are very similar that from ten events.
71
00:04:44.199 --> 00:04:48.839
So you can capture not only on submit, also on click,
72
00:04:48.879 --> 00:04:53.079
on a stroll, on double click, all the events and
73
00:04:53.160 --> 00:04:56.959
also the propagation is working on the server components so
74
00:04:57.000 --> 00:05:01.240
you can pass on a server component some event and
75
00:05:01.519 --> 00:05:06.680
up on the parent of the server components this action
76
00:05:07.759 --> 00:05:11.959
and the powerful thing here is that we move part
77
00:05:12.000 --> 00:05:14.680
of the web platform on the server and you can
78
00:05:14.759 --> 00:05:17.839
access to the to the event and you can access
79
00:05:17.879 --> 00:05:22.759
to the event current target of value for example or
80
00:05:23.199 --> 00:05:26.319
that attribute, or you can rest a form on the server.
81
00:05:27.279 --> 00:05:33.199
In reality, the responsible to the shop is the RPC
82
00:05:33.399 --> 00:05:39.279
or prison that all the code that the developers are
83
00:05:39.720 --> 00:05:42.319
Britain executities on the server.
84
00:05:42.480 --> 00:05:45.079
So this is the powerful thing.
85
00:05:45.480 --> 00:05:51.879
And then we add some extra attributes from IDA from
86
00:05:51.879 --> 00:05:57.199
a tetemis for example an indicator to handle pending the states.
87
00:05:57.160 --> 00:06:02.720
The rower states of this actions m H in a
88
00:06:02.759 --> 00:06:03.279
easy way.
89
00:06:04.160 --> 00:06:07.839
Also, for example, if it's an input, we are supporting
90
00:06:07.959 --> 00:06:13.680
at the bounds. If to support this the bounds on
91
00:06:13.920 --> 00:06:17.759
the server. It's not the client, but it's written on
92
00:06:17.800 --> 00:06:21.879
the server. And and also one.
93
00:06:21.720 --> 00:06:25.879
Of the the ideas of themics that we are supporting
94
00:06:26.040 --> 00:06:31.000
is hyper media, so all the server actions are transferring
95
00:06:31.319 --> 00:06:40.319
al but in a streaming okay, and but yeah, to
96
00:06:40.399 --> 00:06:46.600
understand a little bit better, the how does improved if
97
00:06:46.600 --> 00:06:50.480
we are thinking to the normal way to do a
98
00:06:50.920 --> 00:06:58.079
server interaction with other frameworks. Normally, we are adding a client.
99
00:06:59.639 --> 00:07:04.040
Client to normalize the event, then realize, and then we
100
00:07:04.120 --> 00:07:09.120
are calling some API endpoint. Then we are awaiting the
101
00:07:09.240 --> 00:07:12.560
response of the server, and then we are rendering on
102
00:07:12.680 --> 00:07:16.959
the client, also adding more client gode and in Briza
103
00:07:17.040 --> 00:07:21.879
we change this approach so all the things happen on
104
00:07:21.920 --> 00:07:26.480
the server and then you can decide if render the component,
105
00:07:27.240 --> 00:07:29.879
render the page, or render another component in another place.
106
00:07:30.279 --> 00:07:32.720
But all these things happen on the server and then
107
00:07:32.759 --> 00:07:36.519
it's transferring to themilin and streaming and the users see
108
00:07:36.519 --> 00:07:42.839
the changes much faster because it's the power of streaming
109
00:07:42.879 --> 00:07:47.399
or that doesn't need to await the response to them
110
00:07:47.639 --> 00:07:49.639
do this extra shop on the client.
111
00:07:49.879 -->
00:07:52.480
Gotcha? So how much faster are we talking? I mean,
112
00:07:54.439 --> 00:07:57.240
I hate asking that question because it depends a lot
113
00:07:57.279 --> 00:08:00.279
on what you're doing. But yeah, yeah, can you give
114
00:08:00.319 --> 00:08:02.319
us a ballpark if you benchmarked or anything?
115
00:08:06.240 --> 00:08:11.560
To be honest, no, because now currently the current version
116
00:08:11.600 --> 00:08:15.600
of Brisa, it's very experimental, it's not yet the one
117
00:08:15.639 --> 00:08:19.079
to zero and for the field public version, we focus
118
00:08:19.160 --> 00:08:21.759
a lot on all the ideas to be all these
119
00:08:21.759 --> 00:08:25.680
ideas and now one of one of the idea is
120
00:08:25.759 --> 00:08:28.920
to do all these major marks and also improve the
121
00:08:29.079 --> 00:08:32.279
disperformance and all these things. So it's something that I
122
00:08:32.320 --> 00:08:34.840
can tell you, but if you try it, Brisa, then
123
00:08:34.879 --> 00:08:37.000
you're going to experiment that it's so fast.
124
00:08:37.639 --> 00:08:41.159
Yeah that makes sense. So yeah, a lot of the work,
125
00:08:41.200 --> 00:08:43.639
it sounds like, is offloaded to the server. It's not
126
00:08:43.679 --> 00:08:48.279
done on the front end. It seems like some of
127
00:08:48.320 --> 00:08:50.360
the other systems that I've been playing with, like next
128
00:08:50.399 --> 00:08:52.120
jay As for example, you brought them up a couple
129
00:08:52.120 --> 00:08:55.559
of times, it does some of this, but it doesn't
130
00:08:56.360 --> 00:08:58.159
a lot of the focus is still on the front end.
131
00:08:58.879 --> 00:09:02.759
So how does Freeze balance that between what's done on
132
00:09:02.799 --> 00:09:04.759
the front end what's done on the back end?
133
00:09:08.120 --> 00:09:11.360
Okay, yeah, but by the fault, it's server component.
134
00:09:11.679 --> 00:09:14.679
But in Briza, we don't like to say server components
135
00:09:14.759 --> 00:09:19.120
and client component. But we are telling these people it's.
136
00:09:18.960 --> 00:09:21.519
More familiar for the understand the idea.
137
00:09:21.799 --> 00:09:23.399
But yes, but.
138
00:09:24.399 --> 00:09:28.399
Relative we like to talk about components that works on
139
00:09:28.440 --> 00:09:30.759
the server but also in build time part because if
140
00:09:30.759 --> 00:09:33.919
you have an esthetic side, you can do it with
141
00:09:33.919 --> 00:09:37.639
with Brizia, but then the server actions is not going
142
00:09:37.679 --> 00:09:42.440
to work. It's one of one of the things. But
143
00:09:43.360 --> 00:09:48.000
then we are supporting these were components, and thee of
144
00:09:48.039 --> 00:09:52.000
these were components is that is also powerful because it's
145
00:09:52.080 --> 00:09:56.600
only three kilo whites including the signals itself, and we
146
00:09:58.320 --> 00:10:01.240
with a lot of optimizations in thank it will be
147
00:10:01.360 --> 00:10:06.799
as more timey as possible. And then if you have
148
00:10:07.559 --> 00:10:11.360
hundred WEA components, it's not increase a lot, it's going
149
00:10:11.360 --> 00:10:12.159
to decrease.
150
00:10:13.799 --> 00:10:15.240
Very very small.
151
00:10:17.200 --> 00:10:20.320
Yeah, that makes sense. So you're kind of optimizing for
152
00:10:20.399 --> 00:10:24.440
how much information you have to send up to the client,
153
00:10:25.320 --> 00:10:32.120
including your code, And I like that. I guess the
154
00:10:32.120 --> 00:10:37.799
other question I have is how does it work as
155
00:10:37.799 --> 00:10:39.799
far as like you know, storage and things like that
156
00:10:39.879 --> 00:10:44.000
on the back end, right, are you counting on people
157
00:10:44.000 --> 00:10:47.399
to use something else there to store stuff in a
158
00:10:47.519 --> 00:10:52.519
database or use Firebase or something like that, or am
159
00:10:52.519 --> 00:10:54.159
I completely missing something there?
160
00:10:54.279 --> 00:10:59.840
Yeah? This is okay, this is an important question. We
161
00:10:59.879 --> 00:11:00.399
have support.
162
00:11:00.639 --> 00:11:02.639
Of course, you can use a database and it's not
163
00:11:02.679 --> 00:11:06.679
a problem. But we are supporting a store on the server,
164
00:11:07.600 --> 00:11:11.360
and this store lives on the request time by the fault.
165
00:11:13.000 --> 00:11:20.080
So but in reality we understand it well. And really
166
00:11:20.200 --> 00:11:23.480
there are two stores, one on the server code on
167
00:11:23.559 --> 00:11:28.159
the server components and the other one in their components,
168
00:11:29.240 --> 00:11:32.679
and then you can transfer some properties from the server
169
00:11:32.840 --> 00:11:34.000
store to the client store.
170
00:11:35.480 --> 00:11:38.720
And this is powerful because then.
171
00:11:40.000 --> 00:11:44.360
After transferring some properties from one store to another one,
172
00:11:44.919 --> 00:11:48.519
then on the on the actions and the sever actions.
173
00:11:48.960 --> 00:11:56.080
Also you can modify this store and also we create
174
00:11:56.159 --> 00:11:59.159
a new concept that is the action signals, because if
175
00:11:59.200 --> 00:12:02.840
you modify this is store on the server action, then
176
00:12:02.919 --> 00:12:06.000
the WAB components, the signals of the web components are.
177
00:12:06.720 --> 00:12:08.120
Okay or the changes.
178
00:12:09.679 --> 00:12:13.080
Yeah, that's nice. So what are you using for this store?
179
00:12:13.240 --> 00:12:16.519
Is it kind of a proprietary thing or is it
180
00:12:17.840 --> 00:12:19.720
you know, back it up on whatever database you want
181
00:12:19.720 --> 00:12:21.240
to use, or how does that work?
182
00:12:22.399 --> 00:12:24.279
Well, this is store. This is a store on the server
183
00:12:24.519 --> 00:12:28.120
is very useful for example, if you fetch something or
184
00:12:28.600 --> 00:12:32.240
or you take something from the database on the top
185
00:12:32.320 --> 00:12:35.200
level of the page and then all their components and
186
00:12:35.399 --> 00:12:41.679
consumiting just access with a store for example.
187
00:12:41.799 --> 00:12:44.279
Yeah, I guess what I'm asking about is like the
188
00:12:44.919 --> 00:12:48.840
longer term persistence. So I mean typically you see people
189
00:12:48.919 --> 00:12:51.720
using like an r M with post resql or my
190
00:12:51.840 --> 00:12:55.120
SQL or something like that. So does your store just
191
00:12:55.840 --> 00:12:59.759
have some kind of interface to that where it's you know,
192
00:12:59.799 --> 00:13:03.480
in the process of doing the store stuff also call
193
00:13:03.559 --> 00:13:05.679
these callbacks that push stuff to the database.
194
00:13:09.440 --> 00:13:13.039
Uh. Then, well, this is a job that the developers
195
00:13:13.120 --> 00:13:13.480
need to.
196
00:13:13.399 --> 00:13:17.960
Do, right, but then I can't do it, for example,
197
00:13:18.000 --> 00:13:21.639
in our several action. Then they can access to the
198
00:13:21.720 --> 00:13:25.559
store and save this value to the database, and then
199
00:13:25.799 --> 00:13:29.240
on the initial render then they can do the same
200
00:13:29.320 --> 00:13:33.559
job to the database and then incialize the store on
201
00:13:33.639 --> 00:13:36.279
the middleware for example or in the page.
202
00:13:39.000 --> 00:13:42.840
All right, so on the front end, I saw some
203
00:13:42.879 --> 00:13:50.639
stuff about web components, and I mean it, it seems
204
00:13:50.679 --> 00:13:55.440
interesting to me. It looks a lot like React, and
205
00:13:55.519 --> 00:14:02.039
that's probably on purpose. But yeah, so I guess I'm
206
00:14:02.120 --> 00:14:03.440
wondering what the difference is.
207
00:14:04.879 --> 00:14:05.799
At the end of the day.
208
00:14:06.720 --> 00:14:11.039
Yeah, when we are writing these WA components, it looks
209
00:14:11.159 --> 00:14:16.720
very very similar than React because this is it with signals.
210
00:14:17.320 --> 00:14:20.919
But then there are some difference. One of them is
211
00:14:20.960 --> 00:14:22.159
that finally.
212
00:14:22.039 --> 00:14:26.360
They are the components and these custom elements exist on
213
00:14:26.440 --> 00:14:31.519
the dome and for example, if you need to build
214
00:14:31.639 --> 00:14:35.879
a form, you need to know the attaching technots, for example,
215
00:14:36.720 --> 00:14:38.960
to expose this were component to be.
216
00:14:38.960 --> 00:14:39.840
Part of the form.
217
00:14:40.600 --> 00:14:47.919
And so there are some difference that we try to
218
00:14:47.919 --> 00:14:53.320
improve the developer experience to be more familiar for the
219
00:14:53.320 --> 00:14:57.159
developers in order to build these ware components. And the
220
00:14:57.240 --> 00:15:02.279
good part also is that thanks to create this JAY
221
00:15:02.360 --> 00:15:07.200
six component, then it's very easy to support the service
222
00:15:07.399 --> 00:15:10.120
rendering of this work component thanks to the declarative shovel
223
00:15:10.159 --> 00:15:15.600
bone on the server and also the type safe work
224
00:15:15.720 --> 00:15:19.639
pretty well because we know the the props et cetera.
225
00:15:19.840 --> 00:15:21.559
And then.
226
00:15:22.879 --> 00:15:25.879
When the good part of briss that when you are
227
00:15:25.919 --> 00:15:31.519
reading the x it's easy to identify if a component
228
00:15:31.639 --> 00:15:34.559
is at component or a Ceber component because the web
229
00:15:34.600 --> 00:15:39.600
component it's written as a crystal element and a Ceber component.
230
00:15:39.679 --> 00:15:46.960
It's like the free components with six and I prove
231
00:15:47.039 --> 00:15:48.200
this developer experience.
232
00:15:49.279 --> 00:15:53.440
What we did is that when you are typing some components,
233
00:15:53.519 --> 00:15:56.120
you can see all the components that you can consume.
234
00:15:57.080 --> 00:16:00.840
And the difference here with the normal way to build
235
00:16:01.519 --> 00:16:06.840
the components that the selector of this crystal element is
236
00:16:07.399 --> 00:16:10.360
by based on the file name. So you have a
237
00:16:11.200 --> 00:16:15.120
special folder. It is everything runs on the server except
238
00:16:15.200 --> 00:16:17.759
one one folder, and this folder is the components folder.
239
00:16:18.360 --> 00:16:23.840
And then each name of the each file it's a selector.
240
00:16:24.240 --> 00:16:30.200
So if you have like a custom counter or whatever,
241
00:16:31.840 --> 00:16:35.279
then is the selector of this crustal element.
242
00:16:38.120 --> 00:16:46.080
I'm not sure if I completely follow that. So, yeah,
243
00:16:46.840 --> 00:16:50.720
you want to just kind of give me a brief clarification. Yeah,
244
00:16:52.159 --> 00:16:54.240
I'm not even sure what to ask clarify.
245
00:16:57.000 --> 00:17:00.320
Yeah, okay, to understand it correctly. It's important thing because
246
00:17:00.360 --> 00:17:05.240
if you are building a web component in Briza, then
247
00:17:05.400 --> 00:17:08.759
if you want to use a component on a server component,
248
00:17:09.039 --> 00:17:12.319
not that server component, use a component, you don't need
249
00:17:12.400 --> 00:17:16.200
to do an import of the web component itself. So
250
00:17:16.359 --> 00:17:22.119
automatically this custom element exists. And and to do this
251
00:17:22.359 --> 00:17:27.240
relation between which were components you can consume on the
252
00:17:27.480 --> 00:17:32.319
JASS is based on the name of the web component file.
253
00:17:32.440 --> 00:17:37.119
Okay, so it's it's doing some kind of autoloading and
254
00:17:38.359 --> 00:17:43.200
intelligent discovery to know what what it's got and what's available.
255
00:17:43.319 --> 00:17:48.000
And so yeah, you don't have to goport on every
256
00:17:48.039 --> 00:17:50.160
single component.
257
00:17:52.599 --> 00:17:53.599
Yes, exactly.
258
00:17:53.799 --> 00:17:56.880
Yes, in build time, what we are doing is to
259
00:17:57.039 --> 00:18:00.400
read all the folder of the web components. Then we
260
00:18:00.559 --> 00:18:04.440
know the way components that can be consumed, and.
261
00:18:05.200 --> 00:18:11.480
Then when we detect someware component, it's uh importing Uh yeah,
262
00:18:12.319 --> 00:18:15.920
this rapper to do this the cloud tip show long
263
00:18:16.039 --> 00:18:16.839
of them, et cetera.
264
00:18:17.279 --> 00:18:22.599
That makes sense I mean, besides some of these uh
265
00:18:22.839 --> 00:18:26.480
you know, optimizations for developer experience, which honestly, that one's
266
00:18:26.480 --> 00:18:28.200
a big one for me because I'm always trying to
267
00:18:28.720 --> 00:18:31.519
keep it straight. Okay, where is this I pull it in,
268
00:18:32.000 --> 00:18:33.279
what do I have to do with it? What do
269
00:18:33.400 --> 00:18:35.599
I have to know about it? And so if it
270
00:18:35.680 --> 00:18:39.160
does all of that kind of a build time, then yeah,
271
00:18:39.200 --> 00:18:43.559
there's a lot less a lot less concern for me
272
00:18:43.599 --> 00:18:47.079
because I can just I just follow the convention and
273
00:18:47.200 --> 00:18:47.880
just have it work.
274
00:18:52.559 --> 00:18:52.799
Yeah.
275
00:18:53.559 --> 00:18:55.640
One of the things that we wanted to do with
276
00:18:55.920 --> 00:18:58.640
with this is to do like a sepparssion of concerns,
277
00:18:58.759 --> 00:19:03.279
so that on the server components, all the importance is
278
00:19:03.359 --> 00:19:07.400
for the server code, and then you can consume that
279
00:19:07.440 --> 00:19:10.839
we're components as we're components that is just for some elements.
280
00:19:11.519 --> 00:19:16.000
And this was the bea basically Yeah, it makes sense.
281
00:19:17.279 --> 00:19:20.960
So I mean, do the components look and function basically
282
00:19:21.200 --> 00:19:24.319
like React components or are there some differences that you
283
00:19:24.400 --> 00:19:27.839
ought to be aware of that are going to trip
284
00:19:27.920 --> 00:19:28.160
you up?
285
00:19:31.359 --> 00:19:34.920
They work on the as functions, so it's not working
286
00:19:34.960 --> 00:19:39.519
as class. Ah well, it's very similar time.
287
00:19:40.920 --> 00:19:42.680
So what are the differences you're going to see I'm
288
00:19:42.680 --> 00:19:45.480
assuming kind of the fundamental stuff all works the same.
289
00:19:45.640 --> 00:19:52.799
So the difference between that, so a React.
290
00:19:52.559 --> 00:19:55.519
Component versus a BRESA component.
291
00:19:57.559 --> 00:19:58.640
Okay, uh?
292
00:19:58.920 --> 00:20:01.319
Yeah, for example, in that we are not using capital
293
00:20:02.400 --> 00:20:06.000
and we are not using renders, so they dated the
294
00:20:06.160 --> 00:20:11.599
only happens one render and then thanks to signals, when
295
00:20:12.079 --> 00:20:16.480
some estate change, that is some sub signal change is
296
00:20:16.559 --> 00:20:22.000
reacting without ruining all the all the web component.
297
00:20:23.200 --> 00:20:26.039
So does that change the life cycle of the component then?
298
00:20:26.200 --> 00:20:28.319
And do you have to be aware of some of
299
00:20:28.359 --> 00:20:28.759
that stuff?
300
00:20:28.799 --> 00:20:35.720
Then all the mounting kind of mounting is working as
301
00:20:35.720 --> 00:20:40.359
an normal component. But then updating this component is uh
302
00:20:40.960 --> 00:20:42.079
is this signals approach?
303
00:20:42.440 --> 00:20:42.599
Yes?
304
00:20:43.480 --> 00:20:46.960
So then I guess my question is what's the primary
305
00:20:49.240 --> 00:20:53.440
benefit to using Freeza instead of a reactor view?
306
00:20:53.599 --> 00:20:53.759
Is it?
307
00:20:54.599 --> 00:20:58.880
Is it the developer experience or you know, you also
308
00:20:58.960 --> 00:21:02.519
mentioned the performance. Are those kind of the big reasons
309
00:21:02.519 --> 00:21:04.000
why I might want to look at this?
310
00:21:07.400 --> 00:21:07.599
Yeah?
311
00:21:07.680 --> 00:21:10.599
It of course that when when when when I started
312
00:21:10.640 --> 00:21:14.720
the prison, the main goal was what I said, to
313
00:21:15.039 --> 00:21:19.200
build our applications without Java strip playing code, and this
314
00:21:19.880 --> 00:21:24.559
for me is the most important part. For example, if
315
00:21:24.640 --> 00:21:28.920
you have any commerce, and any commerce almost all the
316
00:21:29.000 --> 00:21:32.839
interactions of sever interactions like ad item to the card
317
00:21:33.599 --> 00:21:37.039
or also an infinite scroll. You can do it with
318
00:21:37.200 --> 00:21:42.640
a server sever action in Briza. And and this is
319
00:21:42.799 --> 00:21:44.200
the big powerful tool.
320
00:21:45.359 --> 00:21:50.359
The load in time be very very fast. And and
321
00:21:50.519 --> 00:21:55.599
then also all the ideas of these surve reactions also
322
00:21:55.680 --> 00:22:04.200
it's too improve this time also during this interaction thanks
323
00:22:04.240 --> 00:22:05.519
to Attemli storm.
324
00:22:06.079 --> 00:22:07.480
I mean a few other things that I said.
325
00:22:07.799 --> 00:22:11.200
The developer experience no go ahead, Yeah sorry sorry. The
326
00:22:11.279 --> 00:22:14.480
developer experience is very similar in really React.
327
00:22:15.000 --> 00:22:19.319
But then also for example, the developers needs to take
328
00:22:19.359 --> 00:22:22.759
account that there are things that in really event is
329
00:22:23.839 --> 00:22:28.039
all the client parties with components, so there are important
330
00:22:28.079 --> 00:22:31.720
things that they need to know, like attach internal for
331
00:22:31.799 --> 00:22:35.400
example as recommend before or the forums, et cetera.
332
00:22:37.359 --> 00:22:39.160
So one other thing I saw on here and I
333
00:22:39.319 --> 00:22:40.839
kind of feel like I buried the lead here a
334
00:22:40.880 --> 00:22:43.079
little bit because this is something that I know a
335
00:22:43.119 --> 00:22:47.000
lot of people look for in whatever they're doing. But
336
00:22:47.119 --> 00:22:53.200
it looks like you have built offerings for fun no Dino,
337
00:22:53.559 --> 00:22:56.759
which kind of makes sense. But you've also got Android
338
00:22:56.839 --> 00:23:00.359
iOS and desktop, So what is that look like?
339
00:23:03.720 --> 00:23:07.759
Okay, about the run time, the Jabski run time.
340
00:23:08.400 --> 00:23:12.359
At the beginning, we started only with band because ah,
341
00:23:13.720 --> 00:23:18.200
when when I started to build Briza was with all
342
00:23:18.319 --> 00:23:22.839
the banding. For example, we are not using bits. We
343
00:23:22.920 --> 00:23:26.480
are using band or the build because it has some
344
00:23:26.960 --> 00:23:30.400
powerful things like the macross that we like, and also
345
00:23:30.480 --> 00:23:33.640
we have some features that thanks to these macros.
346
00:23:35.000 --> 00:23:38.759
But then if us fund to build it, can you
347
00:23:38.880 --> 00:23:42.519
build it for Node and Dino as well without beat?
348
00:23:43.680 --> 00:23:49.599
Okay, yes, yes, yes, yes yeah, thanks to band, we
349
00:23:49.720 --> 00:23:54.319
can build it also for Note and also or we
350
00:23:54.480 --> 00:23:58.920
know we yeah, we are building. We are building from
351
00:23:59.119 --> 00:24:02.119
a four note and also doing some abstractions to work
352
00:24:02.279 --> 00:24:07.240
correctly with with you know, because we realize and also
353
00:24:07.359 --> 00:24:11.400
things to feedback from people that we should support more
354
00:24:11.960 --> 00:24:15.720
run times. And then we implemented Node and then finally
355
00:24:16.160 --> 00:24:19.920
Dinner and also for the one dot zero version we
356
00:24:20.000 --> 00:24:24.799
won't also improve the room time agnostic thing and also
357
00:24:24.880 --> 00:24:29.400
support some clouds that we are not supporting now and
358
00:24:30.440 --> 00:24:32.359
but this is a thing for the future.
359
00:24:33.200 --> 00:24:38.480
And then about the Android iOS or desktop thing. In reality,
360
00:24:38.599 --> 00:24:40.119
what we are doing here is to.
361
00:24:40.279 --> 00:24:46.519
Support to integrate everything with touri okay in a easy way,
362
00:24:46.839 --> 00:24:52.000
so that the developers with only one configuration can turn
363
00:24:52.359 --> 00:24:56.960
your web application to an Android or adios or desktop
364
00:24:57.400 --> 00:25:01.720
in easy way, and all these figuration is automatically by
365
00:25:01.759 --> 00:25:04.000
the CILII of RISA.
366
00:25:05.079 --> 00:25:15.119
Yeah, I'm trying to find a link to Towery. Mhmm,
367
00:25:15.880 -->
00:25:17.079
maybe I'm spelling it wrong.
368
00:25:20.400 --> 00:25:25.519
Yeah, it's always very powerful because it's a rast web
369
00:25:25.599 --> 00:25:28.039
built or for the best stop.
370
00:25:27.839 --> 00:25:33.839
Application, and it's much powerful for example that Electron because
371
00:25:33.880 --> 00:25:35.279
it's tiny and also.
372
00:25:38.039 --> 00:25:39.079
Mattering performance.
373
00:25:39.640 --> 00:25:44.319
Yeah, definitely, and I was spelling it wrong. It's it's
374
00:25:44.519 --> 00:25:46.799
t A U r I for the folks that are
375
00:25:46.839 --> 00:25:51.799
out there looking for it. Wait, some of these folks anyway,
376
00:25:52.079 --> 00:25:58.119
So yeah, cool stuff. So when it does the the
377
00:25:58.240 --> 00:26:02.039
build for the native apps for Android or iOS or
378
00:26:02.079 --> 00:26:05.559
the desktop, you said it's faster than Electron, But does
379
00:26:05.680 --> 00:26:09.359
it have a JavaScript run time in it? Is it
380
00:26:09.440 --> 00:26:12.359
kind of like Capacitor or something like that, or Cordova
381
00:26:13.279 --> 00:26:17.440
or is it more like React native or something like that.
382
00:26:21.319 --> 00:26:24.599
You can use native things thanks to Towery and Towery
383
00:26:25.279 --> 00:26:30.039
you can do some buildings and then you can write
384
00:26:30.720 --> 00:26:31.680
things in rest.
385
00:26:33.160 --> 00:26:33.319
All.
386
00:26:33.359 --> 00:26:37.079
The thing is documented very well in the Towery documentation.
387
00:26:38.839 --> 00:26:41.920
So yeah, in Brisa, the only thing that here we
388
00:26:42.000 --> 00:26:47.839
are doing is an integration that then the developers can
389
00:26:47.960 --> 00:26:49.400
use in an easy way for that.
390
00:26:50.480 --> 00:26:54.759
But all the things are very native and you can.
391
00:26:55.480 --> 00:27:01.680
Yeah, makes sense. So are people using this today for
392
00:27:01.799 --> 00:27:04.079
their applications? You said you're still working on it, but.
393
00:27:06.720 --> 00:27:07.799
Mm hmm. Yeah.
394
00:27:07.920 --> 00:27:10.240
Here one of the improvements that we want to do
395
00:27:10.599 --> 00:27:15.559
for Android or idios, uh that is on the roadmap
396
00:27:15.599 --> 00:27:21.599
of the one is to do two different builds, one
397
00:27:22.039 --> 00:27:24.960
for the server part and the other one for the
398
00:27:25.519 --> 00:27:30.279
execuitable not for the the Android rios, and then to
399
00:27:30.359 --> 00:27:32.839
be connected automatically for these server actions.
400
00:27:33.880 --> 00:27:39.440
And well, yes your questions.
401
00:27:39.559 --> 00:27:42.480
So my question is do you have people actually using
402
00:27:42.640 --> 00:27:44.440
prison now in production.
403
00:27:44.519 --> 00:27:49.480
Or uh huh. Yeah, now a few people it's using it.
404
00:27:49.640 --> 00:27:55.039
But for example Albert that is one of the contributors.
405
00:27:56.200 --> 00:27:59.799
He has his company that is a travel agency all
406
00:28:00.319 --> 00:28:02.680
with RISA, not only the public part, also the back
407
00:28:02.720 --> 00:28:11.119
office with RISA. And yeah, but as I comment, curdly
408
00:28:11.200 --> 00:28:16.759
is experimental preside zero dot and we put that we
409
00:28:17.000 --> 00:28:19.319
don't recommend to use it in production. But of course
410
00:28:19.400 --> 00:28:22.319
there are people that is using it, but almost all
411
00:28:22.359 --> 00:28:26.119
the people is just playing with with with with it.
412
00:28:26.480 --> 00:28:29.640
And also we are creating a great community in Discord.
413
00:28:29.920 --> 00:28:40.400
And there are some production projects, but I feel for now.
414
00:28:40.799 --> 00:28:44.160
That makes sense. So are you hoping that this, you know,
415
00:28:44.279 --> 00:28:46.839
eventually gets to one dot oh and people can use
416
00:28:46.880 --> 00:28:50.240
it in production? Or is this mostly an exercise to
417
00:28:50.400 --> 00:28:53.319
just learn how to build something like this? Or I mean,
418
00:28:53.359 --> 00:28:54.799
what are you hoping to get out of it in
419
00:28:54.880 --> 00:28:55.880
the at the end of the day.
420
00:29:01.559 --> 00:29:04.920
Are you asking about one to zero programs?
421
00:29:05.279 --> 00:29:06.839
No, I'll ask about that in a minute. What I'm
422
00:29:06.880 --> 00:29:10.000
asking about is where do you want this to take you?
423
00:29:10.480 --> 00:29:10.640
Right?
424
00:29:10.799 --> 00:29:14.359
So are you just trying to learn about how to
425
00:29:14.440 --> 00:29:18.440
build things like these frameworks or are you hoping to
426
00:29:18.480 --> 00:29:22.680
build a company around it? Or are you looking to Okay.
427
00:29:22.519 --> 00:29:23.559
Yeah, and I understand.
428
00:29:24.160 --> 00:29:27.160
Hey, I like to give conference talks about it, or
429
00:29:28.160 --> 00:29:30.759
you know, my company that I worked for needed it.
430
00:29:31.000 --> 00:29:33.119
So I just want to solve their problems. There are
431
00:29:33.119 --> 00:29:35.839
a million reasons to do them. A lot of times
432
00:29:37.039 --> 00:29:40.359
it's more than one, right, So yeah, I'm just curious.
433
00:29:42.599 --> 00:29:42.680
Now.
434
00:29:42.799 --> 00:29:45.559
And really one of the things is that all the
435
00:29:45.680 --> 00:29:49.319
projects on my side projects I wanted to are using
436
00:29:49.359 --> 00:29:52.799
this out. So my blog PA is with Riza, and
437
00:29:54.200 --> 00:29:56.079
all the side projects that I want to do with
438
00:29:56.279 --> 00:29:59.559
I want to do it with my own Okay, but
439
00:29:59.759 --> 00:30:04.079
I'll so at the beginning when I started. Also I
440
00:30:04.319 --> 00:30:08.799
liked the idea of learning by the way and and
441
00:30:08.920 --> 00:30:13.000
also the idea of contributing to the web a little
442
00:30:13.039 --> 00:30:15.880
bit better, so and bring my ideas and.
443
00:30:17.960 --> 00:30:20.960
I really did. This was the origin that why I
444
00:30:21.119 --> 00:30:23.920
started in order to to to build prison.
445
00:30:24.759 --> 00:30:26.400
Gotcha. So yeah, what is on that?
446
00:30:26.599 --> 00:30:27.680
Also? Go ahead?
447
00:30:28.720 --> 00:30:36.279
Mhm no, just to comment that also thanks to Mincos
448
00:30:36.720 --> 00:30:41.359
from from Angola and quick that he came to Barcelona
449
00:30:41.440 --> 00:30:45.359
two years ago and and I talked with with him,
450
00:30:45.400 --> 00:30:50.440
and I remember that he talked about week like his baby,
451
00:30:51.039 --> 00:30:54.640
with a lot of passions and all these feelings.
452
00:30:54.920 --> 00:30:59.960
Uh. And then I remember that just at this moment I.
453
00:31:01.240 --> 00:31:03.559
Cameto my mind. Oh, I would like it to be
454
00:31:03.680 --> 00:31:05.599
the framework, but it doesn't make sense to be the
455
00:31:05.680 --> 00:31:09.960
framework without Aroma. And then it's when I started to
456
00:31:10.839 --> 00:31:15.200
I tried the xtgs server actions and at the beginning
457
00:31:15.400 --> 00:31:17.599
was wow. I like the DA, I like the via
458
00:31:17.640 --> 00:31:21.599
of server actions and also devia of archademics, but I
459
00:31:21.680 --> 00:31:26.759
didn't like how ter reactions is implemented in XTES. And
460
00:31:26.839 --> 00:31:28.920
there are a lot of things that I think that
461
00:31:29.599 --> 00:31:34.119
should be better implemented, but it's with a different part
462
00:31:34.160 --> 00:31:37.240
of the part of time. So that I can't contribute
463
00:31:37.279 --> 00:31:41.799
to an XTGS, and then I started writing my ideas.
464
00:31:42.480 --> 00:31:44.000
I have to say, one of the things that I
465
00:31:44.079 --> 00:31:48.480
don't love about some of the things in next GS,
466
00:31:48.680 --> 00:31:52.200
like server actions, is that some of them are a
467
00:31:52.240 --> 00:31:55.920
little bit tricky to get running on your own. Just
468
00:31:56.000 --> 00:31:58.160
to give you an idea, So I like to deploy
469
00:31:58.279 --> 00:32:01.200
my own apps to my own server, and you know,
470
00:32:01.400 --> 00:32:03.359
kind of live in that space. And I know people
471
00:32:03.440 --> 00:32:05.519
think I'm crazy. It's like, just just deploy it to
472
00:32:05.640 --> 00:32:08.680
vercell or just put it on the cloud, but I
473
00:32:08.799 --> 00:32:10.480
want to set it up and run it, you know,
474
00:32:10.680 --> 00:32:13.640
on on doctor containers wherever I want it. And some
475
00:32:13.759 --> 00:32:17.119
of that stuff's just a little bit tricky to do
476
00:32:17.400 --> 00:32:21.920
without the cloud infrastructure that's offered by evercell or netlefi
477
00:32:22.079 --> 00:32:25.119
or something like that. And so that that's kind of
478
00:32:25.160 --> 00:32:27.559
my hang up, the idea that there's a framework out
479
00:32:27.599 --> 00:32:30.039
there that kind of has it
built in and I
480
00:32:30.119 --> 00:32:33.000
can just deploy however I want. I'm digging that. I
481
00:32:33.160 --> 00:32:37.279
like that a lot. What is the deployment story for Briza.
482
00:32:37.640 --> 00:32:43.400
Do you expect people to be using something like versell
483
00:32:43.759 --> 00:32:45.880
or can you deploy it on your own?
484
00:32:46.400 --> 00:32:46.799
Yeah, we.
485
00:32:48.759 --> 00:32:54.240
Have an adaptor for Burcel then Albert that it's a
486
00:32:54.359 --> 00:32:58.440
contributor that has his company with Briza, he is using
487
00:32:58.680 --> 00:33:03.160
a closer. However, we don't have the adapter of clothes
488
00:33:03.319 --> 00:33:08.680
or clover yet, so it's very working in progress. And
489
00:33:10.119 --> 00:33:13.559
also you can use a doctor file with.
490
00:33:13.759 --> 00:33:18.839
Ban or with not or, but for now the only
491
00:33:18.960 --> 00:33:23.000
cloud provider that we have some adapted it ourselves. But
492
00:33:23.799 --> 00:33:26.160
in reality and then it's used a server.
493
00:33:26.359 --> 00:33:34.359
So so I could go set up just a small
494
00:33:34.440 --> 00:33:38.599
droplet on digital or just say here's my code run
495
00:33:38.960 --> 00:33:40.599
and it'll it'll run just fine.
496
00:33:42.640 --> 00:33:46.960
Exactly. Or if you decide yes, or if you decide
497
00:33:47.000 --> 00:33:50.960
for example, the output as a static for example as
498
00:33:51.039 --> 00:33:54.720
my blog, then you can't build it in any city
499
00:33:54.799 --> 00:33:55.559
end for example.
500
00:33:56.240 --> 00:33:58.240
Yeah, I've seen that with a few of the other
501
00:33:58.319 --> 00:34:01.160
frameworks as well, where yeah people do that and then
502
00:34:01.160 --> 00:34:05.319
they deploy it like Amazon S three and then yeah
503
00:34:05.359 --> 00:34:06.960
they can put a web server in front of it
504
00:34:07.079 --> 00:34:13.800
really easily and then it just serves your stuff. So yeah,
505
00:34:15.400 --> 00:34:18.760
very cool. So what is on the roadmap for one zero?
506
00:34:19.400 --> 00:34:21.559
The most important part here is to be a stable.
507
00:34:22.039 --> 00:34:25.000
So now we are prioritizing all the issues that the
508
00:34:25.079 --> 00:34:32.679
community is founding. So for now we are growing the
509
00:34:32.760 --> 00:34:39.800
community and the goal is to to grow more.
510
00:34:39.920 --> 00:34:42.760
And also because we are interested that the people try
511
00:34:42.800 --> 00:34:45.960
it RISA and found issues in order to fix that,
512
00:34:46.840 --> 00:34:49.440
and probably this is the most important topic.
513
00:34:50.159 --> 00:34:52.920
But then also we have some dependency.
514
00:34:53.840 --> 00:34:58.559
For the navigation API that is experimental yet but it's
515
00:34:58.639 --> 00:35:02.480
in the interrupt of these year, so probably this year
516
00:35:02.639 --> 00:35:05.559
is going to be supported in all the browsers. And
517
00:35:06.039 --> 00:35:10.280
because for the single pet application approach, we are using
518
00:35:10.360 --> 00:35:16.159
it and we prefer to await in order to also
519
00:35:16.239 --> 00:35:21.159
be stable this and then in the roadmap, the need
520
00:35:21.239 --> 00:35:27.840
is to increase the adapters to be more room and
521
00:35:27.840 --> 00:35:29.960
diagnostics also and I'm more.
522
00:35:29.880 --> 00:35:33.360
Aligned to two clouds.
523
00:35:34.480 --> 00:35:39.440
Also we need to create a Netlify adapter the closer
524
00:35:39.599 --> 00:35:43.480
once and there are a lot of things to do
525
00:35:43.599 --> 00:35:44.400
in these terms.
526
00:35:45.400 --> 00:35:48.679
And then also for the components, what we want to
527
00:35:48.760 --> 00:35:50.559
do is UH is.
528
00:35:50.599 --> 00:35:55.400
Great mode like partial iteration, to that the developers can
529
00:35:55.480 --> 00:36:01.800
decide that for example that the components UH is iterated
530
00:36:03.039 --> 00:36:07.840
when it's visible for example or in elisible way, or
531
00:36:09.039 --> 00:36:15.559
or by the fault that it is the nature. Then
532
00:36:16.239 --> 00:36:19.800
also we want to support transitions that it is a
533
00:36:19.880 --> 00:36:23.519
proposal from the community, because one of the things that
534
00:36:23.599 --> 00:36:27.440
we did for this roadmap is we bring some ideas
535
00:36:28.239 --> 00:36:31.039
that we want to do it yes or yes, because
536
00:36:32.159 --> 00:36:36.159
at the beginning of the field roadmap, but we move
537
00:36:36.199 --> 00:36:39.400
it to the next one. And then we asked the
538
00:36:39.719 --> 00:36:45.480
community in discord and that they brought the proposals, et cetera.
539
00:36:46.239 --> 00:36:49.920
And also, for example, there is a good proposal to
540
00:36:51.320 --> 00:36:58.119
improve all the offline first things, and it's something very
541
00:36:58.159 --> 00:37:02.880
interesting that we want to implement also, and also in
542
00:37:03.000 --> 00:37:06.320
order to improve the developer experience, we also want to
543
00:37:06.559 --> 00:37:13.400
improve some the current playground because the current playground on
544
00:37:13.480 --> 00:37:18.159
the web site is working only for the components, but
545
00:37:19.519 --> 00:37:24.480
we can improve that because and then for the developers
546
00:37:24.519 --> 00:37:29.079
it's easy to play and see how it works. And
547
00:37:29.480 --> 00:37:34.320
also in increment the number of examples we have so
548
00:37:34.440 --> 00:37:36.639
examples that the developers can try it.
549
00:37:36.920 --> 00:37:38.440
But one also to.
550
00:37:38.880 --> 00:37:45.519
Improve and there are the most important part is to
551
00:37:45.559 --> 00:37:49.599
improve the harder loading that we have because now it's
552
00:37:49.639 --> 00:37:54.000
a little bit slow. It's fast because it's running with
553
00:37:54.159 --> 00:37:57.079
bang and
ban all the build process is very fast.
554
00:37:57.679 --> 00:38:01.519
But currently one of the problems is that instead of
555
00:38:02.400 --> 00:38:06.280
running only the files that change is building all the applications.
556
00:38:06.639 --> 00:38:11.440
Every time, and if you have a very big website,
557
00:38:12.280 --> 00:38:15.840
a web, a very big project, then unitize that it
558
00:38:15.920 --> 00:38:17.480
is a little bit slower.
559
00:38:18.039 --> 00:38:23.360
And yeah, but now thanks to Band, they are improving
560
00:38:23.480 --> 00:38:24.320
that and.
561
00:38:27.159 --> 00:38:34.480
Then implementing new APIs for watch files during this field process.
562
00:38:35.199 --> 00:38:39.119
And also they are building a BAKE that is a
563
00:38:39.360 --> 00:38:44.800
server framework of Band that improves a lot all these things,
564
00:38:44.840 --> 00:38:46.639
and we want to integrate all these things.
565
00:38:48.800 --> 00:38:52.079
Cool. Was there anything else that we should get into
566
00:38:52.280 --> 00:38:53.400
with Breeza.
567
00:38:57.840 --> 00:39:01.320
Well, when I recommend for the developers is to go
568
00:39:01.719 --> 00:39:05.119
to the website is up build and here we have
569
00:39:05.920 --> 00:39:09.960
examples that they can try in ex way, for example,
570
00:39:10.039 --> 00:39:10.760
how to use.
571
00:39:13.159 --> 00:39:20.920
Sexual light in a ster reactions. And also one of
572
00:39:21.000 --> 00:39:23.079
the things that we are supporting that I don't comment
573
00:39:23.239 --> 00:39:25.119
is generators.
574
00:39:25.360 --> 00:39:29.000
So in order to have more control about the streaming
575
00:39:29.079 --> 00:39:34.360
part you can we are supporting as in components but
576
00:39:34.559 --> 00:39:40.599
also as in generators, and then you can decide each chank.
577
00:39:42.039 --> 00:39:44.519
Of the streaming and this is powerful.
578
00:39:44.559 --> 00:39:47.719
For example with a secular light of Band that is returning,
579
00:39:48.599 --> 00:39:51.639
example for a list, it's returning in the streaming, so
580
00:39:51.800 --> 00:39:54.559
then you can render this list in the streaming.
581
00:39:57.079 --> 00:40:01.519
And also your de developers can drive a playground and
582
00:40:02.000 --> 00:40:03.239
play with is that?
583
00:40:04.480 --> 00:40:12.000
And maybe another topic, it's about international internationalization. Maybe you
584
00:40:12.039 --> 00:40:16.360
can talk about it because brizge supporting internationalization, but not
585
00:40:16.559 --> 00:40:20.800
all for the rotin part, so it's also supporting international
586
00:40:21.079 --> 00:40:26.239
internationalization in order to translate all the content of the BASAs.
587
00:40:27.360 --> 00:40:31.320
So what's different about your internationalization because I saw it
588
00:40:31.400 --> 00:40:35.280
on your website. But to be honest, and maybe this
589
00:40:35.480 --> 00:40:40.079
is a naive take
on things, but internationalization, I guess
590
00:40:40.119 --> 00:40:42.599
it depends on the app, right, because some apps it's like, look,
591
00:40:42.639 --> 00:40:45.840
I'm only building this for the US, I'm only building
592
00:40:45.880 --> 00:40:48.559
it for English speaking audiences, and so I don't do
593
00:40:48.679 --> 00:40:52.519
the internationalization. But if you're putting a product out there
594
00:40:52.559 --> 00:40:55.360
that could be used across the world or even you know,
595
00:40:55.840 --> 00:40:57.719
here in the US we have more and more people
596
00:40:57.800 --> 00:41:01.920
speaking Spanish, right your branch into Canada, you hit French
597
00:41:02.000 --> 00:41:04.440
pretty fast, right, So there are a lot of reasons
598
00:41:04.480 --> 00:41:06.320
to do it, But it seems like table stakes to me.
599
00:41:06.480 --> 00:41:10.079
For most of the apps that I'm building, it's like, Okay, well,
600
00:41:10.559 --> 00:41:12.880
I want this to work for English and Spanish speakers
601
00:41:12.880 --> 00:41:16.400
because they're in my market, right, and then as my
602
00:41:16.519 --> 00:41:19.800
market expands, I can add in internationalization. For the other stuff.
603
00:41:20.400 --> 00:41:22.679
So yeah, I guess I just kind of took it
604
00:41:22.760 --> 00:41:26.599
for granted. But yeah, why why are you making it
605
00:41:26.719 --> 00:41:29.519
first class? I guess is one question. And then the
606
00:41:29.639 --> 00:41:32.679
other question is, yeah, what what are you doing there
607
00:41:32.760 --> 00:41:34.760
that's different from maybe other things that I've seen?
608
00:41:37.519 --> 00:41:46.719
Okay, Yeah, Well, in international internationalization, the vaids to for
609
00:41:47.000 --> 00:41:48.239
for CEO.
610
00:41:48.360 --> 00:41:52.199
In order to improve it's important to provide a different
611
00:41:52.280 --> 00:41:56.360
en urils for each language you don't have, well, to
612
00:41:56.480 --> 00:41:59.719
have more content content in different languages, and then the
613
00:42:01.960 --> 00:42:07.199
Google and other searchers can get all the content in
614
00:42:07.320 --> 00:42:11.880
different in different bases. And then for all the routine
615
00:42:11.960 --> 00:42:19.039
we are supporting that exactly, the the isso and then
616
00:42:19.119 --> 00:42:24.079
the name of the page, and also you can't translate
617
00:42:24.159 --> 00:42:29.440
the page name. For example, in Spanish, about us can
618
00:42:29.519 --> 00:42:34.039
be translated to sobers that it's the same in Spanish.
619
00:42:34.960 --> 00:42:37.960
And you can define all these things in the Internal
620
00:42:38.159 --> 00:42:45.639
Internationalization configuration and then it's automatically handled for by BRIZA,
621
00:42:45.960 --> 00:42:51.480
so the developers don't need to do almost anything, so
622
00:42:51.599 --> 00:42:56.599
it's very easy to intepret it. Also, we are supporting
623
00:42:56.960 --> 00:43:00.480
a chair of lands, so if we know that page
624
00:43:00.920 --> 00:43:06.280
is supported in different languages, then to improve the CEO,
625
00:43:07.400 --> 00:43:09.559
we are supporting this tact and also.
626
00:43:09.440 --> 00:43:11.400
The lank attribute in the edgitment.
627
00:43:12.639 --> 00:43:15.400
This for one part that is all the routing part,
628
00:43:16.000 --> 00:43:20.960
and then for translations we are also supporting our implementation
629
00:43:21.119 --> 00:43:26.280
that it's a breach of the echmastry API the intel
630
00:43:27.280 --> 00:43:33.679
and I did it in this way because before doing Brizia,
631
00:43:35.239 --> 00:43:38.360
I have experienced with an open source library that is
632
00:43:38.480 --> 00:43:41.400
next time to late that it's the most use the
633
00:43:41.480 --> 00:43:42.599
library that I have.
634
00:43:42.840 --> 00:43:48.320
That it's internalization library for next years.
635
00:43:49.280 --> 00:43:52.559
And now CORD is used by a lot of people,
636
00:43:53.079 --> 00:43:58.079
so it has like eight eighty thousand dollars per week and.
637
00:44:00.679 --> 00:44:03.360
Have a lot of time of years now.
638
00:44:04.559 --> 00:44:10.199
And when I did this library for many yes, I
639
00:44:10.480 --> 00:44:13.360
see that there are a lot of things that I
640
00:44:13.480 --> 00:44:15.960
can do in the library because I don't have the
641
00:44:16.000 --> 00:44:21.800
control of the framework, and doing this integration directly on
642
00:44:21.960 --> 00:44:27.280
the framework, then it's much powerful for to do for
643
00:44:27.840 --> 00:44:32.840
the art lands, for translating the roots and.
644
00:44:36.719 --> 00:44:41.000
M and also then to bring on the client all.
645
00:44:40.960 --> 00:44:44.880
Of the keys and the cercies that we need to
646
00:44:46.079 --> 00:44:49.920
consuming the component for example, instead of all the dictionary
647
00:44:51.079 --> 00:44:56.239
and the code that is doing that. It's very funny,
648
00:44:56.400 --> 00:45:04.519
it's eight eight hundred bytes, so it's less than one
649
00:45:04.599 --> 00:45:08.440
killow white. And this is why we decided in order
650
00:45:08.559 --> 00:45:15.000
to build our translational scene would be very very tiny,
651
00:45:15.559 --> 00:45:16.519
and all the.
652
00:45:16.880 --> 00:45:17.960
Responsibilities like.
653
00:45:19.480 --> 00:45:25.440
Plualization, et cetera, and the responsibility to do that is
654
00:45:25.519 --> 00:45:26.880
the ex masculad.
655
00:45:27.239 --> 00:45:30.920
Cool, very cool. Yeah, I have to say so. Most
656
00:45:30.960 --> 00:45:35.000
of my development experiences, as most of the listeners already know,
657
00:45:35.719 --> 00:45:37.880
is in Ruby on rails and they have built in
658
00:45:38.559 --> 00:45:39.920
internationalization stuff.
659
00:45:40.000 --> 00:45:40.079
Right.
660
00:45:40.159 --> 00:45:42.880
You just provide the files that give
the translations and
661
00:45:42.920 --> 00:45:45.360
the keys, and it just does it. And it looks
662
00:45:45.400 --> 00:45:48.800
like most yours mostly works the same way. It's hey,
663
00:45:48.920 --> 00:45:51.599
you know this, this is the phrase for this, and
664
00:45:51.679 --> 00:45:55.920
then it just does the thing, which is which is
665
00:45:56.000 --> 00:45:56.559
super nice.
666
00:45:57.400 --> 00:45:59.280
M hm. Yeah.
667
00:45:59.719 --> 00:46:03.519
So you mentioned you did mention having a different u
668
00:46:03.599 --> 00:46:05.920
URL for the different languages. Do you just expect that
669
00:46:06.039 --> 00:46:10.400
in the Oh yeah, it looks like it's in the routing.
670
00:46:12.000 --> 00:46:15.079
You could also do like yeah, domain routing. Yeah, so
671
00:46:15.119 --> 00:46:16.920
it looks like you have all of that, and then
672
00:46:17.000 --> 00:46:22.239
it also does the automatic locale yes detection. And so
673
00:46:22.400 --> 00:46:25.199
if I've got mine my browsers set to US English,
674
00:46:26.480 --> 00:46:28.199
you know, or sometimes I get a wild hair and
675
00:46:28.239 --> 00:46:34.960
I'll do Italian because I speak and read Italian fluently. Right, Yeah,
676
00:46:35.039 --> 00:46:35.960
this is a lot of.
677
00:46:39.039 --> 00:46:41.800
H I mean if he's not if it's a language
678
00:46:41.800 --> 00:46:44.519
that is not supported, then it's logging the old.
679
00:46:44.440 --> 00:46:51.599
Which makes sense. So you mentioned that, you know in
680
00:46:51.679 --> 00:46:54.400
the documentation on here is it looks like it's pretty thorough,
681
00:46:56.480 --> 00:46:58.360
you know, And you've also mentioned that, Yeah, you do
682
00:46:58.480 --> 00:47:02.199
your blog, which is static, and then you know the
683
00:47:02.519 --> 00:47:04.599
other guy is using it for his travel agency, and
684
00:47:04.719 --> 00:47:09.039
so it's actually probably managing data and images and stuff
685
00:47:09.119 --> 00:47:13.239
for people who want to travel. Let's say I decide, okay,
686
00:47:13.280 --> 00:47:15.039
you know what, I'm going to go build something in
687
00:47:15.119 --> 00:47:20.440
Breza and just see how it goes. And I mean,
688
00:47:21.000 --> 00:47:23.480
where do I start? Do I just start with getting
689
00:47:23.559 --> 00:47:27.280
started on the documentation? Should I join Discord? Follow you
690
00:47:27.360 --> 00:47:29.199
on Twitter? Are there other places?
691
00:47:32.599 --> 00:47:35.719
Yeah? If you are to the get the start of
692
00:47:35.800 --> 00:47:38.760
the recommendation, you can see that it's only one comment,
693
00:47:39.480 --> 00:47:43.519
a comment that it's the band Great Prison, and then
694
00:47:43.559 --> 00:47:44.519
you kind of start.
695
00:47:44.960 --> 00:47:47.119
With so I have to use ban some project.
696
00:47:47.880 --> 00:47:51.639
But okay, yes, one of the things is that you
697
00:47:51.760 --> 00:47:55.880
need you need bud for all
the tooling part, and
698
00:47:56.719 --> 00:48:00.239
also you can go to the campos, and then you
699
00:48:00.320 --> 00:48:03.760
can try an example also with only one comment and
700
00:48:03.880 --> 00:48:07.519
you can say like band great prison, and then we
701
00:48:07.679 --> 00:48:10.880
have a flag that is an example, and then you
702
00:48:11.000 --> 00:48:13.159
can put the name of the example and unload.
703
00:48:13.239 --> 00:48:15.920
It makes sense.
704
00:48:17.119 --> 00:48:21.119
And also also we invite the people also to join
705
00:48:21.239 --> 00:48:27.159
to discord and any do anything.
706
00:48:27.639 --> 00:48:32.000
You you can talk on the on the general channel
707
00:48:32.119 --> 00:48:38.280
and we are mum hm, well, we are responding very fast.
708
00:48:38.599 --> 00:48:43.880
And also we like uh in the interaction and feedback there,
709
00:48:44.039 --> 00:48:45.199
so feel free.
710
00:48:45.320 --> 00:48:50.320
Good deal. I don't know if I have anything else.
711
00:48:52.119 --> 00:48:53.719
Was was there anything else that you wanted to hit
712
00:48:53.800 --> 00:48:55.639
or should we just move on to the last part
713
00:48:55.679 --> 00:48:56.159
of the program.
714
00:48:59.800 --> 00:49:05.679
I think we talked a little bit about everything. Of course,
715
00:49:05.719 --> 00:49:08.039
there are a lot of topics and there are a
716
00:49:08.079 --> 00:49:10.480
lot of topics that we didn't talk about it. But
717
00:49:11.199 --> 00:49:17.280
for example, about the layout, all the structure of the pages,
718
00:49:17.960 --> 00:49:20.920
and I want to comment that it's very inspired with
719
00:49:21.119 --> 00:49:27.000
nextges and the pages folder. So it's how we are
720
00:49:27.159 --> 00:49:32.960
defining the pages. And then also we are supporting more
721
00:49:33.079 --> 00:49:38.280
things like suspense or UH an error not if you
722
00:49:38.400 --> 00:49:41.480
have some error on the server component.
723
00:49:41.599 --> 00:49:44.920
It's it's implemented in a different way than Next years.
724
00:49:45.000 --> 00:49:48.719
Because why in React, because it's not boundary that it's
725
00:49:48.800 --> 00:49:53.400
not a ropper. It's like different phases that the component has.
726
00:49:53.920 --> 00:49:57.960
So for example, there're sin component has like appending the
727
00:49:58.039 --> 00:50:02.960
state that this is bands and then this error and
728
00:50:03.119 --> 00:50:05.639
in order to define them. It's a little bit different
729
00:50:05.760 --> 00:50:10.920
than than React. Also, we are supporting mid al ware
730
00:50:11.800 --> 00:50:16.920
web sockets, so we are supporting a lot of topics.
731
00:50:17.519 --> 00:50:21.599
But what I invite the developers is to go to
732
00:50:21.679 --> 00:50:30.400
the documentation ry. It alsopp forestyles we are supporting ah uh.
733
00:50:31.000 --> 00:50:33.360
Also tail wind. We have an adapter for for tail
734
00:50:33.360 --> 00:50:37.800
wind and also another adapter for the CCS. Also you
735
00:50:37.880 --> 00:50:41.199
can use ccs in a normal way. Also we are
736
00:50:41.199 --> 00:50:49.679
supporting CCS models and well but yeah, I invite the
737
00:50:49.760 --> 00:50:52.719
people in order to try it, and yeah.
738
00:50:53.079 --> 00:50:57.239
Very cool. All right, Well, the last part of our
739
00:50:57.280 --> 00:51:02.079
program is picks and picks are just shout outs. It's
740
00:51:02.119 --> 00:51:04.599
an idea I actually stole from a podcast I don't
741
00:51:04.599 --> 00:51:09.760
listen to anymore twit dot TV. I'm not going to
742
00:51:09.800 --> 00:51:12.960
go into why I stopped listening to them, but I
743
00:51:13.159 --> 00:51:16.800
like the idea, so I borrowed it. Incidentally, I'm looking
744
00:51:16.800 --> 00:51:19.039
at borrowing some other ideas from another show I'm listening
745
00:51:19.079 --> 00:51:22.199
to now. But picks is just shout outs about stuff
746
00:51:22.239 --> 00:51:24.880
that you like. So a lot of times people do
747
00:51:27.239 --> 00:51:30.280
like I do board games every time, right, so I'll
748
00:51:30.320 --> 00:51:33.880
do a shout out about a board game, and then
749
00:51:35.639 --> 00:51:39.400
but people do TV shows, they'll do technology stuff too, right,
750
00:51:39.480 --> 00:51:42.239
so they'll pick, Hey, I really like these computers, or
751
00:51:42.280 --> 00:51:45.559
I really like this library or whatever. So I'll go
752
00:51:45.599 --> 00:51:47.079
ahead and do my picks, and then you can go
753
00:51:47.119 --> 00:51:49.199
ahead and throw in anything that you want to make
754
00:51:49.239 --> 00:51:54.119
sure people check out. So my first pick is a
755
00:51:54.159 --> 00:51:58.800
board game. What we played last week with my buddies
756
00:51:59.000 --> 00:52:01.679
was Heat, and I've picked before, but Heat is a
757
00:52:01.800 --> 00:52:05.800
car racing board game. I'm not going to go into
758
00:52:05.840 --> 00:52:11.400
all the details, but the main component of it is
759
00:52:12.400 --> 00:52:16.400
that you're trying to get You're trying to win the race,
760
00:52:17.079 --> 00:52:20.559
and so whoever gets the furthest past the finish line
761
00:52:20.679 --> 00:52:26.480
on the last turn wins. And I guess there's a
762
00:52:26.559 --> 00:52:30.079
campaign mode that I haven't played, where you do multiple
763
00:52:30.239 --> 00:52:33.360
races and then you know, as you win the different races,
764
00:52:33.400 --> 00:52:36.960
you actually get winning money that you can spend to
765
00:52:37.079 --> 00:52:41.480
upgrade your car. But the trick of the game is
766
00:52:41.679 --> 00:52:48.320
that you have heat in your engine, and if you overheat,
767
00:52:48.480 --> 00:52:53.079
then your car spins out and you you have to
768
00:52:53.119 --> 00:52:58.400
go back. And so typically what it is is that
769
00:52:58.519 --> 00:53:00.719
you're taking a turn and then there's
a speed limit
770
00:53:00.800 --> 00:53:04.000
on the turn, and so if you move too many spaces,
771
00:53:04.320 --> 00:53:07.320
every space you move past the speed limit on that turn,
772
00:53:07.920 --> 00:53:13.559
you take heat into your playpile, into your discard pile actually,
773
00:53:14.280 --> 00:53:16.440
and so then you shuffle your discard pile and you
774
00:53:16.480 --> 00:53:18.239
have all that heat. But if you run out of heat,
775
00:53:18.280 --> 00:53:20.800
you can't take any more heat out of your engine
776
00:53:20.920 --> 00:53:23.960
into your hand, into your deck, then you spin out
777
00:53:24.000 --> 00:53:26.519
and you go back to a line on the curve
778
00:53:27.199 --> 00:53:30.119
and so and then you have to still pass it
779
00:53:30.880 --> 00:53:34.360
with that speed limit. And so the trick is is
780
00:53:34.440 --> 00:53:37.239
getting as far around that curve and then managing the
781
00:53:37.360 --> 00:53:40.760
heat as you go through the next two or three curves. Right,
782
00:53:41.920 --> 00:53:44.039
most of them have a long stretch where you can
783
00:53:44.920 --> 00:53:46.840
you know, you can do some things to recover heat,
784
00:53:46.960 --> 00:53:50.079
or sometimes you can do other things to recover heat. Anyway,
785
00:53:50.719 --> 00:53:53.119
and you know there's some variability in your speed and
786
00:53:53.159 --> 00:53:56.400
stuff like that. There are cards that make it a
787
00:53:56.400 --> 00:53:59.400
little more randomized. You're not always playing numbers that you picked.
788
00:54:00.079 --> 00:54:04.719
But anyway, it's a super fun game. I think we
789
00:54:04.800 --> 00:54:07.039
played it in about forty five minutes to an hour.
790
00:54:07.079 --> 00:54:10.760
There were five of us, and so yeah, I'm going
791
00:54:10.800 --> 00:54:16.800
to pick Heat and then yeah, as far as other
792
00:54:16.880 --> 00:54:20.559
things go, I figured out that nineteen twenty three is back.
793
00:54:21.400 --> 00:54:24.000
So that's one of the Yellowstone spin off TV shows.
794
00:54:24.920 --> 00:54:28.719
It's got Harrison Ford and Helen Mirren in it. I
795
00:54:28.840 --> 00:54:31.119
don't know that any of the other actors or actresses
796
00:54:31.239 --> 00:54:32.760
or people that I could just name off the top
797
00:54:32.840 --> 00:54:35.079
of my head that oh they were in this thing
798
00:54:35.119 --> 00:54:38.039
that I also really liked, but it's it's a really
799
00:54:38.079 --> 00:54:41.440
good show. A little bit of a warning there's some
800
00:54:41.679 --> 00:54:46.559
nudity and some language that said. Another pick if you're
801
00:54:47.400 --> 00:54:49.800
if you want to wait for that kind of thing
802
00:54:49.880 --> 00:54:52.679
to be taken out is vid Angel, and so you
803
00:54:52.760 --> 00:54:56.599
can go sign up for vid Angel. Aroll is in Spain.
804
00:54:56.719 --> 00:54:58.400
I don't know if they offer it in Spain. I
805
00:54:58.480 --> 00:55:00.639
know they offer it in the United States. They're actually
806
00:55:00.760 --> 00:55:03.599
based here in Provo, which is not too far from me.
807
00:55:04.280 --> 00:55:06.280
But what they do is is you can load it
808
00:55:06.360 --> 00:55:09.559
up works with Amazon Prime, and then I think if
809
00:55:09.639 --> 00:55:15.360
you have your other subscriptions for like HBO or Paramount
810
00:55:15.400 --> 00:55:18.719
plus or whatever on Amazon Prime then you can watch
811
00:55:18.760 --> 00:55:21.760
some of those shows. Also works with Netflix, and the
812
00:55:21.840 --> 00:55:23.719
way that they do it is they actually have people
813
00:55:23.760 --> 00:55:27.679
who don't mind the language and the nudity and the
814
00:55:27.800 --> 00:55:30.800
sex and whatever else you want taken out, and they're
815
00:55:30.800 --> 00:55:32.760
pretty thorough Like. There's a lot of stuff that when
816
00:55:32.800 --> 00:55:35.239
my wife and I watch we turn it back on.
817
00:55:35.440 --> 00:55:39.000
It's like, Okay, you know, that guy gets shot with
818
00:55:39.159 --> 00:55:42.599
a gun, but you know, it's not super gory. We're
819
00:55:42.639 --> 00:55:44.559
not seeing anything that we don't want to see, so
820
00:55:44.599 --> 00:55:46.960
it'll turn it back on. Right. Some of the language
821
00:55:46.960 --> 00:55:48.840
doesn't bother us, but some of the other language does.
822
00:55:49.079 --> 00:55:51.000
Especially my wife, she's a lot more sensitive to it
823
00:55:51.039 --> 00:55:53.760
than I am. Right, And so we'll we'll say not
824
00:55:53.880 --> 00:55:55.880
these words, but those words, right, and so your sound
825
00:55:55.880 --> 00:55:58.920
will cut out when they say the word, you know,
826
00:55:59.119 --> 00:56:02.639
and it will skip the parts that have the nudity
827
00:56:02.719 --> 00:56:05.599
and sex in it. And so if anything else happens
828
00:56:05.679 --> 00:56:08.039
while that's going on, yeah, you might miss some stuff,
829
00:56:08.079 --> 00:56:12.880
but I haven't found that it really affects the quality
830
00:56:12.920 --> 00:56:15.360
of what we're watching. So anyway, but if you want
831
00:56:15.360 --> 00:56:20.159
to watch nineteen twenty three, I'm enjoying that, I'm also
832
00:56:20.280 --> 00:56:24.840
watching the new season of Reacher. Usually I wait and
833
00:56:24.880 --> 00:56:26.519
I pingj them, and this time I didn't, so I've
834
00:56:26.559 --> 00:56:29.320
been waiting for episodes to come out, which is strange.
835
00:56:29.360 --> 00:56:32.440
But anyway, so those are my picks. And then finally
836
00:56:32.519 --> 00:56:36.719
my final pick is I just got hired new job
837
00:56:37.559 --> 00:56:41.679
at Prize Picks and so they sent me a big
838
00:56:42.440 --> 00:56:45.519
box of swag and so I got a water bottle.
839
00:56:45.719 --> 00:56:47.760
I'm holding it up if you're not watching the camera.
840
00:56:49.119 --> 00:56:51.960
I got some stickers, I got
a backpack, I got
841
00:56:52.039 --> 00:56:55.480
a T shirt. They're going to be shipping me a
842
00:56:55.559 --> 00:56:58.280
laptop to work on, but I'm pretty excited to be
843
00:56:58.360 --> 00:57:01.159
working on that stuff. So as we dive into that,
844
00:57:01.320 --> 00:57:05.679
I will get you more stuff that you know, let
845
00:57:05.760 --> 00:57:07.760
you know what I'm working on. But anyway, those are
846
00:57:07.800 --> 00:57:09.719
my picks. A roll. What are your picks?
847
00:57:11.239 --> 00:57:17.400
Okay? Cool? Okay? My are a little bit different. I
848
00:57:17.559 --> 00:57:23.320
recommend a book that for me change my life. That
849
00:57:23.559 --> 00:57:29.119
is why we sleep and it's very important to know
850
00:57:29.599 --> 00:57:33.840
how we are working and how the sleeps works.
851
00:57:33.920 --> 00:57:40.199
And it's from Matti Walker, and I recommend it and
852
00:57:41.760 --> 00:57:47.519
it's a very important topic. I had problems of sleep
853
00:57:47.599 --> 00:57:52.800
on the past, and I recommend that when for for
854
00:57:53.119 --> 00:57:57.360
every everyone in reality, but also for developers, sometimes we
855
00:57:57.480 --> 00:57:59.039
are thinking.
856
00:57:58.800 --> 00:58:05.079
That we to spend more time on the night with
857
00:58:06.000 --> 00:58:11.000
with a code and then but really is better to stop.
858
00:58:11.920 --> 00:58:16.079
I have a pettyquot routine and this is much powerful
859
00:58:16.199 --> 00:58:20.239
then and at them. So I recommend this book while
860
00:58:20.280 --> 00:58:26.760
we live. And also another topic is a sport. I
861
00:58:27.239 --> 00:58:32.119
recommend to do any sport for everyone. In my case,
862
00:58:32.280 --> 00:58:35.960
I practice parkour for a lot of years, more than twenty.
863
00:58:37.320 --> 00:58:43.920
Yeah, and it's very important to do some sport because.
864
00:58:44.199 --> 00:58:47.000
It's like doing decisions every in every moment you no
865
00:58:47.199 --> 00:58:49.840
and and also then you are focused.
866
00:58:50.079 --> 00:58:56.000
On the current moment. And when you are training some
867
00:58:56.440 --> 00:59:01.039
sport then also brings a lot of power for a
868
00:59:01.119 --> 00:59:06.480
different analysis than or when you're programming. Then it's.
869
00:59:09.119 --> 00:59:12.719
Then very similar because when you're programming, you are taking
870
00:59:12.800 --> 00:59:17.679
decisions every time, and it's a very good way in
871
00:59:17.800 --> 00:59:20.880
order to brain this in a different way, and it's
872
00:59:21.000 --> 00:59:24.679
very positive and I recommend the people to do some
873
00:59:25.519 --> 00:59:26.719
sport very cool.
874
00:59:26.920 --> 00:59:30.559
I have a question about that. I mean I I
875
00:59:31.599 --> 00:59:37.280
do triathlons and marathons, but my question about parkour in
876
00:59:37.360 --> 00:59:41.639
particular is if somebody goes, you know, I've seen videos
877
00:59:41.679 --> 00:59:45.679
of parkour or you know, you know TikTok videos or
878
00:59:45.719 --> 00:59:48.519
something right where somebody's jumping off of something or kicking
879
00:59:48.599 --> 00:59:51.519
off of something or you know, doing a flip downstairs
880
00:59:51.639 --> 00:59:55.360
or something like that. How do people get into parkour? Like,
881
00:59:55.440 --> 00:59:59.559
are there good resources for people to okay, here, here's
882
00:59:59.679 --> 01:00:03.239
baby parkour, here's you know, okay, now you're not going
883
01:00:03.320 --> 01:00:06.079
to hurt yourself parkour, and then here's the risky parkoer.
884
01:00:09.239 --> 01:00:10.639
Yeah, career is very.
885
01:00:12.440 --> 01:00:16.400
Different way in order to join that years ago because
886
01:00:16.480 --> 01:00:20.480
years ago was like a new thing. But now there
887
01:00:20.519 --> 01:00:27.599
are schools academies in almost each city that you can
888
01:00:27.800 --> 01:00:30.480
learn all the things in with crush mats in a
889
01:00:30.599 --> 01:00:35.599
soft environment. And the most important part of parkour is
890
01:00:35.679 --> 01:00:41.159
that you know your limits and all the decisions should
891
01:00:41.239 --> 01:00:45.639
be how you feel. If, for example, you have a
892
01:00:45.719 --> 01:00:50.119
bad day, you are the responsible to the side if
893
01:00:50.719 --> 01:00:56.679
not to the jump today, not because it's not like
894
01:00:56.880 --> 01:01:00.480
competition with other people. That also is an other topic
895
01:01:00.559 --> 01:01:05.480
because now exists competition in parkor. But for me, par
896
01:01:05.719 --> 01:01:10.280
the most important parties to train to ourselves and to
897
01:01:10.480 --> 01:01:15.039
know your limits. And I recommend to be very progressive
898
01:01:15.360 --> 01:01:21.480
in these terms. So to start in without hate, and
899
01:01:23.199 --> 01:01:26.960
and then uh, step by a step you are learning.
900
01:01:27.199 --> 01:01:31.519
So like programming, you you are not going to start
901
01:01:31.639 --> 01:01:35.119
building a framework. You start step by a step and
902
01:01:35.280 --> 01:01:39.559
then uh you're after some years, then you can do
903
01:01:40.960 --> 01:01:41.800
more complex things.
904
01:01:41.880 --> 01:01:44.239
I guess, I guess what I'm asking for is is
905
01:01:44.280 --> 01:01:46.800
there like a tutorial you like out there that says,
906
01:01:47.159 --> 01:01:50.519
here are the basics of how to do parkour.
907
01:01:54.280 --> 01:01:57.760
There are some web pages that there are the technique,
908
01:01:57.880 --> 01:02:03.039
the techniques, and the most important part is how to
909
01:02:04.159 --> 01:02:09.440
d and now how to learn correctly without impact and
910
01:02:09.960 --> 01:02:11.760
and then to learn the basics.
911
01:02:13.760 --> 01:02:18.679
Cool? Yeah, all right, well I'll just go on YouTube
912
01:02:18.719 --> 01:02:24.679
and how
to land without hurting myself? Cool? What else
913
01:02:24.719 --> 01:02:25.360
are you going to pick?
914
01:02:26.039 --> 01:02:31.519
Absolutely? If you if you serve my name at Rocca h,
915
01:02:32.000 --> 01:02:35.760
you can't found the both topics about programming or about
916
01:02:35.920 --> 01:02:39.920
Parker in YouTube for example, my channel a Rocca it's
917
01:02:40.039 --> 01:02:40.639
about Parkle.
918
01:02:41.559 --> 01:02:44.440
But then in Twitter everything is about programming. So it's
919
01:02:44.519 --> 01:02:47.679
like two different walls. So it's it's like Britain not
920
01:02:47.760 --> 01:02:51.760
that have the server wall and the playing walls. But
921
01:02:52.079 --> 01:02:54.440
but yeah, two different topics.
922
01:02:54.719 --> 01:02:56.360
Very cool. You were going to pick something else? I think,
923
01:02:56.360 --> 01:02:57.119
and I interrupted you.
924
01:02:59.880 --> 01:03:04.199
I wanted to recommend a movie that I like it
925
01:03:04.360 --> 01:03:12.159
that it's Life is Beautiful and in Spanish is laveds Vedia.
926
01:03:13.119 --> 01:03:17.079
I watch it three times or four, I think, and.
927
01:03:19.159 --> 01:03:26.280
It's it's like the interpretation of it's there are something
928
01:03:26.360 --> 01:03:31.320
that is wrong, and you can interpret in a different way.
929
01:03:33.800 --> 01:03:39.719
To at least enjoy and be frustrated. And I like
930
01:03:40.000 --> 01:03:40.440
the movie.
931
01:03:40.599 --> 01:03:44.039
And I love that movie Lavi te Bella in Italian.
932
01:03:44.719 --> 01:03:47.800
And so the first part of the movie, they're not
933
01:03:48.119 --> 01:03:53.239
in the the concentration camp. They're in the city. And
934
01:03:53.800 --> 01:03:55.599
the city that they're in is all right, so and
935
01:03:55.679 --> 01:03:58.840
I lived there for five months, and so it's it's
936
01:03:59.000 --> 01:04:01.480
fun to watch the movie and go, yeah, I've been
937
01:04:01.639 --> 01:04:04.039
up that street and I've you know, I've been there
938
01:04:04.159 --> 01:04:07.800
and I've yeah. Anyway, but it's a tremendously good movie.
939
01:04:09.960 --> 01:04:13.280
It's it's a sad movie, but it's it's also a
940
01:04:13.360 --> 01:04:14.760
fun and it's a very good movie.
941
01:04:16.000 --> 01:04:19.159
Yeah, it's sad, but turns meet a lot. Yeah.
942
01:04:19.920 --> 01:04:23.320
Cool. Well you mentioned the discord. You mentioned Twitter. How
943
01:04:23.639 --> 01:04:26.079
do people find you on the internet.
944
01:04:27.239 --> 01:04:31.239
Yeah, in internet, you can find me in Twitter or
945
01:04:31.719 --> 01:04:37.840
inniches with al Raca, and then you can find Briza
946
01:04:38.880 --> 01:04:42.559
with brizea dot build. That is the website, and in
947
01:04:42.639 --> 01:04:47.360
the website we have all the links from Discord and everything.
948
01:04:47.400 --> 01:04:49.159
Yeah, I was going to say the Discord is easiest
949
01:04:49.159 --> 01:04:50.800
to find just by going to the website and clicking
950
01:04:50.840 --> 01:04:51.119
the link.
951
01:04:53.440 --> 01:04:58.360
Yes, and if not, Brizilt build live Discord and we
952
01:04:58.480 --> 01:04:59.760
have a cool.
953
01:05:00.119 --> 01:05:02.599
We'll go ahead and wrap it up. Thanks for coming.
954
01:05:02.639 --> 01:05:03.400
This was a lot of fun.
955
01:05:03.840 --> 01:05:05.039
Thanks for you learnt