UTSKRIFT 🔗
WEBVTT
1
00:00:04.679 --> 00:00:08.400
Hey, welcome back to another episode of the Ruby Rogues podcast.
2
00:00:08.720 --> 00:00:11.279
This week, on our panel, we have a Yushwatya.
3
00:00:11.759 --> 00:00:12.480
Hello. Hello.
4
00:00:13.160 --> 00:00:15.720
I'm Charles Maxwood from Top End Devs. Man, it feels
5
00:00:15.759 --> 00:00:17.399
like it's been a while since we've recorded one of
6
00:00:17.440 --> 00:00:17.839
these dozen.
7
00:00:18.960 --> 00:00:23.519
Yeah, it's been a few months. Yeah, at times, just
8
00:00:23.640 --> 00:00:27.879
been flying for me. So it's all gone back quite quickly.
9
00:00:27.920 --> 00:00:28.960
But it's nice to be back.
10
00:00:29.800 --> 00:00:33.280
Yeah, definitely. For those of you who are listening and going,
11
00:00:33.320 --> 00:00:35.920
didn't you release one like last week or the week before, Well,
12
00:00:35.920 --> 00:00:37.439
there were a few things that happened. I'm just going
13
00:00:37.520 --> 00:00:39.640
to fill you all in. I don't know if you
14
00:00:39.679 --> 00:00:41.799
need all the insight baseball, but it's interesting, and then
15
00:00:41.799 --> 00:00:45.799
I'll introduce our guests. I wound up getting a job
16
00:00:45.799 --> 00:00:49.560
at Price Picks at the end of March. I also
17
00:00:49.759 --> 00:00:52.240
hired my daughter to be putting the episodes out and
18
00:00:52.399 --> 00:00:54.920
she didn't and so I fired her. I had to
19
00:00:54.920 --> 00:01:00.000
fire my own kid, and so Jib who's our editor,
20
00:01:00.320 --> 00:01:04.439
took over posting the shows, and so he went and
21
00:01:04.519 --> 00:01:06.599
found all the ones that hadn't been posted and started
22
00:01:06.599 --> 00:01:09.040
posting him again. So the gap that you all, as
23
00:01:09.120 --> 00:01:13.040
listeners saw was probably back in like April. Right, there
24
00:01:13.359 --> 00:01:15.480
was like a month in March or April that you
25
00:01:15.519 --> 00:01:19.480
didn't see episodes. So you're getting episodes that we recorded
26
00:01:19.519 --> 00:01:24.200
a month or two or three ago, and now we're
27
00:01:24.239 --> 00:01:28.000
kind of back at it and recording episodes again. So anyway,
28
00:01:28.040 --> 00:01:31.239
your gap is different from ours. So but it feels
29
00:01:31.239 --> 00:01:32.920
so good to just get back and talk about the
30
00:01:32.959 --> 00:01:36.319
stuff we love. And we've got two terrific guys who
31
00:01:36.359 --> 00:01:38.760
were here who are working on a very interesting project.
32
00:01:39.439 --> 00:01:46.200
We have Adrianne Poli and Mark and Marco Roth.
33
00:01:47.359 --> 00:01:49.239
Hey, thanks for having us.
34
00:01:50.200 --> 00:01:54.560
Yeah, absolutely, and yeah, I think I'm the only one
35
00:01:54.599 --> 00:01:57.680
of you guys that's not in Europe, so thanks for
36
00:01:57.719 --> 00:02:00.000
coming in the evening or afternoon whenever it is there.
37
00:02:00.840 --> 00:02:04.519
Uh yeah, So I reached out because I ran across
38
00:02:04.560 --> 00:02:08.800
a really interesting project. It's it's Ruby video or Ruby
39
00:02:08.879 --> 00:02:12.599
videos dot dev, which one is it.
40
00:02:12.599 --> 00:02:17.599
It started as a Ruby video and uh, like two
41
00:02:17.639 --> 00:02:23.199
months ago we decided to rebrand it for a bigger
42
00:02:23.240 --> 00:02:29.599
picture on the under the Ruby events dot org. The
43
00:02:29.680 --> 00:02:34.039
project has more ambitions, but we can dive a bit
44
00:02:34.080 --> 00:02:38.360
more into the details and that's later on.
45
00:02:39.240 --> 00:02:42.879
Yeah, makes sense. So when you started, I'm kind of
46
00:02:42.919 --> 00:02:49.439
curious what what was the vision I was?
47
00:02:50.159 --> 00:02:55.479
It was several things occurred at the same time. First,
48
00:02:55.520 --> 00:02:59.400
I visited a similar project in the Python world that
49
00:02:59.599 --> 00:03:03.560
is called the t Video or something like this, which
50
00:03:03.599 --> 00:03:09.919
is a website that indexes something like fifteen thousand Ruby
51
00:03:10.919 --> 00:03:14.840
Python videos of conference and so on. And I was
52
00:03:14.879 --> 00:03:19.280
looking at something similar in the Ruby industry and I
53
00:03:19.360 --> 00:03:22.560
couldn't find anything. Of course, you can always go to
54
00:03:23.560 --> 00:03:28.000
YouTube or Google search and search for whatever things you need,
55
00:03:28.000 --> 00:03:31.479
but I couldn't find a single place where you could
56
00:03:31.520 --> 00:03:38.000
search for a specific topics and get all the conference
57
00:03:38.360 --> 00:03:44.080
on that particular topic in the Ruby industry. So at
58
00:03:44.080 --> 00:03:49.360
that time, I also I was interested to test several
59
00:03:49.439 --> 00:03:53.759
things that were coming out that there was come out.
60
00:03:54.479 --> 00:03:58.919
There was this Esclie trends, and I wanted to build something.
61
00:03:58.919 --> 00:04:04.360
So I started to build a small website that started
62
00:04:04.439 --> 00:04:09.800
with I think eight hundred videos, mostly rails cones, Ruby
63
00:04:09.879 --> 00:04:13.560
coones and so on. That was the proof of concept,
64
00:04:13.560 --> 00:04:17.240
the first proof of concept so largely inspired by a
65
00:04:17.240 --> 00:04:22.680
Byton video, and it had a bit of traction at
66
00:04:22.680 --> 00:04:28.639
the beginning. When it was announced. Of course, it was
67
00:04:29.360 --> 00:04:35.639
open source, and very quickly Marco joined the venture and
68
00:04:35.800 --> 00:04:46.600
came Marco was also maintaining Ruby Conference. If you want
69
00:04:46.639 --> 00:04:48.600
to add more details on this, maybe Marco.
70
00:04:49.680 --> 00:04:52.759
Yeah, so I was maintaining Ruby Conferences dot org, which
71
00:04:52.879 --> 00:04:55.279
used to be this simple website where you can add
72
00:04:55.519 --> 00:04:58.079
o where you can see all the confidences are
Load full transcript
happening
73
00:04:58.079 --> 00:04:58.839
in the Ruby world.
74
00:04:59.240 --> 00:05:02.399
I use all the time. By the way, it's like
75
00:05:02.800 --> 00:05:05.199
what's coming up and where can I submit calls for
76
00:05:05.240 --> 00:05:07.079
proposals and stuff? So yeah, thanks for that.
77
00:05:08.079 --> 00:05:11.079
Yeah, that's that's been like going for a long time.
78
00:05:11.240 --> 00:05:14.120
It's I have been just trying to bring in the
79
00:05:14.240 --> 00:05:16.480
up to date and kind of kept adding these new
80
00:05:16.480 --> 00:05:20.319
events that I saw coming on. But then I realized
81
00:05:20.360 --> 00:05:23.360
that they also had like video links to YouTube playlists
82
00:05:23.360 --> 00:05:27.680
and all these other like topics they had on the website.
83
00:05:28.199 --> 00:05:30.319
And then we decided to add meetups, and then we
84
00:05:30.319 --> 00:05:33.240
were like, yeah, let's maybe redesign this webpage because it
85
00:05:33.240 --> 00:05:36.199
does look dated in a way, so you wanted to
86
00:05:36.279 --> 00:05:40.519
kind of add more features to it. But it kept
87
00:05:40.600 --> 00:05:44.160
kind of like his ideas kept growing and they couldn't
88
00:05:44.240 --> 00:05:46.399
really find a good way to make it happen on
89
00:05:46.439 --> 00:05:50.519
this checker website. And at the same time, then Ruby
90
00:05:50.600 --> 00:05:53.439
video came around and it was like, Oh, actually, this
91
00:05:53.600 --> 00:05:56.079
is very much like what I kind of hadn't visioned
92
00:05:56.120 --> 00:05:59.079
for Ruby Conviences to be. That's why I decided to
93
00:05:59.120 --> 00:06:01.519
kind of join forces with oddly On to kind of
94
00:06:01.720 --> 00:06:05.759
make this one website or kind of contribute to Ruby
95
00:06:05.839 --> 00:06:08.680
Video to make this the thing that I wanted Ruby
96
00:06:08.759 --> 00:06:11.720
Confidence to be. And that's kind of what ties into
97
00:06:11.800 --> 00:06:14.199
this rebranded bed a few months ago, where you want
98
00:06:14.240 --> 00:06:18.160
to bring these two websites together as one. This is
99
00:06:18.160 --> 00:06:20.759
going to be Ruby events dot org and that's in
100
00:06:20.759 --> 00:06:23.439
the future where you will find all the upcoming events,
101
00:06:23.519 --> 00:06:27.040
previous events, and even if you're at the event at
102
00:06:27.040 --> 00:06:29.399
the moment, you can see the schedule and all of that.
103
00:06:29.600 --> 00:06:32.079
So it's kind of just a deep place to go
104
00:06:32.199 --> 00:06:35.480
for anything Ruby events related.
105
00:06:36.279 --> 00:06:39.839
Nice. I usually you have questions because I've got a
106
00:06:39.879 --> 00:06:41.040
ton and I don't want to.
107
00:06:41.480 --> 00:06:43.639
I have a ton of why didn't you continue, I'll
108
00:06:43.720 --> 00:06:44.439
jump in as.
109
00:06:44.319 --> 00:06:48.199
And when okay, sounds good. So I'm kind of curious.
110
00:06:48.199 --> 00:06:51.160
So you decide you want this website, and I think
111
00:06:51.199 --> 00:06:53.639
the closest thing we've had in the past was Confree's
112
00:06:53.720 --> 00:06:57.600
used to host all the videos from all the conferences
113
00:06:57.600 --> 00:06:59.839
that they recorded. But I went and looked, and I
114
00:07:00.079 --> 00:07:03.839
and find them anymore. And I don't know, I don't
115
00:07:03.839 --> 00:07:05.439
know what the story is there, if I'm just not
116
00:07:05.519 --> 00:07:09.120
doing the right Google search or whatever. But anyway, so
117
00:07:10.560 --> 00:07:14.639
you start putting the site together and I mean, how
118
00:07:14.639 --> 00:07:18.519
are you finding the videos? We're just embedding them from YouTube?
119
00:07:18.560 --> 00:07:20.720
And were there any challenges that you're into kind of
120
00:07:20.720 --> 00:07:21.480
pulling this together?
121
00:07:23.600 --> 00:07:28.000
Yeah? For now, we don't host any videos, so we
122
00:07:28.240 --> 00:07:32.720
just index them. So we mostly find them on YouTube
123
00:07:32.720 --> 00:07:38.319
because that's where mostly events are hosting their videos. A
124
00:07:38.360 --> 00:07:43.360
few do host them by themselves, like Brighton. I think
125
00:07:43.399 --> 00:07:51.000
Brighton is an example for something quite recent, but mostly
126
00:07:51.000 --> 00:07:57.959
it's YouTube videos, so we do get the meta data
127
00:07:58.000 --> 00:08:06.240
from YouTube. There is there has been a very big
128
00:08:06.360 --> 00:08:10.680
work and Marco contributed a lot on this to build
129
00:08:11.879 --> 00:08:14.759
all of those yanal file that will describe all the
130
00:08:15.120 --> 00:08:17.959
meta data for all the talks, all the events with
131
00:08:18.120 --> 00:08:21.720
both their links and so on, with the correct speakers,
132
00:08:22.240 --> 00:08:26.519
the correct description. Lots of cleaning of the meta data
133
00:08:26.759 --> 00:08:27.360
has been done.
134
00:08:28.720 --> 00:08:30.800
So do you import it and then clean it up
135
00:08:30.800 --> 00:08:34.440
by hand or do you go find the videos that
136
00:08:34.440 --> 00:08:37.799
you want and then just capture all that information somehow?
137
00:08:37.960 --> 00:08:38.919
Or how does that work.
138
00:08:39.159 --> 00:08:39.399
Yeah.
139
00:08:39.399 --> 00:08:42.639
So we have a few what we call metadata parsers,
140
00:08:43.039 --> 00:08:45.720
and some events have the same structure in the title
141
00:08:45.799 --> 00:08:51.320
of how they arrange their titles, so we can kind
142
00:08:51.360 --> 00:08:54.399
of do some smart logic by splitting on the word
143
00:08:54.480 --> 00:08:58.200
by or by dashes or commas, and then you get
144
00:08:58.679 --> 00:09:01.360
there like ninety percent of the way and then there's
145
00:09:01.440 --> 00:09:03.480
like some left over to do where it just go
146
00:09:03.519 --> 00:09:06.720
in and cleaned up by hand. But I
guess this
147
00:09:06.759 --> 00:09:08.639
could also be improved in the future now that we
148
00:09:08.720 --> 00:09:12.159
have LMS and all of that to be more automated.
149
00:09:12.720 --> 00:09:16.679
But for now this has been proven to work out
150
00:09:16.679 --> 00:09:18.720
really well.
151
00:09:18.799 --> 00:09:21.399
Right, And you said that you have it all in
152
00:09:21.480 --> 00:09:26.240
YAMO files. So when there's a new conference or I
153
00:09:26.279 --> 00:09:28.159
was kind of assuming it was built on like rails
154
00:09:28.240 --> 00:09:31.559
or Hanami and had a database behind it. But is
155
00:09:31.600 --> 00:09:34.440
this more along the lines of something like a jackal
156
00:09:34.799 --> 00:09:38.200
or Bridgetown or something where you know, maybe you say, hey,
157
00:09:38.360 --> 00:09:40.639
my data is in these files, and so I'm just
158
00:09:40.720 --> 00:09:42.919
you know, I just build every time I get a
159
00:09:42.960 --> 00:09:43.600
new conference.
160
00:09:44.080 --> 00:09:46.159
Yeah, so for now, it's it is a rails up
161
00:09:46.200 --> 00:09:49.279
and it has a database. Okay, but what we do
162
00:09:49.440 --> 00:09:52.159
is that we go through all the AMMA files and
163
00:09:52.200 --> 00:09:55.879
import them into the database, just so we have a
164
00:09:55.960 --> 00:09:59.559
nicer interface to queer the data and kind of half
165
00:09:59.639 --> 00:10:05.039
speak profiles and event pages that's just easy to quer
166
00:10:05.080 --> 00:10:08.960
you and kind of build the websites around them, so
167
00:10:08.960 --> 00:10:11.679
they are all genamically generated on the service side and
168
00:10:11.679 --> 00:10:16.720
then served using the traditional rails requests response cycle.
169
00:10:18.159 --> 00:10:22.080
Gotcha, And I guess the other question I have is,
170
00:10:22.159 --> 00:10:24.519
you know, are you mostly focused on conferences or are
171
00:10:24.519 --> 00:10:28.440
you looking to do things with like meetups or if
172
00:10:28.480 --> 00:10:31.600
somebody puts up a good tutorial or something like that,
173
00:10:31.720 --> 00:10:34.039
you know, those are all videos that you may or
174
00:10:34.080 --> 00:10:36.480
may not want to pull in. I guess tutorials aren't events,
175
00:10:36.519 --> 00:10:37.639
but meetups are.
176
00:10:38.840 --> 00:10:39.039
Yeah.
177
00:10:39.080 --> 00:10:41.360
That was one of the reasons why I personally also
178
00:10:41.399 --> 00:10:45.159
wanted to move away from Ruby video, because this was
179
00:10:45.279 --> 00:10:49.399
meant to be focused on events, which also includes meetups,
180
00:10:49.440 --> 00:10:52.320
and we have a few meetup groups on there too,
181
00:10:52.799 --> 00:10:56.600
and not all the meetups are recording videos for the
182
00:10:56.919 --> 00:10:59.759
events and talks, which is also the other thing that
183
00:11:00.399 --> 00:11:02.960
I want to get away from Ruby video, because we
184
00:11:03.039 --> 00:11:05.320
want to still index all the talks that are happening at
185
00:11:05.360 --> 00:11:07.960
these meetups, even if they have no recording to it,
186
00:11:09.279 --> 00:11:13.440
So that you can at them as the titles, at descriptions,
187
00:11:13.440 --> 00:11:15.799
at the media data, at some of the slides if
188
00:11:15.840 --> 00:11:19.120
they have them available, or some of the resources like reposts,
189
00:11:19.120 --> 00:11:22.320
that you can still see that this talk and event
190
00:11:22.399 --> 00:11:25.360
took place at this time by the speaker, and this
191
00:11:25.440 --> 00:11:30.440
is all the information we know about it as well.
192
00:11:30.600 --> 00:11:34.840
But that's the thing. Like with tutorials, I think this
193
00:11:35.039 --> 00:11:38.320
is something that's harder to index in that sense that
194
00:11:38.399 --> 00:11:42.120
it keeps like it stays relevant, which I think this
195
00:11:42.200 --> 00:11:44.879
is still really good on YouTube or anywhere else where
196
00:11:44.919 --> 00:11:49.120
you host these tutorials. So I personally don't see at
197
00:11:49.200 --> 00:11:52.559
least in the near term that we kind of host
198
00:11:52.639 --> 00:11:55.519
these tours on on Ruby events as well.
199
00:11:56.120 --> 00:11:58.879
Okay, So I wonder if we could dig into these
200
00:11:59.000 --> 00:12:02.000
technicals a little bit, because you guys have built an
201
00:12:02.039 --> 00:12:07.159
actual production website using sequel Light and there some new
202
00:12:07.200 --> 00:12:11.360
feed reels features like solid que and also I think
203
00:12:11.360 --> 00:12:15.159
it's the first website that I can definitely remember has
204
00:12:15.320 --> 00:12:20.600
used page view transitions. So in terms of all these
205
00:12:20.639 --> 00:12:24.879
technologies in an actual app, what was your experience.
206
00:12:24.559 --> 00:12:28.120
Like, Yeah, as I said, when I started to build,
207
00:12:29.440 --> 00:12:34.879
I love to build things, but I am an engineer,
208
00:12:34.919 --> 00:12:38.519
so I am an engineer builder, so whenever I tried
209
00:12:38.559 --> 00:12:42.639
to build something new, it also has to be a
210
00:12:42.679 --> 00:12:47.759
way for me to discover tests some new technologies. So
211
00:12:48.679 --> 00:12:52.440
real builders will use proven tech and they just focused
212
00:12:52.519 --> 00:12:56.399
on the on the product, the feature, the and so on.
213
00:12:57.919 --> 00:13:01.399
So for me, as I said, when I had this
214
00:13:01.679 --> 00:13:05.759
initial idea of Ruby video, there were several technology that
215
00:13:05.960 --> 00:13:09.039
all came out and I wanted to try, and page
216
00:13:09.120 --> 00:13:12.799
view transition was one of the technology that I really
217
00:13:12.799 --> 00:13:18.320
wanted to try on. They had this demonstration where there
218
00:13:18.360 --> 00:13:21.039
is the same effect when you click on the
small
219
00:13:21.600 --> 00:13:25.720
thumbnail of a video, then it's zoom up and you
220
00:13:26.200 --> 00:13:31.120
get this nice transition from the index to the show view,
221
00:13:33.279 --> 00:13:37.320
and I think that's pretty cool. At the same time,
222
00:13:37.600 --> 00:13:40.840
I had this feeling that in the rails industry, you know,
223
00:13:41.000 --> 00:13:46.080
always with the same topics, rail is dying and so on.
224
00:13:46.919 --> 00:13:51.759
A lot of the the impression that rail was old
225
00:13:53.039 --> 00:13:57.279
comes from some website built on rails that are that
226
00:13:57.399 --> 00:14:04.360
have some old look that they are not modern. Uh,
227
00:14:05.399 --> 00:14:07.919
that the back end is great, but the front end
228
00:14:08.000 --> 00:14:13.480
is built by back end developers, and I want it also, uh,
229
00:14:14.600 --> 00:14:18.320
this website to be some kind of flagship and that
230
00:14:18.480 --> 00:14:22.080
demonstrates that we we can build. We can get a
231
00:14:22.200 --> 00:14:27.279
nice uicks uh and UI with rails. Uh. You don't
232
00:14:27.320 --> 00:14:31.960
need to react, you don't need whatever front end framework
233
00:14:32.080 --> 00:14:36.440
to do this. And there are lots of technology availables
234
00:14:36.480 --> 00:14:41.480
nowadays with base you transition with Delawyn and some some
235
00:14:41.639 --> 00:14:44.519
component libraries that you can use to get something that
236
00:14:44.679 --> 00:14:45.440
is nice.
237
00:14:45.879 --> 00:14:49.240
Yeah, it looks great as as quite impressed. We just
238
00:14:49.320 --> 00:14:54.159
are clean and simple designers, which is awesome. Does the
239
00:14:54.440 --> 00:14:58.120
page transition to API hooks into tablet drive? Doesn't it?
240
00:14:59.480 --> 00:15:04.320
When Hm, I started the project, it wasn't available with
241
00:15:04.440 --> 00:15:09.600
Turbo drive, so I use a package I don't recall
242
00:15:09.639 --> 00:15:19.759
the name, yes exactly, that provide the the bridge between
243
00:15:19.799 --> 00:15:25.360
Turbo and Pagroot transition. Since then, uh, Patriot transition has
244
00:15:25.399 --> 00:15:30.759
been built in into Turbo, so now it's uh, it's
245
00:15:30.759 --> 00:15:31.639
a native feature.
246
00:15:32.519 --> 00:15:35.879
Cool. And how was this the first time you'd use
247
00:15:36.000 --> 00:15:38.639
sequel light on a production app or how do you
248
00:15:38.720 --> 00:15:39.360
used it before?
249
00:15:41.919 --> 00:15:44.879
For me, it was the first time. Yes, how did you.
250
00:15:44.840 --> 00:15:48.320
Find that change from I'm guessing postgrass that you used
251
00:15:48.320 --> 00:15:50.480
in the past. Was it was it a big change
252
00:15:50.519 --> 00:15:53.039
in terms of thinking and designing or was it pretty
253
00:15:53.120 --> 00:15:55.159
much seamless.
254
00:15:56.240 --> 00:15:59.799
Mm hmmm. I would say it was seamless in terms
255
00:15:59.799 --> 00:16:09.639
of a developer experience. What is nice is that doing
256
00:16:09.679 --> 00:16:14.480
a backup or if we need to dump some database,
257
00:16:14.519 --> 00:16:17.799
it's just a single fight that you need to to move.
258
00:16:23.519 --> 00:16:30.279
Combined with Camal and a small VPS hosting made the
259
00:16:30.360 --> 00:16:36.440
things amazingly cheap to host. That's that was I mean,
260
00:16:37.039 --> 00:16:43.799
compared to Heroku or whatever past where you always end
261
00:16:43.919 --> 00:16:47.960
up with a minimum of fifty year old per month,
262
00:16:48.320 --> 00:16:52.320
we could divide this almost by ten and get better
263
00:16:52.360 --> 00:16:53.360
performance out of it.
264
00:16:54.600 --> 00:17:00.159
So the performance language, I love that. I love that
265
00:17:00.240 --> 00:17:02.799
because yeah, I've had the same experience with Kamal and
266
00:17:03.600 --> 00:17:07.240
some of those tooling, so.
267
00:17:05.920 --> 00:17:09.440
So it's it's yeah. I mean, I wouldn't say that
268
00:17:10.160 --> 00:17:16.440
it was always perfect and that I sometimes spent more
269
00:17:16.480 --> 00:17:19.920
time that than I should have learning all of those
270
00:17:20.319 --> 00:17:23.119
Camal settings and so on, but that's that's something that
271
00:17:23.160 --> 00:17:27.319
I wanted to do also as part of growing experience,
272
00:17:27.359 --> 00:17:29.400
so that that it was okay for me to spend
273
00:17:29.440 --> 00:17:33.039
some time on this. But I'm not sure how you
274
00:17:33.200 --> 00:17:37.640
feel Marco about it. But for me, the the experience
275
00:17:37.680 --> 00:17:41.839
with as with Circulite, has been amazing. I mean that
276
00:17:42.960 --> 00:17:48.000
this the speed, the the API. There is nothing that
277
00:17:48.200 --> 00:17:51.759
really that I couldn't do up to now that I'm
278
00:17:51.880 --> 00:17:57.039
able to do in post grace or whatever database.
279
00:17:57.640 --> 00:18:00.319
Yeah, it's been similar experience for me. I didn't really
280
00:18:00.359 --> 00:18:03.960
have any problems with adapting from coming from prostgress. Mostly
281
00:18:05.279 --> 00:18:08.519
pretty much everything worked as I expected to work, and
282
00:18:09.920 --> 00:18:12.000
also from the query speed and all of that, it
283
00:18:12.000 --> 00:18:14.640
didn't really make any difference for me on how I
284
00:18:14.680 --> 00:18:18.000
built apps. But I think this is mostly also thanks
285
00:18:18.039 --> 00:18:20.599
to active record that does the heavy lifting for us
286
00:18:20.759 --> 00:18:22.880
in the bag we.
287
00:18:22.839 --> 00:18:25.680
Had for the full tech search to do a bit
288
00:18:28.119 --> 00:18:31.559
a bit more integration. I guess that this will with
289
00:18:32.079 --> 00:18:38.119
Rail's eight point one should be mostly covered with something
290
00:18:38.640 --> 00:18:42.720
official from what I understood, but it's not yet. Really
291
00:18:44.519 --> 00:18:52.480
we don't know exactly the boundaries. But now we have
292
00:18:52.759 --> 00:18:56.319
a full tech search that is performed by esk light
293
00:18:56.400 --> 00:18:58.720
and that works quite nicely.
294
00:18:59.599 --> 00:19:03.880
Did yeah have to change your database schema to be
295
00:19:03.960 --> 00:19:06.160
a sequel file instead of an RB file or is
296
00:19:06.200 --> 00:19:08.920
that something that they've fixed Because I knew until like
297
00:19:09.000 --> 00:19:10.640
a couple of years ago, if you wanted to do
298
00:19:10.680 --> 00:19:13.680
full tech search your sequel light, you couldn't have a
299
00:19:13.680 --> 00:19:17.480
schema dot orb it had to be a structured dot sequel.
300
00:19:17.640 --> 00:19:19.279
Is that something that they've changed now?
301
00:19:19.680 --> 00:19:24.319
I think so, because we are still using the RB schema.
302
00:19:24.799 --> 00:19:26.119
Okay, great, that's good to know.
303
00:19:26.480 --> 00:19:29.200
So have you thought about doing like a semantic search
304
00:19:29.240 --> 00:19:30.240
of some kind on there?
305
00:19:31.319 --> 00:19:39.680
Yes, the the very first version of Ruby video I
306
00:19:39.799 --> 00:19:43.279
used malisearch combined.
307
00:19:43.720 --> 00:19:47.119
That was nice to esq light because.
308
00:19:48.400 --> 00:19:53.279
I think at that time uh full tech search. It
309
00:19:53.359 --> 00:19:58.960
was probably possible with esclight, but either I couldn't find
310
00:19:59.839 --> 00:20:05.319
a up to date tutorial or things that that were
311
00:20:05.359 --> 00:20:08.920
built in Ruby. At that time, I feel like it
312
00:20:09.000 --> 00:20:13.480
was still a bit something new in the Reils world
313
00:20:14.039 --> 00:20:19.319
for building a production website. So I started to use
314
00:20:19.359 --> 00:20:26.680
a mail search and we we did some proof of
315
00:20:26.759 --> 00:20:32.400
concept for doing semantic search and like similar topics, similar
316
00:20:33.279 --> 00:20:40.640
finding similar dogs to one tales by. We created some
317
00:20:40.799 --> 00:20:44.680
embeddings and so on. That's something that we didn't push
318
00:20:44.759 --> 00:20:50.000
to production yet, but I'm really interested to work on
319
00:20:50.039 --> 00:20:55.319
this feature uh in in the upcoming months or so.
320
00:20:56.079 --> 00:20:59.240
That's that's really something where I think we can improve
321
00:21:00.480 --> 00:21:02.960
the overall discoverability of the content.
322
00:21:03.640 --> 00:21:09.680
Yeah. I've played with it some, mostly using vector vector
323
00:21:09.759 --> 00:21:13.240
stuff with either elastic search or postgress and yeah, I
324
00:21:13.279 --> 00:21:16.279
mean it's cool stuff and it works out because then
325
00:21:16.319 --> 00:21:19.880
you can if I don't put in exactly the term
326
00:21:20.440 --> 00:21:23.440
that a full tech search would, you know, miss on,
327
00:21:24.359 --> 00:21:26.079
it can figure out what I'm looking for and kind
328
00:21:26.119 --> 00:21:26.960
of give it to me anyway.
329
00:21:27.079 --> 00:21:31.599
So it's definitely something that we'll want to improve to
330
00:21:31.599 --> 00:21:32.839
get some semantic search.
331
00:21:33.480 --> 00:21:37.680
So what other things are you looking to add to it?
332
00:21:37.680 --> 00:21:43.599
It sounds like you're going to merge the Ruby Conferences
333
00:21:43.640 --> 00:21:47.640
dot org and Ruby events dot org. Do you do
334
00:21:47.640 --> 00:21:49.599
you have other ideas of things that you want to
335
00:21:49.599 --> 00:21:51.880
add to this or bring into it, or do you
336
00:21:51.920 --> 00:21:54.440
have kind of a kind of a limited scope that
337
00:21:54.519 --> 00:21:55.119
keeps it simple.
338
00:21:55.279 --> 00:21:57.799
Yeah, I mean there's a bunch you can do and
339
00:21:57.839 --> 00:21:59.640
a bunch of stuff you want to do. But then again,
340
00:21:59.680 --> 00:22:02.720
it's kind of tricky to build out all these features
341
00:22:02.759 --> 00:22:08.759
and make it work, especially because Ruby conscious that didn't
342
00:22:08.799 --> 00:22:11.440
really have a lot of meta data around any of
343
00:22:11.440 --> 00:22:14.200
the events. It was pretty much the name, the dates
344
00:22:14.200 --> 00:22:17.240
in the location right and now on Ruby Events we
345
00:22:17.319 --> 00:22:21.440
have the speakers, the talks, all the descriptions, so it's
346
00:22:21.440 --> 00:22:23.160
not just a one to one copy that we can
347
00:22:23.200 --> 00:22:26.400
take over and then it's good. So yeah, are looking
348
00:22:26.440 --> 00:22:30.039
on ways to bring over all the events. We have
349
00:22:30.079 --> 00:22:32.960
the events index now, but I have no speakers and
350
00:22:33.000 --> 00:22:35.519
no talks touched to them. So that's what be one
351
00:22:35.519 --> 00:22:38.119
thing to just go back to all these events and
352
00:22:38.160 --> 00:22:42.240
to try to add all these old talks so you
353
00:22:42.319 --> 00:22:45.359
have the data for it. But also then looking at
354
00:22:45.880 --> 00:22:49.400
the future. Having attended a bunch of conscious in the
355
00:22:49.480 --> 00:22:52.559
last few years, I noticed that the people that organized
356
00:22:52.599 --> 00:22:55.880
these events struggle with just the whole workflow as well.
357
00:22:56.440 --> 00:22:58.480
And one of the aspects of that is also the
358
00:22:58.519 --> 00:23:02.640
call for papers and finding the right platforms to host it.
359
00:23:02.640 --> 00:23:05.720
It seems to be quite an issue that's quite expensive
360
00:23:05.759 --> 00:23:08.440
for conference organizers to just be able to host the CFP.
361
00:23:09.559 --> 00:23:12.279
So we were also looking in two ways to make
362
00:23:12.319 --> 00:23:15.079
it easier to have like a full process for conference
363
00:23:15.200 --> 00:23:18.960
organizers to go from announcing the
events up until the
364
00:23:19.000 --> 00:23:23.680
point to leasing the videos. To have this full workflow on.
365
00:23:24.880 --> 00:23:28.519
Let's announce the CFP, let's collect the proposals, let's finish
366
00:23:28.599 --> 00:23:32.599
it up. Then let's publish a schedule, let's publish the
367
00:23:32.680 --> 00:23:37.720
actual talk titles, Let's publish the event as I think
368
00:23:37.720 --> 00:23:41.319
that's happening. Then during the event, maybe there's some updates.
369
00:23:41.359 --> 00:23:46.119
Maybe there's just the currently the talk is currently running,
370
00:23:46.920 --> 00:23:49.880
and then after the talk, after the event, you don't
371
00:23:49.920 --> 00:23:55.000
get the recordings attached to the same the same talks.
372
00:23:55.480 --> 00:23:58.160
So just to kind of have this full experience on
373
00:23:59.160 --> 00:24:03.079
for conference organized, but also for attendees, to have this
374
00:24:03.160 --> 00:24:05.920
one interface platform where you can just go to and
375
00:24:06.000 --> 00:24:10.359
find the information you need. Another aspect also was to
376
00:24:12.039 --> 00:24:16.039
add photos official photos from the event, but also from
377
00:24:16.279 --> 00:24:19.839
social media. So if you use the conference hashtag, that
378
00:24:19.880 --> 00:24:22.920
we show these photos right next to the event itself
379
00:24:22.960 --> 00:24:25.440
and give some more impressions of what the event was
380
00:24:25.559 --> 00:24:28.799
like from people that's attend the event over talking about
381
00:24:28.839 --> 00:24:31.599
the event in some way or a number just to
382
00:24:31.680 --> 00:24:35.359
kind of bring the whole community aspect together, especially now
383
00:24:36.000 --> 00:24:39.799
when we have the social media breakup where everybody is
384
00:24:39.880 --> 00:24:42.960
just on some social platform but not everybody is on
385
00:24:43.000 --> 00:24:46.000
the same platform. At least with these rupy events, that
386
00:24:46.000 --> 00:24:49.279
we have one place where we see the stuff that
387
00:24:49.319 --> 00:24:55.720
we want to learn from, at least for the engineering
388
00:24:55.720 --> 00:24:57.359
part of our careers.
389
00:24:58.319 --> 00:25:04.440
Nice with this, like just like running this project, do
390
00:25:04.200 --> 00:25:06.799
you do you guys always see it always as a
391
00:25:06.839 --> 00:25:10.599
passion project? Do you reckon? You might like the sponsorship
392
00:25:10.720 --> 00:25:13.440
or some other kind of revenue model in the future,
393
00:25:13.839 --> 00:25:15.759
because if you're going to do something like come up
394
00:25:15.759 --> 00:25:18.759
with the whole workflow for conferences to run, see I
395
00:25:18.880 --> 00:25:20.640
FeAs and so that seems like quite a lot to
396
00:25:20.680 --> 00:25:21.799
do just for fun.
397
00:25:22.319 --> 00:25:24.240
I mean, I haven't really thought about how you would
398
00:25:24.319 -->
00:25:27.599
monetize it. I'm sure there are ways to do it,
399
00:25:28.119 --> 00:25:32.480
but then again, in the terms of community, it doesn't
400
00:25:32.519 --> 00:25:35.440
really seem to make sense to just monetize the whole
401
00:25:35.480 --> 00:25:39.359
platform for that. So at least for me, it's I
402
00:25:39.440 --> 00:25:42.039
plan it's to be for it to be a passion
403
00:25:42.039 --> 00:25:46.640
project that continues to be the case. And but maybe
404
00:25:47.119 --> 00:25:50.000
has another view about this, No.
405
00:25:49.759 --> 00:25:55.200
No, I mean for me it's those always I've always
406
00:25:55.200 --> 00:25:59.319
wanted to be and to remain a passion project. So
407
00:25:59.400 --> 00:26:04.359
that's also one of the reasons where I know that.
408
00:26:05.920 --> 00:26:08.599
We have lots of ideas of what we can do,
409
00:26:09.480 --> 00:26:13.960
but I mean, we also have day jobs, and so
410
00:26:14.000 --> 00:26:19.720
it has to remain a passion project and so things
411
00:26:19.839 --> 00:26:23.720
might not arrive tomorrow, it might take a bit more time,
412
00:26:23.799 --> 00:26:27.759
but we are doing it this with our little hands
413
00:26:27.799 --> 00:26:32.720
and some help of the community. Also, there's been lots
414
00:26:32.720 --> 00:26:41.000
of contributors lots of very interesting contribution from a various persons.
415
00:26:41.880 --> 00:26:45.680
Maybe some person that you met Marco, but I think
416
00:26:45.720 --> 00:26:50.559
also some person that came naturally to the ripple and
417
00:26:50.759 --> 00:26:53.480
suggested some nice improvements.
418
00:26:54.160 --> 00:26:54.319
Yeah.
419
00:26:54.359 --> 00:26:57.559
The only other aspect that I could see this making
420
00:26:57.640 --> 00:27:01.400
some money at least two account for the cost of
421
00:27:01.480 --> 00:27:04.200
running it would be so if we want to add
422
00:27:04.200 --> 00:27:06.319
sponsors anyway, we want to kind of index all the
423
00:27:06.359 --> 00:27:10.200
sponsors that have sponsored an event and give them a
424
00:27:10.279 --> 00:27:13.480
profile page two to say this company sponsored all these
425
00:27:13.480 --> 00:27:15.440
events and that's what they kind of gave back to
426
00:27:15.480 --> 00:27:19.240
our community. Also that it's more interesting for companies to
427
00:27:19.279 --> 00:27:23.240
sponsor events not just for the duration of the events
428
00:27:23.319 --> 00:27:25.480
or leading up to it that they can see their names,
429
00:27:26.039 --> 00:27:29.720
but also in the archives say these are the companies
430
00:27:29.720 --> 00:27:33.000
that made this event possible. And maybe there are some
431
00:27:33.079 --> 00:27:35.640
companies that would love to still help out or kind
432
00:27:35.640 --> 00:27:37.480
of have the name on the platform to say we
433
00:27:37.519 --> 00:27:40.759
support the rugby community in that way. And I could
434
00:27:40.759 --> 00:27:43.519
see that kind of workout, But I don't see it's
435
00:27:43.599 --> 00:27:45.839
being monetized in a way for you to access any
436
00:27:46.000 --> 00:27:49.680
information or running a call for papers or anything like that.
437
00:27:51.039 --> 00:27:55.559
Yeah, I think that's a natural thing. So I've been
438
00:27:55.599 --> 00:28:02.839
working on a side project that it does index the conferences,
439
00:28:03.240 --> 00:28:08.640
but it also indexes like gems and tutorials and you know,
440
00:28:08.759 --> 00:28:11.400
lets people know when the meetups are coming up, and
441
00:28:12.000 --> 00:28:15.359
you know, basically it's like an all in one directory
442
00:28:15.440 --> 00:28:19.359
for anything having to do with Ruby. It turns out
443
00:28:19.400 --> 00:28:21.400
it's probably a lot more work than what you guys
444
00:28:21.400 --> 00:28:24.920
are doing. But that was what I was looking at too,
445
00:28:25.119 --> 00:28:27.079
was just you know, it's like, hey, you know, this
446
00:28:27.240 --> 00:28:30.359
naturally fits in here where you know, you're looking at
447
00:28:30.480 --> 00:28:35.519
error handling tools right for dev tools under dev tools,
448
00:28:35.519 --> 00:28:38.480
and so then you'd have that banner there because somebody
449
00:28:38.519 --> 00:28:41.720
paid to kind of have their banner or be at
450
00:28:41.720 --> 00:28:43.400
the top of the list or something like that. And
451
00:28:43.440 --> 00:28:45.839
so I think something like this makes a lot of
452
00:28:45.880 --> 00:28:49.720
sense in your case too. Yeah, where somebody is you're
453
00:28:49.720 --> 00:28:53.279
not gatekeeping any content. You're just making people aware, Hey,
454
00:28:53.319 --> 00:28:56.799
they sponsored this video and you know you can find
455
00:28:56.839 --> 00:28:59.160
them here, and it just kind of extends whatever it
456
00:28:59.279 --> 00:29:03.200
was that they got from the conference exactly. Yeah, So
457
00:29:03.559 --> 00:29:06.119
I'm kind of curious, and I guess I could probably
458
00:29:06.119 --> 00:29:08.480
go look this up, But how many conferences of you
459
00:29:08.519 --> 00:29:13.599
indexed and put onto the website?
460
00:29:16.079 --> 00:29:21.200
There are five hundred forty conferences on the website right now.
461
00:29:21.279 --> 00:29:25.880
Oh wow, and I think there are around two hundred
462
00:29:25.920 --> 00:29:29.960
and fifty to half actual talks touched to them. Okay,
463
00:29:29.960 --> 00:29:32.160
so there's still like half of them don't have any
464
00:29:32.359 --> 00:29:35.160
like talks touch to them, but there's still a lot
465
00:29:35.200 --> 00:29:37.759
of data already on the platformance off.
466
00:29:38.599 --> 00:29:43.559
And that's so then seven hundred and ten.
467
00:29:43.440 --> 00:29:46.640
Dogs, That's what I was going to ask, how many talks?
468
00:29:46.720 --> 00:29:48.480
Seven thousand plus talks.
469
00:29:50.000 --> 00:30:00.359
That's amazing, almost three five hundred speakers. Wow, yes, and
470
00:30:00.400 --> 00:30:04.440
that's that's also a nice feature of Ruby Events is
471
00:30:04.480 --> 00:30:10.319
that speakers have their own page where the they we
472
00:30:10.640 --> 00:30:16.039
get some information from their guitar profile and also will
473
00:30:16.119 --> 00:30:21.640
index will list all of their talks. They can if
474
00:30:21.680 --> 00:30:27.559
they connect with Guitar, then they can get a little
475
00:30:27.680 --> 00:30:31.279
mark that will certify their their profile and they can
476
00:30:31.440 --> 00:30:34.880
do some small edits to the content on their their profile.
477
00:30:36.200 --> 00:30:41.319
But we start to have yeah, there's lots of lots
478
00:30:41.319 --> 00:30:47.359
of speakers. Some it's it's interesting when you discover a
479
00:30:47.359 --> 00:30:51.599
speaker and that you can also see what other talks
480
00:30:51.880 --> 00:30:55.400
he gave. So that's uh, brings a lot of serendipity
481
00:30:55.599 --> 00:31:01.319
into the the search experience with the the whole content.
482
00:31:01.839 --> 00:31:06.359
Nice. Yeah, I found's page and yeah.
483
00:31:05.960 --> 00:31:08.359
Yeah, I went looking for my own page in a
484
00:31:08.440 --> 00:31:10.400
very narcissistic quay as well.
485
00:31:11.599 --> 00:31:17.079
Did you I'm spoken? Oh, it says right there, claim
486
00:31:17.119 --> 00:31:17.799
your profile.
487
00:31:18.319 --> 00:31:23.359
Yeah, I'll have found this.
488
00:31:24.599 --> 00:31:26.440
Oh you've got my old stuff in here.
489
00:31:28.200 --> 00:31:28.599
There you go.
490
00:31:29.240 --> 00:31:35.359
Wow, I'm looking for your page, not chuck.
491
00:31:36.119 --> 00:31:38.279
Yeah, and the most recent talk in there for me
492
00:31:38.480 --> 00:31:42.759
is from twenty thirteen. It was a Ruby Rogues panel
493
00:31:43.279 --> 00:31:47.920
I did. Yeah, I did some other talks.
494
00:31:47.559 --> 00:31:50.079
But I'll rest on twenty fifteen ls though, But I
495
00:31:50.119 --> 00:31:53.200
think it's if your middle name there, so it's just
496
00:31:53.319 --> 00:31:56.200
Charles Wood, which has another talk in twenty fifteen.
497
00:31:56.960 --> 00:32:02.039
Oh okay, yeah, we do plant it on speaking more
498
00:32:03.359 --> 00:32:05.359
so so you may see other stuff pop up if
499
00:32:05.400 --> 00:32:06.599
you're wondering that.
500
00:32:06.960 --> 00:32:11.119
Sweet I as I found the topic section where you
501
00:32:11.160 --> 00:32:15.000
can jump into topic and see all the talks that
502
00:32:15.200 --> 00:32:18.319
fit under that, which which I think is super cool.
503
00:32:18.400 --> 00:32:22.839
But just curious about how you tagged each talk with
504
00:32:23.279 --> 00:32:25.480
a number of topics or is it a manual process
505
00:32:25.599 --> 00:32:27.920
or g use like l l m's or something of
506
00:32:28.000 --> 00:32:28.400
that for it.
507
00:32:29.720 --> 00:32:38.680
Yeah, it's it's l M based. We it's we try
508
00:32:38.720 --> 00:32:43.000
to to to Once we get the meta data from
509
00:32:43.039 --> 00:32:46.720
the for for for the does those you file, we
510
00:32:46.720 --> 00:32:50.000
we ingest them into the ESCALI database and then we
511
00:32:50.279 --> 00:32:54.759
try to enhance those meta data. First, if we can
512
00:32:54.880 --> 00:33:00.000
get the transcript of the talk, we'll add the transcript
513
00:33:00.079 --> 00:33:04.480
to our database. We'll do a first cleaning of the
514
00:33:04.559 --> 00:33:08.599
transcript because most of the time the transcript that we
515
00:33:09.079 --> 00:33:14.599
get are not so accurate, and we run them through
516
00:33:14.640 --> 00:33:20.319
a first ai agen that will produce something that is
517
00:33:20.920 --> 00:33:25.799
much cleaner, not perfect, but cleaner. Out of it this,
518
00:33:26.039 --> 00:33:31.240
we build a small summary of the talk where you
519
00:33:31.279 --> 00:33:36.359
can get i don't know, like the main key points
520
00:33:36.359 --> 00:33:40.640
that are covered during this talk. And then out of
521
00:33:40.680 --> 00:33:44.160
this the transcript and the summary, we feed this to
522
00:33:45.440 --> 00:33:49.599
an l LAM with the existing topics that we have
523
00:33:49.880 --> 00:33:55.000
because we try to avoid doing too much. Duplication doesn't
524
00:33:55.039 --> 00:34:01.200
work perfectly, but does a bit and then uh, this
525
00:34:01.920 --> 00:34:08.039
will create the taggings. So in the perfect world, well,
526
00:34:08.079 --> 00:34:11.960
of course we'd like to get some more manual tagging,
527
00:34:12.039 --> 00:34:15.559
but it wasn't given the amount of talks we had
528
00:34:15.639 --> 00:34:19.320
and all the the history that we needed to cover.
529
00:34:20.519 --> 00:34:27.800
The backlogs, the DLM really help us improve do this very.
530
00:34:27.719 --> 00:34:33.480
Quickly, are you Yeah, you were talking about the cost
531
00:34:33.519 --> 00:34:36.280
of running this. Are you are you paying for the
532
00:34:36.440 --> 00:34:39.159
LLLM that you're accessing? Are you running something like olama
533
00:34:39.159 --> 00:34:42.000
on your own thing? On your own.
534
00:34:42.400 --> 00:34:50.840
It's mostly open ai tokens, so okay, and frankly speaking, yes,
535
00:34:51.000 --> 00:34:54.920
I'm paying for this, but I think I probably put
536
00:34:55.039 --> 00:34:58.199
like twenty US dollars or an ace.
537
00:34:58.400 --> 00:35:01.519
Okay, so you have it, spend time. I've seen those
538
00:35:01.559 --> 00:35:05.440
costs go up when people use some of those models, So.
539
00:35:06.000 --> 00:35:08.960
Yeah, no, for now, the models that we are using
540
00:35:09.159 --> 00:35:16.960
for topics and summarize those things are pretty stand out.
541
00:35:19.079 --> 00:35:21.079
Those are the cheap.
542
00:35:20.880 --> 00:35:23.599
Models of I was going to say, you're not paying
543
00:35:23.639 --> 00:35:26.840
for the most recent expensive models.
544
00:35:28.079 --> 00:35:34.280
Well, they are recent, but they are not the largest one, right. Okay,
545
00:35:34.400 --> 00:35:39.239
we have seven thousand videos. It's a lot, but it's
546
00:35:39.320 --> 00:35:45.960
not it's not that much neither, so we don't We
547
00:35:46.039 --> 00:35:52.760
don't ingest thousands of video every day, so the cost remains.
548
00:35:53.320 --> 00:35:54.400
Oh yeah, that makes sense.
549
00:35:55.000 --> 00:36:00.599
Yeah, you know, I haven't counted exactly, but it's it's
550
00:36:00.639 --> 00:36:07.360
something that as I can't afford, I don't need to
551
00:36:07.360 --> 00:36:09.280
find a business model yet for this spot.
552
00:36:15.320 --> 00:36:15.920
Sounds good.
553
00:36:16.559 --> 00:36:19.119
I wonder if if you guys want to switch gears
554
00:36:19.119 --> 00:36:20.760
a little bit and just talk talk a little bit
555
00:36:20.760 --> 00:36:25.079
about stimulus, because you guys are both core maintained as
556
00:36:25.119 --> 00:36:28.360
of that, and is that something you want to discuss.
557
00:36:28.639 --> 00:36:30.920
Do you mean, like SIMS in general, on the context
558
00:36:30.920 --> 00:36:31.840
of in.
559
00:36:31.760 --> 00:36:35.079
General in general and in the context of the website.
560
00:36:35.119 --> 00:36:35.840
I guess.
561
00:36:37.440 --> 00:36:44.039
Sure, I mean yeah, so it's it's just the setup
562
00:36:44.079 --> 00:36:47.760
of hot Wire in terms of governance is a bit strange,
563
00:36:47.760 --> 00:36:50.880
because it's like Reels has a core team and an
564
00:36:50.880 --> 00:36:53.559
issue to even a committed and it's all fairly clear.
565
00:36:54.679 --> 00:36:58.320
With hot Wire and the constituent libraries, things seem a
566
00:36:58.320 --> 00:37:03.039
bit unclear. What is your impression and experience about being
567
00:37:03.119 --> 00:37:09.320
maintained as a stimulus where in slightly less of a
568
00:37:09.440 --> 00:37:13.280
democratic governance structure. I guess from my point of view,
569
00:37:13.320 --> 00:37:17.079
thirty seven signal still holds the keys essentially.
570
00:37:17.840 --> 00:37:21.360
I mean yeah. From my perspective, it always was that
571
00:37:21.719 --> 00:37:25.800
I helped out with triaging issues, trying to respond to issues,
572
00:37:26.719 --> 00:37:28.920
trying to see if you can bring in some of
573
00:37:28.960 --> 00:37:34.360
the small changes at our like no brains, to merge
574
00:37:34.880 --> 00:37:37.599
for bigger features. It was always just me proposing some
575
00:37:37.719 --> 00:37:42.800
features and then somebody from the actual company wouldn't merge
576
00:37:42.840 --> 00:37:46.320
those requests, So there wasn't that fever kind of steering
577
00:37:46.360 --> 00:37:49.280
the whole direction of the framework. It was just us
578
00:37:49.320 --> 00:37:53.559
trying to at least me trying to help out in
579
00:37:53.760 --> 00:37:58.800
some ways. That is straightforward to just do when you
580
00:37:58.840 --> 00:38:00.840
can kind of sit down for a few minutes and
581
00:38:00.880 --> 00:38:02.880
look at these issues that we're coming in.
582
00:38:03.320 --> 00:38:06.000
I think it's reated the same thing on my side,
583
00:38:07.320 --> 00:38:16.360
mostly trying to help. I would say that my involvement
584
00:38:16.480 --> 00:38:21.000
into this stimulus ripple in the past months years has
585
00:38:21.079 --> 00:38:24.320
been way less than what it could have been a
586
00:38:24.360 --> 00:38:29.199
few years ago. But I think it's also in general,
587
00:38:30.920 --> 00:38:38.440
I'm writing way less stimulus controllers since hot wire in general.
588
00:38:38.639 --> 00:38:46.800
I don't know if this is something it might be
589
00:38:46.880 --> 00:38:52.320
feeling too, but we with hot wires and the terminal
590
00:38:52.400 --> 00:38:58.400
streams and morph and so on, Lots of the things
591
00:38:58.599 --> 00:39:03.880
that in the would require some stimulus controlers are now
592
00:39:04.519 --> 00:39:11.480
somehow already included into Turbo and hot wire, So I'm
593
00:39:11.559 --> 00:39:13.559
using way less stimulus in general.
594
00:39:14.960 --> 00:39:18.280
I'll chime in and I'll say that that's my experience
595
00:39:18.320 --> 00:39:21.119
as well. Initially, when they came out with Stimulus, it
596
00:39:21.360 --> 00:39:23.400
was like, this is a breath of fresh air and
597
00:39:23.440 --> 00:39:26.920
I could just put this where I want, And yeah,
598
00:39:27.039 --> 00:39:29.360
then I have to give credit to I used because
599
00:39:29.400 --> 00:39:31.440
I was reading his book and I figured out that
600
00:39:31.599 --> 00:39:33.280
Turbo did a whole bunch of other things for me
601
00:39:33.360 --> 00:39:38.599
that I liked. And so yeah, I've been writing a
602
00:39:38.599 --> 00:39:41.639
lot less Stimulus and just using Turbo streams mostly.
603
00:39:43.159 --> 00:39:43.320
Now.
604
00:39:43.400 --> 00:39:47.000
But the governance, yeah, we know it's a thirty seven
605
00:39:47.119 --> 00:39:56.039
signal repo. They have the final decision on this. I mean,
606
00:39:58.960 --> 00:40:05.159
besides Stimulus, there is with Marco, we built stimulus hues,
607
00:40:05.960 --> 00:40:11.679
which at that time, uh, the idea was okay stimulus
608
00:40:12.079 --> 00:40:17.760
because at that time stimulus was even more uh frozen.
609
00:40:18.000 --> 00:40:21.559
This was really a frozen project. The idea was to
610
00:40:22.119 --> 00:40:27.440
get something done and keep it like this. But we
611
00:40:27.920 --> 00:40:31.280
felt in the community that we needed some more tools
612
00:40:31.280 --> 00:40:36.039
around stimulus, so there were no way to get those
613
00:40:36.079 --> 00:40:43.719
tools into the core product. There were no real plugging capabilities.
614
00:40:44.199 --> 00:40:48.039
And that's where Stimulus Shoes brought this pattern and this
615
00:40:48.199 --> 00:40:54.519
API where you could add to your stamus controllers some
616
00:40:54.960 --> 00:40:59.639
new features and some new capabilities with an API that
617
00:40:59.880 --> 00:41:05.039
was almost feeling like you have you added some plugins
618
00:41:05.079 --> 00:41:09.000
to your stimulus controllers. And that was a way to
619
00:41:09.320 --> 00:41:13.840
somehow okay, keep the stimulus and all their decision and
620
00:41:13.920 --> 00:41:20.800
their like this and build something that could fit into
621
00:41:20.840 --> 00:41:21.440
this model.
622
00:41:22.280 --> 00:41:25.880
Nice. Yeah, I think it's just one of the things
623
00:41:25.880 --> 00:41:27.920
you got to live with with stimulus. I guess it
624
00:41:27.960 --> 00:41:29.599
is what it is. I'm glad that you guys put
625
00:41:29.599 --> 00:41:33.199
in the effort to try and keep things going as
626
00:41:33.239 --> 00:41:37.159
much as possible. But yeah, with with about taking over
627
00:41:37.239 --> 00:41:41.199
so much of the heavy lifting, you only left to
628
00:41:41.239 --> 00:41:44.400
really use stimulus for like the tiny bits where you
629
00:41:44.440 --> 00:41:50.719
need clients out interactivity. I guess so you're connecting that
630
00:41:50.840 --> 00:41:55.320
back to Ruby Events. Was there anything big or heavy
631
00:41:55.360 --> 00:41:59.199
that you felt you absolutely need needed stimulus for on
632
00:41:59.239 --> 00:42:02.239
that website? And if you don't have stimulus, what do
633
00:42:02.239 --> 00:42:05.199
you think you would have used.
634
00:42:06.800 --> 00:42:09.000
I think the biggest piece that we have on Stimilus
635
00:42:09.159 --> 00:42:14.480
use use on Ruby Events is the video player for
636
00:42:14.840 --> 00:42:18.360
the playing the actual videos. I think there's some logic
637
00:42:18.440 --> 00:42:23.440
around that where we have to embed some plugin or
638
00:42:23.440 --> 00:42:26.960
some player in case it's to be light, and that's
639
00:42:26.960 --> 00:42:29.679
what we have to just wrap up in a stimulus
640
00:42:29.719 --> 00:42:32.400
control to make it work. But I think that's pretty
641
00:42:32.440 --> 00:42:35.800
much like the biggest thing we have. There are like
642
00:42:35.880 --> 00:42:40.679
around fifteen or twenty controls. It's not that many. Most
643
00:42:40.719 --> 00:42:43.079
of them are super small and tiny and super specific
644
00:42:43.199 --> 00:42:47.559
for one use case in the app. So it's not
645
00:42:47.719 --> 00:42:50.800
that it actually makes heavy use of stimulus. I think
646
00:42:50.840 --> 00:42:54.480
it's that's the other thing. I think that's just a
647
00:42:54.599 --> 00:42:58.239
testament turboalytis. You can do so much with Turbo we've
648
00:42:58.239 --> 00:43:01.519
had having to go back and write Similus controls yourself,
649
00:43:02.679 --> 00:43:06.360
and if you do, they are super small and
straightforward
650
00:43:06.440 --> 00:43:10.239
to write. So I think that's really the key here.
651
00:43:12.480 --> 00:43:14.400
The other thing about Similus as well is I think
652
00:43:14.440 --> 00:43:19.199
that it is also considered done right, that doesn't I
653
00:43:19.239 --> 00:43:22.440
don't really think there's too much we have to add
654
00:43:22.519 --> 00:43:26.280
to the core itself that you can achieve otherwise. And
655
00:43:28.280 --> 00:43:31.039
with that and having Similous use next to it, I think,
656
00:43:31.280 --> 00:43:33.480
at least for my use cases, it has always been
657
00:43:34.239 --> 00:43:38.360
more than enough. And I guess for the other question
658
00:43:38.440 --> 00:43:40.760
for what I would use if I wouldn't kind of
659
00:43:40.760 --> 00:43:47.400
write stimulus, it would probably be web components. Honestly, I
660
00:43:47.440 --> 00:43:50.360
think they have been very underrated the last few years.
661
00:43:51.119 --> 00:43:55.559
You can achieve very similar outcomes with some basic classes
662
00:43:55.559 --> 00:43:59.480
that you write that are web components. And there's this
663
00:43:59.559 --> 00:44:03.400
other project from Githup, which is inspired by Stimulus, which
664
00:44:03.400 --> 00:44:05.760
I also get the name of that framework, but is
665
00:44:06.880 --> 00:44:09.760
almost like stimulus, but you're for web components, so you
666
00:44:09.880 --> 00:44:16.880
write web components that have targets that have components that
667
00:44:16.880 --> 00:44:24.199
are controls in the same the Yeah, and if I
668
00:44:24.239 --> 00:44:26.719
wouldn't write Seamus, I would probably use that framework or
669
00:44:26.800 --> 00:44:29.119
just pure web components.
670
00:44:30.039 --> 00:44:32.400
Yeah, I got to look up that framework because I
671
00:44:32.480 --> 00:44:36.000
love web components. Like, if I don't have Stimulus available,
672
00:44:36.000 --> 00:44:38.840
which is usually if I'm doing like a static side,
673
00:44:38.840 --> 00:44:42.159
you're probably using bridge down, then I don't bother pulling
674
00:44:42.199 --> 00:44:44.079
in stimulus because a bit too much. So then I
675
00:44:44.199 --> 00:44:47.960
usually use web components And yeah, I love them. They're
676
00:44:48.039 --> 00:44:50.000
web stand that they just seem to work out of
677
00:44:50.039 --> 00:44:52.159
the box quite nicely. So yeah, A big, big fan
678
00:44:52.199 --> 00:44:52.559
of those.
679
00:44:53.239 --> 00:44:53.480
Yeah.
680
00:44:54.800 --> 00:44:57.719
One other thing that I would think about reaching for
681
00:44:58.079 --> 00:45:00.079
is if I didn't have Turbo, i'd be looking and
682
00:45:00.119 --> 00:45:01.000
at HTMX.
683
00:45:02.320 --> 00:45:02.559
Yes.
684
00:45:05.119 --> 00:45:08.199
Yeah. HMX is also interesting because it also feels it's
685
00:45:08.519 --> 00:45:12.400
way more lower level than Turpo, so you have to
686
00:45:12.440 --> 00:45:15.360
kind of write a lot more or more explicitly what
687
00:45:15.400 --> 00:45:19.000
you want to do, which is personally what I dislike
688
00:45:19.079 --> 00:45:21.199
about it. But I guess if you couldn't use Turbo,
689
00:45:21.239 --> 00:45:25.679
it will still be better than the alternatives. Yeah.
690
00:45:25.800 --> 00:45:28.320
Yeah, I have the same complaint. I just I like
691
00:45:28.440 --> 00:45:31.280
that you can just pull in Turbo and suddenly all
692
00:45:31.360 --> 00:45:36.079
your links are magically using table drive. I don't want
693
00:45:36.079 --> 00:45:39.639
to be sitting and writing data attributes for every single
694
00:45:39.719 --> 00:45:44.599
one to make it work. So yeah, similar complaint on HDMX,
695
00:45:46.000 --> 00:45:48.400
And my experience at Stimulus has also been like what
696
00:45:48.519 --> 00:45:51.840
you mentioned, the very small controller is doing very specific things.
697
00:45:52.800 --> 00:45:55.840
So in your opinions, you think Stimulus should have a
698
00:45:55.920 --> 00:45:59.400
standard library that provides a lot of these small things
699
00:45:59.480 --> 00:46:00.320
that are common.
700
00:46:00.320 --> 00:46:03.719
On Yeah, for some time I was feeling that there
701
00:46:03.760 --> 00:46:06.360
is a need for that, but I feel like the
702
00:46:06.400 --> 00:46:09.280
more I've written Stimulus, the less I think that's actually
703
00:46:09.320 --> 00:46:16.840
the case. And I also quite dislike the idea of
704
00:46:17.039 --> 00:46:22.960
importing hope control from some packages because usually it's not
705
00:46:23.119 --> 00:46:26.599
the the child skip part that is annoying to write.
706
00:46:26.599 --> 00:46:29.599
It's usually the markup, and we've had the markup next
707
00:46:29.599 --> 00:46:33.480
to the controller it is pretty much useless. So I
708
00:46:33.519 --> 00:46:36.679
don't think it really makes sense to have pre defined
709
00:46:36.719 --> 00:46:41.360
controllers that you're just important use because yeah, it depends
710
00:46:41.360 --> 00:46:44.119
on the markup if you had some way to kind
711
00:46:44.159 --> 00:46:49.440
of share markup and controls, then maybe, But I think
712
00:46:49.440 --> 00:46:51.639
then again that's kind of where we are with web components.
713
00:46:51.679 --> 00:46:54.559
That's pretty much what that is. You import one element,
714
00:46:54.920 --> 00:46:58.840
it has to behavior attached to it and it's like isolated,
715
00:46:59.440 --> 00:47:02.440
and that's kind of what you use. But if you
716
00:47:02.519 --> 00:47:04.599
don't use that, and I think that's what simlous use
717
00:47:04.639 --> 00:47:07.199
is actually really good that too, because you have these
718
00:47:07.239 --> 00:47:11.280
common behaviors that you can use with these hooks. It
719
00:47:11.480 --> 00:47:13.679
just important sooks that you kind of want and then
720
00:47:13.719 --> 00:47:17.199
you get that behavior, but it don't get ready made
721
00:47:17.239 --> 00:47:19.320
controls that are just important in the use.
722
00:47:19.679 --> 00:47:22.239
Yeah, at some point I thought that for revid and
723
00:47:23.239 --> 00:47:27.639
some standard libraries, it would have a bit more interesting
724
00:47:27.679 --> 00:47:32.639
to get some places where you can basically copy paste
725
00:47:32.679 --> 00:47:42.280
some standard stimulus controllers, because also my experience has been
726
00:47:42.280 --> 00:47:46.440
that I'd never really like to import a stimulus component
727
00:47:46.519 --> 00:47:49.960
from a library. I prefer to have the code because
728
00:47:50.360 --> 00:47:55.679
we are usually talking about what twenty fifty one hundred
729
00:47:55.760 --> 00:47:58.559
lines of code maximum in a stimulus control. What's the
730
00:47:58.599 --> 00:48:01.400
point to import this from a back cage rather than
731
00:48:01.480 --> 00:48:07.719
having this into your into your project directly. So I
732
00:48:07.840 --> 00:48:12.159
prefer to copy and paste directly to the code and
733
00:48:12.559 --> 00:48:14.320
get my own control.
734
00:48:15.360 --> 00:48:17.719
Yeah, I'm gonna agree with you.
735
00:48:17.800 --> 00:48:18.000
There.
736
00:48:18.199 --> 00:48:21.920
There's a stimulus dash components dot com that has a
737
00:48:21.960 --> 00:48:24.679
bunch of ease that pull in other libraries and things,
738
00:48:25.360 --> 00:48:28.599
and every time I've tried to use them, eventually I'm
739
00:48:28.679 --> 00:48:32.360
just like I needed to do something slightly off from
740
00:48:32.400 --> 00:48:36.360
what this does out of the box, and even doing
741
00:48:36.400 --> 00:48:38.519
the kind of inheritance thing that they tell you you
742
00:48:38.559 --> 00:48:41.679
can do with it, it still doesn't quite jive. And
743
00:48:41.719 --> 00:48:44.360
so yeah, I wind up going and finding their source code,
744
00:48:44.760 --> 00:48:47.719
copying it into my thing, and then going all right,
745
00:48:48.199 --> 00:48:51.000
now I can make it do what I want. And
746
00:48:51.039 --> 00:48:53.599
it's usually it's almost always simple enough to where yeah,
747
00:48:53.599 --> 00:48:55.719
I can just reach in and go that changes, and
748
00:48:55.760 --> 00:48:57.480
that changes, and that changes, and I'm good.
749
00:48:57.800 --> 00:49:01.119
Yeah. The framework I was mentioning earlier is called from GitHub.
750
00:49:01.440 --> 00:49:03.039
That's as I mentioned meant.
751
00:49:04.320 --> 00:49:05.400
It's called Catalyst.
752
00:49:06.000 --> 00:49:06.199
Yah.
753
00:49:06.360 --> 00:49:08.239
Interesting, need to check that out for sure.
754
00:49:08.960 --> 00:49:11.239
All right, Well, anything else that we want to delve
755
00:49:11.280 --> 00:49:15.239
into here, I mean we've been going for fifty one minutes.
756
00:49:16.079 --> 00:49:17.800
I guess one thing that I want to just mention
757
00:49:17.880 --> 00:49:21.079
as well is that we have built some
mobile apps too.
758
00:49:21.119 --> 00:49:25.320
Now with Hotwaire Native that we just want to kind
759
00:49:25.320 --> 00:49:27.800
of get out there so if you are at these events,
760
00:49:27.840 --> 00:49:30.360
that you can pull it up and see the schedule
761
00:49:30.519 --> 00:49:32.760
and maybe bookmark some of these talks that you want
762
00:49:32.800 --> 00:49:35.280
to check out later if you miss them in person
763
00:49:35.400 --> 00:49:38.920
or just want to revisit them. And that's kind of
764
00:49:38.920 --> 00:49:41.119
the other thing that I think is really nice about
765
00:49:41.199 --> 00:49:44.599
this whole ecosystem that we have now. But everything is
766
00:49:44.639 --> 00:49:46.840
in one place and you just need this one app
767
00:49:46.880 --> 00:49:50.440
for these events. And previously I have seen some point
768
00:49:50.440 --> 00:49:53.280
of this have their own app or their own PWA's
769
00:49:53.400 --> 00:49:56.559
that you have to install, and at least with this,
770
00:49:56.679 --> 00:49:58.679
it will be this one place where the community can
771
00:49:58.719 --> 00:50:01.239
focus on and contry data through and then you have
772
00:50:01.360 --> 00:50:02.599
it on the go as well.
773
00:50:02.840 --> 00:50:07.519
And what is great is that this is under the
774
00:50:09.519 --> 00:50:13.000
Ruby events all on GitHub, and you have the web
775
00:50:13.039 --> 00:50:18.119
pads that is open source, but also the two mobile
776
00:50:18.199 --> 00:50:23.119
app iOS and Android are both open source projects, so
777
00:50:23.159 --> 00:50:27.400
that's that's also a very nice, uh place to learn
778
00:50:27.440 --> 00:50:33.960
those technology. I wouldn't say that we are providing perfect code,
779
00:50:34.000 --> 00:50:40.000
but at least it's a real projects that are that
780
00:50:40.079 --> 00:50:42.760
are live in production and that you can look at
781
00:50:42.760 --> 00:50:44.039
the code awesome.
782
00:50:44.039 --> 00:50:46.039
I don't know as a native answer is that is
783
00:50:46.079 --> 00:50:47.760
that downloadable from the app stores?
784
00:50:48.480 --> 00:50:48.840
Yes?
785
00:50:49.440 --> 00:50:49.880
Awesome?
786
00:50:50.119 --> 00:50:53.199
So you just look for Ruby events that's it.
787
00:50:53.519 --> 00:50:57.639
Yes awesome, guys, just says the last technical question for
788
00:50:58.079 --> 00:51:00.440
me about the webs I just around you it is.
789
00:51:01.960 --> 00:51:06.719
I've been a fairly vocal critic of thellerency. I'm curious
790
00:51:06.760 --> 00:51:09.239
to understand why you guys are using it. Just is
791
00:51:09.280 --> 00:51:12.000
this something you like? And also how come you using
792
00:51:13.159 --> 00:51:16.920
write wheat and hybernand it instead of like, instead of
793
00:51:17.199 --> 00:51:19.800
es bild or something like that. Just curious about those
794
00:51:19.800 --> 00:51:20.519
two choices.
795
00:51:22.079 --> 00:51:25.840
Can talk about Telwyn and maybe Marco you'll talk about it.
796
00:51:26.800 --> 00:51:37.239
Mm hmm, Well, Telwyn, I think, and we it's not
797
00:51:37.280 --> 00:51:42.960
only using tellwin, but also it's using a set of
798
00:51:43.039 --> 00:51:50.360
components from daisy Ui. Then that is that provides some
799
00:51:50.360 --> 00:51:55.960
some kind of it's a bit the bootstrap uh kind
800
00:51:56.000 --> 00:51:59.880
of components that we used to have in the bootstrap days,
801
00:52:00.159 --> 00:52:08.400
but built for uh delawing. So we use that. I
802
00:52:08.440 --> 00:52:16.079
mean it's it's good in the sense that we didn't
803
00:52:16.119 --> 00:52:19.679
have to make too much decision and and things were
804
00:52:20.000 --> 00:52:24.599
already prepackaged. I know that we had some cases where
805
00:52:25.239 --> 00:52:32.119
uh Tweaking some components was harder than expected. Marco had
806
00:52:32.159 --> 00:52:35.880
some quite a bit of struggle with some component. I
807
00:52:35.920 --> 00:52:41.800
remember we haven't migrated yet. We have a pr open
808
00:52:41.960 --> 00:52:45.079
to migrate to tell in four and day z Ui
809
00:52:45.280 --> 00:52:50.519
five h, which bring more flexibility because we don't we
810
00:52:50.800 --> 00:52:56.440
don't have to import uh the entire day z Ui components.
811
00:52:57.159 --> 00:52:59.360
We can just pick the one that will want so
812
00:52:59.480 --> 00:53:06.400
that that would be a nice improvement. Now, why tellwind
813
00:53:06.559 --> 00:53:13.000
versus other things is probably I'm more familiar to use
814
00:53:13.079 --> 00:53:18.920
telling nowadays than using stand out CSS, but that's I
815
00:53:19.000 --> 00:53:21.079
don't have strong opinion on this.
816
00:53:22.639 --> 00:53:26.800
Yeah, I like tailwind, so I live in your camp.
817
00:53:27.199 --> 00:53:28.800
Yeah, it feels like it's just the de fact of
818
00:53:28.840 --> 00:53:32.400
standards at this point, at least in the wider app community,
819
00:53:32.599 --> 00:53:35.360
that this is what you use. But I can also
820
00:53:35.440 --> 00:53:37.880
see how you dislike it, especially if these classes get
821
00:53:38.000 --> 00:53:40.159
super long and you have to think about how you
822
00:53:40.239 --> 00:53:43.679
break it up. But I think it's still better to
823
00:53:43.840 --> 00:53:47.480
have these complexity at least in in one place, in
824
00:53:47.519 --> 00:53:50.280
the components themselves, not like little around the whole app.
825
00:53:51.000 --> 00:53:54.920
And yeah, we do use a view components a bit.
826
00:53:55.880 --> 00:53:59.760
We should use it more. We have some places where
827
00:53:59.800 --> 00:54:02.480
we know that we would need to refactor a bit
828
00:54:02.719 --> 00:54:09.239
like the the user, the speaker of the nails and
829
00:54:09.320 --> 00:54:11.639
so on. So we know that we have some lots
830
00:54:11.679 --> 00:54:14.559
of duplicates that we could refactor. But
we we do
831
00:54:14.800 --> 00:54:18.320
use a view components, and when you combine view components
832
00:54:18.400 --> 00:54:24.079
with Telwin's that makes it quite quite nice to get
833
00:54:24.159 --> 00:54:29.000
your design system the basics, basic building blocks.
834
00:54:29.599 --> 00:54:32.800
Yep, yeah, I've done that too. I will admit that
835
00:54:33.159 --> 00:54:36.199
I have moved back away from view components and I
836
00:54:36.320 --> 00:54:41.000
just put all my stuff in partials. It's the same
837
00:54:41.079 --> 00:54:44.480
idea right where it's okay, I know I'm going to
838
00:54:44.559 --> 00:54:49.639
have to have a text field or you know, yeah,
839
00:54:49.679 --> 00:54:51.679
an avatar or something like that, and so I just
840
00:54:51.760 --> 00:54:54.639
have a standard partial for it. Just pull it in
841
00:54:54.760 --> 00:54:55.679
and give it what it needs.
842
00:54:56.119 --> 00:54:59.039
Yeah, view components, can we have you handed? I just
843
00:54:59.199 --> 00:55:03.360
like them because and you need a little bit more logic.
844
00:55:03.880 --> 00:55:06.119
They're instead of putting it in help as I think
845
00:55:06.159 --> 00:55:09.239
the view component helps. But yeah, I think for a
846
00:55:09.719 --> 00:55:12.480
majority of use cases, partials or do just fine. It's
847
00:55:12.559 --> 00:55:15.440
just that a little bit of extraving that view component
848
00:55:15.760 --> 00:55:18.119
gives you is useful, but definitely don't need it for
849
00:55:18.239 --> 00:55:18.960
every project.
850
00:55:19.920 --> 00:55:21.400
I think that's a good way to put it, right,
851
00:55:21.440 --> 00:55:24.000
because that's the trade off is that, yeah, you can
852
00:55:24.119 --> 00:55:26.239
just hand in the objects that it needs in order
853
00:55:26.320 --> 00:55:28.440
to figure out what to do, whereas with the partials
854
00:55:28.519 --> 00:55:31.320
you kind of have to you have to finesse it
855
00:55:31.360 --> 00:55:32.760
a little bit and put some of that more of
856
00:55:32.840 --> 00:55:36.679
that into the helpers, which aren't always as targeted as
857
00:55:36.800 --> 00:55:42.400
the view component class, which is essentially like a presenter.
858
00:55:43.320 --> 00:55:43.599
And so.
859
00:55:45.559 --> 00:55:47.760
Yeah, I see the trade offs. I really do like
860
00:55:47.880 --> 00:55:51.960
the view components. I just kept running into funny things
861
00:55:52.039 --> 00:55:53.480
with some of it, or it felt like it was
862
00:55:53.599 --> 00:55:58.199
overkill for some of the simple stuff. And so yeah,
863
00:55:59.199 --> 00:56:02.679
but that idea I've used extensively where yeah, it's okay,
864
00:56:03.000 --> 00:56:07.400
I've got all my tailwind stuff in the view, view
865
00:56:07.440 --> 00:56:10.559
component or the partial, and so it always looks the
866
00:56:10.599 --> 00:56:12.400
same because I always just reach for it when I'm
867
00:56:12.440 --> 00:56:12.960
putting that in.
868
00:56:13.440 --> 00:56:17.599
Yeah, and I guess ask for the beat question, I
869
00:56:17.679 --> 00:56:20.960
think it's it's really from coming from the web Pack
870
00:56:21.079 --> 00:56:23.320
days and where you have the web Pack deft server
871
00:56:23.480 --> 00:56:27.679
running like as a separate process. You really got that
872
00:56:27.840 --> 00:56:30.440
nice developer experience where you update the files and you
873
00:56:30.519 --> 00:56:33.360
don't have to reload the page every time. So just
874
00:56:33.440 --> 00:56:38.159
like this whole experience, from hot reloading to adding dependencies
875
00:56:38.239 --> 00:56:42.320
to integration of the acid pipeline, it just feels like
876
00:56:42.480 --> 00:56:46.440
a well like grounded a package. It just included in
877
00:56:46.480 --> 00:56:49.000
the works. There's no configuration, there's nothing you have to
878
00:56:49.079 --> 00:56:52.679
kind of make work. And if E is built, it
879
00:56:52.760 --> 00:56:58.480
doesn't really handle images. It doesn't really handle style sheets.
880
00:56:58.480 --> 00:57:00.599
I think maybe it doesn't now, but not quite sure.
881
00:57:01.000 --> 00:57:03.519
So it's really just this package of you just included
882
00:57:04.079 --> 00:57:06.920
no configuration, and you've got all the nice benefits that
883
00:57:06.960 --> 00:57:10.239
you don't get with import maps but also don't really
884
00:57:10.280 --> 00:57:13.039
get with VS built. You can get some of that
885
00:57:13.239 --> 00:57:15.239
eas built too, but then you have to write your
886
00:57:15.320 --> 00:57:19.280
custom like watching mechanism to make sure that you reload
887
00:57:19.320 --> 00:57:22.679
the pages. But it feels always so hacky compared to
888
00:57:22.840 --> 00:57:27.480
just using VAT. And yeah, WEAT has focused on developer
889
00:57:27.480 --> 00:57:31.800
experience and just using that tool as it is without
890
00:57:31.880 --> 00:57:38.280
some custom rails, Rappo logic magic, it really feels nice
891
00:57:38.280 --> 00:57:38.840
as it should be.
892
00:57:39.239 --> 00:57:41.920
Yeah, I've used both. The thing that I miss when
893
00:57:41.920 --> 00:57:45.000
I use import maps as the heart reloading of all
894
00:57:45.079 --> 00:57:50.039
the things, you don't have to do hardly any work
895
00:57:50.119 --> 00:57:53.400
to make it work with VAT. The flip side is
896
00:57:53.559 --> 00:57:57.320
is that I like having the I feel like import
897
00:57:57.400 --> 00:58:00.719
maps is more flexible and I can see where everything's
898
00:58:00.719 --> 00:58:04.400
coming from. VAT tends to, at least in the way
899
00:58:04.480 --> 00:58:07.679
I had it set up. It was building out one
900
00:58:07.760 --> 00:58:11.079
file and production for the JavaScript and compressing everything together,
901
00:58:11.199 --> 00:58:14.400
and that made it a little hard to follow sometimes, you.
902
00:58:14.440 -->
00:58:19.840
Mean, like for debucking like in the browser when yeah, that.
903
00:58:20.119 --> 00:58:23.880
Those are the trade offs that I saw. I have
904
00:58:24.039 --> 00:58:27.199
to say that between you know, given given the two options,
905
00:58:27.599 --> 00:58:31.920
I've kind of leaned more toward import maps. But I mean,
906
00:58:32.039 --> 00:58:36.280
I I don't know that I have that much more advantage.
907
00:58:37.440 --> 00:58:40.159
And the hot reloading, like you said, is so nice,
908
00:58:40.199 --> 00:58:43.159
So I don't know. I don't I don't have a
909
00:58:43.199 --> 00:58:45.079
strong feel on this one, but there are things to
910
00:58:45.239 --> 00:58:45.800
like about both.
911
00:58:47.119 --> 00:58:49.239
Yeah. Other thing I like about viata as well is
912
00:58:49.519 --> 00:58:52.159
if you have a syntax error or some like missing
913
00:58:52.199 --> 00:58:56.039
dependencies or some missing or wrong imports, it will tell
914
00:58:56.079 --> 00:58:58.480
you right away with a noble A and say here's
915
00:58:58.679 --> 00:59:01.639
what's wrong on this line. And with import maps you
916
00:59:01.719 --> 00:59:07.679
pretty much get no feedback at all. Yeah, yeah, exactly,
917
00:59:07.800 --> 00:59:10.440
And that's just this a little bit more that you
918
00:59:12.480 --> 00:59:16.320
get with it. But obviously there's more complexity behind the scenes,
919
00:59:16.320 --> 00:59:18.679
which is also what makes it less attractive.
920
00:59:18.679 --> 00:59:19.000
I guess.
921
00:59:19.480 --> 00:59:23.199
For in pot maps you can get hot reloading. Now
922
00:59:23.280 --> 00:59:25.559
with hot wire Spark.
923
00:59:27.320 --> 00:59:32.039
You just made my day. Ye, here's a virtual hu Adrian.
924
00:59:32.360 --> 00:59:33.440
My life is better now.
925
00:59:37.880 --> 00:59:43.360
I've not used it yet really because I'm not really
926
00:59:43.599 --> 00:59:47.760
using in pot maps. But from what of the project
927
00:59:47.840 --> 00:59:52.559
that is made, it's a whole ray who build it
928
00:59:52.840 --> 00:59:56.880
from a thirty seven signals? I think they are using
929
00:59:56.920 --> 01:00:03.119
it mostly internally thirty seven signals because they are mostly
930
01:00:05.039 --> 01:00:10.119
in both maps shop. It does work well with in
931
01:00:10.239 --> 01:00:13.440
both maps and stimulus controller. Then when you have something
932
01:00:13.480 --> 01:00:17.239
a bit more exotic, then you might not have the
933
01:00:17.480 --> 01:00:22.719
full refresh and so on. You can give this try.
934
01:00:23.320 --> 01:00:25.159
Well, if it'll do that, then why the heck are
935
01:00:25.199 --> 01:00:26.280
you using Vietnam Skip?
936
01:00:29.320 --> 01:00:33.199
I don't know. For me, both maps has always been
937
01:00:33.679 --> 01:00:41.119
more trouble than solutions. But it's probably that I didn't
938
01:00:41.199 --> 01:00:48.039
spend enough time getting through the running curve. I don't know. Also,
939
01:00:48.280 --> 01:00:52.599
in my day job, we have more I mean in
940
01:00:52.719 --> 01:00:56.079
both maps. I think what's great when you have a
941
01:00:56.440 --> 01:01:00.480
very limited amount of external dependencies that you will get
942
01:01:00.800 --> 01:01:04.639
So if you mostly have your own stimulus controllers with
943
01:01:04.960 --> 01:01:09.199
very few external dependencies. It's probably quite easy to manage.
944
01:01:09.679 --> 01:01:12.440
But as soon as you want to pull in us
945
01:01:12.559 --> 01:01:16.639
some libraries with their own cess and so on, then
946
01:01:17.159 --> 01:01:25.519
the whole thing becomes way less easy. Ye sometimes yeah, yeah,
947
01:01:25.719 --> 01:01:28.119
for me, I never really click up to now, but
948
01:01:28.559 --> 01:01:29.039
who knows.
949
01:01:29.719 --> 01:01:31.639
All right, well, I'm going to go ahead and push
950
01:01:31.719 --> 01:01:33.960
us into our picks. Our picks is our final segment
951
01:01:34.000 --> 01:01:37.519
of the show. If you've listened before, you know, we
952
01:01:37.679 --> 01:01:40.840
just shout out stuff that we like. If you haven't
953
01:01:40.840 --> 01:01:42.920
listened before, we just shout out stuff that we like.
954
01:01:44.119 --> 01:01:47.079
And so I'll have our usually go first, and then
955
01:01:47.159 --> 01:01:48.840
I will do picks and then you guys do picks.
956
01:01:50.880 --> 01:01:51.039
Right.
957
01:01:51.400 --> 01:01:56.239
So, well, I spent quite a lot of me, you think,
958
01:01:56.320 --> 01:02:01.559
my favorite musician around Europe because it was like twenty
959
01:02:01.639 --> 01:02:05.000
plus day tour. I went for nine shows because I'm
960
01:02:05.000 --> 01:02:08.000
a bit mad, so as around Europe and then the UK. Wow,
961
01:02:08.800 --> 01:02:12.719
so I have to pick him. So Steven Wilson check
962
01:02:12.760 --> 01:02:17.000
out his new album, The Overview. It's ridiculous. It's two
963
01:02:17.159 --> 01:02:20.679
songs of twenty three minutes and eighteen minutes, so it's
964
01:02:20.760 --> 01:02:24.199
completely nuts. It's like something out of the seventies, but
965
01:02:25.039 --> 01:02:29.119
it is very very good space theme progressive rock. If
966
01:02:29.440 --> 01:02:33.199
into that kind of thing, so yeah, check that out.
967
01:02:34.880 --> 01:02:38.119
He's sturing America and the Autumn, I think, so if
968
01:02:38.119 --> 01:02:40.400
you're in America, maybe if you like what, yeah, you
969
01:02:40.440 --> 01:02:44.400
can see him live now. I watched a couple of
970
01:02:44.519 --> 01:02:49.199
movies last week. Coincidentally, both were Woody Allen movies, so
971
01:02:50.840 --> 01:02:52.719
might as well just pick those because I like them both.
972
01:02:52.840 --> 01:02:56.199
One was match Point, which I really liked, I think
973
01:02:56.840 --> 01:03:00.559
not a really really good opening line, which talks about
974
01:03:01.000 --> 01:03:03.559
luck and how people are reluctant to admit just how
975
01:03:03.639 --> 01:03:07.719
much luck plays a role in life, and it compares
976
01:03:07.800 --> 01:03:11.320
it to a ball hitting the top of a tennis
977
01:03:11.440 --> 01:03:14.639
net and for a second it can go either cross
978
01:03:14.679 --> 01:03:17.639
the net or fall right back and depends on your
979
01:03:17.679 --> 01:03:21.280
locks is. And it's just very clever writing and imagery
980
01:03:22.199 --> 01:03:26.679
throughout that movie, which is really good. And then the
981
01:03:26.800 --> 01:03:29.360
other movie I watched was almost the opposite, which is
982
01:03:29.400 --> 01:03:32.679
called Hollywood Ending, which is about as stupid as match
983
01:03:32.760 --> 01:03:36.400
Point was intelligent and deep. Hollywood Ending was about as stupid,
984
01:03:36.920 --> 01:03:40.000
but I really enjoyed it because the jokes were The
985
01:03:40.159 --> 01:03:42.679
jokes were funny, like no matter how stupid the movie
986
01:03:42.880 --> 01:03:46.199
wasn't the ending was. It was really well written and
987
01:03:46.280 --> 01:03:49.519
really funny. So yeah, I'm gonna go with those two
988
01:03:49.599 --> 01:03:52.239
movies as my picks. Yeah, I don't have a tech pick.
989
01:03:52.360 --> 01:03:53.320
I'm just gonna call it there.
990
01:03:53.519 --> 01:03:55.440
All right, good deal. I'm going to throw in some picks.
991
01:03:55.440 --> 01:03:58.360
I always start with the board game. The board game
992
01:03:58.360 --> 01:04:03.360
I'm gonna pick is Camel Up. We had four couples
993
01:04:03.840 --> 01:04:07.280
we got together for my friend's birthday and this is
994
01:04:07.320 --> 01:04:10.079
one of the games we played. It's a pretty simple
995
01:04:10.159 --> 01:04:13.039
game board game. Geek waits it at one point five,
996
01:04:14.159 --> 01:04:17.159
which means that it's you know, your casual gamer can
997
01:04:17.199 --> 01:04:23.079
pick it up pretty easily and run with it. Age
998
01:04:23.159 --> 01:04:26.920
is eight and up can play it. It takes about
999
01:04:26.920 --> 01:04:30.639
a half hour, and it's a camel race around a pyramid,
1000
01:04:31.360 --> 01:04:34.920
and so you roll the dice and you move the camels,
1001
01:04:37.079 --> 01:04:40.000
and yeah, you bet on the camels. You also can
1002
01:04:40.079 --> 01:04:42.000
reserve a space and if a camel lands on it,
1003
01:04:42.079 --> 01:04:44.440
then you know it'll move it forward or back and
1004
01:04:44.519 --> 01:04:47.199
you get money at the end of each round. If
1005
01:04:47.239 --> 01:04:50.800
you bet on the right camel, you get money. And
1006
01:04:50.920 --> 01:04:54.440
then at the end, whoever picked the right camel to
1007
01:04:54.559 --> 01:04:57.679
win the overall race. The first person to do it
1008
01:04:57.760 --> 01:05:00.920
gets more money, the second person gets less, person gets less.
1009
01:05:01.320 --> 01:05:03.079
You can bet on more than one camel. If you
1010
01:05:03.199 --> 01:05:06.599
bet wrong at the end, then you lose a coin
1011
01:05:06.800 --> 01:05:10.440
or a dollar or whatever it is. I mean, that's
1012
01:05:10.599 --> 01:05:13.360
essentially the whole game. You just play until one of
1013
01:05:13.400 --> 01:05:15.360
the camels gets across the line, and then you finish
1014
01:05:15.440 --> 01:05:19.360
the round and the dice you stick them in the
1015
01:05:19.400 --> 01:05:21.960
top of the pyramid, and then you flip the pyramid
1016
01:05:22.039 --> 01:05:24.039
over and push a little thing on the side and
1017
01:05:24.119 --> 01:05:27.239
it drops one of the dice, and whatever color the
1018
01:05:27.320 --> 01:05:29.480
dice is, you move the camels, and then the only
1019
01:05:29.559 --> 01:05:31.599
other rule is is if you move a camel onto
1020
01:05:31.599 --> 01:05:34.480
the same space as another camel, it goes on top
1021
01:05:34.559 --> 01:05:37.519
of the stack of camels. And then if a camel
1022
01:05:37.599 --> 01:05:41.719
underneath any of it, So if a camel has other
1023
01:05:41.800 --> 01:05:43.840
camels on top of it, when it moves, it moves,
1024
01:05:44.920 --> 01:05:46.760
and it moves with all the other camels on top
1025
01:05:46.800 --> 01:05:51.280
of it too, and so anyway, it gets kind of interesting,
1026
01:05:51.440 --> 01:05:55.320
you know, betting and doing all the things there, But
1027
01:05:55.880 --> 01:05:58.400
super fun game if you're looking for a quick game.
1028
01:05:58.719 --> 01:06:01.039
Like I said, it plays up to eight people and
1029
01:06:01.199 --> 01:06:03.400
so yeah. That was part of the reason why we
1030
01:06:03.519 --> 01:06:07.920
were playing it with that group, right, is because it
1031
01:06:08.480 --> 01:06:11.840
kind of fit everybody in. So, yeah, I'm gonna pick
1032
01:06:11.920 --> 01:06:14.960
camel up as as my pick for a board game.
1033
01:06:16.119 --> 01:06:19.840
I've also I'm in the middle of the last book
1034
01:06:20.000 --> 01:06:24.800
of the Sort of Truth series by Terry Goodkind and
1035
01:06:26.920 --> 01:06:31.320
those I've really really enjoyed these books. The first one
1036
01:06:31.480 --> 01:06:34.320
is called Wizard's First Rule, and so I'll put a
1037
01:06:34.400 --> 01:06:38.360
link to that in the in the show notes as well.
1038
01:06:38.559 --> 01:06:45.639
But yeah, it's it's a fantasy, it's high fantasy, and
1039
01:06:45.840 --> 01:06:49.079
I've I don't even know how to describe them to you,
1040
01:06:50.880 --> 01:06:52.360
so just go pick them up. I think there was
1041
01:06:52.440 --> 01:06:54.400
a TV series that they made out of it, too,
1042
01:06:54.519 --> 01:06:56.639
but I haven't watched it, and I don't know how
1043
01:06:56.760 --> 01:06:59.480
close they stuck to the book. So if you've seen
1044
01:06:59.559 --> 01:07:04.519
the TV series and you know, I don't know how
1045
01:07:04.679 --> 01:07:07.000
how good the context is there, but I'm
going to
1046
01:07:07.039 --> 01:07:10.280
pick that. I don't know that I have any technical picks,
1047
01:07:10.400 --> 01:07:14.920
so I will just let Adrian and Marco do their picks. Adrian,
1048
01:07:14.960 --> 01:07:15.679
do you want to go first?
1049
01:07:16.440 --> 01:07:19.679
Okay, I wasn't really prepared for this. I might go
1050
01:07:19.920 --> 01:07:23.519
a bit of topics I don't know. I'm not sure
1051
01:07:23.920 --> 01:07:27.400
about the exact rule of the pig, but I'll talk
1052
01:07:27.440 --> 01:07:34.719
about a recent passion that I had discovered. I've been
1053
01:07:34.760 --> 01:07:39.039
doing quite a lot of sports recently and discovered CrossFit
1054
01:07:39.199 --> 01:07:43.880
and iras. I don't know if you're familiar with iracks.
1055
01:07:43.920 --> 01:07:50.360
It's kind of competition a raise of CrossFit, and just
1056
01:07:51.360 --> 01:07:55.199
purchased some tickets for the next event in Bordeaux November
1057
01:07:55.440 --> 01:08:02.840
and we are and it has been quite amazing how
1058
01:08:03.960 --> 01:08:07.960
I could progress in sport doing this and how motivating.
1059
01:08:08.400 --> 01:08:12.039
So if you are looking for something quite intense and
1060
01:08:12.159 --> 01:08:15.719
to to to to get back to to sport, it's
1061
01:08:15.920 --> 01:08:19.319
it's a nice challenge to to to put to the
1062
01:08:19.960 --> 01:08:24.119
race isn't easy and one of the hardest parts nowadays
1063
01:08:24.239 --> 01:08:27.319
is to get a ticket for some of those race
1064
01:08:27.439 --> 01:08:32.439
because it's very very become very very popular. But it's
1065
01:08:34.399 --> 01:08:40.159
sounds quite challenging and nice. And that's a nice thing
1066
01:08:40.239 --> 01:08:44.359
that I discovered recently. So that's my passion pick, I
1067
01:08:44.399 --> 01:08:50.039
would say. And in terms of technical what.
1068
01:08:51.960 --> 01:08:52.439
What did I.
1069
01:08:56.119 --> 01:08:57.920
Well, we are doing a lot of things with.
1070
01:09:00.439 --> 01:09:01.439
With LLLM.
1071
01:09:01.560 --> 01:09:09.119
Of course nowadays it quite impressive how we can We
1072
01:09:09.199 --> 01:09:12.640
are doing a lot of adaptive learning, and it's pretty
1073
01:09:12.640 --> 01:09:18.279
impressive how we can do this very easily versus what
1074
01:09:19.600 --> 01:09:20.520
we could do in the past.
1075
01:09:21.119 --> 01:09:23.479
Cool. And just to put it out there, the hierrox
1076
01:09:23.600 --> 01:09:26.600
is h y r o X. It took me a
1077
01:09:26.640 --> 01:09:30.880
minute to find it on the Google. So awesome, Marco,
1078
01:09:31.159 --> 01:09:31.840
What are your picks?
1079
01:09:33.039 --> 01:09:36.279
Yeah, I have one for music as well. One of
1080
01:09:36.439 --> 01:09:41.319
my favorite DJs and producers they are They have residency
1081
01:09:41.399 --> 01:09:44.560
now in a new club that just opening Ibisa called Universe,
1082
01:09:45.319 --> 01:09:48.720
and it's this
new hyper club they call it. It's
1083
01:09:48.760 --> 01:09:51.319
like space themed. It's really big, but it's like really
1084
01:09:51.439 --> 01:09:54.279
nice and all is a custom build for that specific club,
1085
01:09:55.159 --> 01:09:57.560
and they have like a new show called Holo Sphere
1086
01:09:58.319 --> 01:10:02.119
and it's like this hollows with like visual LEDs on
1087
01:10:02.159 --> 01:10:05.119
the into the and the outside of that sphere, and
1088
01:10:05.199 --> 01:10:08.319
the DJ is performing in the center of the sphere
1089
01:10:09.159 --> 01:10:11.560
so you get these really nice free D effects and
1090
01:10:11.680 --> 01:10:15.239
it looks really awesome. And I want to go see
1091
01:10:15.279 --> 01:10:18.039
a show of his, like when he's like doing his residency,
1092
01:10:18.159 --> 01:10:21.760
it's like every Monday till September, so I really want
1093
01:10:21.800 --> 01:10:24.119
to go see that. And if you are not familiar
1094
01:10:24.199 --> 01:10:28.640
with his music, then check it out. And I guess
1095
01:10:28.720 --> 01:10:34.800
for the technical pick, I have been quite enjoying a
1096
01:10:34.920 --> 01:10:37.319
tool called hot Wire left tools by a friend of mine.
1097
01:10:38.199 --> 01:10:41.560
It's like a brows extension for hot wire, so you
1098
01:10:41.640 --> 01:10:44.720
can kind of inspect the stumus controls your turbo frames
1099
01:10:44.760 --> 01:10:46.439
and all of that, and there's a lot of stuff
1100
01:10:46.520 --> 01:10:50.119
you can just see in debug using that in the browser.
1101
01:10:51.279 --> 01:10:55.560
And they have been working on a native what do
1102
01:10:55.600 --> 01:10:58.920
you call it, like inspect panel in the browser, so
1103
01:10:59.239 --> 01:11:03.600
like next to you notes, so inspector in the theft
1104
01:11:03.600 --> 01:11:06.920
tools you also get like this new panel now for hatwire.
1105
01:11:07.039 --> 01:11:12.439
So this is really cool to see how this came about. Yeah,
1106
01:11:13.119 --> 01:11:15.159
that's called what do I F Tools and it's available
1107
01:11:15.199 --> 01:11:18.760
in all platforms breaking download extensions.
1108
01:11:18.399 --> 01:11:21.720
For grosss awesome. All right, Well, how do people find
1109
01:11:21.760 --> 01:11:23.359
you guys online? If they want to connect?
1110
01:11:23.760 --> 01:11:25.640
For me, it's my first and last name, dot dev
1111
01:11:25.720 --> 01:11:34.079
Macro dot dev now Arian Paulie pretty much everywhere, mostly
1112
01:11:34.159 --> 01:11:37.239
on Twitter, a bit on the Blue Sky.
1113
01:11:39.439 --> 01:11:43.279
Then what else. Yeah, that's the two main stings and
1114
01:11:43.640 --> 01:11:44.239
on getub.
1115
01:11:44.680 --> 01:11:47.600
All right, cool, Well, thanks for coming and thanks for
1116
01:11:47.640 --> 01:11:51.600
putting this together, because it seems pretty handy and something
1117
01:11:51.640 --> 01:11:54.000
that the community I think needed. Awesome. Thank you so
1118
01:11:54.119 --> 01:11:57.239
much for having us all right, well, folks, until next time,
1119
01:11:57.560 --> 01:11:58.079
Max out