TRANSKRIPT 🔗
WEBVTT
00:00.273 --> 00:04.033
All right. Welcome everyone to another episode of Macro Mayhem. We are coming to
00:04.533 --> 00:07.953
you in person, live, live. Well, not live, but live
00:07.969 --> 00:11.761
to us, live to us from Goatmire in Varberg,
00:11.922 --> 00:15.553
uh, not Stockholm, Varberg, Sweden. Uh, we are
00:15.843 --> 00:19.265
in the last day of the conference now and we have been enjoying it quite
00:19.297 --> 00:22.575
a bit. It's 1:48 PM. Exactly.
00:22.993 --> 00:26.158
On a Friday, the 2nd of October. Yes. Cool.
00:26.801 --> 00:30.352
So yeah, we've been in Warburg with the Goatmire conference.
00:30.400 --> 00:33.581
It's been amazing so far, and we're kind of like readying
00:33.677 --> 00:37.212
up. We're getting ready for the last big finale, but after lunch,
00:37.228 --> 00:40.843
we just decided to sit down a little and give you the news and latest
00:41.343 --> 00:45.068
vlogs that might interest you. So getting to the news,
00:45.502 --> 00:48.603
the first one is that OTP 29.1.1
00:48.940 --> 00:52.379
and also 28 and 27 patch releases were released recently.
00:52.957 --> 00:56.906
And they fix a lot of bugs, but in particularly 3
00:57.406 --> 01:01.049
CVEs that are quite serious. And if you haven't already, you should consider
01:01.964 --> 01:06.267
updating because the CVEs, they affect SSL, for example,
01:06.459 --> 01:09.863
where if a client that you connect to through SSL,
01:10.538 --> 01:13.652
the client could just say that they don't have a pre-shared
01:13.684 --> 01:17.008
key, and then SSL would accept it, and they would not verify the
01:17.040 --> 01:20.408
certificate of the client. So then you would, yeah, just anyone
01:21.530 --> 01:25.216
could be the man in the middle and you would connect to it and SSL
01:25.296 --> 01:29.142
would not throw an error. Bypass verification. Bypass verification,
01:29.158 --> 01:32.507
that's the word. Then also another one, another CVE is in
01:32.587 --> 01:36.193
SSH, where somebody could create an SSH channel
01:36.693 --> 01:39.831
to you and then open up max channels, as many
01:40.331 --> 01:43.885
as they wanted, and then just take all your resources away and
01:43.933 --> 01:47.652
could cripple your application. So that one is fixed now as well. You can open
01:47.732 --> 01:50.441
up to, up to 256 channels,
01:50.634 --> 01:54.305
and you can configure if you need more channels. And the last CVE that
01:54.805 --> 01:58.328
was fixed is in the ASN package, uh, from OTP, where a,
01:58.793 --> 02:02.384
uh, there was a denial of service attack possible in which an abnormally
02:02.400 --> 02:06.151
large object ID could be sent, and that would then cause resource exhaustion.
02:06.600 --> 02:10.062
So that one also has been fixed. And these were pretty severe.
02:10.511 --> 02:14.102
The SSL one was a 9.3 on the CVE
02:14.602 --> 02:17.905
scale. 9.2, I think. 9.2. So definitely get those updates.
02:18.211 --> 02:22.758
Exactly. Next up, Explorer 0.13 is
02:23.032 --> 02:26.463
released. Explorer is a library that has
02:26.576 --> 02:29.814
been taken over maintenance by Alex Kutmos since early this summer.
02:31.143 --> 02:34.983
He's been giving it a lot of love, adding some new features,
02:35.193 --> 02:38.694
some new APIs to work on DataFrames and Series, as well
02:38.872 --> 02:42.498
as bringing it up to speed on the latest Polars.
02:43.407 --> 02:45.858
Polars is the Rust library underneath, and from what I hear, they have a bit
02:46.358 --> 02:49.995
of a moving target. They have a lot of breaking changes,
02:50.107 --> 02:53.700
so it's a bit of work to get Explorer
02:53.941 --> 02:57.614
on the latest. So thank you, Alex, for doing that. Take a look and
02:57.790 --> 03:01.287
yeah. Check it out. The next 3 packages are
03:01.319 --> 03:04.431
all from the same author, Mathias Polikait from
03:04.463 --> 03:08.842
Denmark. I hope I said that kind of correctly. Mathias, he created
03:08.874 --> 03:12.130
the 3 packages you might've seen, or I actually
03:12.146 --> 03:16.396
found them quite useful, so I wanted to share their announcements
03:16.896 --> 03:20.322
here. The first one is LetMe, the library that makes it easy for you to
03:20.338 --> 03:23.398
write policies for access. So you can write a policy for
03:23.526 --> 03:27.003
each actor schema and then which role should have access
03:27.503 --> 03:30.912
to it, you know, and then what kind of access it should have. And it's
03:30.928 --> 03:34.902
a very nice DSL you can use to create access
03:34.918 --> 03:38.955
policies and then use them in your code. So LetMe has received
03:39.083 --> 03:42.560
a small refactoring update and the latest
03:42.592 --> 03:44.867
version is 0.0.4.
03:45.492 --> 03:47.802
3.0.4. It's been a long week.
03:49.101 --> 03:52.293
And then Matthias also updated his popular Flop and
03:52.373 --> 03:56.848
Flop Phoenix library. Those 2 libraries make it easy for you to do pagination,
03:57.923 --> 04:01.114
cursor-based pagination, page-size pagination, and then
04:01.614 --> 04:05.076
also filtering, that kind of stuff, sorting. So everything you would
04:05.576 --> 04:08.765
need to expose in your UI for users to go through your data in the
04:09.265 --> 04:12.887
database, Flop would take over the passing of these parameters,
04:13.144 --> 04:16.783
you know, kind of some validations in there and so on. So I used Flop
04:16.831 --> 04:19.973
before, I quite liked it. And yeah, Flop has a new version now,
04:20.294 --> 04:23.788
0.29.0, and Flop Phoenix has
04:23.820 --> 04:26.946
0.27.0. So check them out if you haven't
04:27.446 --> 04:31.274
already. Nice. Next up, AtomicBucket 0.5 was
04:31.774 --> 04:35.009
released. This is a project that is a fast single-node rate limiter,
04:35.362 --> 04:38.889
which implements the token bucket algorithm. Now, I personally don't
04:39.389 --> 04:42.351
Load full transcript
know what all that means, but I do know that it's a rate limiter,
04:42.415 --> 04:46.247
it is backed by ETS and the Atomics package in Is that
04:46.343 --> 04:49.425
Erlang or Elixir? OTP. In OTP. So it's,
04:49.779 --> 04:53.230
uh, very good for making sure that everything is going in the order
04:53.551 --> 04:57.259
that you specify for the atomics. And, uh,
04:57.644 --> 05:01.176
yeah, it's a good, it's, it's one of those less known OTP packages, I feel
05:01.676 --> 05:03.921
like. So it's a good example of it. That's why I wanted to mention it
05:04.421 --> 05:08.560
here because AtomicBucket makes very smart use of the atomics module
05:08.640 --> 05:11.674
and atomics modules. They make it very easy for you to add counters,
05:11.770 --> 05:15.351
global counters to your Erlang or Elixir application,
05:15.946 --> 05:19.657
and they are perfect for rate limiters, right? So if you want to count how
05:19.801 --> 05:23.464
often a certain user has accessed the API
05:23.737 --> 05:27.031
in the last minute, you could use an atomic for that to
05:27.531 --> 05:30.693
just, you know, increase an integer by 1 every time a request comes in.
05:31.529 --> 05:35.176
And these atomics are not immutable.
05:35.625 --> 05:39.015
Well, they are just integers, but they're not
05:39.515 --> 05:43.026
getting copied into a new value every time you update them. So that's,
05:43.106 --> 05:46.441
you can update them extremely fast, which is great
05:46.457 --> 05:49.614
for rate limiting. Right. And this release, it looked like
05:50.114 --> 05:53.782
it was focused on performance, adding a little bit of macro
05:54.231 --> 05:57.854
helpers to help with some stuff and generally
05:58.354 --> 06:02.391
just developer experience. So take a look. It should be an interesting
06:02.407 --> 06:05.853
release. Exactly. And then the next library that came
06:06.353 --> 06:09.075
out, which I found pretty cool, is called Smolnet,
06:09.235 --> 06:12.971
S-M-O-L-net. And this library uses
06:13.067 --> 06:17.447
a Rust NIF underneath for giving you a more
06:17.495 --> 06:22.967
higher-level or transport-agnostic TCP/IP
06:23.467 --> 06:26.769
stack. So for sending TCP packages, and it does
06:26.881 --> 06:30.973
not use gencp. And the specialty
06:31.473 --> 06:35.048
about SmallNet is that it does not use the kernel network stack
06:35.225 --> 06:38.690
that usually you use. So if you have an application on your server and the
06:39.190 --> 06:43.648
server, the application makes an HTTP request, It uses the server's kernel's
06:44.148 --> 06:47.915
networking logic and code, and then eventually also the internet
06:48.300 --> 06:51.589
card that connects through Ethernet or Wi-Fi to the
06:52.089 --> 06:55.342
internet, actually. And SmallNet abstracts that a little bit and gives you
06:55.423 --> 06:59.979
a bit more a generic approach to it in which you can remove or replace
07:00.476 --> 07:03.620
your actual networking stack with something else.
07:04.262 --> 07:07.855
And this is very interesting if you want to build something on top of TCP,
07:07.871 --> 07:11.128
for example, like encrypted tunnels, or you want to have,
07:11.384 --> 07:15.151
um, Anything like Iroh, for example,
07:18.523 --> 07:21.666
is an interesting package that makes it really easy
07:21.682 --> 07:25.506
to cluster together your applications that might run anywhere
07:26.006 --> 07:29.335
from your local computer to your production server to Raspberry Pi.
07:30.028 --> 07:33.416
And Iroh just creates a network between these really
07:33.481 --> 07:36.989
quickly. And I believe that SmallNet kind of is an idea
07:37.489 --> 07:41.675
around this. And that's bindings to the Rust smalltcp
07:42.799 --> 07:45.753
library. Exactly. S-M-O-L. S-M, small.
07:46.572 --> 07:50.490
Yeah. Great. So, so check it out if you're interested in, in having
07:50.651 --> 07:54.938
really custom TCP/IP communication with your own protocols
07:55.438 --> 07:58.454
or encrypted tunnels, network simulations, packet level tests,
07:59.000 --> 08:02.838
uh, and, and others. So that is SmallNet for you.
08:03.768 --> 08:07.841
All right. And next up, xratatui 0.16 was released.
08:08.226 --> 08:11.177
xratatui is a terminal UI library,
08:11.995 --> 08:15.827
also a Rust NIF to, um, the Ratatouille
08:16.164 --> 08:21.905
Rust library. And that is R-A-T-A-T-U-I,
08:22.274 --> 08:26.010
Ratatouille. Kind of, I think it's a play on the name of, uh, the movie.
08:26.347 --> 08:29.025
Yeah. Ratatouille, the, the mouse, right? Yeah. The mouse.
08:29.634 --> 08:33.344
Um, And so, uh, this version is really
08:33.844 --> 08:35.625
interesting to me because, uh,
08:35.850 --> 08:39.287
Mauricio had brought,
08:39.512 --> 08:42.868
um, he showed me some demos that he was doing with,
08:43.366 --> 08:46.916
um, making it basically have a generic backend, uh,
08:47.077 --> 08:50.064
to render characters or anything anywhere.
08:50.594 --> 08:54.224
Um, and so he's using the, the Tui library then to render
08:54.706 --> 08:57.932
buff, like pixels to a buffer. Even though it is just a, like a
08:57.996 --> 09:01.380
TUI, you can render it to images. And he has a Phoenix
09:01.508 --> 09:05.534
x Ratatouille package that was part of this group
09:06.034 --> 09:09.512
of releases, I guess. And then he also has a Raster x Ratatouille,
09:10.009 --> 09:13.698
which, um, was the one that he sent, DM'd me about, which he
09:13.714 --> 09:17.146
used to, to put Ratatouille on the E-Ink name badges from
09:17.646 --> 09:20.819
last year's Goatmire. Okay. So he showed me updates to it and it has,
09:21.140 --> 09:24.925
you can do 3D renderings, you can do 2D renderings, images. It's very
09:25.425 --> 09:29.614
cool. So if you use, uh, TUI libraries, like check out x-ratatouille.
09:29.903 --> 09:33.050
Yeah, I used x-ratatouille for my LoRa devices,
09:33.114 --> 09:35.668
which
unfortunately I didn't have that much time to show on stage.
09:36.567 --> 09:39.891
But, uh, I had a Nurse device and then in the Nurse device, I wanted
09:40.391 --> 09:43.055
to run a TUI that I can use for sending messages.
09:43.970 --> 09:47.246
Yeah, like a terminal user interface. And I just added Ratatouille to
09:47.746 --> 09:51.164
it and poof, I had the perfect layout, perfect refresh rate.
09:51.276 --> 09:54.967
It was, it was really, really nice. Yeah, it's a really cool library. Exactly.
09:55.528 --> 09:58.751
And the last news item we have is another little library that
09:59.251 --> 10:02.279
was released. It's called Gale, G-A-L-E.
10:02.969 --> 10:06.112
And the interesting part here is that Gale is a Phoenix adapter,
10:07.058 --> 10:10.666
like Bandit, that adds HTTP/3 support,
10:11.083 --> 10:14.707
that is QUIC support. And HTTP/3
10:14.851 --> 10:17.930
has been kind of like a moving target. It's very complex.
10:17.978 --> 10:20.978
It's super complex, yeah. And there hasn't,
10:21.107 --> 10:24.221
I think, yeah, Bandit doesn't have HTTP/3 support yet.
10:24.879 --> 10:28.618
So it's interesting to see Gale that took a shot at this and actually added,
10:28.795 --> 10:32.486
like, used Bandit as a base for HTTP/1 and
10:32.583 --> 10:35.744
2. But then if you upgrade to HTTP/3, it uses a
10:36.033 --> 10:39.532
ZigNIF for handling the communication.
10:40.190 --> 10:43.609
And the performance improvements here were very impressive where
10:44.042 --> 10:47.331
if you would use HTTP/3 with like 7 streams or
10:47.831 --> 10:51.131
12 streams, it would have a 430 times speedup
10:51.420 --> 10:55.637
of bandwidth of communication over HTTP/1
10:55.686 --> 10:59.647
and 2. So again, HTTP/3 seems to be quite experimental
11:00.015 --> 11:03.672
a lot and not every, like there is very little support for it yet.
11:04.441 --> 11:08.386
So it was interesting to see Gale that took a stab at this and maybe
11:08.434 --> 11:11.706
it will replace Bandit. I mean, not replace it, but extend
11:12.206 --> 11:15.811
it and then become a new default or maybe Bandit will eventually integrate.
11:16.052 --> 11:20.127
Or take approach, the approach that Gale took maybe to integrate HTTP/3
11:20.143 --> 11:23.801
as well. Um, I don't see that like anytime soon,
11:23.897 --> 11:27.218
but again, this was an interesting project to, to look at,
11:27.266 --> 11:30.700
to see how it would be possible. Yeah. And actually looking at these
11:30.812 --> 11:34.229
lists of blog posts and releases that we have here, it's also very interesting
11:34.261 --> 11:37.261
to see that we have a lot of NIF-based libraries going out.
11:37.711 --> 11:40.855
I think it's great that we have such great interop with other
11:40.919 --> 11:44.911
native languages. And even though we don't have an HTTP/3 QUIC
11:45.088 --> 11:48.037
implementation for Elixir yet, we can lean on other,
11:48.775 --> 11:51.949
other ecosystems to add support for until we get one,
11:52.478 --> 11:55.075
if we get one. If we get one, you know, this way we can also
11:55.107 --> 11:58.232
reuse what other, um, projects do. Like you
11:58.313 --> 12:02.464
can use a ZigNIF or a RustNIF, right? And then, you know, everyone just uses
12:02.480 --> 12:05.847
one RustNIF to have HTTP/3 support,
12:06.328 --> 12:09.679
but then you can add it to your ecosystem very quickly. So huge shout
12:10.179 --> 12:13.225
out to the Rustler team, the Ziglar team, and the,
12:13.626 --> 12:18.022
the, the folks behind, uh, is it CMake for C-based
12:18.522 --> 12:22.000
NIFs? So it is, we're standing on the shoulders of giants here.
12:22.209 --> 12:25.498
That's for sure. So yeah, whenever somebody says, oh, Elixir is not fast
12:25.998 --> 12:28.370
enough, I'm like, what do you need? You know, what needs to be fast?
12:28.947 --> 12:32.509
And then, okay, well, let's write a Rust library for it and then it's going
12:33.009 --> 12:35.912
to be amazing. Exactly. So fast. You just have to think about how you send
12:36.412 --> 12:39.059
and receive the data, but otherwise, yeah,
12:39.364 --> 12:42.430
you can use Rust and then nobody should complain about speed anymore.
12:43.876 --> 12:47.633
Speaking of giants, our first blog post here is by José
12:48.133 --> 12:51.502
Valim himself, Evolving Programming Languages in the AI Era.
12:51.984 --> 12:55.533
This is, um, kind of the extension
12:55.822 --> 13:00.319
of his ElixirConf US talk, and we cannot recommend
13:00.819 --> 13:04.331
reading this one enough because it is challenging some questions in our community,
13:04.669 --> 13:08.342
how we move forward. That's also showing like some of the use case for
13:08.390 --> 13:12.397
the type system. So what did you think of this? I enjoyed it
13:12.639 --> 13:14.682
a lot. It's a more,
13:16.195 --> 13:19.878
I would say vague, spectacular, not spectacular,
13:19.960 --> 13:23.445
where you speculate. That's the word I'm looking for.
13:23.494 --> 13:26.553
Thank you. He speculates about how the future could look like
13:26.847 --> 13:30.257
for software engineering in general, but also in particular to open
13:30.757 --> 13:34.377
source communities and language communities like the Elixir community. In this AI
13:34.810 --> 13:38.144
era. Yeah. What will be in 2 years from now? Where will
13:38.192 --> 13:40.324
we be? And what do we need to look out for?
13:40.981 --> 13:45.245
Because he raises very good points. For example, he focuses
13:45.309 --> 13:48.980
on 2 parts. One of them is a little bit how we humans
13:49.092 --> 13:52.876
as developers will be impacted by the AI
13:53.376 --> 13:56.851
era, but then also how will programming languages need to
13:56.883 --> 14:00.572
evolve and what will they focus on? instead of what they have
14:01.072 --> 14:05.132
focused on in the past, like what will change there? And the
14:05.148 --> 14:08.729
first part is about the community building part. Do you want to talk about that?
14:09.532 --> 14:14.076
Well, I think there's a couple of questions here is that one
14:14.124 --> 14:18.267
of the questions he posed, rhetorical questions, I think, is that if
14:18.925 --> 14:22.714
the language is no longer that important because AI
14:23.214 --> 14:25.876
can just generate whatever code, Does it really matter?
14:26.149 --> 14:30.062
Does it all of— does work on languages themselves matter? Are AIs
14:30.094 --> 14:33.942
just going to be generating like assembly bytecode for your machines in the future?
14:34.600 --> 14:37.470
But now you're jumping ahead. Now you're talking about the programming languages. Oh,
14:37.695 --> 14:40.998
that was right. Yeah. But let me talk about the community aspect first.
14:41.399 --> 14:45.007
Because the community aspect here is obviously important to us as a community
14:45.507 --> 14:49.498
because a community is also built around the frameworks
14:49.998 --> 14:52.785
and libraries and the language. That we all use,
14:53.170 --> 14:57.132
right? So you have the Elixir language, but then you have Phoenix and other,
14:57.582 --> 15:01.126
and NURS, like other, and Ash, like all these frameworks,
15:01.447 --> 15:05.666
they kind of build the overall community by creating
15:05.762 --> 15:09.628
a community of their own. And now with AI being able
15:10.128 --> 15:13.221
to write most of the things you need, the question here will
15:13.721 --> 15:17.199
be, will these frameworks still be a driving
15:17.311 --> 15:21.067
factor to our community? And then if they aren't,
15:21.244 --> 15:24.808
what will be, right? So how will we continue to get,
15:25.274 --> 15:29.128
to build a community and to keep it together and share and collaborate
15:30.477 --> 15:33.191
on software, which brings us together usually?
15:34.042 --> 15:37.735
Again, José, he doesn't give any answers. He's just asking questions,
15:37.799 --> 15:40.754
but I think it's an important aspect. Right.
15:41.894 --> 15:45.218
And then he moves onwards, which you also mentioned, like how
15:45.330 --> 15:48.330
will programming languages evolve a little bit.
15:48.795 --> 15:50.942
And I think he makes a great point that he also has made before,
15:51.022 --> 15:54.179
which is, if you make a language easy to use to a
15:54.679 --> 15:57.656
human, it will also be easy to use to an LLM. And we've heard this
15:57.769 --> 16:01.166
at a couple of conference talks here and at ElixirConf US.
16:01.839 --> 16:05.605
I think Zach Daniel mentioned that quite a bit for his talk at
16:06.105 --> 16:09.595
ElixirConf, which the recordings are out. So they're all very
16:09.627 --> 16:13.201
good questions though. They're all very good points that I I think it is
16:13.313 --> 16:16.775
something that we see with AI usage is that it's easy for a human,
16:17.080 --> 16:20.783
if you can understand it well, I think that's the draw of Elixir for a
16:20.927 --> 16:24.598
lot of us. It makes a lot of sense. And yet we also see Elixir
16:25.098 --> 16:28.526
scores very well for some of those Trust Me Bro benchmarks.
16:29.006 --> 16:32.613
That's research. Research. Yeah. Yeah.
16:32.693 --> 16:35.835
But so José, yeah, he makes some valid points about
16:36.335 --> 16:40.163
this. And then, then he continues talking about the actual language design and how a
16:40.663 --> 16:43.898
language will evolve now that you have different requirements coming from
16:44.251 --> 16:47.828
LLMs. And first, one of the discussion points in
16:47.940 --> 16:51.999
maybe the broader ecosystem was, do we still need compilers
16:52.175 --> 16:55.720
or will LLMs just start writing assembly? Is it just
16:56.105 --> 16:59.971
a text-to-assembly machine? Exactly. Like, do we still need languages like
17:00.471 --> 17:04.078
Elixir and everything? And he says, yeah, of course not. Like, we will still use
17:04.543 --> 17:08.152
languages still. Did I say this right? Like, he does not buy the argument
17:08.652 --> 17:11.649
that we will not use languages anymore and everything will be assembly.
17:12.194 --> 17:15.392
Because, yeah, a language, the abstraction that it brings and
17:15.440 --> 17:18.557
the ecosystem and the foundation that it brings, you don't
17:18.589 --> 17:22.142
want to rebuild this for every single project. Right. And he's also not
17:22.642 --> 17:26.450
saying that Elixir is the perfect tool for every single job. There are specializations
17:26.466 --> 17:30.806
within languages that we see. Some are really good at processing
17:30.919 --> 17:34.548
lots of data really quickly. Some are really good at parallelization. Some are good
17:35.048 --> 17:38.362
at doing scientific verification, like Lean, for example, is a
17:38.862 --> 17:42.067
very specialized language for mathematical proofs. Like you would
17:42.567 --> 17:45.607
not want to write this yet again in assembly. And then also, how do you
17:46.107 --> 17:48.940
share it with others? How, you know, other mathematicians, they would need to start reading
17:48.972 --> 17:52.352
your, your assembly code. Not to mention if I wrote my
17:52.417 --> 17:55.621
library, my Phoenix app or whatever, not Phoenix,
17:55.925 --> 17:59.354
assembly-based app to work on my dev machine,
17:59.867 --> 18:03.103
then you have to support your server or something, your NURBS device,
18:03.215 --> 18:06.900
whatever. All the work that we have been doing and that frameworks
18:07.400 --> 18:11.322
and libraries and kernels and operating systems give us, I mean, that is It's
18:11.822 --> 18:13.791
not for nothing, right? Exactly. Yeah.
18:14.673 --> 18:18.425
But one aspect that he says will be interesting is
18:18.537 --> 18:21.872
agentic tooling. So how do we make our language more accessible
18:21.984 --> 18:25.608
and more effective and usable to the LLM?
18:26.939 -->
18:31.300
What I found interesting here is that he says that like
18:31.800 --> 18:35.276
some of the aspects that already helped writing to
18:35.776 --> 18:39.284
write better and more verified code, like specs and types,
18:39.364 --> 18:42.913
for example, That is something that languages or like Elixir,
18:42.929 --> 18:46.815
for example, already has, but it might not be used enough because humans,
18:47.313 --> 18:50.301
you know, they're rather lazy and they don't want to write code. And then also
18:50.801 --> 18:54.027
the types or the specs on top of it. But now— Now with LLMs.
18:54.380 --> 18:58.010
LLMs, you can say, always write the spec, always write the type.
18:58.154 --> 19:01.592
Exactly. So, and then that gives better tooling
19:01.688 --> 19:05.125
for other LLMs or other agents at a later point to go back and
19:05.157 --> 19:08.449
know how to use that. Not to mention the fact that we can then do
19:08.949 --> 19:12.400
our static code analysis with the tooling that's being built around the type system
19:12.900 --> 19:16.880
and things like that. Exactly. And my LLMs always have been writing specs,
19:17.442 --> 19:20.397
even though I never asked them to. It's helpful because they show up in the
19:20.897 --> 19:24.444
code hints when you do an LSP hover. Yeah. Yeah. When you
19:24.944 --> 19:26.435
still look at the code, like,
19:27.880 --> 19:30.466
if you look at the code. I'm outing myself. I still look at the code.
19:30.594 --> 19:33.919
Oh, he does. I still do too, but my LSP never worked, so I
19:34.015 --> 19:37.451
don't have that anyway. But yeah,
19:37.499 --> 19:41.045
so this is an interesting part where if a language now
19:41.286 --> 19:44.495
already offers these kind of formal verification
19:44.995 --> 19:48.395
systems like specs and types and so on, the usage of
19:48.411 --> 19:52.166
those will maybe increase because LLMs don't mind
19:52.262 --> 19:56.338
also writing specs and types and these kinds of things themselves,
19:56.530 --> 20:00.943
right? So if a language offers this, now LLMs can really like
20:01.024 --> 20:04.585
boost it and use it a lot. And then it's also the the obligation
20:04.633 --> 20:08.048
of the language to then use it more and help more and find more bugs
20:08.080 --> 20:11.670
with it. So on. Right. Yeah. So I like the direction
20:12.170 --> 20:15.662
our community is going with the type system. I think this is a great improvement.
20:15.934 --> 20:19.509
Definitely. I found a lot of, uh, well, not too many though, but sometimes
20:19.525 --> 20:21.737
you make a change and then all of a sudden you get a big ass
20:21.769 --> 20:25.456
warning and I'm like, oh, okay, well, maybe I fix it. Or when, what was
20:25.488 --> 20:29.095
it? 1.18, 1.19 was released with the first
20:29.223 --> 20:32.381
comings of the type system. And then it spat out all those warnings of like,
20:32.846 --> 20:36.390
this is an unused function head because it cannot match or things like With maps
20:36.599 --> 20:39.054
and structs and that kind of stuff. That was a big difference. That was a
20:39.102 --> 20:42.232
big deal. So, um, I think we will see more
20:42.732 --> 20:45.747
of that as the type system gets fully developed for, I think,
20:45.763 --> 20:48.411
structs and— I think it's fully developed now.
20:49.679 --> 20:52.231
Well, when, oh, when we start typing it ourselves,
20:52.745 --> 20:55.698
typing our functions. Which might or might not come in the future. Which might or
20:56.198 --> 20:59.486
might not come. José, he pushes it. He delays it as much as possible because
20:59.986 --> 21:02.761
his argument, and I agree with him, is If we can do it for the
21:03.261 --> 21:06.213
developer, why would we need to ask them to, right? So they try to really
21:06.229 --> 21:09.505
go as far as possible. And yeah,
21:09.826 --> 21:13.343
2 other points that José made is about the future of
21:13.439 --> 21:16.073
LSPs, language server protocols,
21:16.587 --> 21:18.931
processes? Protocols. Language server protocols, yeah.
21:20.280 --> 21:23.973
So will they still be relevant? Because as like
21:24.037 --> 21:27.634
how humans use an LSP is when they actually write code and then
21:27.731 --> 21:31.312
you might have autocompletion. Or you might go to definition, that kind of stuff.
21:32.790 --> 21:36.629
And he argues LSP will continue to be very valuable
21:36.725 --> 21:40.436
and important, not that much for the autocompletion or
21:40.936 --> 21:44.403
the go to, but like not for the autocompletion, but for the
21:44.596 --> 21:48.402
go to definition, for example. Right. And when your agent
21:48.451 --> 21:52.129
knows how to say, hey, I'd like the entire body of this function,
21:52.547 --> 21:56.080
can you tell me where that is? It doesn't have to go reading useless junk
21:56.580 --> 22:00.061
into the context to then You know, try and find it. It knows how
22:00.093 --> 22:03.943
to do all of that with the LSP. Yeah. So actually LSP
22:04.443 --> 22:07.521
might change a little bit like this so that they offer more
22:07.585 --> 22:11.131
support to LLMs to find code, find the call sites
22:11.323 --> 22:15.077
of a function and that kind of stuff. Because right now my LLM always
22:15.093 --> 22:19.136
uses basically regex through the entire file
22:19.377 --> 22:22.505
system instead of using the more intelligent LSP
22:22.570 --> 22:25.939
tools. So Yeah, hopefully Elixir can—
22:25.955 --> 22:29.035
It'll be interesting to see how it all develops. Definitely.
22:29.228 --> 22:32.581
Yeah. And then lastly, um, there's one
22:33.081 --> 22:35.742
argument that he makes, which I also agree with, is that,
22:36.672 --> 22:40.186
um, previously for also for many other languages, the debuggers
22:40.699 --> 22:44.839
that you add to your code and then you execute it have been the primary
22:44.935 --> 22:48.464
way of understanding
the code and debugging it basically.
22:48.962 --> 22:52.026
But he argues that that will go away a little bit because LLMs,
22:52.251 --> 22:55.363
they don't want to set a breakpoint, run your code,
22:55.603 --> 22:58.876
find, you know, the issue, set another breakpoint,
22:58.908 --> 23:02.357
rerun the code and so on. But they will rather want
23:02.857 --> 23:06.657
to have runtime observability, which we have with IEX,
23:06.673 --> 23:10.138
for example. If you run the server locally in local
23:10.638 --> 23:14.197
development, you can IEX into it and then you can run functions, you can
23:14.293 --> 23:17.002
read the logs. You can read the state in memory,
23:18.140 --> 23:22.050
all through these very nice REPLs that we have. So he argues that
23:22.082 --> 23:25.992
that will become the primary way for the LLMs to debug
23:26.409 --> 23:29.758
basically what is happening in your application. Yeah. Right?
23:30.960 --> 23:34.405
Yeah. Many smart things. I'm not surprised. It's a really good blog
23:34.421 --> 23:39.597
post. It is. So definitely go take a read. I can't
23:39.629 --> 23:43.282
recommend it enough. And it's like, I think it's just a collection of
23:43.314 --> 23:46.758
thoughts that he said he put together from discussions at ElixirConf
23:46.903 --> 23:50.091
and all this work on the type system, being in the community,
23:51.004 --> 23:53.968
a lot of uncertainty with our industry right now. So,
23:54.593 --> 23:57.829
um, yeah, it's interesting to see where José's head
23:58.329 --> 24:01.658
is at, at least. Yeah, because he has always been a bit more critical or
24:02.158 --> 24:05.375
realistic, pragmatic about it than others in the industry. So I,
24:05.967 --> 24:09.204
I, I value his opinion quite a bit because I know it comes from
24:09.268 --> 24:12.151
a point where— He's thought about it a lot. He's thought about it. Yeah.
24:12.696 --> 24:16.480
And there's also some discussion on the Elixir forum about this article. So we'll leave
24:16.980 --> 24:18.900
a link in the show notes for if you want to check that out and
24:19.400 --> 24:21.786
see what others are talking about. And share your own thoughts about it. Yeah.
24:22.652 --> 24:27.381
Then we have 2 more blog posts. One of them is by my ex-colleague
24:27.782 --> 24:32.126
and friend, Ryan Zidago. He wrote a nice little blog post about keep
24:32.626 --> 24:36.134
your product knowledge close to the code. And what he argues for
24:36.198 --> 24:40.000
in this blog post is that When you think about function docs
24:40.112 --> 24:43.868
and module docs, usually as a developer, you think about writing
24:43.980 --> 24:47.559
the technical aspects of what, you know, what you
24:47.576 --> 24:51.107
will see, like the function or the module you're describing. But Ryan,
24:51.187 --> 24:54.878
he argues that in these documentation blobs, you should also
24:54.959 --> 24:58.473
add the product knowledge and the reason why this function does that,
24:58.490 --> 25:01.716
for example. And I fully agree with him. And I think I also have
25:02.216 --> 25:05.568
done that quite a bit in my past. Where when you wrote a module that
25:06.068 --> 25:09.872
behaves a certain way, you also document
25:09.968 --> 25:14.351
why it behaves a certain way based on the product requirements.
25:14.400 --> 25:17.900
So based on the business requirements about these decisions you made,
25:18.414 --> 25:22.026
right? Because they belong together. The product decision influenced your
25:22.526 --> 25:26.185
code decision. So if you only document how the code works
25:26.201 --> 25:29.686
and not document why it works a certain way, In the future,
25:29.702 --> 25:32.996
it's also harder for you or another developer to go in and understand,
25:33.092 --> 25:37.142
well, why is it doing this thing? Right. It's like co-locating your Phoenix
25:37.642 --> 25:41.304
templates, but kind of at a higher level of thought.
25:41.770 --> 25:45.594
Yeah. Like to just add product information next
25:46.094 --> 25:49.049
to technical information. Exactly. Yeah. So very nice blog post by Ryan.
25:49.884 --> 25:53.323
Yep. And last up, we have a blog post by Herman Verschuuten,
25:53.901 --> 25:57.800
uh, about Bluebeam. Blue-green deployments, um, on his own
25:57.848 --> 26:01.104
server, his own bare metal server. Uh, it was mentioned in
26:01.136 --> 26:04.472
the XAML thread on the forum, but it's kind of
26:04.648 --> 26:08.096
a neat article because he walked
26:08.596 --> 26:12.907
through all of the steps that he took to get this custom deployments
26:13.407 --> 26:17.061
working with Caddy, um, shipping his
26:17.093 --> 26:20.493
releases to the server with, I think it's SSH over the XAML tool.
26:21.087 --> 26:23.753
And some problems he ran into specifically with EPMD.
26:24.154 --> 26:28.829
Yeah. XAML is X-A-M-A-L. So it's like a Kamal rewrite
26:29.038 --> 26:32.346
in Elixir. Elixir XAML. Elixir Kamal.
26:32.893 --> 26:36.603
Elixir Kamal. Yeah. X-A-A-M-A-L. Yeah.
26:37.422 --> 26:40.538
So yeah, Herman, he documented the
26:40.603 --> 26:44.120
problems very interestingly or really well that you
26:44.217 --> 26:48.102
will run into when you deploy an Elixir app. For example, EPMD,
26:48.552 --> 26:52.163
which is a service that Erlang uses to cluster your
26:52.663 --> 26:57.089
machines together, and that connects to one port
26:57.154 --> 27:01.005
on your system. So if that port is blocked by
27:01.505 --> 27:05.242
the old application, you can't start the new application in
27:05.742 --> 27:09.623
a blue-green deployment way. So you can really only stop the old application
27:09.671 --> 27:12.929
so that it frees up that port and then start the new application.
27:13.426 --> 27:16.635
And that's really required because if you didn't know which port to talk
27:16.715 --> 27:19.426
on, then it wouldn't be able to discover you. Like it would
just be guessing
27:19.539 --> 27:22.779
at ports. So, uh, EPMD is a really useful
27:22.892 --> 27:26.565
app, but it's also, um, has these constraints.
27:26.774 --> 27:30.015
So what did he do? I think he used Caddy.
27:30.287 --> 27:33.448
Well, I'm not, I know he used Caddy, uh,
27:33.656 --> 27:37.121
in front of the whole thing. So he, he started Caddy and Caddy connects to
27:37.330 --> 27:41.100
ports 80443 and you know, 9000-something that
27:41.600 --> 27:45.351
you use for EPMD. So Caddy is the only application that is continuously connected
27:45.851 --> 27:49.265
to those ports. And then Caddy exposes these
27:49.361 --> 27:52.649
ports to your application, but it
27:53.149 --> 27:57.045
doesn't expose that exact port, but it might
27:57.622 --> 28:00.927
give you port 9001 for application 1 and
28:01.427 --> 28:05.322
then 9002 for application 2. And it redirects
28:05.338 --> 28:08.723
these ports to then the port 9000, which your EPMD
28:08.851 --> 28:11.899
service might listen to. So, uh, yeah,
28:11.915 --> 28:15.667
basically Caddy does the, the proxying here. And that
28:16.167 --> 28:19.452
allows you to then do blue-green deployments properly because you can spin up
28:19.532 --> 28:23.285
one application and connect it to port 9001 and
28:23.365 --> 28:27.343
wait until it's good, healthy, and then switch over just the,
28:27.696 --> 28:31.288
um, which application then sends data to the port 9000.
28:31.945 --> 28:35.907
Exactly. And Herman also mentioned in his article how much difficulty
28:35.955 --> 28:39.884
he had with getting Caddy to work with this system of blue-green
28:40.384 --> 28:43.754
deployments. And whatnot. There's an API for it, but it seems like it
28:44.254 --> 28:47.738
prefers if you reload the Caddyfile, the config file for it. And then eventually
28:47.770 --> 28:51.835
he mentioned that he found that there's a Unix socket to configure it separately.
28:52.284 --> 28:56.108
So it's a good read. I know Herman is using this in production. He runs
28:56.608 --> 28:59.802
a business where he has a lot of apps. So he's
29:00.302 --> 29:03.754
doing this in production. It's a good read. Um, check it out. I will need
29:04.254 --> 29:06.099
to look into it because I need to— You need to do something similar.
29:06.164 --> 29:07.674
We talked about this. Yes, exactly.
29:09.117 --> 29:12.819
Anyways, that finishes the news and blog section. We have one little
29:13.319 --> 29:16.793
section about meetups and conferences. So take it away. Do you have your timer ready?
29:17.306 --> 29:20.719
Not today. I can set up a timer. Alrighty. I'll be done
29:20.735 --> 29:23.203
before you get us started. Meetups and conferences.
29:23.556 --> 29:27.193
NERD meetup EU is on October 14th. We meet at 7 PM
29:27.322 --> 29:30.382
CET, European Central, Central European Time.
29:31.809 --> 29:36.031
It is this month we are Joining Isaiah
29:36.274 --> 29:39.759
DeRose-Wilson, the
previous ex, he just
29:40.259 --> 29:43.627
recently departed, the CTO of SmartRent is going
29:43.643 --> 29:46.719
to join us where Frank and John and a lot of the core team were
29:47.219 --> 29:50.889
working for a while. He's built a lot of cool little robots and
29:51.389 --> 29:55.188
he's going to talk about them. So yeah, come join us for the Nearest
29:55.688 --> 29:59.213
Meetup EU. We are remote. That's October 14th at 7
29:59.229 --> 30:02.265
PM. Central European. Remote via Zoom. Yep.
30:02.490 --> 30:05.395
Okay. Uh, also upcoming is CodeBeam Europe,
30:05.684 --> 30:09.600
the conference in Haarlem, Netherlands. That's October 21st, 22nd.
30:10.097 --> 30:13.532
And there's an unconference organized by the EEF beforehand.
30:14.109 --> 30:16.661
Um, there will be links in the description to go register for those.
30:17.319 --> 30:21.187
Um, they will be a great time. You're speaking there, right? I am speaking about
30:21.687 --> 30:24.589
the vulnerability work I've been doing with the EEF to secure the,
30:25.022 --> 30:28.744
uh, Beam ecosystem. Right. So this is a great conference. I went last
30:29.244 --> 30:33.314
year, um, and it's more than just Elixir, but it's a great convergence
30:33.814 --> 30:37.324
of the Erlang, Elixir, Glean folks, everyone from
30:37.372 --> 30:40.644
all corners of the OTP land. Exactly. So look for those.
30:41.141 --> 30:44.092
And yeah, if there's other meetups, conferences,
30:44.284 --> 30:48.341
things you'd like us to highlight, send them in. Um, we are happy to announce
30:48.438 --> 30:52.207
them here on the show. Good. Peter, even though We
30:52.707 --> 30:56.060
have fewer items to talk about. You were slower than usual. So next time,
30:57.119 --> 31:00.041
next time we have to speed up again. Yeah. Next time. Well,
31:00.491 --> 31:04.199
Peter, do you have a joke for us? I do have a joke. Let me
31:04.327 --> 31:07.265
check my very long list of puns. Um,
31:07.699 --> 31:10.251
well, I do have a DNS joke, but it might not resolve.
31:11.471 --> 31:14.746
Yeah. Wasn't too good. Oh, come on. Nah, it wasn't too good. Okay. It's always
31:14.858 --> 31:18.503
DNS. It's always DNS. Okay. One more. Um, how about this one?
31:21.308 --> 31:25.081
Did you know that a mosquito can fly, but a fly can't
31:25.259 --> 31:28.905
mosquito? Also pretty bad.
31:29.114 --> 31:32.627
It's pretty bad. It's pretty bad. In a live situation like this, you actually see
31:33.127 --> 31:35.865
that somebody's not laughing. No. Um, okay.
31:36.026 --> 31:39.173
Spare the audience. Spare the audience. One last one. This one is good.
31:39.254 --> 31:42.789
This one is good. Okay. Okay. So what is important?
31:45.428 --> 31:49.291
When an ant goes to another country, it is called
31:49.836 --> 31:53.442
an import ant. That one's
31:53.942 --> 31:56.280
better. That is better. That is better. You should have led with that one.
31:56.488 --> 32:00.592
Good. Okay. That's it. And that's it. That's our first
32:00.608 --> 32:04.022
section of the episode. So if you're not interested in our discussion
32:04.522 --> 32:07.965
about Goatmire, where we are currently, and we will also go back to after this
32:08.465 --> 32:11.235
recording, you know, you may tune out now, turn off the radio.
32:11.492 --> 32:14.505
Um, which I also spoke about in my talk quite a bit.
32:14.842 --> 32:19.186
So maybe I could, you know, interest you in staying with us because
32:19.686 --> 32:23.402
we will talk about our experience here at Goatmire, interesting talks we've seen,
32:23.659 --> 32:26.768
interesting discussions we had, uh, learnings.
32:27.121 --> 32:30.311
It's been a lot of fun. It's been so much fun. So this
32:30.811 --> 32:32.860
is, this is a discussion section now, right? Right.
32:33.854 --> 32:37.140
Right. Goatmire. Where do you want to start? Oh man, so much. I mean,
32:37.156 --> 32:40.827
you were here first. You arrived last Friday already, right? I arrived on Saturday
32:41.327 --> 32:44.756
morning. Saturday morning. And so I helped out with some of the setup
32:45.256 --> 32:47.853
for all of this secret show that was going on.
32:48.832 --> 32:51.529
Um, so if you're listening to this,
32:51.962 --> 32:54.289
um, I guess you could have been here.
32:54.770 --> 32:58.462
There's some, some listeners that have come up and said hello, but if
32:58.962 --> 33:02.313
you were not here, you're wondering right now, what is this secret show
33:02.813 --> 33:07.032
that we're talking about? Um, and Lars and largely
33:07.064 --> 33:10.611
Flora, who did the puppet show at Goatmire last year,
33:11.140 --> 33:14.485
describing the lifecycle of a process. Yeah. have taken
33:14.985 --> 33:18.921
it to a whole nother level. And let's see,
33:19.100 --> 33:22.221
what do you want to talk about first? There's a tree. There's a giant LED
33:22.350 --> 33:26.223
tree. Okay, I can talk about my play
33:26.723 --> 33:30.193
because before we started recording this, I literally went on stage and played
33:30.322 --> 33:34.664
a goat. And I was killed by Lars,
33:35.085 --> 33:38.309
who played Odin. I don't know why he killed me.
33:39.317 --> 33:42.859
I still don't know. The finale has not happened yet. And so we need to,
33:43.404 --> 33:45.712
we do need to wrap this up because I want to see that finale.
33:45.888 --> 33:48.773
Exactly. But so what Gus is talking about,
33:48.789 --> 33:52.027
basically in between talks, I think 3 or 4 times a day,
33:52.716 --> 33:55.729
there are short little sketches that they play on stage,
33:55.906 --> 33:59.816
which for example, I just played where I was a goat sleeping. And then Odin
33:59.929 --> 34:03.182
came in and said, have you finished your work? And I'm like, yes, I did
34:03.198 --> 34:06.067
finish my work. And he said, okay, then deploy it because I have a meeting
34:06.099 --> 34:10.781
with the investors coming up. And I
deploy it with like a huge 3-meter-tall
34:11.775 --> 34:14.966
tree that has nerves because like it uses nerves
34:14.998 --> 34:17.580
to make LEDs on leaves flicker.
34:18.125 --> 34:21.861
So I was deploying it while the tree was flickering and then
34:21.893 --> 34:24.635
Odin killed me. I don't know with his— I don't know why he did that.
34:24.763 --> 34:28.003
Because he's an asshole. Apparently. But yeah,
34:28.371 --> 34:30.648
he's extracting all value like a good capitalist.
34:31.354 --> 34:34.705
Not paying me for it. Apparently not paying you for it.
34:35.042 --> 34:38.844
He's been pushing hard deadlines. And then you had to get help
34:38.892 --> 34:42.228
from Mimir, which is a, in Nordic mythology,
34:42.741 --> 34:46.559
the god of wisdom. The smartest man alive or smartest god.
34:46.912 --> 34:50.377
He's a floating head in the mythology and in the
34:50.877 --> 34:54.258
show. There's a giant floating head which has someone inside,
34:54.291 --> 34:57.290
and Mimir represents the god of wisdom. So it's AI.
34:58.204 --> 35:02.150
And Mimir has been spewing toilet
35:02.650 --> 35:06.240
paper All over to help the goats write,
35:06.320 --> 35:09.800
write the code and get it pushed to production. So for a while there,
35:09.848 --> 35:13.665
the tree was all red and yellow and looked unhealthy because
35:14.483 --> 35:18.251
there was just so much toilet paper on the stage. So, so that
35:18.751 --> 35:21.860
is just one part of Goatmire that was already, that already would have been the
35:22.196 --> 35:25.323
greatest, coolest thing we could talk about for the entire next year. Right.
35:25.628 --> 35:28.675
But then there were also the, the, the starting show on, on Wednesday.
35:29.266 --> 35:32.245
Right. I didn't see it because I was the first speaker right after, so I
35:32.423 --> 35:36.001
couldn't see it too well from behind the stage, but you saw it,
35:36.065 --> 35:39.273
right? Yeah, I mean, it's still part of the goat story,
35:40.442 --> 35:44.872
and it introduced Odin and Lars and a whole bunch of the characters
35:44.904 --> 35:48.328
in this. But I kind of actually
35:48.828 --> 35:52.142
want to talk about the orchestra. Oh, yes. And the live music that
35:52.642 --> 35:56.532
we have, because there's not only people that are up there on
35:57.032 --> 36:00.270
stage acting out some of these scenes, there's also music to accompany them,
36:02.341 --> 36:05.725
which is what I was helping set up when I came here early. Because a
36:06.225 --> 36:09.647
lot of fun. Because listener, imagine, I mean, you imagine an
36:09.663 --> 36:13.417
orchestra or maybe you just imagine, you know, like a xylophone
36:14.017 --> 36:17.307
and a drum set and a crash cymbal.
36:17.761 --> 36:21.711
And then also you had like a bell. So these
36:21.743 --> 36:25.223
are all instruments. And when we talk about live music, you would think that people
36:25.351 --> 36:28.606
play these instruments. However— That's not the case.
36:28.815 --> 36:33.096
It's not the case. These are Nerves-powered devices? These are Nerves-powered devices,
36:33.289 --> 36:36.031
and they're spread out throughout the entire auditorium.
36:37.073 --> 36:40.200
So the glockenspiel, which is the
36:40.700 --> 36:43.455
xylophone-like thing, is right up at the front. There's a drum set kind of up
36:43.955 --> 36:48.057
at the front, but up in the balcony, there's 3 singing bowls.
36:48.522 --> 36:51.426
There's cymbals somewhere over in the crowd.
36:51.555 --> 36:55.838
There's a whole bunch of stuff. A whole orchestra. A whole orchestra.
36:56.207 --> 36:59.191
And it's all connected to a Wi-Fi network in the theater.
36:59.817 --> 37:03.587
And it's all, all the devices, they're all like Raspberry Pis that are just
37:04.087 --> 37:07.919
powered there. And they are hooked up to a cluster on
37:08.419 --> 37:12.187
that network. And they're all driven by a laptop offstage. And that laptop
37:12.267 --> 37:15.810
has an app in it that one shows a whole dashboard of
37:15.939 --> 37:19.624
all the devices that are connected and, and controlling. It's like the, the big
37:20.124 --> 37:24.512
controller of everything. And they're taking MIDI files, the music,
37:25.073 --> 37:28.518
the digital music files, and dropping them into the
37:28.599 --> 37:32.525
app. And then they click play and then the whole orchestra just starts going and
37:32.541 --> 37:35.874
it's just sending RPC calls to all of the devices that say,
37:35.890 --> 37:38.342
hey, play this note now. Hey, play this note now. Hey, play this note now.
37:38.390 --> 37:41.034
So for every note you have an RPC call or is it kind of like
37:41.114 --> 37:44.720
buffered or periodic? It's buffered a little bit because network latency. So they
37:45.220 --> 37:49.364
say in When your clock reaches this time, then play
37:49.478 --> 37:52.999
that note. Okay. Right. And all the notes are driven by solenoids.
37:53.689 --> 37:57.343
So a solenoid is just a little device.
37:57.423 --> 38:01.062
It has an iron or steel core
38:01.126 --> 38:04.577
inside of it, a rod that can slide up and down, and then
38:05.077 --> 38:07.988
it has a wrap of copper wire. And so when you apply a current through
38:08.488 --> 38:11.125
that wire, it creates a magnetic field, which then triggers the iron to move.
38:11.638 --> 38:14.795
To move, like up or down. Up or down. So it's used
38:14.811 --> 38:18.674
for valves a lot. So it's like a switch on-off, things like
38:19.174 --> 38:22.664
that. And here we're using it, we're triggering it really fast to like be
38:23.164 --> 38:26.495
the hammer to hit the xylophone. Or for the drums,
38:26.703 --> 38:30.101
it's pulling down and it pulls the drumstick and hits the drum.
38:31.335 --> 38:33.578
The drums are really cool, by the way. They are really cool. So cool.
38:33.803 --> 38:37.329
Yeah. And the thing is, when I first
heard the music, I was like,
38:37.345 --> 38:41.351
okay, this is a background track. You're just playing, you know, you're pressing play on
38:41.851 --> 38:45.320
the speaker. AV tech guy to go play a cue. Exactly. Okay, play. But no,
38:45.820 --> 38:49.730
these are real devices spread out through the audience, through the theater.
38:50.700 --> 38:53.920
And yeah, and then you see that, oh, because you hear the xylophone and there's
38:54.420 --> 38:57.220
a nice melody and everything, it kind of sounds like a MIDI thing. And it
38:57.720 --> 39:00.340
resonates through the whole theater. It does. And then you're like, hang on, that's a
39:00.840 --> 39:03.980
real device, actually, a real instrument. And it's played by a Neurse
39:04.480 --> 39:07.960
device, which is— Just so cool. And I'm really happy because
39:08.460 --> 39:12.067
I got to Rickroll the audience. I don't know if you saw my 10-minute
39:12.567 --> 39:16.156
spiel up on stage. I think you might've been prepping or chilling after your talk.
39:16.637 --> 39:19.956
But, um, I had 10 minutes on stage where I was talking about,
39:20.389 --> 39:24.317
we'll get to them, the badges. But, um, and last
39:24.817 --> 39:27.925
year I had pseudo mode, if you remember. Pseudo mode for the badge. For the
39:28.425 --> 39:31.356
badge. Right. And it's in the settings. And so when you activate pseudo mode,
39:31.933 --> 39:35.364
uh, you get a Rickroll on the screen. Um, so this year I was
39:35.380 --> 39:38.748
telling them how to, how, how to use these badges. And of course I have
39:38.764 --> 39:42.005
sudo mode, which again plays a Rickroll on the screen.
39:42.518 --> 39:45.743
Um, but when I was up on the stage, I was showing the simulator and
39:46.243 --> 39:49.673
had all the big simulator, the image on there. And then I got the,
39:50.234 --> 39:52.817
I got the team behind the stage to say, hey, when I go to sudo
39:53.317 --> 39:55.769
mode, can you play the Rickroll on the orchestra? The Rickroll.
39:56.668 --> 40:00.389
Nice. So that was a lot of fun. Yeah. You were Rickrolling
40:00.422 --> 40:04.079
the audience with NURBS-powered instruments. With NURBS-powered instruments.
40:04.674 --> 40:08.192
And then it has been a part of several talks now too. Um,
40:08.208 --> 40:11.791
the Fledex talk, which is the library that is
40:11.823 --> 40:14.538
used to power all of the LEDs. Um,
40:15.502 --> 40:19.181
Matthias, uh, had done his talk where he was talking about
40:19.197 --> 40:22.105
how all of it works, showing some code examples. And when he did the code
40:22.605 --> 40:25.993
examples, the tree, which it's a 4-meter-tall tree,
40:26.282 --> 40:29.704
like, what is that? 12 feet, 13 feet. Who knows?
40:29.881 --> 40:32.434
Um, for American Listeners,
40:33.429 --> 40:35.981
13-tall-foot tree. Um,
40:36.703 --> 40:40.588
and it has 900 NeoPixel LEDs
40:40.716 --> 40:44.793
on it, 3 strands of 300. And so each
40:44.905 --> 40:48.420
of those strands can drive the LEDs and to any color,
40:48.741 --> 40:52.417
uh, individually addressable. So along the length of the strip,
40:52.433 --> 40:55.980
you can say, I want LED 13 to be red or something like that.
40:56.077 --> 40:59.656
Yeah. So it's wrapped up around the tree, which means then they've
40:59.672 --> 41:03.265
counted all the LEDs very meticulously and they can light the
41:03.345 --> 41:07.451
leaves individually. They can light the stem individually. And yeah,
41:07.467 --> 41:10.675
it's been cool. But during Matthias's talk, since he wrote the
41:11.175 --> 41:15.117
Fletch library, he actually connected to the tree and showed the different animations
41:15.165 --> 41:18.550
that you can do with Fletch, the ways you can find things, how it's,
41:18.983 --> 41:22.591
yeah, it was very cool. I mean, so we, we had the talks,
41:22.848 --> 41:26.938
uh, the, the little place in between, we had the instruments,
41:27.082 --> 41:30.389
we had the tree. And you also already mentioned the badge. And I
41:30.889 --> 41:34.293
think the badge that, well, if you're just listening to the audio,
41:34.325 --> 41:36.654
you can't see it right now, but we're going to hold it into the camera.
41:37.538 --> 41:41.634
We described it, you know, also in the last episode, but it's
41:42.134 --> 41:45.457
a little tablet with a full-size keyboard and a couple of special
41:45.730 --> 41:49.264
buttons. And it has, in the standard form, it has a kind
41:49.764 --> 41:53.104
of transparent tainted background so you can see inside
41:53.604 --> 41:57.246
it. Yeah. And it has a little LCD screen. OLED even.
41:57.599 --> 42:01.576
No, it's just LCD. Just LCD screen. And it's running on AtomVM.
42:02.025 --> 42:06.259
And I mean, last year already you had some badges, which compared to these felt,
42:06.516 --> 42:09.643
you know, like the beta version of badges. And this feels to
42:10.143 --> 42:13.556
be like the 1.0 version of the badge. I certainly learned a lot when we
42:13.572 --> 42:17.341
did the badges last year. But the cool thing is you also
42:17.841 --> 42:20.725
had a workshop about them on Tuesday, right? Where you first handed them out.
42:20.933 --> 42:24.444
Right. Out of a sudden, like, okay, there are some
42:24.700 --> 42:27.953
apps on here that are cool, but then people just started going nuts
42:28.162 --> 42:31.206
with adding their own. Absolutely crazy. I've been blown away.
42:31.511 --> 42:34.380
The people who got the badges early also like learned how to put code on
42:34.412 --> 42:37.905
them. And then of course, with the advent of AI and
42:38.017 --> 42:41.351
whatnot, LLMs, people have just been going to town.
42:41.783 --> 42:45.004
It's crazy. I've been, every time someone comes
42:45.504 --> 42:47.248
up to me and says, hey, look at the badge. This is the app I
42:47.748 --> 42:51.719
made. Like, I'm just blown away. So, so which, which some of
42:52.219
--> 42:55.665
the apps that I saw were Connect Four between
42:55.729 --> 42:58.987
2 badges. Between 2 badges. So at the top of the badges,
42:59.099 --> 43:02.469
there are 2 little LED— no, what's that?
43:02.806 --> 43:05.454
Yeah. IR receiver and transmitter. Yeah.
43:05.598 --> 43:08.727
Infrared transmitter and receiver. And if you
43:09.227 --> 43:12.498
hold them top to top, 2 badges, they can communicate
43:12.998 --> 43:16.879
through infrared. And you can use that to then, for example, play Connect
43:16.911 --> 43:20.842
Four. Right. The intended use case for this was to be I
43:21.342 --> 43:24.832
call it poor man's NFC. You tap 2 badges together and then you
43:25.332 --> 43:28.887
can share your contact details. And that's worked surprisingly well.
43:29.560 --> 43:32.508
I was not certain that it would work so well, but people seem to be
43:32.540 --> 43:36.194
having a good time sharing their contact info. Um, and so,
43:36.706 --> 43:39.991
but since it's there, it's exposed to some of the things that the, the,
43:40.216 --> 43:43.805
the apps can take advantage of. So Benjamin Mildy,
43:44.462 --> 43:47.557
uh, lost Cobra Kai on the forum and most places online.
43:47.991 --> 43:51.798
He made Connect Four where you put
43:52.298 --> 43:55.959
the badges up next to each other, you press, you can start
43:56.104 --> 43:58.449
your moves and then it sends it to the next badge and then they can
43:58.949 --> 44:01.598
see their moves. And then from there, it's, yeah, it's really cool.
44:01.742 --> 44:05.357
And so Connect Four, and then we also saw, which other apps did you see?
44:06.256 --> 44:10.417
For IR, I saw a couple people using multiplayer
44:10.917 --> 44:13.887
games where they would share the joining info.
44:14.354 --> 44:17.415
And then connect to Wi-Fi and then just connect
44:17.915 --> 44:22.731
directly to them. And so one guy made a racing game and
44:23.231 --> 44:26.371
it renders like much faster than I ever thought it would.
44:26.532 --> 44:29.655
Is it like 30 frames per second even? Not quite 30 frames per second.
44:30.092 --> 44:33.977
It's like 4 frames per second. Oh, still good enough. Yeah. Plenty fun. And then
44:34.477 --> 44:38.042
you could move the race. You could play with your arrows. You could play
44:38.542 --> 44:41.597
with the arrow keys or there's an accelerometer on the badge. And so you can
44:41.634 --> 44:45.124
tilt it. And so, isn't that just, it's so much fun.
44:45.797 --> 44:48.569
So you tilt it to the right and then the car drives to the right.
44:48.698 --> 44:52.095
Exactly. Tilt it to the left, it drives to the left. Can you accelerate and
44:52.287 --> 44:55.700
decelerate maybe? You had to press the spacebar for the acceleration.
44:55.812 --> 44:59.226
So that's the next step then. Yeah. I'll tell him he shouldn't, he should
44:59.242 --> 45:02.350
make it like that. I've also seen,
45:03.424 --> 45:06.405
um, Doodle Jump. Do you know that game? Doo Doo Jump?
45:06.709 --> 45:10.333
Doodle. Doodle Jump. It's the one where it's like platforms and you're
45:10.833 --> 45:14.472
trying to go up infinitely, essentially. And so originally
45:14.488 --> 45:16.975
the first version he showed me is like, oh, you have this little blob and
45:17.475 --> 45:19.670
it's bouncing from platform to platform and you can control it with the arrows.
45:20.087 --> 45:23.456
Then he did the same thing with the accelerometer. Then you can rotate
45:23.956 --> 45:27.291
the badge and make it, make the game work. And then
45:27.708 --> 45:31.141
he changed the blob to a goat for Goatmire. Of course. Of course.
45:31.879 --> 45:35.200
And then he made the different platforms. Some of them
45:35.700 --> 45:38.809
are trampoline, they bounce you way up. Some of them are They break the first
45:39.309 --> 45:43.282
time you hit them. Some of them have spikes on them. So I'm just
45:43.782 --> 45:47.033
shocked that it can handle all this. And that is all running on AtomVM,
45:47.113 --> 45:50.672
right? All of it's running on AtomVM. Okay. In Elixir. In Elixir.
45:51.152 --> 45:54.519
Someone else made a Tamagotchi. Uh, someone made a,
45:54.583 --> 45:58.190
like a 3D, uh, like the Raycaster
45:58.414 --> 46:01.508
Wolfenstein. Right. Like, like Doom kind of thing
46:01.620 --> 46:05.451
where you walk towards, like through A maze
46:05.788 --> 46:09.778
of rooms with walls to the side and you can move forward and sideways.
46:10.034 --> 46:13.303
Right. The one I'm really excited for and
46:13.479 --> 46:16.124
that I need to spend some more time because it's a bit more of an
46:16.624 --> 46:19.056
involved change, but it is going to be, it's going to land as a PR
46:19.665 --> 46:23.239
and we're going to have it in eventually. But, um, there is
46:23.431 --> 46:26.411
an implementation of an app store for,
46:26.956 --> 46:30.225
for, for the badges. And I think that's super cool.
46:30.707 --> 46:35.217
Um, because yes, the games are really neat, but as myself,
46:35.297 --> 46:38.989
I don't want to include them all by default on the base firmware.
46:39.390 --> 46:42.407
And they take up a lot of space if they have big images and things
46:42.907 --> 46:45.457
like that. So you can't download all the apps, you can't include them all.
46:46.051 --> 46:49.389
But if there's an app store, you can download them, you can offload them,
46:49.566 --> 46:52.631
you can do whatever. Like, I'm really excited for that.
46:52.792 --> 46:56.483
And I've talked with a different Matthias. Yeah. Um,
46:56.708 --> 46:59.645
he's, uh, been implementing this and so That's,
47:00.014 --> 47:03.948
it's really cool. I'm excited for that. Um, but look for those changes after
47:04.448 --> 47:08.091
Goatmire. I think this thing, it seems like it's a fun, it's a fun
47:08.203 --> 47:12.089
toy. It's a fun way to like have your first hands-on
47:12.137 --> 47:15.332
experience
with AtomVM. And I'm really excited to see where people take this.
47:15.670 --> 47:18.929
But it's great hardware too. You know, it's, it's a good LCD screen.
47:18.977 --> 47:23.200
It's a good keyboard and it has the infrared and the accelerometer.
47:23.441 --> 47:27.371
Yeah. Yeah. So. There's so many, there's a lot of capacity that
47:27.871 --> 47:30.897
you can just play around with. Yeah. And that's what I learned last year with
47:31.397 --> 47:34.744
the E-Ink badges. They're really cool devices, but our use
47:34.760 --> 47:38.303
case for them was, I mean, it was just really
47:38.803 --> 47:42.182
minimal. It had 2 buttons on it, an E-Ink screen,
47:43.577 --> 47:47.072
and that's about it. Yeah, the refresh rate was not great to, and not
47:47.088 --> 47:50.422
fast enough to write, uh, to play games. I mean, you made Snake on it,
47:50.470 --> 47:53.932
but that's about the limit of what you could do. It was updating once
47:54.432 --> 47:56.289
a second, so that was still okay. Oh, speaking of Snake, I saw someone made
47:56.305 --> 47:59.403
Snake. Someone made Tron, someone made, uh,
47:59.676 --> 48:03.514
yeah, a bunch of stuff. And, and the, so yesterday evening
48:03.546 --> 48:07.223
we went out for dinner and somebody else showed you, showed you the batch and
48:07.723 --> 48:10.129
you were blown away. I was blown away. So,
48:11.574 --> 48:14.770
so we ship these with AtomVM and the idea is that you would
48:15.270 --> 48:19.105
run this with AtomVM because it's an Elixir conference. And of
48:19.121 --> 48:21.642
course we are encouraging that, but someone else had said,
48:22.556 --> 48:26.482
Hey, this is a really cool hardware platform. And I know that what's inside the
48:26.982 --> 48:30.151
chip is an ESP32-S3. And,
48:30.728 --> 48:34.077
um, it's supported
48:34.093 --> 48:36.801
for a lot of like retro gaming emulators.
48:37.458 --> 48:40.919
And so there's a project, I don't know which one he actually did, but he
48:41.419 --> 48:45.437
basically forked it, added support for the keyboard, um, and then got
48:46.030 --> 48:49.555
a retro gaming emulator running on this badge in C or Rust or whatever
48:50.055 --> 48:53.312
it was. written in. Um, and so when he handed it to me, it was
48:53.504 --> 48:57.470
loaded up with old school Mario. It was Mario playing on
48:57.743 --> 49:00.794
the little screen. On the badge. And the keyboard worked and
49:01.294 --> 49:04.198
like, oh, I was just blown away. And it was, it was a very fast
49:04.698 --> 49:08.742
refresh rate, faster than we have with AtomVM, to be expected because they're,
49:08.903 --> 49:12.114
it's not rendering, it's rendering in buffers and can do
49:12.614 --> 49:15.261
a lot of optimizations, whereas we render each frame completely.
49:15.806 --> 49:18.996
So it was very cool. There's a lot of potential for these devices.
49:19.173 --> 49:22.459
I'm really excited to see what people do with them. And yeah,
49:22.940 --> 49:25.825
hopefully at some point in the future, I think that we might be able to
49:26.325 --> 49:29.320
make these available for people who didn't go to Goatmire. Yeah. But for now,
49:29.464 --> 49:32.558
if you are not here, I, yeah,
49:32.638 --> 49:35.636
you really missed out so much. You did. Not to add to the FOMO,
49:35.860 --> 49:39.018
but— Well, yeah, but I mean, now it's over and you could just only feel
49:39.066 --> 49:42.256
bad for not being here. We told
49:42.756 --> 49:45.943
you, you gotta come. We told you many times, like, this is the conference of
49:46.443 --> 49:49.773
the year and it will not happen next year. And after that, it's undecided
49:49.789 --> 49:53.058
yet. So I think this, that also has led
49:53.234 --> 49:57.385
Lars and the team to make it the biggest event
49:57.481 --> 50:00.285
and everything they wanted to do now. Yeah.
50:00.718 --> 50:04.051
It's okay. Lars needs a life. He's just been— He needs a
50:04.551 --> 50:07.015
life. He needs a rest. Yeah, he does. Really. I think it was his wife
50:07.031 --> 50:10.557
mostly who said, well, yeah. Yeah. I think
50:10.717 --> 50:14.644
it's, it's something that's incredibly fulfilling, but he also I
50:15.144 --> 50:18.606
don't think he gets to experience the conference. He's behind the scenes, in the,
50:18.815 --> 50:22.360
behind the stage, like prepping the next person. Okay. Are you ready to go speak?
50:22.441 --> 50:26.243
Are you ready to do this? Not to mention the whole show that's going on.
50:26.580 --> 50:29.917
So it's been exciting. I also have really liked to
50:29.965 --> 50:33.430
see that Pushin has been mentioned a lot and used
50:33.559 --> 50:36.895
in some of the skits used by a lot of presenters that
50:36.928 --> 50:40.361
are putting their slides or projects on Pushin. Yeah. How has
50:40.393 --> 50:44.580
that been? It's been absolutely amazing and
50:45.080 --> 50:48.879
a little, not overwhelming, but like intimidating at
50:49.379 --> 50:52.938
how much people like the platform. Yeah. So people just
50:53.438 --> 50:55.633
started signing up for it and then I walk around and they're like, oh,
50:56.114 --> 50:59.643
you're Peter. Are you that Peter? The Push-in Peter? I'm like, yeah, I'm the
51:00.143 --> 51:03.574
Push-in Peter. So I got plenty of signups and it's just
51:04.074 --> 51:07.713
the best feeling. It's an amazing feeling. I went to the lightning
51:07.809 --> 51:10.247
talks 2 days ago and that's when I saw it for the first time.
51:10.712 --> 51:13.808
Where the speaker of the lightning talk, he said, well, this is my project.
51:14.225 --> 51:17.096
And I put it on this thing that people like, which is called Pushin.
51:17.225 --> 51:20.256
So here's the link to pushin.eu. And I was like,
51:20.320 --> 51:23.561
man, that felt so good. Yeah. And that
51:24.061 --> 51:26.736
has been, yeah, kind of snowballing. It's come up quite a few times. Yeah.
51:26.833 --> 51:30.217
And it's just now I see it on the slides a lot. People talk
51:30.717 --> 51:34.869
to me about their use cases. I have plenty of feature requests
51:35.369 --> 51:37.740
as well, but also people like who say, oh, I really want to use this
51:38.240 --> 51:42.180
full-time. Um, lots of development on that front. Right. And I
51:42.228 --> 51:45.882
think the greatest thing, one of the greatest things about the Elixir community
51:46.058 --> 51:49.520
in general is the culture. We have a
51:50.020 --> 51:53.142
very, people are nice, just genuinely
51:53.642 --> 51:57.613
nice people in our community. And I feel like this is a great way for
51:58.238 --> 52:02.069
you to, like a great place to launch Pushin because I mean,
52:02.197 --> 52:06.107
it's Git hosting. It's not, it's completely agnostic to whatever language,
52:06.428 --> 52:09.907
but because you're in this community, I feel like People are
52:10.407 --> 52:13.309
really supportive. People are gonna send you bug reports and not, you know,
52:14.753 --> 52:18.219
be mad. Your code is terrible. I hate your platform.
52:18.299 --> 52:21.636
Why don't you just use GitHub? Exactly. Yeah, no, I, that is
52:22.294 --> 52:25.294
also why I decided to kind of launch it here first.
52:25.359 --> 52:28.808
I mean, I would always have done that, but I felt really good about first
52:29.308 --> 52:32.483
inviting everyone in the Elixir community to it because yeah,
52:32.819 --> 52:36.109
I do need to beta test it and stress test it and I don't have
52:36.609 --> 52:39.203
all the features yet. you know, all the scalability in the world.
52:39.716 --> 52:43.291
Like, this is a very, very nice community to launch that product in. It is.
52:43.547 --> 52:46.897
Yeah. And it has like already gotten beyond that community.
52:47.025 --> 52:50.504
I'm getting interest from JavaScript, which is scary.
52:51.401 --> 52:55.232
Unleash the cannon. Hold back. Yeah. Like, I'm happy
52:55.248 --> 52:58.662
to collaborate with you on your projects, but maybe
52:58.710 --> 53:01.820
hold back on like promoting it too hard because I can't
53:02.320 --> 53:06.485
support 10, 100,000 users, right? Right. Your one server.
53:06.886 --> 53:09.436
Yeah, I still only have one server. That's going to change in the next,
53:09.452 --> 53:12.371
in this month actually. And then I need to work on CI, which is going
53:12.871 --> 53:15.498
to happen the month after. Well, since we last talked about it,
53:16.027 --> 53:19.507
you've announced you're going full-time on Pushin, right? Yes. So from October,
53:19.652 --> 53:23.613
so today's October 2nd, it's already my second day full-time on
53:23.725 --> 53:27.013
Pushin. I'm still going to do the EEF security work. So don't worry about
53:27.513 --> 53:30.605
that. I, that's my part-time that also pays my bills. We worry about that.
53:30.846 --> 53:34.213
We worry about getting a message from you. Yeah. Sometimes I
53:34.710
--> 53:37.212
feel bad when I message people on Slack, just say hi,
53:38.238 --> 53:40.210
you know, and then they're like, oh my God, I already know what's going to
53:40.710 --> 53:45.037
happen next. Yeah. But no, that's going to continue with
53:45.537 --> 53:48.276
the EF for at least a couple of more months until next year.
53:49.126 --> 53:52.830
However, we do struggle with financing and, uh,
53:53.856 --> 53:57.801
yeah, so this, this whole security work has been financed by the
53:57.945 --> 54:01.778
EF through donations from foundations and so on, but that money is
54:01.874 --> 54:05.324
drying up. We do have a little bit more, but yeah,
54:05.564 --> 54:08.870
it's not enough to really do this sustainably for longer
54:08.934 --> 54:12.271
than, let's say, 7 more months. So until like mid next year.
54:13.106 --> 54:16.844
Yeah. So if you, and I think all of you in the ecosystem
54:17.278 --> 54:21.417
have profited from this work, you know, you're living in a secure,
54:21.786 --> 54:25.060
more secure ecosystem now. Yeah,
54:25.621 --> 54:29.408
go talk to your boss, to your CTO, whoever has the
54:29.908 --> 54:33.860
credit card basically. Yeah. And tell them that they need to start
54:34.360 --> 54:37.660
financing this security work in the EFF. And they can do that with a sponsorship.
54:38.699 --> 54:42.200
If they, yeah, they can just sign up for it. There are different new tiers
54:42.700 --> 54:46.580
also. They can now pay more than $10,000 a year, which also has
54:47.080 --> 54:50.700
held the EFF a little bit back. Now they can go up to $64,000 a
54:51.200 --> 54:55.020
year. And also project-based financing is also there. So if they want to give
54:55.520 --> 54:58.800
more, that's certainly possible as well. And also you personally,
54:59.300 --> 55:00.640
if you just become an EFF member for $100 a year,
55:02.537 --> 55:06.389
You are supporting this work and not only financially, but also kind
55:06.889 --> 55:10.882
of with your vote, with your number. Because if we say we
55:11.382 --> 55:14.525
have a large, very large community and many of the Elixir developers
55:14.653 --> 55:18.553
are EEF members, then that also gives us more negotiation
55:18.601 --> 55:21.939
power when talking to foundations and people with money.
55:22.693 --> 55:25.806
Right. This has been a topic that's come up a number of times during the
55:26.306 --> 55:30.219
conference and it's really important work for community. And we can't
55:30.719 --> 55:33.941
stress enough how bad it would be if the EFF did
55:34.441 --> 55:38.161
not exist. So, um, let's make sure
55:38.661 --> 55:41.866
that we don't get to that point. Let's make sure the funding keeps, uh,
55:42.252 --> 55:45.364
keeps the EFF afloat and doing the great work that they do.
55:45.941 --> 55:49.712
So please, please talk to the decision makers.
55:49.968 --> 55:53.129
Just to make it clear, if by, in the next couple of
55:53.629 --> 55:57.459
months, if we don't find substantial new financing,
55:58.149 --> 56:00.955
this work will cease next year, beginning of next year.
56:01.500 --> 56:04.675
Yeah. That's it. And then there will be no one
56:04.723 --> 56:08.571
in the ecosystem who looks for reports for vulnerabilities and reports them
56:09.373 --> 56:12.884
and does the whole triaging and publishing of the CVEs and
56:13.384 --> 56:16.813
that. There will be nobody left because I can't work without getting paid
56:17.313 --> 56:20.918
for it. You know, Jonathan, the CCO of EEF, he also can't work without
56:21.418 --> 56:24.303
getting paid for it. And he already has been getting paid less than he should
56:24.803 --> 56:28.509
have because money was drying up. Yeah, so very
56:28.525 --> 56:32.089
clear, if we don't get money, this work will cease. That's it.
56:32.458 --> 56:35.589
Cut and dry. Cut and dry. But anyway, we have
56:36.089 --> 56:39.682
to go back to the beautiful Goatmire conference now. We haven't even spoken about
56:40.182 --> 56:43.984
talks and learnings. Not to mention it's been amazing talks. The talks
56:44.032 --> 56:46.922
were amazing. Okay, real quick. One, one. What's your favorite? But I don't want to
56:46.986 --> 56:50.661
toot my own horn, but I think I really I
56:51.879 --> 56:55.326
put so much creativity into my talk and it was the first talk of the
56:55.826 --> 56:59.029
conference on Wednesday morning after the first
56:59.529 --> 57:03.325
theatrical play of all of you, of the team around Lars. And then
57:03.357 --> 57:07.220
I came out and I thought, I can't come out here, first talk of Goatmire
57:07.669 --> 57:10.907
and be a boring, just clicking through the slides talk.
57:11.548 --> 57:14.802
So what did I do? So first of all, you had
57:15.302 --> 57:18.553
on a whole Viking outfit. Yes. Um, it was,
57:19.066 --> 57:23.138
it was a sight to see, to say the least, at 9
57:23.638 --> 57:27.145
AM on a Wednesday morning. Um, yeah. So you had
57:27.645 --> 57:30.880
a whole outfit and then you also were very visual
57:31.233 --> 57:34.503
in your descriptions of how radios work. Um,
57:34.840 --> 57:38.206
so you're, you, you compared radio waves to that
57:38.286 --> 57:41.621
of a pendulum and the swinging of a pendulum. And before the,
57:42.230 --> 57:45.115
before, before your talk, you were like, hey Gus, do you have anything that's like,
57:45.339 --> 57:48.129
like a pendulum? I was like, uh, we could put a badge on a string
57:48.161 --> 57:51.018
or something. He's like, I kind of wanted something more rigid or something.
57:51.147 --> 57:54.166
I'll figure it out. Come his talk,
57:54.647 --> 57:58.036
he's up there on the stage swinging his arms back and forth like a crazy
57:58.536 --> 58:02.339
guy. I became the pendulum. You became the pendulum. There's some really good photos
58:02.435 --> 58:05.358
of you up there that are probably trickling out by now,
58:05.743 --> 58:08.939
but it was fun. It was so much fun. I mean,
58:09.035 --> 58:11.765
the talk, like, I wanted to talk about LoRa,
58:12.166 --> 58:15.538
but then I fell down the rabbit hole into how radio
58:16.038 --> 58:19.199
works. And I explained everything from AM to FM to digital radio.
58:19.632 --> 58:23.256
And then to how LoRa works, it was kind of built up. I kept,
58:23.320 --> 58:26.094
I wanted to keep it general so that everyone takes something away from it.
58:27.249 --> 58:30.825
But it was also mostly about the creativity, just being the Viking.
58:31.338 --> 58:34.913
And when I came out, I was like, Goatmire, because I was so pumped.
58:35.010 --> 58:38.120
I was so pumped and everyone was so pumped. It was so much fun.
58:38.313 --> 58:41.424
It was great energy to bring to the start of the conference. Yeah. And I
58:41.584 --> 58:44.903
did floss. I did floss. You did floss because of course you're swinging your arms
58:44.951 --> 58:48.280
up on stage and, you know, Some of them just,
58:48.780 --> 58:50.760
one of them slips behind your back while you're— Exactly. I was doing a little
58:51.260 --> 58:54.740
flossing on stage in a Viking costume. It's just a weird pendulum.
58:55.120 --> 58:58.540
I was the weirdest pendulum ever, but I think I made my point and that's
58:59.040 --> 59:02.440
what counts. Exactly. Yeah. And with that, we're going
59:02.940 --> 59:07.000
to talk probably more about Goatmire. And we also have CodeBeam coming up where I'm
59:07.500 --> 59:10.060
going to speak. And are you going to attend CodeBeam? I will not be there.
59:10.560 --> 59:13.920
I'm taking a well-deserved break. You do. You do. You really worked hard.
59:15.094 --> 59:18.670
Yeah. So whoever will, like whoever's at the CodeBeam
59:18.782 --> 59:21.685
conference, please come and say hi to me.
59:22.375 --> 59:26.127
I'm more than happy to talk with you about this podcast, about anything,
59:26.464 --> 59:29.463
Pushin, Elixir coding, whatnot. Just, you know, approach me,
59:29.479 --> 59:32.975
say hi. And with that, thank you very much for
59:33.475 --> 59:36.679
listening. We have to go back to the conference now. I really don't want to
59:37.179 --> 59:40.319
miss that finale. Exactly. We need to go back. It's actually, it's fika time.
59:40.737 --> 59:44.053
Oh, it's fika time. It's fika time. That is a Swedish— Nah, they can
59:44.553 --> 59:46.677
look it up. Oh, okay. It's a Swedish specialty. Look up what fika is.
59:47.095 --> 59:50.668
F-I-K-A. F-I-K-A, exactly. So it's fika
59:51.168 --> 59:54.499
time, everyone. Have a good one. Thank you for joining in and see you next
59:54.999 --> 59:55.931
time on Macro Mayhem.