BẢN CHÉP ÂM THANH 🔗
WEBVTT
NOTE
Transcription provided by Podhome.fm
Created: 7/6/2024 4:54:52 PM
Duration: 5433.389
Channels: 1
1
00:00:15.105 --> 00:00:16.885
Hello and welcome to podcast.init.
2
00:00:18.400 --> 00:00:20.900
Today, we are recording on April 21,
3
00:00:21.200 --> 00:00:21.700
2015.
4
00:00:23.040 --> 00:00:26.340
Your hosts today are Tobias Macy and Chris Patti.
5
00:00:26.655 --> 00:00:31.875
And today, we're happy to be speaking with a few of the members of the Kibbe core development team.
6
00:00:32.575 --> 00:00:35.555
So, Ryan, if you would please start off by introducing yourself.
7
00:00:36.920 --> 00:00:40.300
Alright. Yeah. I'm I'm Ryan. I'm a developer in Kansas City.
8
00:00:40.840 --> 00:00:43.020
I originally am from Washington State.
9
00:00:44.075 --> 00:00:47.615
I've been programming since I was, like, 9 or 10,
10
00:00:48.955 --> 00:00:49.455
and,
11
00:00:50.395 --> 00:00:58.940
my favorite part of programming is making the computer talk to other things and make them do stuff. So like from routing drivers to interface with hardware
12
00:00:59.480 --> 00:01:02.060
or making my phone control my TV and computer.
13
00:01:04.255 --> 00:01:04.755
Gabriel,
14
00:01:05.055 --> 00:01:13.150
I would like to introduce yourself. Hey. Yeah. So I'm Gabriel Petitier. I'm, from France. I'm living near near Paris right now, and
15
00:01:13.930 --> 00:01:17.470
I'm a I'm a computer scientist too, and I've been working
16
00:01:17.850 --> 00:01:21.375
in the industry for a few years now. And I started
17
00:01:21.914 --> 00:01:24.414
programming, like, you know, when I was a teenager.
18
00:01:24.795 --> 00:01:27.134
And I I've been really interested
19
00:01:27.435 --> 00:01:34.130
in this and how to make things things work the way I want, and I've been tinkering since then. And,
20
00:01:35.149 --> 00:01:35.549
so,
21
00:01:36.030 --> 00:01:36.850
I've been
22
00:01:37.185 --> 00:01:39.445
playing with Python because, as soon
23
00:01:39.825 --> 00:01:46.080
as I found it, I I was, like, in love because it was a first long grace to to make so much sense.
24
00:01:46.560 --> 00:01:50.900
So so I was so I've been, very happy to to be able to
25
00:01:51.200 --> 00:01:51.940
work with it
26
00:01:52.640 --> 00:01:53.140
since.
27
00:01:53.685 --> 00:01:58.825
And, so that's all I came to Kiwi because it was a great framework in
28
00:01:59.445 --> 00:02:02.505
in Python, so I came and gave a hand. So
29
00:02:02.880 --> 00:02:03.700
that's for me.
30
00:02:04.080 --> 00:02:04.580
Great.
31
00:02:04.880 --> 00:02:05.700
And, Matthew?
32
00:02:07.280 --> 00:02:07.780
So
33
00:02:08.480 --> 00:02:09.620
I first
34
00:02:09.925 --> 00:02:13.145
claimed for thinking to making a podcast about us.
35
00:02:13.685 --> 00:02:16.345
It was a a real surprise for all of us.
36
00:02:17.160 --> 00:02:17.660
So
37
00:02:18.280 --> 00:02:19.820
I'm mature about 32
38
00:02:20.200 --> 00:02:24.460
years old, and I love musics, and I love programming.
39
00:02:25.905 --> 00:02:26.785
And it's,
40
00:02:27.345 --> 00:02:28.065
the same as,
41
00:02:29.425 --> 00:02:31.525
Ryan. I learned about,
42
00:02:32.160 --> 00:02:33.620
when I was 10 years old.
43
00:02:34.959 --> 00:02:36.020
It was literally
44
00:02:36.400 --> 00:02:36.900
writing
45
00:02:37.599 --> 00:02:39.860
something I got on a book
46
00:02:40.445 --> 00:02:48.385
on a screen. Even if I didn't knew how to run it, it was like opening edit, typing to come online writing some things
47
00:02:48.740 --> 00:02:53.160
and then try to rename the file with a dotcom doesn't work.
48
00:02:53.460 --> 00:02:53.960
DotExecute
49
00:02:54.340 --> 00:02:56.655
doesn't work. That that doesn't work until,
50
00:02:57.995 --> 00:02:58.735
my uncle
51
00:02:59.195 --> 00:03:00.095
start to teach
52
00:03:00.875 --> 00:03:02.975
me what was programming exactly,
53
00:03:03.435 --> 00:03:04.640
teach me me basic,
54
00:03:05.180 --> 00:03:06.880
teach me to visual basic.
55
00:03:07.740 --> 00:03:09.040
I was actually working,
56
00:03:09.340 --> 00:03:10.080
in that,
57
00:03:11.260 --> 00:03:13.280
in the police department.
58
00:03:14.284 --> 00:03:14.784
And
59
00:03:15.084 --> 00:03:17.584
then computer science. I did a lot of stuff.
60
00:03:18.125 --> 00:03:20.465
It's like full stack development from
61
00:03:20.765 --> 00:03:21.265
Securinals,
62
00:03:21.724 --> 00:03:23.640
from the script, from managing servers,
63
00:03:25.480 --> 00:03:26.460
system administrator,
64
00:03:28.520 --> 00:03:29.420
web security.
65
00:03:30.520 --> 00:03:31.395
I don't know.
66
00:03:32.415 --> 00:03:33.475
Until I got,
67
00:03:34.495 --> 00:03:35.875
I find pythons, and
68
00:03:36.415 --> 00:03:38.355
I wanted to do a project with,
69
00:03:38.655 --> 00:03:40.115
some music in pythons.
70
00:03:41.200 --> 00:03:46.420
And, well, the rest of the story, I guess, would be on the next question we we will ask,
71
00:03:47.120 --> 00:03:48.340
but that doesn't.
72
00:03:50.675 --> 00:03:53.815
So how did you folks get introduced to Python initially?
73
00:03:55.155 --> 00:03:57.540
Well, on my side, it was on Linux,
74
00:03:57.940 --> 00:03:59.860
like, Linux affair. It's like,
75
00:04:00.420 --> 00:04:01.640
a French website,
76
00:04:02.980 --> 00:04:05.724
talking about lot of Linux stuff and stuff.
77
00:04:06.905 --> 00:04:08.364
And it was really
78
00:04:08.745 --> 00:04:11.245
when I was sick of doing
79
00:04:12.185 --> 00:04:12.924
all the
80
00:04:13.224 --> 00:04:14.430
same stuff in c,
81
00:04:14.909 --> 00:04:16.050
managing a list,
82
00:04:16.830 --> 00:04:17.330
thinking
83
00:04:17.630 --> 00:04:18.930
always about memory,
84
00:04:19.389 --> 00:04:19.889
creating
85
00:04:20.190 --> 00:04:24.415
class that is taking a lot of time. And I was wanting to focus on
86
00:04:25.375 --> 00:04:27.635
the artist side. I wanted to create
87
00:04:28.015 --> 00:04:31.075
not to do the same things all over again. And
88
00:04:31.935 -->
Load full transcript
00:04:36.099
just show me a solution about it, and it was called Python. This
89
00:04:36.400 --> 00:04:37.300
is how it started.
90
00:04:38.400 --> 00:04:43.025
Well, I can I can go on that too because I was I started
91
00:04:43.725 --> 00:04:44.705
developing with
92
00:04:45.245 --> 00:04:49.665
the QBasic at first? And, for a number of years when I was teenager,
93
00:04:50.125 --> 00:04:53.370
I I linked in code with this. And when I start started
94
00:04:54.310 --> 00:04:55.530
learning other languages,
95
00:04:55.990 --> 00:04:59.130
I was surprised because I didn't find anything
96
00:04:59.670 --> 00:05:00.410
that was
97
00:05:00.854 --> 00:05:05.595
as easy to to learn and that but, so it seemed like the power of
98
00:05:06.055 --> 00:05:09.750
to do complex things had to to use very
99
00:05:10.530 --> 00:05:12.310
more much more complex languages.
100
00:05:12.930 --> 00:05:19.495
And, so I was ready to to let go of simplicity. But, when I found Python, I was light shocked because,
101
00:05:20.135 --> 00:05:20.715
it was
102
00:05:21.495 --> 00:05:28.235
even simpler and a lot a lot better than everything I have I have found until now. So I,
103
00:05:29.340 --> 00:05:30.880
I I just I I started
104
00:05:31.259 --> 00:05:33.440
when I was in a in a
105
00:05:34.380 --> 00:05:35.360
computer course.
106
00:05:35.745 --> 00:05:40.485
I was learning about a lot of stuff in computer science, but there was no
107
00:05:41.104 --> 00:05:42.085
no no
108
00:05:42.385 --> 00:05:49.080
course about Python. But I just found a little book about Python, and I learned the basics of the syntax.
109
00:05:50.020 --> 00:05:50.260
And,
110
00:05:50.900 --> 00:05:53.800
and got from there, I thought I thought it
111
00:05:54.294 --> 00:05:55.195
on my own,
112
00:05:55.815 --> 00:05:56.715
thought it myself.
113
00:05:57.255 --> 00:05:57.755
So
114
00:05:58.775 --> 00:06:00.555
so it was, like, yeah,
115
00:06:00.935 --> 00:06:05.510
finding the the right language from my mind. So it was quite a discovery.
116
00:06:07.889 --> 00:06:14.445
That's very cool. It's always neat to hear when people sort of, you know, have these problems and especially when it, you know, it's at the intersection
117
00:06:14.985 --> 00:06:16.125
of our art and technology.
118
00:06:16.905 --> 00:06:17.565
That's great.
119
00:06:18.240 --> 00:06:21.300
Ryan, why don't you go ahead and tell us about how you got introduced to Python?
120
00:06:22.960 --> 00:06:33.555
Well, we needed to rewrite the software at our work and the old software was written using Zul Runner. It was all in JavaScript and it was just horrible and slow. It was hard to work on,
121
00:06:34.419 --> 00:06:35.160
poorly designed.
122
00:06:36.100 --> 00:06:40.360
So I was looking for something that I could use for make making desktop applications,
123
00:06:41.300 --> 00:06:43.880
and I didn't really wanna do CC plus plus.
124
00:06:44.245 --> 00:06:48.505
I wanted it to run on Linux. I wanted
something with rapid development capabilities. And
125
00:06:49.045 --> 00:06:53.420
looking around, I found Python, and I fell in love with it once I got past the lack of braces.
126
00:06:56.760 --> 00:07:01.340
Akshay, thank you for joining us. Could you just give a brief inter introduction
127
00:07:02.155 --> 00:07:04.735
and tell us about how you got introduced to Python?
128
00:07:06.074 --> 00:07:06.735
Hi, guys.
129
00:07:07.435 --> 00:07:08.414
Akshay here.
130
00:07:10.050 --> 00:07:10.550
Okay.
131
00:07:11.010 --> 00:07:13.590
Now I got introduced to 5. Essentially,
132
00:07:14.210 --> 00:07:17.670
I started with, you know, working on the market at that
133
00:07:18.265 --> 00:07:18.765
time,
134
00:07:19.305 --> 00:07:20.925
in some level, I think. And
135
00:07:21.945 --> 00:07:24.765
I was looking for a framework that we're working on
136
00:07:25.280 --> 00:07:29.699
those. The only 2 available options at that time were, Jiwi and,
137
00:07:30.880 --> 00:07:32.419
empty corrugate, automated.
138
00:07:33.280 --> 00:07:34.660
Yeah. Empty 4 g. Yeah.
139
00:07:35.745 --> 00:07:36.885
Yeah. So
140
00:07:37.345 --> 00:07:38.165
in my research,
141
00:07:38.625 --> 00:07:42.005
I found out that the only option that was any
142
00:07:42.305 --> 00:07:43.525
worked for me was,
143
00:07:44.065 --> 00:07:44.565
Kiwi.
144
00:07:44.950 --> 00:07:46.010
That's when I started
145
00:07:46.390 --> 00:07:49.930
and came into, like, actually, it was first thing that I,
146
00:07:50.710 --> 00:07:52.090
worked on with. Right?
147
00:07:52.550 --> 00:07:53.050
Great.
148
00:07:54.925 --> 00:07:55.425
So,
149
00:07:57.165 --> 00:08:01.585
anyone who knows the story, can you tell us about how the Kibbe project got started?
150
00:08:03.699 --> 00:08:04.759
As we've mentioned.
151
00:08:05.380 --> 00:08:05.880
Yeah.
152
00:08:07.620 --> 00:08:08.120
It's
153
00:08:08.580 --> 00:08:11.400
it wasn't Kibbe at the start. It was named Pianti.
154
00:08:11.995 --> 00:08:13.455
At the same time as,
155
00:08:14.155 --> 00:08:17.854
what Ashkei said about, MT 4 g, we were,
156
00:08:18.315 --> 00:08:21.870
Thomas Simpson was the initial creator of the toolkit
157
00:08:22.330 --> 00:08:24.350
because he was trying to,
158
00:08:26.330 --> 00:08:28.670
to make, user interface
159
00:08:29.095 --> 00:08:30.794
easily in multi touch,
160
00:08:31.335 --> 00:08:34.154
and he didn't found anything that works for him.
161
00:08:34.535 --> 00:08:36.714
Also, secure on solution was
162
00:08:37.750 --> 00:08:38.570
was not
163
00:08:38.950 --> 00:08:39.450
working
164
00:08:39.910 --> 00:08:40.410
with
165
00:08:41.589 --> 00:08:43.050
with multi touch concept.
166
00:08:43.430 --> 00:08:50.245
It's like UT, GTK, it was not even started. There is not even a multi touch event on Linux. It was
167
00:08:50.625 --> 00:08:51.765
before everything.
168
00:08:52.705 --> 00:08:56.450
The tablet was not something you are you were using.
169
00:08:57.310 --> 00:08:57.810
So
170
00:08:58.190 --> 00:09:00.370
we started the toolkits, and
171
00:09:00.910 --> 00:09:03.605
at, like, 3, 4 months after,
172
00:09:04.385 --> 00:09:06.485
I was having the same issues,
173
00:09:07.185 --> 00:09:07.685
troubling,
174
00:09:08.625 --> 00:09:11.820
having issue to find a good toolkit about it. And
175
00:09:12.360 --> 00:09:13.900
until I see
176
00:09:14.520 --> 00:09:19.415
the option, see about Python, starting to play with it, and then I just found
177
00:09:20.435 --> 00:09:24.454
a Google code, with PyMt on it. I joined this.
178
00:09:25.650 --> 00:09:27.830
I asked Thomas to join the project,
179
00:09:29.570 --> 00:09:31.670
and it was very welcoming.
180
00:09:32.450 --> 00:09:34.150
We did a lot of cleanups.
181
00:09:35.755 --> 00:09:37.295
We have been able to
182
00:09:38.395 --> 00:09:41.295
join the Google Summer of Code via
183
00:09:42.010 --> 00:09:44.670
NU Group because we work far on it.
184
00:09:45.850 --> 00:09:48.030
And we have been able to meet,
185
00:09:48.570 --> 00:09:50.910
from now at least 1
186
00:09:51.275 --> 00:09:52.415
time per year.
187
00:09:53.595 --> 00:09:54.895
And then
188
00:09:56.955 --> 00:09:59.375
when KMT was quite of great,
189
00:10:00.700 --> 00:10:01.680
Android was
190
00:10:02.380 --> 00:10:04.800
growing a lot. And at some point,
191
00:10:05.500 --> 00:10:06.000
we
192
00:10:06.620 --> 00:10:07.440
we were forced
193
00:10:07.820 --> 00:10:09.440
we were forced to
194
00:10:09.964 --> 00:10:10.464
rethink
195
00:10:10.845 --> 00:10:11.584
the toolkits
196
00:10:12.045 --> 00:10:13.904
to be able to be more performanced
197
00:10:14.365 --> 00:10:18.065
and to have a graphic stack stack that works on mobiles
198
00:10:18.550 --> 00:10:22.810
because all we were using the all of NGL function, etcetera.
199
00:10:23.190 --> 00:10:25.370
It absolutely doesn't work on mobile.
200
00:10:26.045 --> 00:10:28.865
So we did, like, free iteration
201
00:10:29.405 --> 00:10:30.785
before getting Kiwi
202
00:10:31.405 --> 00:10:33.265
the way it is currently.
203
00:10:34.740 --> 00:10:38.440
And all has happened in a week in US.
204
00:10:39.060 --> 00:10:40.339
We're at is,
205
00:10:40.820 --> 00:10:41.800
parent's house
206
00:10:42.545 --> 00:10:44.964
alone in 1 week, and we just
207
00:10:45.425 --> 00:10:47.204
think about what we want
208
00:10:47.584 --> 00:10:48.725
and really didn't
209
00:10:49.185 --> 00:10:49.685
check
210
00:10:50.779 --> 00:11:02.555
what the other were doing. Just think what we like, how we would like to do it, and we were brainstorming the whole day. And we invented, like, the language.
211
00:11:02.935 --> 00:11:03.675
We invented
212
00:11:04.935 --> 00:11:09.675
the way of the input event are working right now, etcetera. There's
213
00:11:10.439 --> 00:11:12.379
lot of thing happened this week.
214
00:11:13.240 --> 00:11:14.060
And TVs
215
00:11:16.279 --> 00:11:16.779
growing
216
00:11:17.675 --> 00:11:18.415
every month?
217
00:11:18.875 --> 00:11:20.255
I think it's because,
218
00:11:20.795 --> 00:11:25.510
you are working on this since at least 2 years, I think from 2, 008,
219
00:11:26.210 --> 00:11:27.270
2, 000 to 2010.
220
00:11:28.050 --> 00:11:29.590
And then when you decided
221
00:11:29.970 --> 00:11:31.190
to rework everything,
222
00:11:31.884 --> 00:11:44.530
you had a lot of stuff in mind that you wanted to change, and you had a lot of a lot to experiment at this time. To experiment, but, for example, the Kiwi language, I at this time, I didn't even knew about QML
223
00:11:45.390 --> 00:11:53.075
or QT. I heard about it few months after, and, yes, we are very similar even if we are far more powerful than us.
224
00:11:54.415 --> 00:11:54.915
And
225
00:11:56.655 --> 00:12:14.384
but it's it's really like brainstorming. We tried to write it in a way. Like, we tried YAML, and it just didn't work. We tried a lot of other language. Like, what about XML? Even in parenting, we were being able to build a whole UI and attach events in XML.
226
00:12:14.920 --> 00:12:17.180
It was working, but, well,
227
00:12:17.880 --> 00:12:20.940
it doesn't please us. Yeah. Nobody likes it.
228
00:12:23.045 --> 00:12:24.665
But it's something that happened.
229
00:12:25.125 --> 00:12:25.625
Yeah.
230
00:12:25.925 --> 00:12:31.019
Right. Well, I mean, it it it kinda makes sense in a way, right, if you're thinking in terms of what's the most elegant
231
00:12:31.399 --> 00:12:34.300
way to express a user interface. And
232
00:12:34.680 --> 00:12:38.620
other projects have done that at various points in times. Right? And
233
00:12:39.195 --> 00:12:39.695
inevitably,
234
00:12:40.154 --> 00:12:43.774
when they choose that, nobody's happy with it. But you guys
235
00:12:44.154 --> 00:12:50.820
just had the foresight to say, we're not happy with it, and we're gonna go a completely different direction. And we're certainly glad you did.
236
00:12:51.440 --> 00:12:55.060
And and this is something that drive us from the start actually because
237
00:12:55.735 --> 00:12:58.555
we never think about how the other we're doing.
238
00:12:59.495 --> 00:13:02.154
Otherwise, we will fall into the same issues.
239
00:13:02.455 --> 00:13:09.070
Yeah. If you think about GTK and QT, so where they build UIs, the way they use events,
240
00:13:09.850 --> 00:13:10.350
it's
241
00:13:11.050 --> 00:13:12.190
they have an historic,
242
00:13:12.745 --> 00:13:18.205
and we were being able to just create from the start what would be a modern way.
243
00:13:18.905 --> 00:13:22.960
But I guess if we were doing it again right now, we might
244
00:13:23.580 --> 00:13:27.279
just came up with a different solution, a different way to do things.
245
00:13:31.145 --> 00:13:37.565
So so this kinda leads really well into the next question. What made you folks choose Python as the basis for Kivy?
246
00:13:38.680 --> 00:13:41.180
I don't have a real answer about it.
247
00:13:42.200 --> 00:13:45.980
Because Python is the language of metal make that make sense.
248
00:13:46.520 --> 00:13:50.324
That's all I think. It's the right language at the right time.
249
00:13:50.625 --> 00:13:54.404
Yeah. I think you you you you had used,
250
00:13:54.865 --> 00:14:01.070
Python for some time before. You had tried a lot of technology, and if you did that in Python, it was
251
00:14:01.390 --> 00:14:04.850
yeah. I mean yeah. You you said earlier because you you
252
00:14:05.255 --> 00:14:05.915
you wanted
253
00:14:06.375 --> 00:14:07.834
something different than
254
00:14:08.295 --> 00:14:11.274
from c. So I guess that's that's answer.
255
00:14:11.735 --> 00:14:13.834
I was starting a project called,
256
00:14:14.839 --> 00:14:15.660
and it was,
257
00:14:17.640 --> 00:14:27.035
a software when you can put well, actually, it's kind of, what you are doing on your day job, Gabriel. It's putting objects on the table and making music with it.
258
00:14:27.415 --> 00:14:30.635
And I was I was needed a simple things,
259
00:14:31.230 --> 00:14:34.210
having a possibility to have buttons and labels
260
00:14:34.910 --> 00:14:35.650
in OpenGL.
261
00:14:36.430 --> 00:14:40.495
Yeah. There is absolutely no good solution for it, at least a
262
00:14:41.055 --> 00:14:48.835
solution that looks good and when you can do everything and easy to use. I was starting to write it in c plus plus
263
00:14:49.959 --> 00:14:50.620
and spending
264
00:14:51.560 --> 00:15:05.185
so much time on it. This is how I discovered Python, TNT, and, you know, the rest of the story. Just, as I say, came up at the right time. So that is so bad. Go, JavaScript. But we don't know why Thomas
265
00:15:05.990 --> 00:15:07.290
chose chose the Python.
266
00:15:07.670 --> 00:15:15.645
No. And he's not here. He's not here. He's lost at the sands of time. Yeah. I lost. His story is lost. Okay.
267
00:15:16.265 --> 00:15:16.665
Alright.
268
00:15:17.145 --> 00:15:19.325
I I honestly, just guys,
269
00:15:20.105 --> 00:15:21.085
is at least
270
00:15:21.865 --> 00:15:23.245
a language that,
271
00:15:23.970 --> 00:15:26.470
give you time to focus on issues,
272
00:15:26.930 --> 00:15:31.910
not in the language itself. Right. Yeah. But not really dealing with the language. That's what I love
273
00:15:32.530 --> 00:15:45.220
to. Yeah. Yeah. Yeah. Me too. Forget about it. You just sometimes say, I love Python because you you just gain so much time of doing things that on over language, you will spend a lot more.
274
00:15:45.600 --> 00:15:46.100
Yeah.
275
00:15:47.735 --> 00:16:03.965
Well, that's 1 of the things that makes Kivy so enjoyable to work with. Right? Is because language, as you said, it it kind of allows you to be so expressive, and it kinda stays out of the way. And you can think in very high level abstract terms. Mhmm. I haven't had a lot a lot of time to play with Kibby, but
276
00:16:04.525 --> 00:16:24.755
I was very impressed when I was doing the prep for this episode, how I was able to sort of, like, download Kibbe, download the tutorial, and it's like, hey. I'm actually assembling, you know, a UI on the screen with widgets and labels. And and it's it all just kinda works and is very straightforward. And, like, it's not like you mentioned some of these other UI paradigms like,
277
00:16:26.015 --> 00:16:27.955
cute cute or or GTK,
278
00:16:28.709 --> 00:16:31.290
where there's this whole huge, like, conceptual
279
00:16:31.670 --> 00:16:36.810
framework that you have to wrap your head around before you can make anything happen on the screen.
280
00:16:37.194 --> 00:16:43.454
I I think I think it's awesome that you guys did do choose Python, and also it's a testament to your good design that
281
00:16:43.915 --> 00:16:47.580
using Kivy is just such a pleasure to pick up and run with.
282
00:16:48.120 --> 00:16:50.780
Well, some people we have the concepts
283
00:16:51.320 --> 00:16:54.365
in Kibbe too, but you have to to learn. But
284
00:16:54.845 --> 00:17:06.740
some some people struggle more than others to to get them, but it's easy. Once you you got them, it's easy to forget about it because they fit your mind really well, I think. But
285
00:17:07.040 --> 00:17:10.020
so we we try to to to improve the documentation,
286
00:17:10.925 --> 00:17:14.705
because for some people, it's more important for than for others.
287
00:17:15.165 --> 00:17:18.945
But, I I I do think the concept are good. They they may
288
00:17:19.330 --> 00:17:21.670
need better explanation sometime, but
289
00:17:22.370 --> 00:17:23.590
I agree very good.
290
00:17:25.490 --> 00:17:27.510
So what were some of the major influences
291
00:17:27.890 --> 00:17:31.274
and inspirations for the way that Kibbe was implemented,
292
00:17:32.054 --> 00:17:33.674
or was it all just happy accident?
293
00:17:35.174 --> 00:17:37.595
Definitely a few happy accidents, I guess.
294
00:17:38.500 --> 00:17:41.240
At least the Kiwi language is not the accident.
295
00:17:41.860 --> 00:17:42.360
Yep.
296
00:17:42.660 --> 00:17:43.160
Wow.
297
00:17:43.620 --> 00:17:46.115
The the the event system is
298
00:17:46.995 --> 00:17:52.934
more, traditional, I guess, I would say, the the way It's the event system. Yes. Not the inputs 1.
299
00:17:53.554 --> 00:17:54.054
Okay.
300
00:17:55.600 --> 00:17:59.940
So in Kiwi, we have all the inputs are
301
00:18:01.600 --> 00:18:04.179
are the same but separated. It's like
302
00:18:04.784 --> 00:18:07.044
you have the same base place,
303
00:18:08.065 --> 00:18:09.445
and it's not really
304
00:18:09.985 --> 00:18:10.485
surplus.
305
00:18:11.024 --> 00:18:11.684
It's like,
306
00:18:13.620 --> 00:18:19.880
to be simple, you have a touch event. And in the touch, you know what the touch is capable of.
307
00:18:20.565 --> 00:18:21.945
So on the documentation,
308
00:18:22.325 --> 00:18:23.065
we have
309
00:18:23.764 --> 00:18:24.424
The profile.
310
00:18:24.885 --> 00:18:31.530
Yeah. There is a profile. I
the profile said your touch is able to spot a 2 d position.
311
00:18:32.230 --> 00:18:33.530
A 3 d position
312
00:18:34.230 --> 00:18:35.050
is supporting
313
00:18:36.365 --> 00:18:37.905
a 2 d pressure
314
00:18:38.525 --> 00:18:39.825
or etcetera.
315
00:18:40.125 --> 00:18:42.065
So and for each profile,
316
00:18:42.845 --> 00:18:44.785
you have a set of attributes
317
00:18:45.200 --> 00:18:48.500
that is added to the original touch glass.
318
00:18:49.680 --> 00:18:50.900
So it's kind of,
319
00:18:52.080 --> 00:18:57.665
it's making the input completely abstract because it work on touchpad, but it can work also on,
320
00:18:58.465 --> 00:19:00.325
a table with camera behind
321
00:19:00.625 --> 00:19:06.630
when it is able to detect the pressure or the shape of your finger. This is information that
322
00:19:07.010 --> 00:19:12.375
you can receive and use it, or it can just work with a simple cursor.
323
00:19:13.075 --> 00:19:15.175
And we tried also to use
324
00:19:16.035 --> 00:19:20.230
I have been able in the Leap Motion beta developer, so I
325
00:19:20.690 --> 00:19:21.190
received
326
00:19:21.809 --> 00:19:23.590
and no. Even before the
327
00:19:24.529 --> 00:19:26.309
before the beta, I received
328
00:19:28.175 --> 00:19:29.155
a a late motion
329
00:19:29.615 --> 00:19:30.115
device.
330
00:19:32.095 --> 00:19:35.315
And it's it was quite nice to to try,
331
00:19:35.930 --> 00:19:40.430
using it. We we were almost being able to use directly in giving.
332
00:19:40.890 --> 00:19:45.625
Just a little bit of rubber, and it was done. And the same for Kinect.
333
00:19:46.645 --> 00:19:50.905
And you cannot do that with other toolkit, honestly. That's amazing.
334
00:19:52.290 --> 00:19:54.070
In Kiwi, you can just provide
335
00:19:55.010 --> 00:19:58.150
there, and all your widgets will be able to
336
00:19:59.325 --> 00:20:00.705
to use it because also
337
00:20:01.164 --> 00:20:03.105
1 of the big things in Kivy
338
00:20:03.645 --> 00:20:05.585
is every widget we've wrote
339
00:20:06.330 --> 00:20:08.110
is built on
340
00:20:08.570 --> 00:20:10.350
the touch events.
341
00:20:10.810 --> 00:20:11.790
And the touch,
342
00:20:12.410 --> 00:20:15.275
by design, very there can be multiple 1.
343
00:20:15.755 --> 00:20:17.615
So you always think about it.
344
00:20:18.795 --> 00:20:21.135
Mean meaning, you can press
345
00:20:21.515 --> 00:20:23.455
2 buttons at the same time
346
00:20:24.090 --> 00:20:27.950
on a Kiwi application. You cannot do that on other application.
347
00:20:28.330 --> 00:20:32.110
Gdk, q t, or even the web. It's not made up.
348
00:20:33.884 --> 00:20:40.625
You create 2 button on a form, you cannot press at the same time. You can do it in Kibbe, and it's opening a lot of,
349
00:20:41.164 --> 00:20:42.065
multi user
350
00:20:43.440 --> 00:20:43.940
application.
351
00:20:44.800 --> 00:20:45.300
Mhmm.
352
00:20:46.320 --> 00:20:47.460
You you mentioned the
353
00:20:47.840 --> 00:20:48.420
the conception
354
00:20:48.800 --> 00:20:51.060
of widgets, and and that's what I
355
00:20:51.394 --> 00:20:53.815
something that I really appreciate in Kivi.
356
00:20:54.514 --> 00:20:58.750
When you're doing Python and using, for example, GTK or Qt
357
00:20:59.850 --> 00:21:03.870
over frameworks that are repels of c plus plus layer libraries,
358
00:21:04.570 --> 00:21:07.470
and you you you don't have access to the underlying
359
00:21:08.285 --> 00:21:09.665
layer. You can't extend
360
00:21:09.965 --> 00:21:17.185
things the way you want. And when you are working in a library that is built in the language you are using,
361
00:21:17.509 --> 00:21:20.970
And especially in a as dynamic language as Python,
362
00:21:21.429 --> 00:21:25.370
you are free to extend about, anything, and you you can
363
00:21:25.750 --> 00:21:26.809
plug your parts
364
00:21:27.335 --> 00:21:32.155
just the the way you want. And I think it's a freedom, but you you rarely
365
00:21:32.615 --> 00:21:33.015
have,
366
00:21:33.655 --> 00:21:37.309
even because, for example, if you extend the C plus plus program,
367
00:21:37.690 --> 00:21:39.470
you do not have as much freedom
368
00:21:39.850 --> 00:21:41.070
to tinker with
369
00:21:41.450 --> 00:21:43.150
the with the elements of the framework
370
00:21:43.475 --> 00:21:45.495
as, as in Python because
371
00:21:45.875 --> 00:21:48.375
things can be closed, things can be
372
00:21:49.715 --> 00:21:51.095
built, and you aren't
373
00:21:51.475 --> 00:21:52.855
supposed to integrate
374
00:21:53.370 --> 00:21:54.830
too much with the framework.
375
00:21:55.290 --> 00:21:58.350
Based on you have quite a lot of power at this level.
376
00:21:58.810 --> 00:21:59.310
And
377
00:21:59.610 --> 00:22:01.835
I think it's more like
378
00:22:02.535 --> 00:22:07.755
being on the shoulder of Giant, which is Python, and having the
379
00:22:08.055 --> 00:22:09.835
the feature as at the right level
380
00:22:10.690 --> 00:22:11.190
just
381
00:22:11.650 --> 00:22:13.030
so you can grab them.
382
00:22:14.530 --> 00:22:15.670
And, for for the
383
00:22:16.450 --> 00:22:17.510
the touch system,
384
00:22:18.130 --> 00:22:21.825
and just like other things, it's a bit
385
00:22:22.325 --> 00:22:22.825
of
386
00:22:23.325 --> 00:22:27.025
a throwing to the object oriented philosophy.
387
00:22:27.940 --> 00:22:29.560
So that instead of
388
00:22:29.940 --> 00:22:37.125
putting places on on things, you have 1 place, but eventually you have multiple places to to describe your events.
389
00:22:37.765 --> 00:22:41.385
It's not the object model which shows what,
390
00:22:42.085 --> 00:22:44.825
the event is. It's the data inside.
391
00:22:45.125 --> 00:22:49.509
And that's I I think it's indeed quite quite a good idea, quite
392
00:22:49.809 --> 00:22:50.389
a powerful
393
00:22:53.090 --> 00:22:53.590
Abstraction?
394
00:22:54.405 --> 00:22:56.505
Abstraction. Yes. Perfect. Perfect.
395
00:22:58.405 --> 00:23:07.610
So But I I I guess
that's A bit a bit like duct taping, but for for events, it's a if it asks something, you are you can use it this way.
396
00:23:08.950 --> 00:23:10.970
So to to answer to the question,
397
00:23:12.025 --> 00:23:12.925
the influential
398
00:23:13.625 --> 00:23:15.965
or inspiration on the Kiwi design,
399
00:23:16.345 --> 00:23:18.045
it's like Python itself.
400
00:23:19.145 --> 00:23:19.645
Yeah.
401
00:23:20.505 --> 00:23:21.565
Yeah. That's great.
402
00:23:23.040 --> 00:23:28.820
That is very cool. It's like it's like not only is Kivy written in Python, but it's also designed to be Pythonic
403
00:23:29.360 --> 00:23:30.100
in nature.
404
00:23:33.185 --> 00:23:34.645
It's a concept because
405
00:23:35.505 --> 00:23:36.485
what is Pythonic?
406
00:23:37.505 --> 00:23:47.030
When you start Python, you you read a lot about being Pythonic. This is Pythonic. This is not. Where's definition of that? There's absolutely no documentation
407
00:23:47.330 --> 00:23:48.550
saying this is
408
00:23:49.145 --> 00:23:52.205
something that looked great in Python. This is not.
409
00:23:53.385 --> 00:23:55.805
So at the time of writing Kibbe on clientele.
410
00:23:56.870 --> 00:23:58.490
There is the the Zen of Python.
411
00:23:59.190 --> 00:24:07.925
But, there was a a great, conference about this, in the in the last Python that I watched on on YouTube last week. It was the
412
00:24:08.545 --> 00:24:10.325
explaining the difference between
413
00:24:11.105 --> 00:24:15.019
watching the PEP 8 compatible code and watching Pythonic
414
00:24:15.559 --> 00:24:17.899
code, and it was very, very interesting.
415
00:24:18.360 --> 00:24:28.345
So I think I don't really know who who did it, but it was really great. Yeah. It was Raymond Headinger. I I was there for that talk, and he definitely did a very good job of that. So,
416
00:24:29.519 --> 00:24:42.825
we'll we'll certainly add a link to that in the show notes so that other people can watch it because it was Great. It really did give a very good concrete example of what is Pythonic and what is not because, like you, I've when I first started learning Python, I kept coming across these references
417
00:24:43.365 --> 00:24:45.720
of Pythonic versus non Pythonic code, and
418
00:24:46.760 --> 00:24:57.595
It's it's very subjective, and there doesn't really seem to be any firm conclusion as to what really makes something Pythonic. It's more just the way that it feels when you're dealing with it. So Yeah.
419
00:24:58.054 --> 00:25:00.875
You really did a great job of distilling it down to its essence.
420
00:25:03.320 --> 00:25:03.820
So
421
00:25:04.200 --> 00:25:14.115
speaking of distilling things down to their essence, 1 of the amazing things about Kibbe is that it's comparatively simple to learn. I mean, I understand that there are some concepts that you have to wrap your head around. But
422
00:25:14.735 --> 00:25:16.195
as I said to you, you know,
423
00:25:16.735 --> 00:25:36.495
I I was able to sort of at least pick up the rudiments of it and and if not run with it, then then walk with it with in a matter of a couple of hours. And that hasn't been my experience with various other UI frameworks that I've attempted to use, like cute or, you know, I remember getting pretty frustrated with with tickle t k back in the day.
424
00:25:37.745 --> 00:25:39.135
Mhmm. Yeah. So
425
00:25:40.030 --> 00:25:41.250
how did you folks
426
00:25:41.950 --> 00:25:44.290
make how did you folks come up with a design,
427
00:25:45.870 --> 00:25:55.255
that embodies this ease of use? I can only imagine it was it was on purpose. It can't have been just a happy accident. Can it? I I think what,
428
00:25:55.735 --> 00:26:00.020
Matthieu described earlier, it's, and some something I try to do,
429
00:26:00.720 --> 00:26:08.665
sometime too is to to say, okay. Forget about or or technically, things can be done, but what would I want to use? It's like a,
430
00:26:09.605 --> 00:26:10.905
design driven development.
431
00:26:11.205 --> 00:26:16.049
You you say, okay. I want to use something like this. Let's let's imagine it's possible.
432
00:26:16.669 --> 00:26:22.370
And then we then then you you you write the code that you would want to write,
433
00:26:22.695 --> 00:26:26.395
and, when you can you try to make it happen. It's a just
434
00:26:26.935 --> 00:26:35.679
to put some some code. What would wouldn't it be wouldn't it be nice if this code worked this way? Just and I think that's something very.
435
00:26:36.540 --> 00:26:41.760
But when when I write Python, something some a lot of time, I don't have to look at the documentation.
436
00:26:42.465 --> 00:26:43.365
I I
437
00:26:43.665 --> 00:26:44.565
say, what if
438
00:26:45.185 --> 00:26:58.530
it worked this way that would be that would just be nice, and you want it on this works, And that's I I think what's the pleasure of Python is that things just comes naturally. You don't have to to to check the people
439
00:26:59.125 --> 00:27:01.304
for for the long a lot of time about
440
00:27:01.605 --> 00:27:11.450
how, what would be the most natural way to do 1 thing. And you can come up with it and be right 90% of the time. And I think
441
00:27:12.230 --> 00:27:13.690
building the the API
442
00:27:14.150 --> 00:27:14.810
this way
443
00:27:15.174 --> 00:27:18.315
is just the the what I would call,
444
00:27:18.934 --> 00:27:19.915
call Pythonic.
445
00:27:20.294 --> 00:27:20.794
So
446
00:27:23.270 --> 00:27:24.730
you you can just avoid
447
00:27:25.909 --> 00:27:26.409
experiment
448
00:27:26.710 --> 00:27:27.210
experimenting
449
00:27:27.510 --> 00:27:28.409
with API
450
00:27:29.190 --> 00:27:33.774
even before building it. I I think it's the key for this.
451
00:27:34.794 --> 00:27:38.815
This is what my experience I'm being with Kiwi in terms of designing.
452
00:27:39.195 --> 00:27:41.180
What we generally do is, first
453
00:27:41.740 --> 00:27:42.720
of all, look into
454
00:27:43.100
--> 00:27:44.800
how it's been done in other interfaces.
455
00:27:45.180 --> 00:27:45.920
For example,
456
00:27:46.380 --> 00:27:49.920
let's see how something is implemented in Android or in
457
00:27:50.300 --> 00:27:50.800
Qt.
458
00:27:52.085 --> 00:27:57.945
But after that, after first looking into how it's done in other places, we generally tend to ask ourselves
459
00:27:59.070 --> 00:28:02.770
how would it be more intuitive? How would it be simpler, and
460
00:28:03.550 --> 00:28:07.730
how can it be made in such a way that it can be, you know, just
461
00:28:08.575 --> 00:28:11.875
something that clicks into your mind and something that you can just,
462
00:28:12.655 --> 00:28:14.675
write down without having to look at the documentation.
463
00:28:15.919 --> 00:28:16.580
And, generally,
464
00:28:16.960 --> 00:28:21.220
if you what we do normally try to do is pass everything to
465
00:28:21.679 --> 00:28:22.660
Tito or Matthew
466
00:28:23.039 --> 00:28:24.980
for that matter, and that's what is
467
00:28:25.475 --> 00:28:27.095
on IRC, we call him Theater.
468
00:28:27.955 --> 00:28:30.695
So he generally makes it very simple
469
00:28:31.635 --> 00:28:45.195
and figured out how it should generally be, and he has an art for it for making things as simple as possible. Even if the rest of us miss it, if it goes through him, it's simply divide to such a,
470
00:28:45.675 --> 00:28:48.015
such a place that, you know, it just
471
00:28:48.395 --> 00:28:49.615
becomes very simple,
472
00:28:49.919 --> 00:28:50.580
very straightforward
473
00:28:50.960 --> 00:28:52.179
for anyone to use.
474
00:28:53.120 --> 00:28:54.179
Cool. Thanks.
475
00:28:55.840 --> 00:28:56.340
Yeah.
476
00:28:57.360 --> 00:28:58.340
I have some problems.
477
00:29:00.215 --> 00:29:04.235
So what are some of the biggest challenges that you have experienced
478
00:29:04.535 --> 00:29:15.715
in building Kivy both, you know, either early on or most recently some of the biggest challenges that you've come across whether it's in the design or the actual development or maybe in, making
479
00:29:16.095 --> 00:29:17.715
it making it performant enough?
480
00:29:18.895 --> 00:29:21.554
I think performance is definitely the biggest 1 there.
481
00:29:22.480 --> 00:29:23.300
Biggest challenge.
482
00:29:24.320 --> 00:29:26.340
It's really hard to get everything to work
483
00:29:27.040 --> 00:29:32.095
the right way and get it all fast and everything, especially when you get on to these mobile devices where we're kind of
484
00:29:32.395 --> 00:29:35.855
almost trying to put a square peg in a round hole by putting Python on
485
00:29:36.155 --> 00:29:38.495
these Java based Android devices.
486
00:29:39.595 --> 00:29:40.095
But
487
00:29:41.140 --> 00:29:44.520
really I think that's the biggest challenge is just getting it
488
00:29:44.980 --> 00:29:46.760
to work and be fast
489
00:29:48.660 --> 00:29:49.960
in that native speed.
490
00:29:51.125 --> 00:29:57.065
And on desktop, it's pretty good most of the time, but on on the the mobile devices, it's a little harder.
491
00:29:58.250 --> 00:30:01.310
I bet. I mean, to me, that's that was 1 of the things that really
492
00:30:01.690 --> 00:30:11.505
blew my socks off about Kivi is that this 1 toolkit works so well on the desktop, on mobile phones, on mobile tablets. I mean, that is an achievement unto itself.
493
00:30:12.500 --> 00:30:17.240
When you compare it to Java, where Java is really all about being heavily multi threaded,
494
00:30:17.940 --> 00:30:24.865
and that's what these devices are made to do is these heavily multi threaded applications, and we have this Python application that's stuck in 1 thread.
495
00:30:25.485 --> 00:30:26.285
Yeah. And that
496
00:30:27.485 --> 00:30:30.465
And on it, I have a word about it. Even if
497
00:30:31.070 --> 00:30:31.810
I I talk,
498
00:30:32.350 --> 00:30:33.550
the kid about it,
499
00:30:34.030 --> 00:30:36.130
2 years ago, but still
500
00:30:36.510 --> 00:30:41.105
all the current solution that is going on the community, like, it's
501
00:30:42.445 --> 00:30:44.545
not going to work for us in mobile.
502
00:30:45.085 --> 00:30:49.230
K? They have a good solution that works that will work only on desktop.
503
00:30:50.090 --> 00:30:54.190
If you want to do mobile development, this is not how you need to think.
504
00:30:54.490 --> 00:30:56.670
And I'm very, very, very sad
505
00:30:57.865 --> 00:30:59.885
to to see that there is absolutely,
506
00:31:01.865 --> 00:31:05.325
no consideration about mobile development in the Python community,
507
00:31:05.780 --> 00:31:06.840
except for us.
508
00:31:07.460 --> 00:31:08.120
It's like
509
00:31:08.580 --> 00:31:12.520
3 weeks ago or yes. 3 weeks ago, I got an invitation
510
00:31:12.820 --> 00:31:15.240
to be part of the language
511
00:31:15.855 --> 00:31:16.355
summit,
512
00:31:17.455 --> 00:31:19.075
on TICON. Mhmm. And
513
00:31:19.375 --> 00:31:21.155
because they wanted to talk about
514
00:31:21.695 --> 00:31:22.675
the mobile app,
515
00:31:23.000 --> 00:31:26.539
In the end, there is absolutely no discussion about it. Still,
516
00:31:26.840 --> 00:31:29.659
there is so much thing to do on the language itself.
517
00:31:30.405 --> 00:31:36.025
Can you imagine, like, right now, to be able to support Android, we still need to patch Python
518
00:31:36.645 --> 00:31:38.585
to be able to cross compile it.
519
00:31:38.950 --> 00:31:43.050
This is not something that is supported from the start in the language.
520
00:31:43.750 --> 00:31:44.970
So it can
521
00:31:46.045 --> 00:31:47.505
might not be something
522
00:31:47.805 --> 00:31:51.585
that you can understand or or or realize. But
523
00:31:52.045 --> 00:32:01.130
for me, having a language that I need to patch to change to be able to support a new platform like Android, and it's like Linux or being able to
524
00:32:01.510 --> 00:32:02.490
to compile for
525
00:32:02.950 --> 00:32:03.850
from my
desktop
526
00:32:04.230 --> 00:32:05.130
doesn't look
527
00:32:06.284 --> 00:32:12.385
great. Right? And this is 1 of the step. There's so many other step. And then fixing the JIEL,
528
00:32:13.080 --> 00:32:18.700
a lot of, Evan Giddos say it's not an issue, etcetera. We on Android, there is no multiprocessing,
529
00:32:19.975 --> 00:32:24.155
and you will never been able to use it because this is not out.
530
00:32:24.455 --> 00:32:24.955
So
531
00:32:25.575 --> 00:32:34.080
Yeah. They they don't want it. They they don't want it. I I tried to I spent, in early week trying to make it work, like, 2 years ago, and and,
532
00:32:34.780 --> 00:32:38.135
in the end, I understood that it wouldn't work because
533
00:32:38.755 --> 00:32:39.255
there's
534
00:32:39.794 --> 00:32:47.370
a system feature that is lacking, and the Android dev don't want it into because that will that could be a performance problem.
535
00:32:47.670 --> 00:32:50.090
So there's there's just no way
536
00:32:50.390 --> 00:32:52.330
for for Yes. So to communicate
537
00:32:52.774 --> 00:32:57.034
and, and to and to to do what's what's needed for multiprocessing.
538
00:32:57.654 --> 00:32:59.274
So you just can't have it.
539
00:32:59.575 --> 00:33:14.144
So you have to find over solution, indeed. And we have services to to to delay to put task in in the background, but it's clearly not enough. We are we have to find This is not this is absolutely not enough. Let's say you have a request,
540
00:33:15.245 --> 00:33:16.304
you are doing some
541
00:33:16.924 --> 00:33:19.184
I don't know. You you are loading images
542
00:33:19.990 --> 00:33:20.570
in synchronously.
543
00:33:21.190 --> 00:33:23.450
Okay? So you are putting time,
544
00:33:23.909 --> 00:33:26.570
for getting your data from the web,
545
00:33:27.725 --> 00:33:30.304
decoding it, the PNG into RGBA,
546
00:33:30.684 --> 00:33:37.820
uploading it into the GPU, etcetera. There is 1 part we can make it a little bit faster with with threads.
547
00:33:38.120 --> 00:33:40.140
But because it's threads and it's,
548
00:33:40.680 --> 00:33:41.900
a Python threads,
549
00:33:42.915 --> 00:33:48.055
it's the same as having just a callback in the clock on your main thread?
550
00:33:48.675 --> 00:33:51.340
It's it's actually worse. Or threads just
551
00:33:51.900 --> 00:33:56.720
they are just good to to avoid blocking the UI, but they won't make anything faster,
552
00:33:57.179 --> 00:34:09.205
except if you are able to to release the deal. But you have to go very low level for that. So it's not and you have to it's very limited. You can't do a lot without the deal. So
553
00:34:10.010 --> 00:34:10.510
Yes.
554
00:34:10.890 --> 00:34:16.670
And I don't so if anybody remember about the the project I heard about, and
555
00:34:17.515 --> 00:34:20.174
somebody is trying to solve that
556
00:34:20.714 --> 00:34:22.734
by starting 1 interpreter
557
00:34:23.434 --> 00:34:24.734
for each call.
558
00:34:25.490 --> 00:34:25.990
Okay?
559
00:34:26.290 --> 00:34:27.830
And he's able
560
00:34:28.210 --> 00:34:32.390
to move object, Python object, from 1 interpreter to another.
561
00:34:33.075 --> 00:34:33.575
I
562
00:34:34.035 --> 00:34:35.974
I didn't know about this. And
563
00:34:36.275 --> 00:34:37.895
so in that way,
564
00:34:38.195 --> 00:34:41.734
we might be able to do some work on 1 interpreter completely
565
00:34:42.060 --> 00:34:43.520
separated on 1 core
566
00:34:44.060 --> 00:34:51.355
but in the same process. And when you're done with it, you can put an op the object on the queue and get it on the first
567
00:34:52.055 --> 00:34:52.555
thread
568
00:34:53.575 --> 00:34:55.595
without any cost, without any deal.
569
00:34:55.975 --> 00:34:59.435
That will be awesome if it's actually work on mobile.
570
00:34:59.890 --> 00:35:01.670
It can be a solution for us.
571
00:35:02.210 --> 00:35:06.470
It sounds like to me, it it you know, it's really interesting hearing you guys talk about that.
572
00:35:07.545 --> 00:35:13.645
I've kind of I was a Ruby person before I was a Python person. I've been into Python now for 4 or 5 months,
573
00:35:13.945 --> 00:35:16.980
and I I saw many of the same discussions
574
00:35:17.280 --> 00:35:19.700
over there. Like, you know, it seems like
575
00:35:20.160 --> 00:35:26.635
the old school dynamic languages are all kinda struggling with these same issues. They don't really transition very well to the platforms,
576
00:35:27.415 --> 00:35:32.470
and they don't really have a good concurrency story. They really don't do threading very well.
577
00:35:32.950 --> 00:35:42.425
Anyway, it seems like it seems like hope you know, there there should be, like, either a new generation of of these languages or maybe some new language that supports these paradigms out of the box.
578
00:35:43.945 --> 00:35:44.445
Yeah.
579
00:35:45.785 --> 00:35:46.685
If if you
580
00:35:47.065 --> 00:35:51.770
if you want to support multiple calls and to to be able to to transition
581
00:35:52.230 --> 00:35:53.210
to share memory,
582
00:35:54.310 --> 00:35:55.370
this way, yeah,
583
00:35:55.990 --> 00:35:57.210
very dynamic languages
584
00:35:58.285 --> 00:36:00.625
are are not really able to to help. So,
585
00:36:01.085 --> 00:36:02.305
not yet. Maybe
586
00:36:02.845 --> 00:36:04.545
there is some discussion.
587
00:36:05.380 --> 00:36:05.880
Absolutely.
588
00:36:06.420 --> 00:36:09.880
So if you folks were to start the project over, what would you do differently?
589
00:36:12.135 --> 00:36:15.435
I suppose, if you don't mind, I'd like to mention 1 thing.
590
00:36:15.735 --> 00:36:24.430
Okay. 1 advantage of Kiwi on par on, mobile essentially is that the whole UI is based on open g s. I don't think we've talked about that.
591
00:36:25.049 --> 00:36:27.710
But because of that, essentially, what happens is,
592
00:36:28.745 --> 00:36:31.165
you know, anything that is based in graphics is
593
00:36:31.705 --> 00:36:32.925
essentially very fast.
594
00:36:33.305 --> 00:36:36.285
And if you really want to do do some share this
595
00:36:36.700 --> 00:36:41.760
and stuff like that. That part is not worked on by anything. So
596
00:36:42.220 --> 00:36:45.120
Yeah. That is 1 of the advantages that is, you know,
597
00:36:46.225 --> 00:36:47.585
not available in other,
598
00:36:47.985 --> 00:36:48.485
languages.
599
00:36:48.785 --> 00:36:49.285
We
600
00:36:49.665 --> 00:36:50.405
in TV,
601
00:36:51.105 --> 00:36:55.100
shear is in, effects, that you shared is up made very easy.
602
00:36:55.500 --> 00:36:56.000
Implement
603
00:36:56.940 --> 00:37:03.680
Alexander Taylor. He did a effect widget and even before that using shear is was pretty easy in Kiwi.
604
00:37:04.295 --> 00:37:04.795
So
605
00:37:05.575 --> 00:37:06.475
in that sense
606
00:37:07.335 --> 00:37:08.155
on mobiles
607
00:37:08.535 --> 00:37:15.340
many things can be made very easy so if you were let's say doing anything related to, Open GL or,
608
00:37:16.280 --> 00:37:17.340
graphics directly,
609
00:37:17.720 --> 00:37:19.100
that wouldn't be bogged down.
610
00:37:19.535 --> 00:37:20.275
But it's
611
00:37:21.535 --> 00:37:24.115
this is 1 example of the design we choose.
612
00:37:24.494 --> 00:37:25.234
It's like
613
00:37:25.535 --> 00:37:26.515
not showing
614
00:37:26.850 --> 00:37:28.070
OpenGL to the users.
615
00:37:28.530 --> 00:37:31.830
And even if if it's not fully complete,
616
00:37:32.290 --> 00:37:34.150
like, there is still a lot of
617
00:37:34.450 --> 00:37:36.150
room for improvement here.
618
00:37:36.615 --> 00:37:38.474
But still, we have
619
00:37:38.775 --> 00:37:40.714
simple class that you can just
620
00:37:41.174 --> 00:37:43.994
use it to build your graphics, and all the OpenGL
621
00:37:44.295 --> 00:37:52.410
is optimized and done in the background. It's completely transparent, and this is what is making Kibbe on the graphic fast.
622
00:37:52.875 --> 00:37:56.895
Even if some people are making even faster with new project,
623
00:37:57.355 --> 00:38:01.050
still, the the initial solution is quite better than
624
00:38:01.990 --> 00:38:06.650
the other 1 can be. And and it it's it's actually a pretty thin wrapper.
625
00:38:07.005 --> 00:38:14.625
It's not very hard to to go around it and to to poke at the low level. And, there's I think that that's something
626
00:38:15.005 --> 00:38:23.210
that's quite a success to in the in the design, that you you can you you can easily use very advanced features, like stencil
627
00:38:23.830 --> 00:38:24.330
or
628
00:38:24.805 --> 00:38:25.305
or
629
00:38:26.405 --> 00:38:26.905
touching
630
00:38:28.405 --> 00:38:28.905
graphics,
631
00:38:29.765 --> 00:38:30.265
textures,
632
00:38:30.565 --> 00:38:31.785
or making them wrap,
633
00:38:32.400 --> 00:38:33.700
or more modifying,
634
00:38:35.200 --> 00:38:35.780
to change
635
00:38:36.160 --> 00:38:37.540
and building mesh mesh
636
00:38:38.000 --> 00:38:44.005
or things like this. And but it's very, very easy to just go To do the same thing in raw OpenGL,
637
00:38:44.865 --> 00:38:50.485
would be like, for well, it's a nightmare for for simple minded people like me.
638
00:38:53.370 --> 00:38:53.870
So
639
00:38:54.810 --> 00:38:56.270
but about about performances,
640
00:38:56.970 --> 00:39:03.915
yeah. The the graphic part is is is very great. It's not not the issue. You can can do a lot if you manage to
641
00:39:04.295 --> 00:39:07.035
to to to be careful about the important parts.
642
00:39:07.335 --> 00:39:12.369
It you can do a lot because you have all the full power of the of the g p GPU.
643
00:39:13.390 --> 00:39:13.890
What's
644
00:39:14.190 --> 00:39:18.130
hard is is if you have number crunching or a lot of
645
00:39:19.055 --> 00:39:22.675
AV operations to do in the background. So that's that's
646
00:39:23.375 --> 00:39:24.595
a bit a bit harder.
647
00:39:25.270 --> 00:39:30.810
Yeah. Most of the time, this is you could you'll Python that you can make this,
648
00:39:31.510 --> 00:39:32.810
the application slow.
649
00:39:34.655 --> 00:39:36.895
If you are building a UI with,
650
00:39:37.295 --> 00:39:39.555
1, 000 widgets, you might
651
00:39:39.855 --> 00:39:40.755
have an issues,
652
00:39:41.535 --> 00:39:43.395
with it on mobile. Instead,
653
00:39:43.775 --> 00:39:45.800
if you are able to
654
00:39:46.580 --> 00:39:50.680
write 1 widget that can manage the 100 behind,
655
00:39:51.220 --> 00:39:53.240
let's say if the 100 were,
656
00:39:54.484 --> 00:39:54.984
blocks
657
00:39:55.684 --> 00:39:57.704
on 2 d games, I don't know,
658
00:39:58.164 --> 00:39:58.984
or maze,
659
00:39:59.924 --> 00:40:05.359
so you can find a way to manage it yourself, not using the Kiwi widget. Then
660
00:40:05.660 --> 00:40:06.800
you will,
661
00:40:08.060 --> 00:40:09.440
execute less Python,
662
00:40:09.825 --> 00:40:11.925
and the graphic bar will just follow
663
00:40:13.265 --> 00:40:16.405
as you want. Yeah. I think that's what, is
664
00:40:17.345 --> 00:40:17.845
is
665
00:40:18.190 --> 00:40:19.890
pushing a lot on Kivant
666
00:40:20.910 --> 00:40:23.010
to do the for game development.
667
00:40:23.390 --> 00:40:32.605
We have still a lot of work on it, but it's very promising for every game development with Kivi. It's again further to Kivi. Yes. It's a very good project.
668
00:40:34.080 --> 00:40:35.760
To answer the question on,
669
00:40:36.240 --> 00:40:39.700
what we would change in the project, if we were to start from,
670
00:40:40.400 --> 00:40:41.380
scratch today,
671
00:40:41.765 --> 00:40:44.164
I think we already discussed about this.
672
00:40:44.885 --> 00:40:48.585
We were essentially looking for changes that we need to do in a major,
673
00:40:49.500 --> 00:40:55.040
release, let's say. So something like 2 0. And for that, we discussed on things like this. Essentially,
674
00:40:55.500 --> 00:40:58.365
1 of the major drawback as we discussed discussed earlier
675
00:40:58.825 --> 00:40:59.965
is the concurrency.
676
00:41:00.905 --> 00:41:07.619
So I would hope we would be somehow able to solve that issue because that is 1 of the major issues
677
00:41:08.240 --> 00:41:09.460
considering even,
678
00:41:09.839 --> 00:41:14.635
your smart word is gonna have multiple codes. But you should be able to take advantage of that.
679
00:41:15.495 --> 00:41:16.795
About that, just
680
00:41:17.335 --> 00:41:25.910
1 word is I was talking about it on, earlier on IRC. It's about React dot GS, and I read few things about React,
681
00:41:26.850 --> 00:41:27.350
native.
682
00:41:27.775 --> 00:41:29.475
So it's a project from Facebook
683
00:41:30.015 --> 00:41:31.235
that JavaScript
684
00:41:31.535 --> 00:41:32.835
is driving UI,
685
00:41:34.015 --> 00:41:35.395
the UI of your application.
686
00:41:36.495 --> 00:41:36.995
And
687
00:41:37.920 --> 00:41:43.059
the way it work on the native part is, like, they're they have a thread
688
00:41:43.520 --> 00:41:44.980
executing the UI.
689
00:41:45.484 --> 00:41:47.505
But also UI is driven
690
00:41:47.885 --> 00:41:48.785
from JavaScript
691
00:41:49.165 --> 00:41:50.305
on another thread.
692
00:41:51.885 --> 00:41:54.704
If you think about Android, they do the same.
693
00:41:55.070 --> 00:41:57.730
They have a UE thread. They have a that,
694
00:41:59.470 --> 00:42:02.690
is right that run on UE thread. So you can
695
00:42:03.085 --> 00:42:05.585
drag your UE thread, and you have threads
696
00:42:06.125 --> 00:42:09.745
around it that can control and push things into your UI.
697
00:42:10.045 --> 00:42:12.785
This is something we completely miss in Qlik
698
00:42:13.309 --> 00:42:14.049
by design.
699
00:42:14.750 --> 00:42:15.250
And
700
00:42:16.109 --> 00:42:16.609
our
701
00:42:18.109 --> 00:42:20.690
biggest thing is because we are using opengl
702
00:42:21.925 --> 00:42:22.665
and OpenGL
703
00:42:23.005 --> 00:42:23.505
require
704
00:42:23.845 --> 00:42:24.345
you
705
00:42:24.685 --> 00:42:25.185
to
706
00:42:25.525 --> 00:42:28.105
execute all the commands in the main thread.
707
00:42:28.484 --> 00:42:31.225
If you think about shared context, etcetera,
708
00:42:31.710 --> 00:42:33.250
we can't go this way
709
00:42:33.550 --> 00:42:34.050
because,
710
00:42:34.910 --> 00:42:37.490
we have a lot of platforms to support,
711
00:42:38.109 --> 00:42:38.609
and
712
00:42:39.205 --> 00:42:41.305
means we cannot just use it.
713
00:42:41.845 --> 00:42:50.360
So we are stuck with this approach right now, and we we would need to redesign it from scratch. It will integrate with Ashcase that
714
00:42:51.620 --> 00:43:04.015
maybe trying to find a way of having a thread just displaying the UI and focus on that, loading the images, doing all the OpenGL and then having your main thread
715
00:43:04.315 --> 00:43:05.215
driving it.
716
00:43:06.040 --> 00:43:12.540
We might get better performance. But, again, you cannot assume it unless you have an experiment about it.
717
00:43:13.375 --> 00:43:15.075
Yeah. But would it be hard,
718
00:43:15.454 --> 00:43:17.555
currently, for example, to say, okay.
719
00:43:18.575 --> 00:43:20.175
I I put every every
720
00:43:20.940 --> 00:43:25.280
everything in the all all my logic in separate thread, and I only,
721
00:43:26.060 --> 00:43:27.599
everything that will change
722
00:43:28.060 --> 00:43:29.440
the property that affect
723
00:43:31.005 --> 00:43:31.505
widget
724
00:43:31.805 --> 00:43:33.585
is, like, you know, call call
725
00:43:34.365 --> 00:43:35.825
call later, call
726
00:43:36.285 --> 00:43:37.425
schedule once,
727
00:43:37.885 --> 00:43:40.610
would would it you think it would be a lot of work?
728
00:43:41.330 --> 00:43:43.270
It will be a lot of work. Yeah. Okay.
729
00:43:44.450 --> 00:43:46.150
So what are some of the most interesting
730
00:43:46.530 --> 00:43:49.510
or strange things that you've seen to be used for?
731
00:43:51.115 --> 00:43:53.775
I think the coolest thing I've seen to be used for
732
00:43:54.075 --> 00:43:57.055
is what Gabrielle works on at work.
733
00:43:57.595 --> 00:44:01.040
That object is stable. That's just Yeah. Really cool.
734
00:44:01.980 --> 00:44:12.285
Well, if if you want, well, I I can thanks a lot for for the props. Yeah. I'll I'll I'll explain a little for for people. So we are I I I may be a bit
735
00:44:12.665 --> 00:44:18.525
unusual, because I'm 1 of the people not using currently Kiwi for mobile or platforms.
736
00:44:18.970 --> 00:44:20.830
I'm using it on big tables,
737
00:44:21.770 --> 00:44:22.270
like,
738
00:44:23.210 --> 00:44:24.110
giant iPads
739
00:44:24.410 --> 00:44:24.730
from,
740
00:44:25.610 --> 00:44:27.470
40 to 80 inches
741
00:44:27.915 --> 00:44:28.115
the
742
00:44:31.475 --> 00:44:33.415
so so we are putting
743
00:44:33.955 --> 00:44:36.695
key key application on on on these tables,
744
00:44:37.120 --> 00:44:38.580
and, we are using
745
00:44:39.280 --> 00:44:41.940
the the the point that objects
746
00:44:42.400 --> 00:44:43.620
are to do
747
00:44:44.080 --> 00:44:46.325
when we put them on the table
748
00:44:46.705 --> 00:44:48.725
and, to to detect the features.
749
00:44:49.265 --> 00:44:52.005
And, this way, we we we check about
750
00:44:52.385 --> 00:44:54.165
the the ID of the object,
751
00:44:54.510 --> 00:44:56.609
and you we use protocol
752
00:44:56.990 --> 00:44:57.490
TUIO
753
00:44:58.109 --> 00:44:58.770
to send
754
00:45:00.430 --> 00:45:01.010
this data
755
00:45:01.390 --> 00:45:03.809
to other applications. So this way, we can build
756
00:45:04.505 --> 00:45:06.765
application that make use of objects.
757
00:45:07.305 --> 00:45:12.170
And, this is all done in TV, so it's quite cool, I admit.
758
00:45:12.790 --> 00:45:13.430
It's but,
759
00:45:14.470 --> 00:45:19.930
I've I've seen a lot of cool things done done with Kivi, and the things I didn't
760
00:45:20.485 --> 00:45:24.505
have an idea that people will do. There's a project
that is using Kiwi
761
00:45:24.965 --> 00:45:25.465
for
762
00:45:26.325 --> 00:45:26.965
for commanding,
763
00:45:28.060 --> 00:45:31.920
sending commands to to telemetry equipments for for
764
00:45:33.100 --> 00:45:34.560
cars and the prototypes
765
00:45:35.340 --> 00:45:36.720
adjusting. We are
766
00:45:37.255 --> 00:45:40.555
TV being used for educational gains, for,
767
00:45:41.734 --> 00:45:42.555
for children.
768
00:45:42.935 --> 00:45:44.715
There is TV used in
769
00:45:48.760 --> 00:45:49.900
medical equipment,
770
00:45:51.080 --> 00:45:51.400
for indoor
771
00:45:52.840 --> 00:45:54.540
on on Android Android applications
772
00:45:55.480 --> 00:45:55.980
for
773
00:45:56.945 --> 00:45:57.605
for pharmaceutics
774
00:45:57.905 --> 00:45:58.405
or
775
00:45:58.705 --> 00:45:59.845
IV industry.
776
00:46:00.225 --> 00:46:05.820
It is quite cool to see Kiwi used in all sort of places like this. So
777
00:46:06.700 --> 00:46:16.515
the I think what's what cool about it is that the framework doesn't force you in a direct direction. You can you can take it and build what you what you want with it. So
778
00:46:16.975 --> 00:46:18.195
it's it's very interesting.
779
00:46:19.135 --> 00:46:19.635
Yeah.
780
00:46:21.370 --> 00:46:22.590
Is a framework. It's really,
781
00:46:23.370 --> 00:46:25.070
a toolbox for the developer.
782
00:46:25.610 --> 00:46:26.670
You can use it
783
00:46:27.210 --> 00:46:30.030
just you are making buttons, inputs,
784
00:46:30.705 --> 00:46:31.365
scroll view,
785
00:46:31.985 --> 00:46:32.485
etcetera.
786
00:46:33.025 --> 00:46:36.485
Or you can do a complete custom UI, and then
787
00:46:36.865 --> 00:46:37.365
it's
788
00:46:37.665 --> 00:46:40.245
the artist inside you that is picking
789
00:46:41.490 --> 00:46:42.869
Can do anything with it.
790
00:46:43.410 --> 00:46:43.910
Neat.
791
00:46:44.210 --> 00:46:55.425
Gabriel, do you think you'd be willing to or can you I don't know if your work will allow, but, if you can, maybe put a link just to anything that's that's out there about your work project with the big table.
792
00:46:55.964 --> 00:46:57.025
Of course. Of course.
793
00:46:57.579 --> 00:47:06.960
Of course, my work will allow. Yeah. I'll put a I'll put a put a link so people can check what we do. And, yeah, if that's if they enjoy it, that would be great.
794
00:47:08.685 --> 00:47:13.265
Okay. 1 of the coolest things that I've ever seen Kiwi being used for was done by Matthew.
795
00:47:13.805 --> 00:47:14.785
Now he
796
00:47:15.130 --> 00:47:17.230
used it for an interactive movie.
797
00:47:17.930 --> 00:47:19.950
What he eventually did was like
798
00:47:21.290 --> 00:47:24.590
Yeah. It was a project last year to tell stories.
799
00:47:26.155 --> 00:47:28.974
I was contracted to be able to
800
00:47:29.674 --> 00:47:32.255
to make a system for displaying movies
801
00:47:32.950 --> 00:47:34.170
k, on the theaters,
802
00:47:34.550 --> 00:47:38.250
and a lot of people in the rules was adding lasers.
803
00:47:39.030 --> 00:47:41.609
And they was able to point out something
804
00:47:41.954 --> 00:47:42.775
on the movies.
805
00:47:43.555 --> 00:47:47.974
K? So we have a infrared camera that is looking on the screen
806
00:47:48.595 --> 00:47:52.970
and we are able to analyze them and put it back into the movies.
807
00:47:54.630 --> 00:47:56.570
So there is multiple movies.
808
00:47:56.870 --> 00:47:57.770
1 is
809
00:47:58.915 --> 00:47:59.655
like, say,
810
00:48:00.755 --> 00:48:07.095
it's a boy who is trying to let a girl, but he want to show it's the best
811
00:48:07.395 --> 00:48:08.215
boy ever.
812
00:48:08.630 --> 00:48:16.010
So every step, he's trying to do something like drinking the beer faster by his friends. And to drink the beer faster,
813
00:48:16.470 --> 00:48:17.450
all the audience
814
00:48:18.145 --> 00:48:21.605
must put the pointer on the beer of the heroes
815
00:48:21.985 --> 00:48:24.245
and move the pointer as fast as possible
816
00:48:24.625 --> 00:48:26.645
until there is no more beer. Okay.
817
00:48:26.960 --> 00:48:32.260
And then gain some points, and there is another game when the audience
818
00:48:32.640 --> 00:48:33.460
must follow
819
00:48:33.760 --> 00:48:34.420
a shape
820
00:48:34.744 --> 00:48:36.204
and the shape is starting
821
00:48:36.664 --> 00:48:37.404
to shrink
822
00:48:37.785 --> 00:48:48.870
more and more and more. And if there is too much pointer of size or shape, then you'll you'll lost. Or if all the onions stay in the shape, you win, etcetera. So you get the ID.
823
00:48:49.970 --> 00:48:54.485
And at the end, you have, an amount of points, and depending of the points,
824
00:48:54.945 --> 00:48:57.285
the plot is not the same at the end.
825
00:48:58.705 --> 00:49:02.085
This is 1 1 usage of Qb really,
826
00:49:02.450 --> 00:49:04.790
yeah, really fun and interesting to explore.
827
00:49:06.210 --> 00:49:09.349
I don't suppose by any chance you have a link to that that you can share?
828
00:49:09.890 --> 00:49:10.390
Yes.
829
00:49:10.930 --> 00:49:11.430
Excellent.
830
00:49:12.755 --> 00:49:13.735
That'd be great.
831
00:49:14.355 --> 00:49:14.855
So
832
00:49:15.315 --> 00:49:19.815
what are some of the changes and features that you're particularly excited about in the future of Kibby?
833
00:49:20.350 --> 00:49:20.850
I
834
00:49:21.230 --> 00:49:25.010
think a big thing is gonna be getting in some multi language support.
835
00:49:26.990 --> 00:49:27.490
Allowing
836
00:49:27.870 --> 00:49:30.815
right to left text and reshaping of some of these,
837
00:49:31.835 --> 00:49:32.815
Eastern scripts
838
00:49:33.515 --> 00:49:36.655
where a character looks different when it's next to
839
00:49:36.955 --> 00:49:38.095
a certain character
840
00:49:39.359 --> 00:49:41.619
and just opening up Kivi to more people
841
00:49:41.920 --> 00:49:42.819
in that way
842
00:49:43.200 --> 00:49:44.900
Yeah. That can work in their language.
843
00:49:45.519
--> 00:49:47.295
So that's Yeah. That's an
844
00:49:47.675 --> 00:49:49.934
interesting challenge because a lot of,
845
00:49:51.275 --> 00:49:56.335
text is actually quite complicated to display, and we're doing It is. Everything in
846
00:49:56.830 --> 00:50:00.530
in Open GL means we have a lot of the burden, on us.
847
00:50:00.830 --> 00:50:01.650
So but,
848
00:50:02.190 --> 00:50:03.730
thankfully, there are some libraries
849
00:50:04.030 --> 00:50:06.495
we can make use of, but it's still quite
850
00:50:08.495 --> 00:50:11.475
some work. And even the standard solutions like HarfBuzz,
851
00:50:12.095 --> 00:50:15.940
there's virtually no documentation for it. You just have to go and find
852
00:50:16.420 --> 00:50:16.920
examples,
853
00:50:17.300 --> 00:50:18.760
look at other people's code.
854
00:50:19.300 --> 00:50:21.720
That's really all there is available for us.
855
00:50:23.035 --> 00:50:26.415
In terms of features, we we were essentially looking to,
856
00:50:26.875 --> 00:50:27.455
you know,
857
00:50:27.915 --> 00:50:28.415
change
858
00:50:28.795 --> 00:50:30.235
everything we can in terms of
859
00:50:30.910 --> 00:50:33.570
next, we're looking forward to a 2.0 release.
860
00:50:34.110 --> 00:50:34.930
So, hopefully,
861
00:50:36.590 --> 00:50:37.410
we'll have
862
00:50:37.845 --> 00:50:41.625
not released before that. But for DuPont release, hopefully, we can fix
863
00:50:42.244 --> 00:50:44.265
almost as many issues that we have,
864
00:50:44.805 --> 00:50:45.305
essentially,
865
00:50:45.660 --> 00:50:48.160
for multithreading and extra, other things like that.
866
00:50:48.620 --> 00:50:51.040
And 1 other thing that we didn't talk about was
867
00:50:51.660 --> 00:50:52.160
UI.
868
00:50:52.955 --> 00:50:56.735
Right now, the widget sets that we have are generally started,
869
00:50:57.435 --> 00:51:00.095
something that was geared geared towards desktops.
870
00:51:00.395 --> 00:51:01.375
They weren't really
871
00:51:01.890 --> 00:51:05.110
started from the ground up thinking mobile in mind.
872
00:51:05.570 --> 00:51:09.430
So 1 of the things that I'd like to see come up next is
873
00:51:10.235 --> 00:51:11.535
widgets that are designed,
874
00:51:12.395 --> 00:51:13.775
keeping in mind mobile,
875
00:51:14.395 --> 00:51:17.535
and their speedy and vast performance on
876
00:51:17.915 --> 00:51:18.415
mobile.
877
00:51:20.349 --> 00:51:24.130
Yeah. And integration in in platform specific UIs,
878
00:51:24.510 --> 00:51:28.050
it's something that people ask quite a lot. Even
879
00:51:28.430 --> 00:51:29.650
these days, people
880
00:51:30.335 --> 00:51:33.555
use temps a lot more or as more, like, thankfully,
881
00:51:34.335 --> 00:51:35.075
thanks to
882
00:51:35.375 --> 00:51:38.515
Google Material UI. They understand that they can
883
00:51:38.980 --> 00:51:49.615
design the UI in the way they want, and we give a lot of freedom for that. So they they I think they they they there may be less demand for it in the future.
884
00:51:49.915 --> 00:51:52.415
But even on desktop, for example,
885
00:51:52.715 --> 00:51:56.150
being able to integrate more in the in the
886
00:51:56.450 --> 00:51:58.470
UI as a user is used to,
887
00:51:59.170 --> 00:52:00.550
maybe an important
888
00:52:01.090 --> 00:52:02.230
step to to do.
889
00:52:02.684 --> 00:52:03.904
And even using,
890
00:52:04.365 --> 00:52:06.464
for example, shortcuts or accessibility
891
00:52:06.765 --> 00:52:07.265
features,
892
00:52:07.885 --> 00:52:09.184
there's quite a lot
893
00:52:09.565 --> 00:52:18.880
to do. And I think something to note is that Kiwi, historically, has not been developed with a longer, what, road map.
894
00:52:19.225 --> 00:52:25.005
It was like, oh, I need some I need this. Let's try to add it and see how it works.
895
00:52:25.305 --> 00:52:25.805
And
896
00:52:26.819 --> 00:52:32.039
thinking the design, but 1 step at a time. And so we are there's not a
897
00:52:32.420 --> 00:52:35.955
lot of long term features that we are planning, but
898
00:52:36.435 --> 00:52:39.095
we we we try to do that for 2.0,
899
00:52:39.635 --> 00:52:41.255
as as what I said before.
900
00:52:41.635 --> 00:52:45.335
But, so we have a Wiki page about this. So if people are interested,
901
00:52:46.730 --> 00:52:49.230
we'll we'll try to we'll put a link on that.
902
00:52:50.250 --> 00:52:50.750
Absolutely.
903
00:52:51.930 --> 00:52:53.710
Now may maybe just
904
00:52:56.845 --> 00:52:58.944
I I would like to talk about 1 thing,
905
00:52:59.885 --> 00:53:00.944
about it. It's like
906
00:53:01.724 --> 00:53:03.984
even if the podcast is about TV,
907
00:53:04.580 --> 00:53:08.200
Kiwi is just 1 piece of all the project
908
00:53:08.580 --> 00:53:11.240
that we, as core developer, are managing.
909
00:53:12.935 --> 00:53:13.675
It's like
910
00:53:14.214 --> 00:53:14.714
we,
911
00:53:15.895 --> 00:53:17.835
are doing Python for Android.
912
00:53:18.295 --> 00:53:23.849
It's a separate project that is, is being able to comp you can compile Python
913
00:53:24.230 --> 00:53:25.930
and some of the Python extension
914
00:53:26.790 --> 00:53:28.170
on Android. So
915
00:53:28.485 --> 00:53:34.505
most of the time, you need to patch the extension if you want to be able to combine it. We're exactly the same for,
916
00:53:34.805 --> 00:53:39.200
iOS. It's not Python for iOS because it is a separate project and application,
917
00:53:39.500 --> 00:53:41.600
so we call it Kivi iOS.
918
00:53:41.980 --> 00:53:43.120
We also manage,
919
00:53:44.065 --> 00:53:48.085
we invented actually because there is no good project about it,
920
00:53:49.984 --> 00:53:50.484
library
921
00:53:50.865 --> 00:53:51.684
to use
922
00:53:52.500 --> 00:53:53.560
the native language
923
00:53:53.860 --> 00:54:00.920
of the platform directly from Python. For example, if you want to touch some of the Java API on Android,
924
00:54:02.415 --> 00:54:06.595
Before, it was very complex to get it. It's like
you need to route
925
00:54:06.975 --> 00:54:07.555
a gany,
926
00:54:08.495 --> 00:54:12.069
a wrapper that we call you Java, and so you
927
00:54:12.690 --> 00:54:17.405
will wrap it into a Python extension, and then you can use it. Let's
928
00:54:17.865 --> 00:54:18.365
say
929
00:54:18.825 --> 00:54:23.645
there is absolutely no contribution on this part, then we invented Pygenius.
930
00:54:24.185 --> 00:54:24.685
So
931
00:54:25.060 --> 00:54:25.720
because Java
932
00:54:26.580 --> 00:54:27.400
can instruct,
933
00:54:28.180 --> 00:54:28.680
instruct
934
00:54:29.380 --> 00:54:30.760
I don't Introspect introspect.
935
00:54:31.460 --> 00:54:32.345
Introspect it.
936
00:54:34.265 --> 00:54:35.165
Then we build
937
00:54:35.625 --> 00:54:39.885
that just use the power of the Java language to be able to
938
00:54:40.980 --> 00:54:58.010
do the duck typing as you would do on the Java. And you can call directly methods that even if you didn't import them. This is very cool because we have also another project called the Kiwi remote shell. You just start the Kiwi application on your mobile. It gives you an SSH
939
00:54:58.390 --> 00:54:58.890
server.
940
00:54:59.269 --> 00:55:02.650
Then you can connect onto it. And you have a Python console
941
00:55:02.950 --> 00:55:05.210
where you can start to import Pygenius
942
00:55:05.675 --> 00:55:08.655
and test the Android APIs in lives.
943
00:55:09.355 --> 00:55:12.095
You can create an Android widget in Python
944
00:55:12.395 --> 00:55:13.615
and add it to your
945
00:55:14.589 --> 00:55:15.809
PV application,
946
00:55:16.109 --> 00:55:21.730
etcetera. This is something cool. We don't have the same for iOS, but it can be completely durable.
947
00:55:22.315 --> 00:55:26.575
And the same for what we do for Pygeneus. We do the same for iOS,
948
00:55:27.035 --> 00:55:29.615
with objective c, and it's called Pyogr. G.
949
00:55:30.920 --> 00:55:48.695
So as you can see, kv is only the u v part, but to be able to execute it and allow the user to use a feature on your form. We have also a lot of opportunity. I miss the 1 most important 1, is player. And player is also a good invention because we build
950
00:55:49.150 --> 00:55:51.730
all first step. So the solution
951
00:55:52.190 --> 00:55:52.690
that
952
00:55:53.230 --> 00:55:53.730
the
953
00:55:54.030 --> 00:55:57.970
buyer and buyer is like the wrapper to be able to
954
00:55:58.325 --> 00:56:02.265
call the language the destination language, whichever are object.
955
00:56:02.724 --> 00:56:03.224
Now
956
00:56:03.765 --> 00:56:05.144
we have player,
957
00:56:05.490 --> 00:56:06.309
and it will abstract
958
00:56:07.569 --> 00:56:08.069
all
959
00:56:08.609 --> 00:56:09.109
the
960
00:56:10.130 --> 00:56:11.170
the features of
961
00:56:11.809 --> 00:56:16.505
yeah. Platform specific features. Like, if you want to access to the GPS,
962
00:56:17.525 --> 00:56:18.905
you don't want to write,
963
00:56:19.365 --> 00:56:22.985
specific code
for Android and iOS and other platform.
964
00:56:23.369 --> 00:56:24.589
So we have just,
965
00:56:25.409 --> 00:56:26.509
a facade
966
00:56:27.289 --> 00:56:29.630
as we called, and we have different implementation
967
00:56:32.565 --> 00:56:33.225
pair platform.
968
00:56:33.925 --> 00:56:36.425
And we have that for a lot of things.
969
00:56:38.005 --> 00:56:41.705
That's it. So currently, this is that the future of Kiwi,
970
00:56:43.000 --> 00:56:47.980
it's bad that the question is only for the Kiwi because Mhmm. We did a lot,
971
00:56:48.440 --> 00:56:48.940
outside
972
00:56:49.240 --> 00:56:49.740
Kiwi,
973
00:56:50.235 --> 00:56:54.255
And we have also a card to play on that. As you said, Gabrielle,
974
00:56:55.115 --> 00:56:56.895
people were asking about,
975
00:56:57.835 --> 00:57:00.010
is there a way to make,
976
00:57:00.330 --> 00:57:05.550
to create native interface in Python? And there is absolutely no good alternative,
977
00:57:06.410 --> 00:57:06.910
today.
978
00:57:07.825 --> 00:57:15.444
And we have all the tool to build a new library, not Kivy, because it doesn't work the same, and I'm not sure who
979
00:57:15.860 --> 00:57:19.640
do it with, with it. But if we will start from scratch
980
00:57:20.100 --> 00:57:21.640
like Ionic did,
981
00:57:23.585 --> 00:57:26.005
it's we have all the tool for it.
982
00:57:26.305 --> 00:57:29.765
It might be 1 of the future of the
983
00:57:30.625 --> 00:57:31.925
new Python library.
984
00:57:33.290 --> 00:57:39.710
Yeah. Because we are trying to cover a lot of use cases, and maybe some of it, they are not covered
985
00:57:40.395 --> 00:57:40.895
correctly
986
00:57:41.195 --> 00:57:45.215
in or can't be correctly covered in HTML laundering.
987
00:57:46.075 --> 00:57:51.280
Yeah. We yeah. Said actually a a very, very bad bad thing to to try with
988
00:57:51.580 --> 00:57:55.760
Gmail. Yeah. TV have no tools to be able to do HTML rendering,
989
00:57:56.115 --> 00:57:58.135
And we will not be able to provide,
990
00:57:58.515 --> 00:58:06.210
not soon, not in the future because it's a very big things to have. In Open GL, this is also our
991
00:58:06.510 --> 00:58:07.650
our core issues.
992
00:58:08.109 --> 00:58:14.645
It's it's a big point for us, and this is where all the performance is going on. Because we're in opengl,
993
00:58:15.425 --> 00:58:20.390
try to find the library that works. You can try webit directly. It's just a mess.
994
00:58:20.869 --> 00:58:24.089
And there is project around it that's trying to do it
995
00:58:24.549 --> 00:58:27.130
and it's not going to work on mobile
996
00:58:27.430 --> 00:58:28.650
soon either and
997
00:58:29.085 --> 00:58:30.705
except if you want dependencies
998
00:58:31.085 --> 00:58:37.610
that was you I don't remember how much. 50 megabytes, let's say. Mhmm. Might be even more. Yeah.
999
00:58:37.910 --> 00:58:39.210
But 1 of the things that
1000
00:58:39.750 --> 00:58:41.210
we we we did effectively,
1001
00:58:42.550
--> 00:58:43.450
was the the
1002
00:58:43.830 --> 00:58:45.130
things that are separate
1003
00:58:45.750 --> 00:58:46.250
and
1004
00:58:46.934 --> 00:58:49.595
the Python prompt read, kv, EOS,
1005
00:58:51.015 --> 00:58:52.635
and, player and pygeneus,
1006
00:58:53.174 --> 00:58:54.234
everything is
1007
00:58:54.780 --> 00:58:55.280
separated
1008
00:58:55.580 --> 00:58:58.000
and can be reused. So, indeed,
1009
00:58:58.540 --> 00:59:00.320
we tried not to put everything
1010
00:59:00.620 --> 00:59:00.860
in Kiwi, and,
1011
00:59:02.300 --> 00:59:02.800
and
1012
00:59:03.500 --> 00:59:04.000
so
1013
00:59:04.444 --> 00:59:09.265
people have to have to understand. But if they if they want something in Kiwi,
1014
00:59:09.724 --> 00:59:11.424
in the the Kiwi ecosystem
1015
00:59:12.180 --> 00:59:24.615
and, not everything. They can go and work with us anyway. We we are when we are open to to and we we and we are very open for help in the various project outside of Kiwi. So
1016
00:59:25.075 --> 00:59:27.895
they we can we can come 1 of the best example.
1017
00:59:28.970 --> 00:59:29.690
It's using
1018
00:59:30.250 --> 00:59:32.750
people are using it as an alternative solution
1019
00:59:33.450 --> 00:59:37.150
that's not working very well, and we are very performance on it.
1020
00:59:37.715 --> 00:59:39.495
So there is a lot of contribution
1021
00:59:40.115 --> 00:59:43.655
and a lot of focus on this project. Mhmm. This is awesome.
1022
00:59:45.490 --> 00:59:52.915
That's very cool. The Kibbe remote shell project in particular sounds really, really neat. I mean, I can just envision people sort of
1023
00:59:53.315 --> 00:59:59.335
live coding on their mobile devices from their the the the comfort of their laptop. It sounds really, really nifty.
1024
01:00:00.500 --> 01:00:01.480
Yeah. No. Except
1025
01:00:01.860 --> 01:00:04.120
it's just for testing. You don't
1026
01:00:04.740 --> 01:00:07.240
you have no way to save what you did.
1027
01:00:07.625 --> 01:00:10.845
Just a share. But it it could be improved. It just Yes. As
1028
01:00:11.224 --> 01:00:13.165
a share, but it it could be improved.
1029
01:00:14.025 --> 01:00:15.964
Remember that we are very few
1030
01:00:16.420 --> 01:00:17.079
active contributor.
1031
01:00:17.940 --> 01:00:18.440
Mhmm.
1032
01:00:19.619 --> 01:00:30.555
We and the community is growing, in my point of view, very fast, and we are not a lot to handle everything. We are we are getting so much backlog.
1033
01:00:31.255 --> 01:00:31.755
Yeah.
1034
01:00:32.960 --> 01:00:35.299
Lot more new user than new new contributors.
1035
01:00:35.680 --> 01:00:44.555
But Yeah. And maybe this is something that can keep us because if you are not be able to answer everything and letting all things goes by itself,
1036
01:00:45.175 --> 01:00:46.234
it's not good.
1037
01:00:47.015 --> 01:00:49.730
That's what can we do, Ad? Yeah.
1038
01:00:51.330 --> 01:00:57.670
Well, 1 of the last questions that we have here, I'll save I'll save it for that, but maybe we can maybe we can help with that.
1039
01:00:59.035 --> 01:01:00.575
That would be great.
1040
01:01:01.995 --> 01:01:08.860
So, yeah, before we get to that last question, just 1 more. Wondering if there are any new platforms or operating systems that
1041
01:01:09.420 --> 01:01:15.260
you are looking to add support for such as the Sailfish OS from Jala or the new Ubuntu phone,
1042
01:01:15.580 --> 01:01:16.480
operating system.
1043
01:01:17.945 --> 01:01:20.265
I I've been wanting to to to,
1044
01:01:20.905 --> 01:01:26.660
to help, Ubuntu Ubuntu support, but I've I've had a a few look at it and tried
1045
01:01:27.200 --> 01:01:27.700
when
1046
01:01:28.079 --> 01:01:32.980
we were adding SDR because that was a path to for it. But I didn't
1047
01:01:33.280 --> 01:01:42.174
find the time in the last 6 months to work on it. So if anybody is interested, that will be cool. I'm pretty sure Firefox OS won't be possible,
1048
01:01:42.859 --> 01:01:43.359
but,
1049
01:01:43.900 --> 01:01:44.700
I because
1050
01:01:45.446 --> 01:01:48.000
Don't say don't say impossible.
1051
01:01:49.339 --> 01:01:50.299
Well, it would be
1052
01:01:51.005 --> 01:01:57.665
but if if somebody is able to do it, that would be great. But I don't think Mozilla people would be happy about this. But
1053
01:01:59.645 --> 01:02:04.289
if you have an idea, I I I I I wouldn't say impossible for you. Okay?
1054
01:02:04.670 --> 01:02:04.990
But,
1055
01:02:05.710 --> 01:02:07.329
I think with the question of practicality
1056
01:02:08.270 --> 01:02:09.569
on Firefox OS,
1057
01:02:10.235 --> 01:02:16.015
the specs of the base phone are so low that right now, I think it's not practical.
1058
01:02:16.795 --> 01:02:17.295
Mhmm.
1059
01:02:18.180 --> 01:02:20.680
Yeah. It's very, very is it is it cheaper
1060
01:02:21.060 --> 01:02:24.580
is it cheaper Firefox phone is quite local. It's
1061
01:02:25.060 --> 01:02:26.200
it was low spec.
1062
01:02:26.660 --> 01:02:26.905
Yeah.
1063
01:02:29.545 --> 01:02:43.730
Very cool. So now here is that question that I mentioned previously. This is your opportunity to to rally support to your cause. Is there anything in particular that you would like to ask our listeners to help with? It can be something as simple as,
1064
01:02:44.055 --> 01:02:47.355
you know, you guys need help fixing some documentation
1065
01:02:47.734 --> 01:02:50.714
problems or help dealing with the backlog
1066
01:02:51.015 --> 01:02:51.400
or
1067
01:02:51.960 --> 01:02:54.940
whatever. Like, how can how can our listeners help,
1068
01:02:55.400 --> 01:02:59.020
because Kivi is an awesome project and it deserves it deserves to be supported.
1069
01:03:01.615 --> 01:03:05.315
Well, probably the best way is just people get out there, start using it,
1070
01:03:05.694 --> 01:03:06.835
start figuring out,
1071
01:03:07.135 --> 01:03:11.530
you know, what they like about it, what do they not like, what could
be improved upon it.
1072
01:03:12.150 --> 01:03:13.770
The feedback helps a lot.
1073
01:03:14.390 --> 01:03:18.175
There's always room for help in the documentation and examples especially.
1074
01:03:18.875 --> 01:03:21.135
We allow people complaining there's not enough examples
1075
01:03:21.675 --> 01:03:22.815
of how to do things.
1076
01:03:24.140 --> 01:03:27.599
Yeah. There are a lot of things. They they can try to reproduce bugs
1077
01:03:27.900 --> 01:03:33.345
if they they see something. Maybe some bugs have been resolved and not fixed and not marked as fixed.
1078
01:03:33.905 --> 01:03:35.285
Or if, somebody
1079
01:03:35.585 --> 01:03:36.085
pushed
1080
01:03:36.545 --> 01:03:48.070
a a a a pull request and that nobody finds the time to test it Mhmm. They can say, oh, it works for me too. But that's a lot of help for us because we have confidence that it's we can
1081
01:03:48.450 --> 01:03:53.964
we can check it, and, and, it will probably be a good work to to manage.
1082
01:03:54.345 --> 01:03:55.484
And, yeah,
1083
01:03:56.265 --> 01:03:59.724
giving feedbacks. View is a lot of work on the documentation
1084
01:04:00.600 --> 01:04:03.260
already, but it's a big, big, big documentation.
1085
01:04:03.560 --> 01:04:04.060
So
1086
01:04:04.360 --> 01:04:08.380
it's always great to to to have a look and see maybe things have been
1087
01:04:09.535 --> 01:04:11.795
changed or they they need improvements.
1088
01:04:12.255 --> 01:04:15.714
That's that's always great to to to look. And, anyway,
1089
01:04:16.930 --> 01:04:18.390
I'm sure a lot of people
1090
01:04:19.250 --> 01:04:24.790
use TV and, not sure if they can help, and, they they just have to know, but
1091
01:04:25.385 --> 01:04:29.805
we are very welcoming to to that. We don't always have time to react,
1092
01:04:30.345 --> 01:04:30.845
immediately
1093
01:04:31.385 --> 01:04:33.085
to but we we try.
1094
01:04:33.570 --> 01:04:36.390
Yeah. I'd like to add this thing. Now,
1095
01:04:36.930 --> 01:04:37.430
GSOC
1096
01:04:38.050 --> 01:04:42.545
selection students just ended, and there'll be a lot of students that didn't get through.
1097
01:04:43.085 --> 01:04:46.945
I'd like to tell them, you know, they shouldn't just wait for ESOC.
1098
01:04:47.405 --> 01:04:48.625
If they really want
1099
01:04:48.925 --> 01:04:56.060
to go forward, they should just go ahead and choose the project of their liking. Let's say, if you like Kiwi, just
1100
01:04:56.360 --> 01:04:57.020
go there,
1101
01:04:57.675 --> 01:05:01.215
start contributing to it even if you weren't selected for the SOC.
1102
01:05:01.595 --> 01:05:04.255
Just continue working on project that you're interested
1103
01:05:04.555 --> 01:05:09.860
in. And, you know, just start small. Start with some simple documentation fixes.
1104
01:05:10.400 --> 01:05:17.385
In fact, not this is not just for students. For anyone who's interested in helping out here, we really need a lot of people helping out. And
1105
01:05:17.845 --> 01:05:19.865
if you can just start smaller,
1106
01:05:20.700 --> 01:05:22.880
just add some simple documentation access,
1107
01:05:23.980 --> 01:05:24.559
and GRDF
1108
01:05:24.940 --> 01:05:27.815
makes it very easy. All you have to do is create a login,
1109
01:05:28.675 --> 01:05:30.855
open a web form, just look at the documentation.
1110
01:05:31.315 --> 01:05:34.230
We feel even if it's just as simple as, you
1111
01:05:35.670 --> 01:05:45.185
know, English correction or grammar correction, just go ahead and do it online and then submit. All you have to do is click on the submit button and a new PI submit it. That's it.
1112
01:05:45.805 --> 01:05:50.760
That's how easy it is to get in. Now once you get in and for people who are already
1113
01:05:51.060 --> 01:05:51.700
aware of,
1114
01:05:52.420 --> 01:05:57.880
they're a bit more advanced, they can get into other stuff. You know, slowly either either gradually
1115
01:05:58.875 --> 01:06:07.535
increase your commitment level or if you are comfortable straight away go to the number of open issues on gidhub and see what you can work at.
1116
01:06:08.075 --> 01:06:08.500
And
1117
01:06:09.300 --> 01:06:13.000
I'm mentioning this in terms of GSOC because, you know,
1118
01:06:14.420 --> 01:06:23.355
contributing to any open source project helps. It helps not only the open source project itself, but it also helps you, the contributor, in terms of
1119
01:06:23.894 --> 01:06:30.860
adding to your portfolio. And right now, open source is a very good way to add to your portfolio.
1120
01:06:31.720 --> 01:06:36.300
A lot of the major companies are looking for experience people experience with open source.
1121
01:06:38.655 --> 01:06:40.895
Absolutely. I think it's no accident that,
1122
01:06:41.455 --> 01:06:46.275
LinkedIn now has a very prominent place in your LinkedIn profile to add your GitHub repository.
1123
01:06:47.210 --> 01:06:47.710
Yep.
1124
01:06:49.050 --> 01:06:50.510
Oh, could I miss that?
1125
01:06:51.690 --> 01:06:56.109
I have 2 things to add about it. It's like you guys asking for
1126
01:06:56.465 --> 01:06:59.125
that we are open to all the contribution.
1127
01:07:00.865 --> 01:07:03.445
It's almost the case for everybody.
1128
01:07:04.465 --> 01:07:06.130
A lot of open source project. Right?
1129
01:07:07.089 --> 01:07:09.589
What you are really missing is people that
1130
01:07:09.970 --> 01:07:11.190
are able to
1131
01:07:11.970 --> 01:07:13.910
each time ever step back about
1132
01:07:14.645 --> 01:07:16.505
the feedback of of others
1133
01:07:17.525 --> 01:07:26.320
and giving us a good solution for for it. Because we have so much backlog that even if we have a lot a lot of more contribution, if it's documentation
1134
01:07:26.780 --> 01:07:31.520
issues, most of the time is merged right away because we are always
1135
01:07:32.140 --> 01:07:33.040
great. But
1136
01:07:33.705 --> 01:07:40.925
when you when people are starting just to
ask a little bit of question and then when we have to talk about it,
1137
01:07:41.380 --> 01:07:43.720
it's taking a lot of time for all of us.
1138
01:07:45.140 --> 01:07:46.680
It's will be nice
1139
01:07:47.220 --> 01:07:51.605
if great people also can contribute us directly with solution
1140
01:07:51.985 --> 01:07:53.205
or having,
1141
01:07:54.145 --> 01:07:56.805
asking to maintain a project like
1142
01:07:57.265 --> 01:07:58.565
or for Android,
1143
01:07:59.080 --> 01:08:02.300
just having a a looks from time to time, like,
1144
01:08:03.160 --> 01:08:07.260
7 day per week will be awesome on Python for Android just to
1145
01:08:07.565 --> 01:08:14.545
answer to other people saying, okay, your recipes on the Python 400 is great. You have few things to change, etcetera.
1146
01:08:15.260 --> 01:08:19.199
We, Evan, on the small team cannot handle so much.
1147
01:08:20.940 --> 01:08:23.520
It's already too much, in my
1148
01:08:24.465 --> 01:08:25.845
So we need maintainers
1149
01:08:26.385 --> 01:08:26.885
and,
1150
01:08:28.945 --> 01:08:34.130
and that's 1 of the first points. The second point I I want to raise, if
1151
01:08:35.170 --> 01:08:40.790
if if somebody in the world would like to sponsor us even for the Kiwi Association,
1152
01:08:41.885 --> 01:08:42.785
to be able
1153
01:08:43.405 --> 01:08:47.185
to buy new hardware. The current 1, we are using,
1154
01:08:48.364 --> 01:08:49.585
already too much
1155
01:08:50.320 --> 01:08:54.580
for building our unit test, and Matam, another core developer,
1156
01:08:55.040 --> 01:08:57.780
is trying to use it also for releasing,
1157
01:08:58.639 --> 01:08:59.139
kvnightlies
1158
01:09:00.065 --> 01:09:02.085
as a well built package.
1159
01:09:03.265 --> 01:09:04.245
We are able
1160
01:09:04.625 --> 01:09:07.125
only to run Linux Windows
1161
01:09:07.505 --> 01:09:09.445
when you start to run
1162
01:09:09.840 --> 01:09:10.340
iOS,
1163
01:09:11.440 --> 01:09:12.420
OSX, sorry,
1164
01:09:13.120 --> 01:09:16.820
all the server is crashing. We are very limited by
1165
01:09:17.920 --> 01:09:19.705
the environments we are testing
1166
01:09:20.085 --> 01:09:21.685
on. And I'm sure if we have,
1167
01:09:22.245 --> 01:09:25.864
better hardware, we will be able to choose the.
1168
01:09:26.804 --> 01:09:27.304
Madam,
1169
01:09:27.765 --> 01:09:30.010
we're very happy to push all of it,
1170
01:09:31.030 --> 01:09:38.435
There is Kiwi iOS when I want to do the nightlies, but there is no hardware for it. And at some point, we need also to increase
1171
01:09:39.695 --> 01:09:40.995
our unit test coverage.
1172
01:09:41.695 --> 01:09:56.755
This is very, very low. Every time we move something on the code, even Python 400 on Kibbe, it will it might have an impact somewhere else, and we don't see it. We see it only because an user is reporting us, an issue
1173
01:09:57.135 --> 01:10:06.040
of we as code developer are using a part where we're completing master and then it breaks. This is not cool. This is something that can be seen
1174
01:10:06.500 --> 01:10:10.440
before that, and this is a critical point of the project.
1175
01:10:10.980 --> 01:10:14.945
There is a lot of, lot of widget we need to maintain. We are,
1176
01:10:15.345 --> 01:10:16.245
looking forward,
1177
01:10:16.705 --> 01:10:22.005
forward to the version 2, and we don't have the 2 to be able to do it in
1178
01:10:22.929 --> 01:10:23.830
a in a clean
1179
01:10:24.370 --> 01:10:24.870
way.
1180
01:10:25.889 --> 01:10:37.385
So talking about increasing unit test coverage, it strikes me that that might be a tricky thing for people who say, I wanna help, I wanna dive in. Right? Because in order to test write tests for code,
1181
01:10:37.800 --> 01:10:41.420
have to have a really solid understanding of how it works and what you're testing.
1182
01:10:42.200 --> 01:10:42.700
Yep.
1183
01:10:43.080 --> 01:10:43.820
Not necessarily.
1184
01:10:44.440 --> 01:10:44.940
But
1185
01:10:46.015 --> 01:10:50.035
if I can say, I mean, is that's actually how I started coming,
1186
01:10:50.495 --> 01:10:53.040
helping Kiwi in the very first place
1187
01:10:53.520 --> 01:10:56.800
because I I I found the bag, and I say, okay.
1188
01:10:57.200 --> 01:11:08.035
I I just want to to check if it's ready or bag, and to reduce my my card to very simple. And when it was simple enough to to test, directly, well, it was
1189
01:11:08.335 --> 01:11:20.255
nearly a new unit test, so it could be introduced directly in the in the in the little library. So just doing a little little test case of a simple bug, It's
1190
01:11:20.875 --> 01:11:22.415
already quite helpful, actually.
1191
01:11:22.955 --> 01:11:30.960
If you if you look at a bug report and you generate a a news a test case for it, it's a it's a very, very, very cool contribution.
1192
01:11:32.780 --> 01:11:36.935
Well, I'd like I won't like to discourage anyone from use writing unit
1193
01:11:37.415 --> 01:11:43.035
test case directly, but I think what the, Matthew was hinting at was
1194
01:11:43.540 --> 01:11:45.239
we recently added a
1195
01:11:46.980 --> 01:11:49.320
link on our web page for donation
1196
01:11:50.179 --> 01:11:50.679
directly.
1197
01:11:51.304 --> 01:11:52.684
We, lack the hardware,
1198
01:11:52.985 --> 01:11:55.565
and we would definitely love to get some
1199
01:11:55.945 --> 01:11:57.164
new hardware for testing.
1200
01:11:57.545 --> 01:11:58.045
And
1201
01:11:58.450 --> 01:12:02.150
as he said, we need, new hardware to be able to,
1202
01:12:02.610 --> 01:12:04.790
you know, set up nightly packages
1203
01:12:05.170 --> 01:12:06.135
for testers
1204
01:12:06.675 --> 01:12:09.335
and stuff like that. We need a lot more,
1205
01:12:10.275 --> 01:12:12.215
influx in terms of money also.
1206
01:12:14.060 --> 01:12:16.720
So if best way would be if someone would hire,
1207
01:12:17.420 --> 01:12:18.400
Matthew directly,
1208
01:12:18.780 --> 01:12:20.560
I think, for working with
Kiwi.
1209
01:12:23.705 --> 01:12:24.205
No.
1210
01:12:24.824 --> 01:12:27.165
Honestly, at least supporting for the.
1211
01:12:28.240 --> 01:12:30.500
You don't know about it guys, but for example,
1212
01:12:30.800 --> 01:12:34.500
the new reboot of the KPI US, the version of the,
1213
01:12:35.280 --> 01:12:36.020
it was
1214
01:12:36.560 --> 01:12:38.145
done to be to support
1215
01:12:38.605 --> 01:12:39.825
all the different,
1216
01:12:40.845 --> 01:12:42.465
CPU, not only area,
1217
01:12:43.085 --> 01:12:45.665
but also the 64 version and
1218
01:12:48.520 --> 01:12:49.340
the the simulators.
1219
01:12:49.960 --> 01:12:50.460
Okay?
1220
01:12:51.400 --> 01:12:53.420
And last week, I booked,
1221
01:12:54.040 --> 01:12:56.620
1 new iPad to be able to finally
1222
01:12:57.145 --> 01:12:57.885
test it.
1223
01:12:58.585 --> 01:12:59.085
But,
1224
01:12:59.784 --> 01:13:00.605
it's like
1225
01:13:01.225 --> 01:13:10.010
nobody else will do it and will offer me an iPad, and it's very hard to ask that on the Internet. I don't know how to do.
1226
01:13:12.790 --> 01:13:13.449
And, well,
1227
01:13:14.230 --> 01:13:15.530
I don't know how to say.
1228
01:13:16.195 --> 01:13:22.775
But, yes, sponsoring at least, the kiwi product may give us a little more space,
1229
01:13:23.715 --> 01:13:28.600
to buy things and at least maybe put bounty on the biggest issue
1230
01:13:28.980 --> 01:13:32.680
to be able to make the community participating
1231
01:13:33.380 --> 01:13:34.465
more on the
1232
01:13:35.344 --> 01:13:36.565
biggest issue we've got.
1233
01:13:38.945 --> 01:13:44.085
Yeah. I mean, it's it's definitely a tricky problem. Right? Like, I I'm definitely and I'm guessing Tobias
1234
01:13:44.530 --> 01:13:45.030
isn't
1235
01:13:45.489 --> 01:13:49.270
either. Neither of us are particularly connected with mobile hardware manufacturers.
1236
01:13:50.290 --> 01:13:52.469
You know, we can certainly I can certainly
1237
01:13:53.090 --> 01:13:59.315
contribute some cash, but it's tough. I don't I don't know how to hook you up with those hardware manufacturers.
1238
01:14:00.655 --> 01:14:03.070
I mean, 1 thing that I would suggest is,
1239
01:14:03.389 --> 01:14:08.369
you know, yours is a project that an awful lot of people get an awful lot of value out of.
1240
01:14:08.670 --> 01:14:09.170
Maybe
1241
01:14:09.630 --> 01:14:13.175
a way to handle this might be to reach out to the Python community
1242
01:14:13.875 --> 01:14:19.050
through things like, you know, the Python weekly newsletter or Pycoders or or that kind of thing
1243
01:14:19.610 --> 01:14:23.550
to to basically say, hey, the Kibbe project is struggling. We're looking for
1244
01:14:23.929 --> 01:14:27.389
hardware and we're looking for sponsors to help us get that hardware.
1245
01:14:27.925 --> 01:14:30.585
I think you might be surprised, you know, people
1246
01:14:31.045 --> 01:14:35.385
working in these various companies might might see that and be able to help you out.
1247
01:14:37.110 --> 01:14:38.330
That's a good idea. Yep.
1248
01:14:40.710 --> 01:14:43.770
That's definitely a good idea that we should take up on.
1249
01:14:48.035 --> 01:14:48.855
That's great.
1250
01:14:49.315 --> 01:14:52.695
Well, we we like to do with every episode, we like to do
1251
01:14:53.400 --> 01:14:54.780
picks. These can be
1252
01:14:55.719 --> 01:15:05.725
anything that you're interested in or like or wanna recommend to our listening audience. It can be technology related or or not. I usually recommend a beer because I like craft beer.
1253
01:15:06.585 --> 01:15:07.085
So,
1254
01:15:07.625 --> 01:15:09.325
Tobias, why don't you get us started?
1255
01:15:09.785 --> 01:15:12.030
Sure. So I'm gonna keep it short.
1256
01:15:12.349 --> 01:15:16.770
First pick I'm gonna choose is the Zeal offline documentation browser.
1257
01:15:17.309 --> 01:15:22.125
So for people who use Mac OS, there's a similar project called Dash
1258
01:15:22.505 --> 01:15:28.365
and Zeal is the version of that that will run on Linux. So it's a way for you to download
1259
01:15:29.239 --> 01:15:32.380
the documentation for various programming languages and libraries
1260
01:15:32.920 --> 01:15:41.555
and have access to them when you're not online. So if you're on a plane, you wanna be able to look up a particular Python method, you have it stored right on your laptop.
1261
01:15:42.255 --> 01:15:47.110
And the next pick that I'll let you choose is a comic strip called Commit Strip.
1262
01:15:47.670 --> 01:15:51.130
It's actually published in French and English and it's just
1263
01:15:51.989 --> 01:16:00.565
a daily comic strip about the life of developers and it's usually got some pretty amusing content. So definitely recommend that.
1264
01:16:02.065 --> 01:16:04.945
So I just wanna second your recommendation of Zeel. I,
1265
01:16:05.989 --> 01:16:11.530
before I I was made very happy and given the Mac laptop and my current gig, I was working with a Linux,
1266
01:16:12.230 --> 01:16:14.489
a Linux desktop and a Windows laptop.
1267
01:16:14.965 --> 01:16:15.465
And,
1268
01:16:15.925 --> 01:16:16.425
I,
1269
01:16:17.365 --> 01:16:25.600
I had been a huge fan of Dash for years and still am. Now that I'm back on the Mac, But when I was working in Linux and Windows, Zeel was was certainly
1270
01:16:26.060 --> 01:16:29.715
a really excellent analog and and does the job quite nicely.
1271
01:16:30.275 --> 01:16:38.290
And and for anybody who hasn't used this kind of thing before, what's super cool about these things is you can hook them into your IDE or editor of choice.
1272
01:16:38.690 --> 01:16:50.805
And with the dock all offline and already downloaded and everything, it's like it really is instantly at your fingertips. And and the way the UI works is really, really kind of nice. I highly recommend it.
1273
01:16:51.665 --> 01:16:56.940
So I'll move on to my picks real quick. And the first pick that I will pick is unshockingly
1274
01:16:57.320 --> 01:16:57.980
a beer.
1275
01:17:00.920 --> 01:17:09.205
Jack at Jack's Abbey Brewery here in in Framingham, Massachusetts is a brewery that I'm rather fond of. I haven't yet tried a beer from them that I really disliked.
1276
01:17:09.665 --> 01:17:10.065
And,
1277
01:17:10.820 --> 01:17:14.120
and they make a beer called Smoke and Dagger.
1278
01:17:14.580 --> 01:17:16.360
And it is a really delicious,
1279
01:17:17.380 --> 01:17:25.960
dark beer with a lightly smoky flavor. It's considered to be a Roush beer, which is not a a variety that I have a lot of a lot of experience with.
1280
01:17:26.360 --> 01:17:26.860
But,
1281
01:17:27.320 --> 01:17:41.765
it's it's really tasty. It's it's I've tasted some German smoke beers that a friend of mine is into, and, you know, it was just a little too much for me. It was kinda like falling face first into a camp, you know, the can't the ashes of a campfire with your mouth open.
1282
01:17:42.305 --> 01:17:42.805
But,
1283
01:17:43.170 --> 01:17:43.570
it's
1284
01:17:44.130 --> 01:17:44.630
exactly.
1285
01:17:45.170 --> 01:17:47.110
But this one's this one's pretty tasty,
1286
01:17:47.410 --> 01:17:49.750
dark and malty, I I highly recommend it.
1287
01:17:50.770 --> 01:17:51.270
So
1288
01:17:51.955 --> 01:17:57.175
the next thing I wanna recommend is a movie which for some reason here in the United States,
1289
01:17:57.955 --> 01:18:15.025
it was slammed by the critics. The critics really didn't like it and I really don't understand. I think they're on crack because I think it's a really good movie and is a story that was well told, well acted, and and just worth seeing. And that's called A Woman in Gold or Woman in Gold, excuse me. There's no a in there.
1290
01:18:15.724 --> 01:18:16.224
And
1291
01:18:16.570 --> 01:18:20.270
it's about this woman and her family pre World War 2,
1292
01:18:21.449 --> 01:18:23.230
you know, during in Austria,
1293
01:18:24.170 --> 01:18:42.895
when the Nazi Germans were were sort of taking over and about what happened to her and her family and the story of a particular priceless piece of art that used to hang in her household. And I won't say any more than that. I will just say, if you look it up on Rotten Tomatoes or whatever your other favorite movie site is and see it rated low by the critics,
1294
01:18:43.455 --> 01:18:46.595
ignore it and go see it anyway because I think it's really good.
1295
01:18:48.495 --> 01:18:50.515
And the last pick that I have
1296
01:18:51.295 --> 01:18:51.795
is,
1297
01:18:52.850 --> 01:18:53.350
a,
1298
01:18:54.450 --> 01:18:56.950
excuse me, last pick that I have
1299
01:18:57.810 --> 01:18:58.310
is,
1300
01:18:59.175 --> 01:19:03.435
jeez, I lost my last pick. Well then, I guess I'm gonna keep it short and leave it at 2.
1301
01:19:04.855 --> 01:19:07.515
Matthew, what what kind of picks do you have for us?
1302
01:19:09.480 --> 01:19:11.340
The first 1 will be IATAZ.
1303
01:19:12.360 --> 01:19:14.280
I'm not sure about the pronunciation is,
1304
01:19:15.000 --> 01:19:18.140
yet another Python formatter from Google.
1305
01:19:18.475 --> 01:19:21.695
Mhmm. Yeah. K. It's actually a formatter that
1306
01:19:22.075 --> 01:19:23.295
you just feel,
1307
01:19:24.075 --> 01:19:26.495
you give your Python file and give you
1308
01:19:26.840 --> 01:19:29.820
a very great Python file with,
1309
01:19:31.320 --> 01:19:32.940
with actually state 8.
1310
01:19:33.400 --> 01:19:33.925
And it's
1311
01:19:35.284 --> 01:19:38.585
this is the most working tools I ever seen
1312
01:19:39.045 --> 01:19:43.625
from all the other ones, like auto pet 8 or pet 8 5,
1313
01:19:43.980 --> 01:19:45.119
if I remember well.
1314
01:19:45.739 --> 01:19:46.239
And
1315
01:19:46.780 --> 01:19:48.079
thanks to this project,
1316
01:19:48.699 --> 01:19:55.775
I own some of the project I'm working on. I just use the tools to clean all the files. And then,
1317
01:19:56.475 --> 01:19:59.215
with my student, I can ask them
1318
01:19:59.820 --> 01:20:04.080
to focus on the code and not in the formatting of pythons
1319
01:20:04.780 --> 01:20:10.045
when they just start to learn Python. So it's a it's a good tool for me. That was my first pick.
1320
01:20:10.585 --> 01:20:14.445
My second pick will be a project I'm working on. It's
1321
01:20:14.745 --> 01:20:15.485
main chinese.com.
1322
01:20:16.190 --> 01:20:19.810
It's not really related to Python even if all project,
1323
01:20:20.270 --> 01:20:26.105
is running on Python and it's built with Flask and Jinja, etcetera and very good HTML5
1324
01:20:26.645 --> 01:20:28.825
stuff. In Chinese, it's a website
1325
01:20:29.605 --> 01:20:30.245
that you
1326
01:20:30.990 --> 01:20:32.290
that will bring,
1327
01:20:32.670 --> 01:20:33.890
you can learn Chinese,
1328
01:20:35.630 --> 01:20:36.530
in a story.
1329
01:20:36.910 --> 01:20:40.210
Okay? You will be a little dragon, and you will,
1330
01:20:41.055 --> 01:20:46.114
have an in child. The cat will try to add you in the world of all the Chinese,
1331
01:20:46.655 --> 01:20:49.074
world. And you will learn vocabulary,
1332
01:20:49.455 --> 01:20:50.500
grammar, and then
1333
01:20:51.460 --> 01:21:07.860
talking with your browser as a dialogue. So we are using the latest HTML 5, web audio and web speech streams to make it happen. It's still in beta. You can ask for a subscription, but we are launching a kick starter soon, and every feedbacks will
1334
01:21:08.239 --> 01:21:08.980
be welcome.
1335
01:21:11.200 --> 01:21:15.060
And 1 last thing, just because you said beer, I'm sure you
1336
01:21:15.595 --> 01:21:20.495
might never test it. I tested only 1 time in my life. It's called,
1337
01:21:21.675 --> 01:21:23.570
in French, La Reine Scrochon.
1338
01:21:24.430 --> 01:21:28.449
And so La Reine Scrochon is a Belgian beer,
1339
01:21:28.989 --> 01:21:31.010
and it's made in
1340
01:21:31.925 --> 01:21:32.985
how do you call
1341
01:21:34.005 --> 01:21:34.985
I miss a vocabulary.
1342
01:21:36.085 --> 01:21:37.785
Where is the beer is made?
1343
01:21:38.245 --> 01:21:38.985
A brewery.
1344
01:21:40.005 --> 01:21:41.145
Brewery. Okay.
1345
01:21:42.989 --> 01:21:43.890
Not an automatist
1346
01:21:44.270 --> 01:21:44.989
1, but,
1347
01:21:45.630 --> 01:21:49.250
an old 1, very old 1. Everything is done by hand.
1348
01:21:50.475 --> 01:21:51.695
Okay. It's artisanal.
1349
01:21:52.074 --> 01:21:53.055
It's the word.
1350
01:21:54.074 --> 01:21:54.574
No.
1351
01:21:54.875 --> 01:21:58.170
Yes. Yes. That's the word. Yeah. Okay. So it's
1352
01:21:58.810 --> 01:22:02.270
1 of the last year done in artisanal in Belgium,
1353
01:22:03.050 --> 01:22:07.045
and I have been able to visit it only 1 time in
1354
01:22:07.445 --> 01:22:07.945
Sunday.
1355
01:22:08.565 --> 01:22:09.864
And after the visit,
1356
01:22:10.565 --> 01:22:14.185
in front of the sun, we drink a whole beer. I was completely
1357
01:22:14.965 --> 01:22:15.864
out of nowhere.
1358
01:22:16.450 --> 01:22:19.750
I it was very hard to get back to my house after that.
1359
01:22:20.050 --> 01:22:22.310
And it's very light. Just 1?
1360
01:22:22.770 --> 01:22:31.325
Yes. Just just 1, but very, very light, very tasty. It's doesn't even look like bronze or brown beer, etcetera.
1361
01:22:32.745 --> 01:22:33.960
It's almost
1362
01:22:34.660 --> 01:22:39.480
water. Okay? But on the taste, you feel like it's a beer
1363
01:22:39.860 --> 01:22:40.600
very light.
1364
01:22:41.060 --> 01:22:41.800
Right? Just
1365
01:22:42.260 --> 01:22:42.785
I liked
1366
01:22:44.145 --> 01:22:45.125
it. That's it.
1367
01:22:45.425 --> 01:22:46.565
Wow. That sounds delicious.
1368
01:22:47.105 --> 01:22:52.380
If you could, at the end of the show, give us links to that beer and those projects that would be awesome.
1369
01:22:52.760 --> 01:22:53.260
Okay.
1370
01:22:56.440 --> 01:22:57.739
So let's see,
1371
01:22:58.520 --> 01:22:59.020
Akshay,
1372
01:22:59.585 --> 01:23:00.324
you're up.
1373
01:23:01.585 --> 01:23:06.244
Okay. First thing that I'd like I'd like to share is essentially
1374
01:23:07.425 --> 01:23:07.925
mangoes.
1375
01:23:09.010 --> 01:23:10.870
I'm from India, and I love mangoes.
1376
01:23:11.410 --> 01:23:13.270
And you can try them out
1377
01:23:13.730 --> 01:23:19.775
at in this season, the best thing to have. And the second thing I'd like to share
1378
01:23:20.474 --> 01:23:26.199
is 1 of the most ridiculous things I've ever seen giving the use for was essentially,
1379
01:23:27.699 --> 01:23:29.239
tiktatra playing machine
1380
01:23:29.940 --> 01:23:30.840
being controlled
1381
01:23:31.219 --> 01:23:31.719
remotely
1382
01:23:32.020 --> 01:23:33.400
by a Kiwi controller.
1383
01:23:33.940 --> 01:23:34.440
So
1384
01:23:36.885 --> 01:23:40.025
I had no practical purpose other than essentially just playing
1385
01:23:40.725 --> 01:23:42.025
with that tool with the machine,
1386
01:23:42.405 --> 01:23:43.305
using a controller.
1387
01:23:44.900 --> 01:23:50.920
That's very cool. Actually, I I I'm a huge fan of mangoes, and I don't know about where you are, but here in the United States,
1388
01:23:51.300 --> 01:24:01.144
this particular season, you get these yellow mangoes. Sometimes they're called champagne mangoes. Oh, man. Those things are so delicious. I've got 2 in my kitchen ripening right now.
1389
01:24:02.390 --> 01:24:02.890
Amazing.
1390
01:24:04.230 --> 01:24:05.449
Ryan, how about you?
1391
01:24:06.230 --> 01:24:08.730
Alright. Well, for my pick, I used to be a smoker
1392
01:24:09.304 --> 01:24:13.165
and I have since quit smoking and switched to e cigarettes.
1393
01:24:13.545 --> 01:24:16.180
Haven't had an actual cigarette in almost a year now
1394
01:24:16.740 --> 01:24:18.680
and so my pick is a flavor.
1395
01:24:20.020 --> 01:24:23.000
It is called the Milk Ma'am by Vaping Rabbit.
1396
01:24:24.515 --> 01:24:28.135
It's described as a frosted fruit tart milkshake.
1397
01:24:29.475 --> 01:24:34.760
So like a milkshake made with pop tarts, and it's just it's nice and smooth and delicious and
1398
01:24:35.139 --> 01:24:35.639
fruity
1399
01:24:36.420 --> 01:24:37.960
and makes nice big clouds.
1400
01:24:38.980 --> 01:24:39.480
Cool.
1401
01:24:40.035 --> 01:24:43.255
Yeah. It's funny. E cigarettes seem like a like a like,
1402
01:24:43.955 --> 01:24:46.115
a trend these days. I I
1403
01:24:47.600 --> 01:24:50.239
nicotine has never been my my drug of choice, but,
1404
01:24:50.719 --> 01:24:57.744
but, it's I was at ChefCon a few weeks ago, and it was just amazing to me how many people had these things out and were using them. It's,
1405
01:24:58.304 --> 01:25:00.565
it's it's really quite a quite a thing.
1406
01:25:01.905 --> 01:25:04.565
So, Gabriel, what PIX do you have for us?
1407
01:25:05.640 --> 01:25:11.260
Well, I have 2 PIX, and, 1 the first 1 is the technology as you as you suggested.
1408
01:25:11.720 --> 01:25:12.040
And,
1409
01:25:12.635 --> 01:25:22.200
I'm using a a a Windows Manager that I don't think a lot of people use, but I think it's the best thing in the world. So that we encourage
1410
01:25:22.740 --> 01:25:25.320
people to use it. And it's called, I3WM,
1411
01:25:26.580 --> 01:25:28.120
and it's, on the i3wm.org.
1412
01:25:29.300 --> 01:25:30.360
And it's, like,
1413
01:25:30.725 --> 01:25:34.245
awesome, but better and way better. And, it's a very
1414
01:25:34.805 --> 01:25:38.105
really the most flexible thing I ever seen, but
1415
01:25:38.805 --> 01:25:45.989
quite easy to use. So I will give the link, and I will encourage people to train it and be be out.
1416
01:25:47.010 --> 01:25:50.555
And this my second gig, is a French comic,
1417
01:25:52.055 --> 01:25:52.555
author,
1418
01:25:53.415 --> 01:25:55.435
watching the comic video,
1419
01:25:55.895 --> 01:26:00.040
comic comic strips on the Internet, and it's it translates some of his,
1420
01:26:01.780 --> 01:26:11.395
strips, in English. So you can you can read it, too, and it's it's, an amazing artist, and he's and he's quite geeky, and he he has a lot of
1421
01:26:11.855 --> 01:26:18.360
very, cultural geek, things and, some pixel art are wonderful, some diamonds, a lot of Tim Bank,
1422
01:26:19.240 --> 01:26:33.290
very and crazy, crazy stories and and a wonderful, wonderful artist. So, Boulay is is called Boulay, and his, his website is Boulay Corp, and I'll give the link to and, it's literally, really
1423
01:26:33.670 --> 01:26:34.570
a must masterpiece,
1424
01:26:35.830 --> 01:26:36.650
in the continuous,
1425
01:26:36.950 --> 01:26:46.554
continuous producer, almost masterpiece. So I I would encourage you to to read this guy. And the EBIT collaboration with, Zach Weiner, which is the author of
1426
01:26:46.910 --> 01:26:47.410
SMBC
1427
01:26:48.190 --> 01:26:51.470
comic that a lot of geek knows. So it's quite,
1428
01:26:53.230 --> 01:26:54.210
it's becoming
1429
01:26:54.590 --> 01:26:59.535
slowly known, I think, in the US, but not yet, as much as, he should.
1430
01:27:00.074 --> 01:27:02.094
So Yeah. I I said 1, Gabriel.
1431
01:27:02.395 --> 01:27:03.215
Is amazing.
1432
01:27:05.330 --> 01:27:06.150
I love it.
1433
01:27:07.890 --> 01:27:09.270
So where was my topics?
1434
01:27:10.610 --> 01:27:26.690
Very cool. Well, hey. You know, this has been an incredible episode. I I have learned so much, and and I was already impressed with Kiwi and its and I have now realized there's a whole constellation of of subprojects and then co projects under the covers there, and I've walked away even more impressed.
1435
01:27:27.070 --> 01:27:35.985
First of all, thank you all and especially those of you who are up at now probably 3 o'clock in the morning taking the time to talk to us here in the East Coast of the United States.
1436
01:27:36.490 --> 01:27:41.630
And and thank you all for for just for being such amazingly talented, creative,
1437
01:27:42.330 --> 01:27:42.830
technically,
1438
01:27:43.610 --> 01:27:52.470
astute people for creating this awesome piece of technology that we love to play with. We look forward to seeing what, you know, what there is to come from from you guys.
1439
01:27:52.950 --> 01:27:59.370
And, hopefully, as a result of this podcast, we can get more people to pitch in and help you along with some of the heavy lifting.
1440
01:28:00.070 --> 01:28:06.955
Yeah. Definitely. Thank you all for joining us. It's been a lot of fun. It's great talking to you all. So for anybody who would like to
1441
01:28:07.575 --> 01:28:11.915
follow you or find out more about what you're up to, if you could each just
1442
01:28:12.310 --> 01:28:14.250
provide a way that people can
1443
01:28:14.630 --> 01:28:17.290
keep in touch and see what you're see what you're doing.
1444
01:28:18.710 --> 01:28:21.855
It was really fun not talking to you guys. Thanks a lot.
1445
01:28:22.815 --> 01:28:24.435
Yeah. It was great. Very interesting.
1446
01:28:25.695 --> 01:28:29.155
I think we are we we have a dedicated page about us,
1447
01:28:29.455 --> 01:28:30.755
on the on the kiwi.org
1448
01:28:31.370 --> 01:28:33.390
website, the about us page.
1449
01:28:33.770 --> 01:28:37.310
So you can you can see about us here. And,
1450
01:28:37.850 --> 01:28:39.070
so most of the
1451
01:28:39.765 --> 01:28:45.705
community activity is happening in the Google Groups and and then the ERC channel.
1452
01:28:46.085 --> 01:28:53.610
So it's you can go here and and talk to us or or anyway, we we try to be to cover all the bases
1453
01:28:54.995 --> 01:28:55.735
be it Twitter
1454
01:28:56.195 --> 01:28:58.375
or or Facebook or Google plus
1455
01:28:58.835 --> 01:29:02.295
or over or or Reddit. We try to be everywhere, but
1456
01:29:02.660 --> 01:29:05.960
the the place where I was the most proactive user
1457
01:29:06.340 --> 01:29:08.600
is IRC. So if you want,
1458
01:29:09.540 --> 01:29:11.239
you can see here. That's here.
1459
01:29:12.054 --> 01:29:15.914
Great. And thank you, Chris and Tobias, for inviting us because,
1460
01:29:16.215 --> 01:29:19.114
also, this is the first time we are meeting invoice.
1461
01:29:20.050 --> 01:29:21.590
Yeah. Okay. That's great.
1462
01:29:23.010 --> 01:29:25.590
So thank you for that. Yeah. Thank you.
1463
01:29:25.890 --> 01:29:30.185
Absolutely. Well, it's Skype. It's pretty easy, so you guys should maybe take advantage of it and and,
1464
01:29:30.825 --> 01:29:44.545
and have meetings every once in a while. Although, I know time zone difficulties can be can be a bit of a challenge. But sometimes, it's worth it because it's a higher bandwidth mode of communication. Right? I mean, like, IRC and email and all this are are wonderful, but sometimes
1465
01:29:45.005 --> 01:29:49.745
the human voice, there's there's nothing like it. If you can't have face to face, this is the second best thing.
1466
01:29:51.150 --> 01:29:54.450
I think the only thing stopping us from doing that to now was hesitation,
1467
01:29:55.390 --> 01:29:59.745
and we'll definitely take a cue in, try to continue this. Yeah.
1468
01:30:00.285 --> 01:30:02.465
Well, I'm glad we can get that started, William.
1469
01:30:03.005 --> 01:30:03.905
Thanks a lot.
1470
01:30:04.445 --> 01:30:04.945
Thanks.