WEBVTT

NOTE
Transcription provided by Deepgram

00:00:01.199 --> 00:00:06.180
<v Speaker 0>Alright. Let's do this. Geek News Central, episode

00:00:06.960 --> 00:00:10.559
<v Speaker 0>eighteen forty five. Leading story today is gonna

00:00:10.559 --> 00:00:13.700
<v Speaker 0>be Apple working on all new operating system,

00:00:15.315 --> 00:00:17.555
<v Speaker 0>which I think we've talked about before on

00:00:17.555 --> 00:00:20.035
<v Speaker 0>the show. At least not me, but my

00:00:20.035 --> 00:00:22.835
<v Speaker 0>dad. Todd's talked about it in the show

00:00:22.835 --> 00:00:25.474
<v Speaker 0>before. And a little bit more information kinda

00:00:25.474 --> 00:00:28.294
<v Speaker 0>coming out on this story. Apple is developing

00:00:28.355 --> 00:00:31.599
<v Speaker 0>an all new operating system code named Charismatic

00:00:32.140 --> 00:00:38.940
<v Speaker 0>according to Bloomberg's Mark Gurman. This is likely

00:00:38.940 --> 00:00:42.655
<v Speaker 0>Apple's long rumored home OS operating system. In

00:00:42.655 --> 00:00:45.215
<v Speaker 0>a report last month, Gurman said both Apple's

00:00:45.215 --> 00:00:47.795
<v Speaker 0>rumored smart home hub in twenty twenty six

00:00:47.855 --> 00:00:50.335
<v Speaker 0>and a tabletop robot in twenty twenty seven

00:00:50.335 --> 00:00:52.894
<v Speaker 0>will run the new operating system. He said

00:00:52.894 --> 00:00:55.714
<v Speaker 0>the software platform will blend elements of tvOS

00:00:56.335 --> 00:00:59.510
<v Speaker 0>and watchOS. For example, he he expects there

00:00:59.510 --> 00:01:02.149
<v Speaker 0>to be hexagonal grid of apps just like

00:01:02.149 --> 00:01:06.790
<v Speaker 0>on the Apple Watch. I know you guys

00:01:06.790 --> 00:01:08.149
<v Speaker 0>know my dad's a big fan of the

00:01:08.149 --> 00:01:12.705
<v Speaker 0>Apple community. He had a plethora of Apple

00:01:12.705 --> 00:01:14.985
<v Speaker 0>devices, and one of his features he used

00:01:14.985 --> 00:01:17.025
<v Speaker 0>to talk about all the time was being

00:01:17.025 --> 00:01:19.424
<v Speaker 0>able to move your mouse across the different

00:01:19.424 --> 00:01:22.305
<v Speaker 0>devices and grab things from across them. So

00:01:22.305 --> 00:01:23.985
<v Speaker 0>I'm sure a lot of this is gonna

00:01:23.985 --> 00:01:27.030
<v Speaker 0>be leading to, you know, a super integrated

00:01:27.090 --> 00:01:30.770
<v Speaker 0>home, that's exclusive to Apple. I mean, Apple,

00:01:30.770 --> 00:01:33.010
<v Speaker 0>for a long time, has closed off their,

00:01:33.890 --> 00:01:37.810
<v Speaker 0>APIs to things like their, what do you

00:01:37.810 --> 00:01:40.230
<v Speaker 0>call it there? The AirPods to the phone,

00:01:41.465 --> 00:01:43.945
<v Speaker 0>to, like, the public. So, you know, it's

00:01:43.945 --> 00:01:48.505
<v Speaker 0>gonna be very close ended, I assume. But

00:01:48.505 --> 00:01:51.385
<v Speaker 0>really cool stuff. They've always developed cool new

00:01:51.385 --> 00:01:54.025
<v Speaker 0>stuff and really interesting kinda how we're leading

00:01:54.025 --> 00:01:57.750
<v Speaker 0>back into the, smart home. I'm thinking back

00:01:57.750 --> 00:02:00.390
<v Speaker 0>to Nest and, Tony Fidel. If you guys

00:02:00.390 --> 00:02:04.490
<v Speaker 0>have ever read his book, Build, phenomenal phenomenal

00:02:04.630 --> 00:02:08.175
<v Speaker 0>read. It talks about the well, he goes

00:02:08.175 --> 00:02:10.095
<v Speaker 0>to the creation of the iPod and then

00:02:10.095 --> 00:02:12.655
<v Speaker 0>going on to building out Nest before being

00:02:12.655 --> 00:02:15.695
<v Speaker 0>bought out by Google. So really awesome read

00:02:15.695 --> 00:02:18.735
<v Speaker 0>if you haven't checked that out, but, kinda

00:02:18.735 --> 00:02:20.255
<v Speaker 0>reminds me of that. You know? Just going

00:02:20.255 --> 00:02:23.650
<v Speaker 0>back into that, smart home era. See what

00:02:23.650 --> 00:02:25.970
<v Speaker 0>we'll do here. All these companies will start

00:02:25.970 --> 00:02:31.490
<v Speaker 0>releasing new home devices, I'm sure. But the

00:02:31.490 --> 00:02:33.970
<v Speaker 0>platform was really revolves around clock faces and

00:02:33.970 --> 00:02:37.455
<v Speaker 0>widgets, and it'll have multi user support. Berman

00:02:37.995 --> 00:02:40.955
<v Speaker 0>said, users will primarily interact with it using

00:02:40.955 --> 00:02:44.955
<v Speaker 0>Siri voice commands, but touch will also be

00:02:44.955 --> 00:02:47.915
<v Speaker 0>an option. Some of the preinstalled apps from

00:02:47.915 --> 00:02:51.275
<v Speaker 0>Apple will apparently include calendar, camera, music reminder,

00:02:51.275 --> 00:02:55.140
<v Speaker 0>and notes. So this device is meant to

00:02:55.140 --> 00:02:57.540
<v Speaker 0>be easily shared. They include a front facing

00:02:57.540 --> 00:02:59.940
<v Speaker 0>camera that can scan users' faces as they

00:02:59.940 --> 00:03:02.840
<v Speaker 0>walk toward it and automatically change the layout,

00:03:02.980 --> 00:03:05.620
<v Speaker 0>features, and content to the preferences of that

00:03:05.620 --> 00:03:09.715
<v Speaker 0>person. So the camera is always recording. It's

00:03:09.715 --> 00:03:12.375
<v Speaker 0>always on. And it kinda goes for the

00:03:12.515 --> 00:03:15.555
<v Speaker 0>the the microphone too with the it being

00:03:15.555 --> 00:03:20.435
<v Speaker 0>largely driven by Siri. Kinda interesting. We all

00:03:20.435 --> 00:03:28.020
<v Speaker 0>know the Apple's big privacy. We wanna do

00:03:28.020 --> 00:03:30.020
<v Speaker 0>a little shout out to our incredible sponsors

00:03:30.020 --> 00:03:33.780
<v Speaker 0>at GoDaddy. Score exclusive deals and discounts at

00:03:33.780 --> 00:03:37.194
<v Speaker 0>GoDaddy or, actually, at Geek News Central dot

00:03:37.194 --> 00:03:40.954
<v Speaker 0>com forward slash GoDaddy. And to you, all

00:03:40.954 --> 00:03:44.075
<v Speaker 0>of our listeners, as you know, you are

00:03:44.075 --> 00:03:46.875
<v Speaker 0>the heartbeat of this show. If you wanna

00:03:46.875 --> 00:03:49.194
<v Speaker 0>support GNC, head to Geek News Central dot

00:03:49.194 --> 00:03:52.050
<v Speaker 0>com forward slash insider and become a GNC

00:03:52.190 --> 00:03:56.670
<v Speaker 0>insider. We are not living live. I know

00:03:56.670 --> 00:03:58.590
<v Speaker 0>he used to always be living live, but

00:03:58.590 --> 00:04:00.770
<v Speaker 0>we are not living live. This is prerecorded.

00:04:01.710 --> 00:04:04.895
<v Speaker 0>But, that doesn't mean you can't grab yourself

00:04:04.895 --> 00:04:07.215
<v Speaker 0>a modern podcast app at podcast apps dot

00:04:07.215 --> 00:04:09.855
<v Speaker 0>com. Definitely will open you up to the

00:04:09.855 --> 00:04:13.055
<v Speaker 0>full podcast listening experience. Streaming stats is a

00:04:13.055 --> 00:04:17.180
<v Speaker 0>really, really cool feature. Of course, you can

00:04:17.180 --> 00:04:18.620
<v Speaker 0>check out the full Geek News Central universe

00:04:18.620 --> 00:04:20.060
<v Speaker 0>at geek news central dot com, where you'll

00:04:20.060 --> 00:04:21.900
<v Speaker 0>find all of our partner shows and, of

00:04:21.900 --> 00:04:23.740
<v Speaker 0>course, tons of great content produced on a

00:04:23.740 --> 00:04:26.700
<v Speaker 0>weekly basis. Stay in the loop, follow or

00:04:26.700 --> 00:04:29.600
<v Speaker 0>subscribe to the podcast via your favorite podcast

00:04:29.740 --> 00:04:31.445
<v Speaker 0>apps, and and don't forget to sign up

00:04:31.445 --> 00:04:36.085
<v Speaker 0>for our newsletter for insider scoops. So email

00:04:36.085 --> 00:04:38.645
<v Speaker 0>us directly at geek news central dot com

00:04:38.645 --> 00:04:40.725
<v Speaker 0>or geek news central or geek news at

00:04:40.725 --> 00:04:43.620
<v Speaker 0>g mail dot com. Geek news at g

00:04:43.620 --> 00:04:45.920
<v Speaker 0>mail dot com. We do wanna continue to

00:04:45.920 --> 00:04:47.940
<v Speaker 0>thank our long term sponsor of the podcast,

00:04:48.400 --> 00:04:53.280
<v Speaker 0>GoDaddy, and thank them for their support. They've

00:04:53.280 --> 00:04:54.640
<v Speaker 0>been a long time support of the show.

00:04:55.345 --> 00:04:56.705
<v Speaker 0>Much as long as I can remember, as

00:04:56.705 --> 00:04:59.044
<v Speaker 0>long as he's been doing the podcast. So,

00:05:00.065 --> 00:05:02.385
<v Speaker 0>still got the codes. They're still ready to

00:05:02.385 --> 00:05:04.465
<v Speaker 0>rock and roll. You can start yourself a

00:05:04.465 --> 00:05:08.385
<v Speaker 0>website today. I recently started my own, little

00:05:08.385 --> 00:05:10.680
<v Speaker 0>website that I've been playing with, and it's

00:05:10.680 --> 00:05:12.920
<v Speaker 0>been cool. GoDaddy makes it really easy to

00:05:12.920 --> 00:05:16.200
<v Speaker 0>get a word WordPress site built up. We

00:05:16.200 --> 00:05:19.800
<v Speaker 0>typically offer two really big deals, I will

00:05:19.800 --> 00:05:22.360
<v Speaker 0>say. They do codes that make it easier.

00:05:22.360 --> 00:05:25.475
<v Speaker 0>It could be new central. Grad GoDaddy's economy

00:05:25.475 --> 00:05:27.415
<v Speaker 0>hosting for just six ninety nine a month.

00:05:27.555 --> 00:05:29.315
<v Speaker 0>That's a full year of hosting with free

00:05:29.315 --> 00:05:32.615
<v Speaker 0>domain name, professional email, and an SSL certificate.

00:05:33.955 --> 00:05:35.875
<v Speaker 0>If in if you're interested in WordPress, like

00:05:35.875 --> 00:05:37.395
<v Speaker 0>I was talking about, it's just twelve ninety

00:05:37.395 --> 00:05:39.960
<v Speaker 0>nine. Twelve ninety nine a month. And includes

00:05:39.960 --> 00:05:42.040
<v Speaker 0>a free domain name, professional email, and an

00:05:42.040 --> 00:05:44.520
<v Speaker 0>SSL certificate, which is kinda sweet. Because I

00:05:44.520 --> 00:05:47.820
<v Speaker 0>think if you don't go through the codes,

00:05:47.960 --> 00:05:50.200
<v Speaker 0>you the email's like an add on. The

00:05:50.200 --> 00:05:52.765
<v Speaker 0>SSL certificate's an add on. So you get

00:05:52.765 --> 00:05:54.205
<v Speaker 0>you get all this for a year with

00:05:54.205 --> 00:05:55.645
<v Speaker 0>the codes, and it really is gonna save

00:05:55.645 --> 00:05:57.885
<v Speaker 0>you a lot of money upfront, with setting

00:05:57.885 --> 00:06:01.165
<v Speaker 0>up your website. If you just need a

00:06:01.165 --> 00:06:03.245
<v Speaker 0>don't domain name all all all by itself,

00:06:03.245 --> 00:06:07.310
<v Speaker 0>just eleven ninety nine. Just, head over to

00:06:07.310 --> 00:06:10.509
<v Speaker 0>the codes at, geek news central dot com

00:06:10.509 --> 00:06:16.270
<v Speaker 0>slash godaddy. And, list of codes we got

00:06:16.270 --> 00:06:19.425
<v Speaker 0>all set up there. If you're not technically

00:06:19.485 --> 00:06:22.925
<v Speaker 0>inclined, GoDaddy also does a little website builder.

00:06:22.925 --> 00:06:24.605
<v Speaker 0>You can do a three thirty thirty day

00:06:24.605 --> 00:06:26.525
<v Speaker 0>trial, and, really, mhmm, you only have to

00:06:26.525 --> 00:06:31.430
<v Speaker 0>build the website once. Right? And then we

00:06:31.430 --> 00:06:34.630
<v Speaker 0>use GoDaddy products and services here at Geek

00:06:34.630 --> 00:06:36.950
<v Speaker 0>News Central. All the websites are run off

00:06:36.950 --> 00:06:41.350
<v Speaker 0>GoDaddy and, WordPress. So it's, it's really, really

00:06:41.350 --> 00:06:43.590
<v Speaker 0>convenient. Makes it really easy to update and

00:06:43.590 --> 00:06:46.965
<v Speaker 0>share. Start your own podcast today. Come on

00:06:46.965 --> 00:06:48.645
<v Speaker 0>over to our codes. Actually, I have it

00:06:48.645 --> 00:06:51.305
<v Speaker 0>in the header now. It's linked, for anyone

00:06:51.365 --> 00:06:56.405
<v Speaker 0>to, click on. Thanks for keeping us online,

00:06:56.405 --> 00:06:58.485
<v Speaker 0>and we think, GoDaddy for their ongoing support

00:06:58.485 --> 00:07:01.620
<v Speaker 0>of the podcast. And of course, you and

00:07:01.620 --> 00:07:04.020
<v Speaker 0>your families and your friends share the codes

00:07:04.020 --> 00:07:05.140
<v Speaker 0>with them if they're trying to build a

00:07:05.140 --> 00:07:06.660
<v Speaker 0>website so that they can get a nice

00:07:06.660 --> 00:07:12.340
<v Speaker 0>deal and get that, really easily. Onto my

00:07:12.340 --> 00:07:16.414
<v Speaker 0>next little piece of news today. We, got

00:07:16.414 --> 00:07:19.474
<v Speaker 0>malicious Rust Crates steal Solana and Ethereum keys.

00:07:19.935 --> 00:07:25.294
<v Speaker 0>Eighty four twenty four. Downloads confirmed. Cybersecurity researchers

00:07:25.294 --> 00:07:27.935
<v Speaker 0>have discovered two malicious Rust Crates impersonating a

00:07:27.935 --> 00:07:31.169
<v Speaker 0>legitimate library called Fastlog to steal Solana and

00:07:31.169 --> 00:07:34.210
<v Speaker 0>Ethereum wallet keys from source code. The crates

00:07:34.210 --> 00:07:36.690
<v Speaker 0>named Faster Log and Async Print l n

00:07:36.690 --> 00:07:38.449
<v Speaker 0>were published by the threat actor under the

00:07:38.449 --> 00:07:41.990
<v Speaker 0>alias Rust Guru Man and Dumb and Based

00:07:42.130 --> 00:07:45.035
<v Speaker 0>on May twenty fifth twenty twenty five, amassing

00:07:45.175 --> 00:07:48.615
<v Speaker 0>eighty four twenty four downloads in total. According

00:07:48.615 --> 00:07:53.895
<v Speaker 0>to software supply chain, security company, Socket. I

00:07:53.895 --> 00:07:56.810
<v Speaker 0>know you guys all know I mean, or

00:07:56.810 --> 00:07:59.770
<v Speaker 0>you may not know that Rust is, highly

00:07:59.770 --> 00:08:03.690
<v Speaker 0>praised for security and memory safety. But, you

00:08:03.690 --> 00:08:06.010
<v Speaker 0>know, this kind of proves that, even supply

00:08:06.010 --> 00:08:08.650
<v Speaker 0>chain attacks can still happen and cause, you

00:08:08.650 --> 00:08:11.470
<v Speaker 0>know, someone just includes that that cargo package,

00:08:12.455 --> 00:08:14.615
<v Speaker 0>and it starts doing its work silently in

00:08:14.615 --> 00:08:17.895
<v Speaker 0>the background. So in it so the crates

00:08:17.895 --> 00:08:20.935
<v Speaker 0>include working login code for cover and embedded

00:08:20.935 --> 00:08:23.414
<v Speaker 0>routines that scan source files for Solana and

00:08:23.414 --> 00:08:27.020
<v Speaker 0>Ethereum private keys, then exfiltrate matches via h

00:08:27.020 --> 00:08:29.340
<v Speaker 0>g p HTTP post to a hard coded

00:08:29.340 --> 00:08:36.080
<v Speaker 0>command and control c two endpoint. Following responsible

00:08:36.140 --> 00:08:38.555
<v Speaker 0>disclosure, the maintainers of crate IO have taken

00:08:38.555 --> 00:08:40.635
<v Speaker 0>steps to remove Rust packages and disable the

00:08:40.635 --> 00:08:42.795
<v Speaker 0>two accounts. It has also preserved logs of

00:08:42.795 --> 00:08:46.735
<v Speaker 0>a threat actor operator. The threat actor operate

00:08:46.954 --> 00:08:50.555
<v Speaker 0>act the threat actor operated users along with

00:08:50.555 --> 00:08:55.490
<v Speaker 0>the malicious crates for further analysis. Oh, malicious

00:08:55.490 --> 00:08:58.290
<v Speaker 0>code was executed at runtime when running or

00:08:58.290 --> 00:09:02.870
<v Speaker 0>testing a project depending on them. So apparently,

00:09:02.930 --> 00:09:05.250
<v Speaker 0>they didn't do anything malicious at build time.

00:09:05.250 --> 00:09:07.170
<v Speaker 0>So people could have downloaded it and never

00:09:07.170 --> 00:09:09.365
<v Speaker 0>ran it, you know, for a project that

00:09:09.365 --> 00:09:11.605
<v Speaker 0>they were working on. So a lot of

00:09:11.605 --> 00:09:13.445
<v Speaker 0>these may may have been short short lived

00:09:13.445 --> 00:09:17.845
<v Speaker 0>downloads. But, it's kinda funny they say. It's

00:09:17.845 --> 00:09:22.210
<v Speaker 0>called a typosquatting attack. Involve the threat actor

00:09:22.210 --> 00:09:24.770
<v Speaker 0>retaining the logging functionality of the actual library

00:09:24.770 --> 00:09:28.290
<v Speaker 0>while introducing malicious code changes during a log

00:09:28.290 --> 00:09:31.250
<v Speaker 0>packing operation that recursively search Rust files in

00:09:31.250 --> 00:09:36.305
<v Speaker 0>a directory for Ethereum Solana private keys. It's

00:09:38.365 --> 00:09:40.365
<v Speaker 0>very crazy how clever people can get with

00:09:40.365 --> 00:09:44.285
<v Speaker 0>some of these, you know, like, misdirection almost.

00:09:44.285 --> 00:09:45.645
<v Speaker 0>And there's a picture here that says, you

00:09:45.645 --> 00:09:48.225
<v Speaker 0>know, the the real one's called Fast Log.

00:09:48.710 --> 00:09:51.990
<v Speaker 0>The fake one's called Fast Log. And then

00:09:51.990 --> 00:09:54.630
<v Speaker 0>there's another one that's malicious called Async Print

00:09:54.630 --> 00:09:57.830
<v Speaker 0>l n, which I don't know how you

00:09:57.830 --> 00:09:59.510
<v Speaker 0>got that from Fast Log. Oh, I guess

00:09:59.510 --> 00:10:01.270
<v Speaker 0>it comes up when you type in Fast

00:10:01.270 --> 00:10:05.375
<v Speaker 0>Log as the third result. That's rough. Oh,

00:10:05.375 --> 00:10:07.214
<v Speaker 0>it's I guess it's because fast logs are

00:10:07.214 --> 00:10:10.995
<v Speaker 0>rust async log, high performance asynchronous logging. Okay.

00:10:11.454 --> 00:10:16.014
<v Speaker 0>Well, that makes sense. So as of, today

00:10:16.899 --> 00:10:19.220
<v Speaker 0>at least as of this article being written,

00:10:19.380 --> 00:10:21.540
<v Speaker 0>both the Git of accounts linked to the

00:10:21.540 --> 00:10:24.740
<v Speaker 0>Rust traits are no longer available. Wojcenco told

00:10:24.740 --> 00:10:26.740
<v Speaker 0>the Hacker News that the malicious code does

00:10:26.740 --> 00:10:28.740
<v Speaker 0>not get triggered during compilation or when the

00:10:28.740 --> 00:10:30.580
<v Speaker 0>crates are downloaded. So, yeah, it's so at

00:10:30.580 --> 00:10:32.725
<v Speaker 0>only at run time. It It only kicks

00:10:32.725 --> 00:10:34.165
<v Speaker 0>in when the program executes and hits the

00:10:34.165 --> 00:10:39.045
<v Speaker 0>relevant code paths. Yeah. I mean, there's still

00:10:39.045 --> 00:10:41.285
<v Speaker 0>some people who probably ran that and probably

00:10:41.285 --> 00:10:48.230
<v Speaker 0>ended up leaking their, their keys. So, you

00:10:48.230 --> 00:10:50.150
<v Speaker 0>know, I I wish them the best. That's

00:10:50.150 --> 00:10:53.830
<v Speaker 0>all I can say. That's that's stuff. A

00:10:53.830 --> 00:10:55.590
<v Speaker 0>little bit more on Rust and kinda maybe

00:10:55.590 --> 00:11:00.725
<v Speaker 0>leaning into this dependency on open source, the,

00:11:00.725 --> 00:11:05.524
<v Speaker 0>you know, the cargo, system. Rust has, the

00:11:05.524 --> 00:11:08.404
<v Speaker 0>Rust Foundation signs joint statement on open source

00:11:08.404 --> 00:11:13.050
<v Speaker 0>infrastructure stewardship. So today, the Rust Foundation joined

00:11:13.050 --> 00:11:15.770
<v Speaker 0>other open source infrastructure stewards in publishing a

00:11:15.770 --> 00:11:19.370
<v Speaker 0>joint statement on sustainable stewardship. In this play

00:11:19.450 --> 00:11:21.450
<v Speaker 0>in this post works, we'd like to explain

00:11:21.450 --> 00:11:23.290
<v Speaker 0>why we chose to sign this statement, why

00:11:23.290 --> 00:11:24.810
<v Speaker 0>it matters for Rust, and how we can

00:11:24.810 --> 00:11:27.975
<v Speaker 0>move forward as a community. It's kinda related

00:11:27.975 --> 00:11:34.075
<v Speaker 0>to that previous one. You know, this this

00:11:34.615 --> 00:11:39.275
<v Speaker 0>this document is, to me, reads as Rust's

00:11:39.335 --> 00:11:42.720
<v Speaker 0>pledge to kinda, like, treat open sources, you

00:11:42.720 --> 00:11:44.800
<v Speaker 0>know, something that's as important as, you know,

00:11:44.800 --> 00:11:46.720
<v Speaker 0>the roads and water and electricity. A lot

00:11:46.720 --> 00:11:50.080
<v Speaker 0>of, systems depend on open source software that

00:11:50.080 --> 00:11:52.980
<v Speaker 0>are under licenses that allow them for commercial

00:11:53.040 --> 00:11:56.735
<v Speaker 0>use, and and they're maintained by, you know,

00:11:56.735 --> 00:12:03.055
<v Speaker 0>small teams or individuals, you know. You know,

00:12:03.055 --> 00:12:04.975
<v Speaker 0>it's it's a lot of packages too. It's

00:12:04.975 --> 00:12:08.580
<v Speaker 0>like curl, if anyone's used curl before, SQLite,

00:12:09.440 --> 00:12:16.560
<v Speaker 0>Zlib, LibreOffice is also, open source. So it

00:12:16.560 --> 00:12:20.000
<v Speaker 0>is important to treat those, software as critical

00:12:20.000 --> 00:12:24.555
<v Speaker 0>infrastructure because I I I I use curl

00:12:24.555 --> 00:12:26.635
<v Speaker 0>in a a lot of my projects just,

00:12:26.635 --> 00:12:31.275
<v Speaker 0>you know, doing API calls. So, yeah, that

00:12:31.355 --> 00:12:32.795
<v Speaker 0>you know, I would I would want to

00:12:32.795 --> 00:12:34.955
<v Speaker 0>make sure that the the maintainer of curl

00:12:34.955 --> 00:12:38.639
<v Speaker 0>kept maintaining it, which, I think his name's

00:12:38.639 --> 00:12:41.040
<v Speaker 0>Daniel Steinberg. I think he I follow him

00:12:41.040 --> 00:12:44.720
<v Speaker 0>on Mastodon. He is very active about, Kroll

00:12:44.720 --> 00:12:48.259
<v Speaker 0>and keeping AI out of the the package

00:12:48.639 --> 00:12:51.435
<v Speaker 0>and or the, the library. So it's it's

00:12:51.435 --> 00:12:53.035
<v Speaker 0>pretty cool. He he he's done a lot

00:12:53.035 --> 00:12:56.475
<v Speaker 0>of, hard work maintaining that system. So I'll

00:12:56.475 --> 00:12:58.075
<v Speaker 0>I'll check him out if you guys have,

00:12:58.635 --> 00:13:03.870
<v Speaker 0>time on Mastodon. He's like Daniel Steinberg. I

00:13:03.950 --> 00:13:05.710
<v Speaker 0>have to double check that. Yeah. Because I

00:13:05.710 --> 00:13:07.070
<v Speaker 0>I I would feel horrible if that's his

00:13:07.070 --> 00:13:09.170
<v Speaker 0>name. I'll put it in the show notes.

00:13:10.029 --> 00:13:12.270
<v Speaker 0>But so back to the article. Why we're

00:13:12.270 --> 00:13:14.990
<v Speaker 0>having this conversation. Every piece of Rust software

00:13:14.990 --> 00:13:17.550
<v Speaker 0>from personal projects to large scale pro production

00:13:17.550 --> 00:13:21.125
<v Speaker 0>systems depend on common infrastructure. For Rust, that

00:13:21.125 --> 00:13:25.865
<v Speaker 0>means crates. Io for package distribution, docs. Rs

00:13:26.084 --> 00:13:29.384
<v Speaker 0>for documentation hosting, and broader e e ecosystem

00:13:29.524 --> 00:13:33.204
<v Speaker 0>of registries, CI services, and content delivery networks

00:13:33.204 --> 00:13:37.570
<v Speaker 0>that keep everything running smoothly. So, yeah, crates.

00:13:37.570 --> 00:13:41.170
<v Speaker 0>Io is all open source, I guess. So

00:13:41.170 --> 00:13:43.250
<v Speaker 0>thanks to our incredible community, crates has crates.

00:13:43.250 --> 00:13:46.370
<v Speaker 0>Io has grown exponentially, now serving billions of

00:13:46.370 --> 00:13:49.029
<v Speaker 0>downloads per month and supporting millions of developers

00:13:49.250 --> 00:13:52.265
<v Speaker 0>worldwide. This growth is a testament to Rust's

00:13:52.265 --> 00:13:55.945
<v Speaker 0>vibrant ecosystem and expanding adoption across industries. Excuse

00:13:55.945 --> 00:14:04.589
<v Speaker 0>me. Rust infrastructure, though, relies on bandwidth, compute

00:14:04.589 --> 00:14:07.970
<v Speaker 0>power, storage staff, and volunteer time. The expectations

00:14:08.029 --> 00:14:11.089
<v Speaker 0>around open source software have also evolved substantially,

00:14:11.470 --> 00:14:15.390
<v Speaker 0>with governments and enterprises demanding reliability, security, and

00:14:15.390 --> 00:14:18.850
<v Speaker 0>speed. And this is often a conversation that

00:14:20.135 --> 00:14:22.635
<v Speaker 0>a lot of developers talk about is, well,

00:14:23.735 --> 00:14:25.895
<v Speaker 0>you guys are all using these packages. We

00:14:25.895 --> 00:14:28.215
<v Speaker 0>have these big corporate companies that are using

00:14:28.215 --> 00:14:31.015
<v Speaker 0>these packages, but offer no support to these

00:14:31.015 --> 00:14:36.470
<v Speaker 0>open source, you know, libraries to continue actually

00:14:36.470 --> 00:14:39.910
<v Speaker 0>developing even though their infrastructure critically depends on

00:14:39.910 --> 00:14:41.910
<v Speaker 0>it. So, you know, kind of an interesting

00:14:41.910 --> 00:14:47.855
<v Speaker 0>thought there. The joint statement highlights that these

00:14:47.855 --> 00:14:50.415
<v Speaker 0>expectations come with real and rising costs and

00:14:50.415 --> 00:14:52.575
<v Speaker 0>that most of this is currently born by

00:14:52.575 --> 00:14:55.475
<v Speaker 0>a small group of organizations and individuals. Meanwhile,

00:14:55.535 --> 00:14:58.830
<v Speaker 0>many large scale users, including commercial enterprises that

00:14:58.830 --> 00:15:02.370
<v Speaker 0>generate enormous value from Rust, use crates. Io

00:15:02.590 --> 00:15:06.350
<v Speaker 0>without contributing back to its sustainability. With the

00:15:06.350 --> 00:15:08.910
<v Speaker 0>exponential increase in usage we are experiencing, we

00:15:08.910 --> 00:15:10.590
<v Speaker 0>need to find a more sustainable way to

00:15:10.590 --> 00:15:12.190
<v Speaker 0>run our services that is fair for the

00:15:12.190 --> 00:15:14.505
<v Speaker 0>developers who are contributing to the e Rust

00:15:14.505 --> 00:15:17.545
<v Speaker 0>ecosystem and the enterprise companies that are building

00:15:17.545 --> 00:15:19.385
<v Speaker 0>the tools and systems so many of us

00:15:19.385 --> 00:15:24.985
<v Speaker 0>rely on today. So we've got another session

00:15:24.985 --> 00:15:27.950
<v Speaker 0>called the path forward. The Rust Foundation exists

00:15:27.950 --> 00:15:30.350
<v Speaker 0>to ensure the long term sustainability of the

00:15:30.350 --> 00:15:33.230
<v Speaker 0>Rust programming language and ecosystem. We feel that

00:15:33.230 --> 00:15:35.630
<v Speaker 0>it's right that we take a proactive approach

00:15:35.630 --> 00:15:40.574
<v Speaker 0>to this topic. So, yeah, they they're going

00:15:40.574 --> 00:15:43.334
<v Speaker 0>public saying that they're gonna be working to

00:15:43.334 --> 00:15:49.574
<v Speaker 0>support open source projects, you know? And, yeah,

00:15:49.574 --> 00:15:53.670
<v Speaker 0>they're inviting everyone to benefit from Rust, whether

00:15:53.670 --> 00:15:56.310
<v Speaker 0>as a hobbyist, researcher, or small business, or

00:15:56.310 --> 00:15:58.310
<v Speaker 0>global enterprise to be part of this effort

00:15:58.310 --> 00:16:00.630
<v Speaker 0>as well. You know, over the coming six

00:16:00.630 --> 00:16:03.430
<v Speaker 0>to twelve months, we'll be hosting community forums

00:16:03.430 --> 00:16:07.495
<v Speaker 0>and discussions, consulting with project maintainers and ecosystem

00:16:07.635 --> 00:16:10.515
<v Speaker 0>leaders, working closely with other package registries to

00:16:10.515 --> 00:16:13.235
<v Speaker 0>learn from different approaches, and researching solutions that

00:16:13.235 --> 00:16:17.395
<v Speaker 0>maintain Rust's open and accessible nature. These steps

00:16:17.395 --> 00:16:19.555
<v Speaker 0>will inform our approach to ensure long term

00:16:19.555 --> 00:16:23.209
<v Speaker 0>sustainability. You know, I am you guys will

00:16:23.209 --> 00:16:26.250
<v Speaker 0>learn as you listen to the show, with

00:16:26.250 --> 00:16:28.110
<v Speaker 0>Chris and I doing some of the podcast

00:16:28.170 --> 00:16:32.190
<v Speaker 0>that I am a huge fan of Rust.

00:16:32.410 --> 00:16:36.425
<v Speaker 0>I think it's awesome. I'm hardly at all

00:16:36.425 --> 00:16:38.025
<v Speaker 0>experienced with it. I've played with it a

00:16:38.025 --> 00:16:39.785
<v Speaker 0>little bit as from time to time, but

00:16:39.785 --> 00:16:43.465
<v Speaker 0>it it is fun to work with. The

00:16:43.465 --> 00:16:46.630
<v Speaker 0>bar checker system is cool. It's fresh. So

00:16:46.630 --> 00:16:48.149
<v Speaker 0>if you're a developer and you've never touched

00:16:48.149 --> 00:16:49.670
<v Speaker 0>Rust, it's a fun it's a fun route

00:16:49.670 --> 00:16:51.270
<v Speaker 0>to to to go down and and try

00:16:51.270 --> 00:16:52.630
<v Speaker 0>out if you if you like to try

00:16:52.630 --> 00:16:57.510
<v Speaker 0>some system stuff. You know? And so in

00:16:57.830 --> 00:16:59.110
<v Speaker 0>on the other hand, if you if you're

00:16:59.110 --> 00:17:00.970
<v Speaker 0>in a position where you're at a company,

00:17:02.035 --> 00:17:04.395
<v Speaker 0>where that makes big decisions for, like, IT

00:17:04.395 --> 00:17:07.055
<v Speaker 0>budgets and you rely on open source tools,

00:17:07.195 --> 00:17:12.475
<v Speaker 0>like Libra Office or PostgreSQL, Rust, you you

00:17:12.475 --> 00:17:14.795
<v Speaker 0>should definitely consider setting aside some funding or

00:17:14.795 --> 00:17:18.240
<v Speaker 0>sponsorships for those projects. It's equivalent in importance

00:17:18.240 --> 00:17:20.240
<v Speaker 0>to paying for a bit of insurance. You

00:17:20.240 --> 00:17:22.800
<v Speaker 0>know, your support gives you communication line, helps

00:17:22.800 --> 00:17:26.020
<v Speaker 0>prevent future security breaches and supply chain messes

00:17:26.080 --> 00:17:28.240
<v Speaker 0>like this just this previous one just now,

00:17:28.240 --> 00:17:31.705
<v Speaker 0>the Fast Log, by moving these projects into

00:17:31.705 --> 00:17:33.865
<v Speaker 0>a position where they can consider be bringing

00:17:33.865 --> 00:17:36.365
<v Speaker 0>more team members onto work in these critical

00:17:36.424 --> 00:17:38.424
<v Speaker 0>areas that, like, they require a lot of

00:17:38.424 --> 00:17:40.424
<v Speaker 0>time and attention. You know? It's it's not

00:17:40.424 --> 00:17:43.465
<v Speaker 0>easy to to develop critical infrastructure that is

00:17:43.465 --> 00:17:46.890
<v Speaker 0>reliable and works very fast all the time.

00:17:46.890 --> 00:17:50.250
<v Speaker 0>You know, if you ask these, open source

00:17:50.250 --> 00:17:52.809
<v Speaker 0>maintainers to to put in extra time and

00:17:52.809 --> 00:17:55.450
<v Speaker 0>effort for, you know, no funding, stuff to

00:17:55.450 --> 00:17:57.945
<v Speaker 0>work their day job. You know? Some are

00:17:57.945 --> 00:17:59.625
<v Speaker 0>lucky enough to be able to actually be

00:17:59.625 --> 00:18:01.785
<v Speaker 0>supported by the package, you know, public support,

00:18:01.785 --> 00:18:07.565
<v Speaker 0>but, you know, that's not everyone. So, yeah,

00:18:07.945 --> 00:18:13.200
<v Speaker 0>just just a cool initiative by the Rust

00:18:13.200 --> 00:18:17.120
<v Speaker 0>Foundation. I I really, really, send my kudos

00:18:17.120 --> 00:18:21.360
<v Speaker 0>out to them. Amazing, amazing, statement. And I

00:18:21.360 --> 00:18:22.720
<v Speaker 0>hope to see more of this from the

00:18:22.720 --> 00:18:30.575
<v Speaker 0>community, and from corporations worldwide. You know? Here's

00:18:30.575 --> 00:18:33.455
<v Speaker 0>a fun, little open source tool while we're

00:18:33.455 --> 00:18:36.415
<v Speaker 0>talking about it. If you, are a was

00:18:36.415 --> 00:18:41.130
<v Speaker 0>that DocuSign user? Well, there's a, package called

00:18:41.130 --> 00:18:43.503
<v Speaker 0>DocuSeal on GitHub that allows you to self

00:18:43.503 --> 00:18:47.610
<v Speaker 0>host, your own version of DocuSign. Don't let

00:18:47.610 --> 00:18:50.730
<v Speaker 0>the your contracts and your company files get

00:18:50.730 --> 00:18:58.275
<v Speaker 0>into the, other people's hands. You do not

00:18:58.275 --> 00:19:00.995
<v Speaker 0>wanna save your important documents on someone else's

00:19:00.995 --> 00:19:02.915
<v Speaker 0>server. You've seen time and time again all

00:19:02.915 --> 00:19:05.650
<v Speaker 0>these data breaches. Keep it local. You know,

00:19:05.650 --> 00:19:07.570
<v Speaker 0>it's it's not like you're gonna need a

00:19:07.570 --> 00:19:09.090
<v Speaker 0>whole server to do that. You could just

00:19:09.090 --> 00:19:11.250
<v Speaker 0>probably host it on a little machine. So,

00:19:11.250 --> 00:19:13.890
<v Speaker 0>you know, talk to your IT team about

00:19:13.890 --> 00:19:21.465
<v Speaker 0>switching over to DocuSeal instead of DocuSign. I

00:19:21.465 --> 00:19:23.945
<v Speaker 0>tried out well, I attempted to try out

00:19:23.945 --> 00:19:26.345
<v Speaker 0>a new email client on Linux. If any

00:19:26.345 --> 00:19:29.225
<v Speaker 0>of you are running Linux and are trying

00:19:29.225 --> 00:19:32.025
<v Speaker 0>not to use Thunderbird anymore, there's a cool

00:19:32.025 --> 00:19:33.865
<v Speaker 0>new or I maybe not new, but a

00:19:33.865 --> 00:19:36.240
<v Speaker 0>cool app called MailSpring. It's got a lot

00:19:36.240 --> 00:19:40.180
<v Speaker 0>of sweet features. I got this article from

00:19:43.360 --> 00:19:46.500
<v Speaker 0>I don't wanna butcher his name. Jivakar Gosh.

00:19:49.495 --> 00:19:53.054
<v Speaker 0>So he loves this client, and, I think

00:19:53.054 --> 00:19:54.534
<v Speaker 0>it was pretty cool too. So let me

00:19:54.534 --> 00:19:57.335
<v Speaker 0>share with you, what his experience was, and

00:19:57.335 --> 00:19:59.274
<v Speaker 0>then I'll share it with you my experience,

00:20:01.015 --> 00:20:05.590
<v Speaker 0>just launching the app. But think email clients

00:20:05.590 --> 00:20:08.070
<v Speaker 0>can't find a balance between aesthetic aesthetics and

00:20:08.070 --> 00:20:11.270
<v Speaker 0>functionality? Want a professional looking email client with

00:20:11.270 --> 00:20:14.549
<v Speaker 0>professional features? Well, MailSpring is my go to

00:20:14.549 --> 00:20:18.150
<v Speaker 0>free and open source email client that combines

00:20:18.150 --> 00:20:21.485
<v Speaker 0>sleek design with powerful features. So another open

00:20:21.485 --> 00:20:25.924
<v Speaker 0>source tool here. We love open source. When

00:20:25.924 --> 00:20:28.044
<v Speaker 0>I say Mailspring is my favorite email app

00:20:28.044 --> 00:20:30.765
<v Speaker 0>and not Thunderbird, I'm not claiming Mailspring is

00:20:30.765 --> 00:20:33.265
<v Speaker 0>better than Thunderbird because better would mean Mailspring

00:20:33.404 --> 00:20:35.725
<v Speaker 0>can do everything Thunderbird can and then some

00:20:35.725 --> 00:20:38.040
<v Speaker 0>more. That's not the case. And Thunderbird is

00:20:38.040 --> 00:20:40.680
<v Speaker 0>more feature rich is the is the more

00:20:40.680 --> 00:20:45.480
<v Speaker 0>feature rich alternative. However, Mailspring can do a

00:20:45.480 --> 00:20:48.120
<v Speaker 0>few things that Thunderbird can't. It brings a

00:20:48.120 --> 00:20:50.040
<v Speaker 0>different set of features and priorities to the

00:20:50.040 --> 00:20:51.935
<v Speaker 0>table and I personally just align better with

00:20:51.935 --> 00:20:54.095
<v Speaker 0>what it has to offer, which essentially boils

00:20:54.095 --> 00:20:56.335
<v Speaker 0>down to the five following features. And before

00:20:56.335 --> 00:20:58.015
<v Speaker 0>I talk about the features, I feel like

00:20:58.015 --> 00:20:59.695
<v Speaker 0>I really resonate with this kind of this

00:20:59.695 --> 00:21:02.335
<v Speaker 0>idea. There are some, you know, like, especially

00:21:02.335 --> 00:21:04.410
<v Speaker 0>with, like, note taking apps. You know, we

00:21:04.410 --> 00:21:10.410
<v Speaker 0>have Evernote, Obsidian, Notion. I personally use an

00:21:10.410 --> 00:21:14.010
<v Speaker 0>app called Logsec. There's so many different options,

00:21:14.010 --> 00:21:15.530
<v Speaker 0>and and what it comes down to is

00:21:15.530 --> 00:21:16.890
<v Speaker 0>what it works for you. What what do

00:21:16.890 --> 00:21:18.590
<v Speaker 0>you what do you think looks the nicest

00:21:18.650 --> 00:21:20.835
<v Speaker 0>or what makes it you what what what

00:21:20.915 --> 00:21:22.835
<v Speaker 0>how do you find it easy to navigate?

00:21:22.835 --> 00:21:25.715
<v Speaker 0>I like Logitech. I don't know why I

00:21:25.715 --> 00:21:27.635
<v Speaker 0>like Logitech. I just I just it provides

00:21:27.635 --> 00:21:30.115
<v Speaker 0>a daily journal. I write, kinda keeps track

00:21:30.115 --> 00:21:31.555
<v Speaker 0>of, like, what I've been going on through

00:21:31.555 --> 00:21:35.769
<v Speaker 0>the last few months. Or, and then my

00:21:35.769 --> 00:21:38.330
<v Speaker 0>notes are kinda organized in that time scheme

00:21:38.330 --> 00:21:41.929
<v Speaker 0>as well. But I also kinda like the

00:21:41.929 --> 00:21:43.929
<v Speaker 0>linking feature where you you you can link

00:21:43.929 --> 00:21:46.010
<v Speaker 0>a document, and then within that document, it's,

00:21:46.010 --> 00:21:48.409
<v Speaker 0>like, links to several other documents. It it's

00:21:48.409 --> 00:21:50.294
<v Speaker 0>it's a beautiful thing. And then it it

00:21:50.294 --> 00:21:52.135
<v Speaker 0>all comes with graph views. So, you know,

00:21:52.135 --> 00:21:53.654
<v Speaker 0>you get to see how your all your

00:21:53.654 --> 00:21:55.575
<v Speaker 0>information kinda ties together as well as long

00:21:55.575 --> 00:21:58.554
<v Speaker 0>as you're linking correctly. But back to Mailspring.

00:22:00.135 --> 00:22:03.575
<v Speaker 0>So, modern design with theming support. Mailspring is

00:22:03.575 --> 00:22:05.420
<v Speaker 0>hands down one of the most sleek looking

00:22:05.420 --> 00:22:07.820
<v Speaker 0>FOSS email clients out there for an open

00:22:07.820 --> 00:22:13.180
<v Speaker 0>source. Offering a clean, polished design that looks

00:22:13.180 --> 00:22:18.325
<v Speaker 0>modern. Everything from the padding and the margins

00:22:18.405 --> 00:22:19.845
<v Speaker 0>sorry. I'm just like I don't know why

00:22:19.845 --> 00:22:21.525
<v Speaker 0>I'm blanking on this. Every everything from the

00:22:21.525 --> 00:22:23.365
<v Speaker 0>paddings and the margins to the font styles

00:22:23.365 --> 00:22:26.565
<v Speaker 0>look thoughtfully crafted. It lays out a lot

00:22:26.565 --> 00:22:28.965
<v Speaker 0>of information, but it does that with a

00:22:28.965 --> 00:22:31.125
<v Speaker 0>level of minimalism that I just can't help

00:22:31.125 --> 00:22:33.389
<v Speaker 0>but love. So I I guess he it

00:22:33.470 --> 00:22:36.429
<v Speaker 0>and it does have a very sleek, easy

00:22:36.429 --> 00:22:38.590
<v Speaker 0>to approach look. It the the screen's not

00:22:38.590 --> 00:22:42.750
<v Speaker 0>too cluttered. You know, the mailboxes are nice

00:22:42.750 --> 00:22:45.495
<v Speaker 0>and neat. The font looks pretty sweet, but

00:22:45.495 --> 00:22:47.095
<v Speaker 0>that might just be his personal font. But,

00:22:47.095 --> 00:22:49.254
<v Speaker 0>you know, if you run a custom font

00:22:49.254 --> 00:22:51.674
<v Speaker 0>on your machine, that probably would just automatically

00:22:51.815 --> 00:22:57.629
<v Speaker 0>apply. So he talks a lot about the

00:22:57.629 --> 00:23:01.230
<v Speaker 0>theme customization, link tracking, and pixel tracking is

00:23:01.230 --> 00:23:04.029
<v Speaker 0>a thing apparently. These are the main features

00:23:04.029 --> 00:23:06.669
<v Speaker 0>that set MailSpring apart from other desktop email

00:23:06.669 --> 00:23:09.570
<v Speaker 0>clients. Usually, these functionalities are reserved for professional

00:23:09.710 --> 00:23:11.924
<v Speaker 0>email marketing software. The fact that we're getting

00:23:11.924 --> 00:23:13.445
<v Speaker 0>them in a consumer level tool is just

00:23:13.445 --> 00:23:15.605
<v Speaker 0>brilliant. When writing an email, you can simply

00:23:15.605 --> 00:23:17.524
<v Speaker 0>press a button to enable link tracking or

00:23:17.524 --> 00:23:20.105
<v Speaker 0>pixel tracking or both for that specific email.

00:23:20.404 --> 00:23:22.164
<v Speaker 0>Link tracking does exactly what it sounds like.

00:23:22.164 --> 00:23:23.605
<v Speaker 0>If you include a link in your email

00:23:23.605 --> 00:23:25.350
<v Speaker 0>and a recipient clicks it, you'll get a

00:23:25.429 --> 00:23:27.590
<v Speaker 0>notification. Oh, this is it. That's what that's

00:23:27.590 --> 00:23:31.289
<v Speaker 0>kinda crazy. Meanwhile, pixel tracking is essentially stealthy

00:23:31.590 --> 00:23:34.150
<v Speaker 0>read receipts. You'll get a notification when someone

00:23:34.150 --> 00:23:39.665
<v Speaker 0>opens your email. Wow. You know? And this

00:23:39.665 --> 00:23:41.825
<v Speaker 0>is just built into some of the tools

00:23:41.825 --> 00:23:44.225
<v Speaker 0>we use every day, you know, just made

00:23:44.225 --> 00:23:49.585
<v Speaker 0>by these large companies. And obviously, not for

00:23:49.585 --> 00:23:51.745
<v Speaker 0>us to see. They're the ones tracking, you

00:23:51.745 --> 00:23:53.650
<v Speaker 0>know, how long it takes us to open

00:23:53.650 --> 00:23:57.970
<v Speaker 0>emails, you know, especially Google. I mean, I'm

00:23:57.970 --> 00:23:59.650
<v Speaker 0>sure you've heard my dad talk about de

00:23:59.650 --> 00:24:03.010
<v Speaker 0>googling your life, but, yeah, they they track

00:24:03.010 --> 00:24:04.785
<v Speaker 0>track everything here. You do. I was just

00:24:04.945 --> 00:24:06.465
<v Speaker 0>listening to the show. He was talking about

00:24:06.465 --> 00:24:09.765
<v Speaker 0>the DS ID or something DS ID cache,

00:24:10.465 --> 00:24:15.845
<v Speaker 0>which automatically applies to follow your content, ad.

00:24:16.785 --> 00:24:19.105
<v Speaker 0>It's almost like your your content ad rights

00:24:19.105 --> 00:24:23.720
<v Speaker 0>or something, which I'm just like, just another

00:24:23.720 --> 00:24:29.240
<v Speaker 0>layer of tracking. Right? But sending an email

00:24:29.240 --> 00:24:31.400
<v Speaker 0>for job interviews, knowing when they saw your

00:24:31.400 --> 00:24:33.960
<v Speaker 0>message can give you actionable information about when

00:24:33.960 --> 00:24:36.105
<v Speaker 0>to send a follow-up. Okay. That's a clever

00:24:36.105 --> 00:24:39.225
<v Speaker 0>thing. Same same applies to sending support emails.

00:24:39.225 --> 00:24:41.385
<v Speaker 0>You can gauge whether your message was received

00:24:41.385 --> 00:24:43.305
<v Speaker 0>and act accordingly. So, yeah, I could kinda

00:24:43.305 --> 00:24:44.825
<v Speaker 0>see that. Like, if you're trying to set

00:24:44.825 --> 00:24:48.840
<v Speaker 0>something up, I mean, I don't know. This

00:24:48.840 --> 00:24:51.400
<v Speaker 0>this I I feel like that's still kinda

00:24:51.400 --> 00:24:53.880
<v Speaker 0>niche to kind of a business application or

00:24:53.880 --> 00:24:55.640
<v Speaker 0>something. You didn't wanna pay for, one of

00:24:55.640 --> 00:24:58.520
<v Speaker 0>those business accounts or whatever. That's cool. I

00:24:58.520 --> 00:25:04.695
<v Speaker 0>think that's pretty sweet. Next up, you get

00:25:04.695 --> 00:25:08.774
<v Speaker 0>the email analytics. Wow. Okay. So this is

00:25:08.774 --> 00:25:11.735
<v Speaker 0>definitely like some open source business email type

00:25:11.735 --> 00:25:15.669
<v Speaker 0>of thing. This is awesome. Mailspring provides a

00:25:15.669 --> 00:25:18.149
<v Speaker 0>comprehensive analytics dashboard that gives you insight into

00:25:18.149 --> 00:25:19.909
<v Speaker 0>your email performance. You can not only see

00:25:19.909 --> 00:25:21.830
<v Speaker 0>how many emails you receive, but want deep

00:25:21.909 --> 00:25:24.390
<v Speaker 0>detailed metrics about your sent emails. How many

00:25:24.390 --> 00:25:25.750
<v Speaker 0>you sent, how many of them were open,

00:25:25.750 --> 00:25:28.245
<v Speaker 0>and how many got replies. If you're sending

00:25:28.245 --> 00:25:30.885
<v Speaker 0>a significant volume of emails, the analytics can

00:25:30.885 --> 00:25:33.385
<v Speaker 0>even show you which subject lines and templates

00:25:34.165 --> 00:25:38.805
<v Speaker 0>perform better. Wow. Giving you giving you data

00:25:38.805 --> 00:25:41.785
<v Speaker 0>driven insights into what gets read more often.

00:25:42.260 --> 00:25:44.660
<v Speaker 0>While these features are technically geared towards marketing

00:25:44.660 --> 00:25:46.340
<v Speaker 0>use cases, yes. It's like a little more

00:25:46.340 --> 00:25:49.780
<v Speaker 0>business, they're valuable for non marketers too. Okay?

00:25:49.780 --> 00:25:52.340
<v Speaker 0>So tell me how. If you're job hunting,

00:25:52.340 --> 00:25:54.500
<v Speaker 0>you get data on how many of your

00:25:54.500 --> 00:25:56.804
<v Speaker 0>emails are being opened and replied to, helping

00:25:56.804 --> 00:25:58.965
<v Speaker 0>you understand if the problem is your subject

00:25:58.965 --> 00:26:04.565
<v Speaker 0>lines or the message count content. I don't

00:26:04.565 --> 00:26:10.325
<v Speaker 0>know. Tell us what you think. Other than

00:26:10.325 --> 00:26:16.220
<v Speaker 0>that, snooze emails, set reminders, send later, in

00:26:16.220 --> 00:26:20.700
<v Speaker 0>app email translations. Oh, that's kinda cool. Do

00:26:20.700 --> 00:26:22.220
<v Speaker 0>the I mean, I feel like if you

00:26:22.220 --> 00:26:27.914
<v Speaker 0>just use, you know, your email app in

00:26:27.914 --> 00:26:30.495
<v Speaker 0>the browser, you're gonna get the auto translation

00:26:30.554 --> 00:26:32.475
<v Speaker 0>anyway. So this is if you're using a

00:26:32.475 --> 00:26:35.195
<v Speaker 0>dedicated email app too. So that's that's another

00:26:35.195 --> 00:26:41.100
<v Speaker 0>thing. Obviously, this is a GitHub package. So

00:26:41.100 --> 00:26:43.980
<v Speaker 0>I'm not sure how you go about, installing

00:26:43.980 --> 00:26:47.980
<v Speaker 0>that on something like a Windows, but, on

00:26:47.980 --> 00:26:50.560
<v Speaker 0>Linux, you can get the snap flat pack.

00:26:51.435 --> 00:26:52.955
<v Speaker 0>I'm sure there's a way to just directly,

00:26:53.355 --> 00:26:54.955
<v Speaker 0>compile it from the the GitHub. You know,

00:26:54.955 --> 00:26:56.555
<v Speaker 0>that's probably what you do on Windows. So

00:26:56.555 --> 00:26:58.735
<v Speaker 0>you probably directly compile it from the GitHub.

00:26:59.275 --> 00:27:03.275
<v Speaker 0>Download that, zip. Compile it right there. They

00:27:03.275 --> 00:27:04.955
<v Speaker 0>might even have just a EXE on their

00:27:04.955 --> 00:27:06.155
<v Speaker 0>site. So I would I would check them

00:27:06.155 --> 00:27:14.230
<v Speaker 0>out. Mailspring. Up next. Let's see. I found

00:27:14.230 --> 00:27:16.570
<v Speaker 0>three point one, three point five patch release

00:27:16.789 --> 00:27:19.894
<v Speaker 0>patch release packed with fixes instability boost. I

00:27:19.894 --> 00:27:21.654
<v Speaker 0>hope you guys don't mind a little bit

00:27:21.654 --> 00:27:24.695
<v Speaker 0>more of the, the dev lane leaning articles.

00:27:24.695 --> 00:27:26.634
<v Speaker 0>That's kinda what I get in my feeds.

00:27:28.615 --> 00:27:31.095
<v Speaker 0>And we already talked about some Linux stuff.

00:27:31.095 --> 00:27:32.455
<v Speaker 0>I already I know we talked about some

00:27:32.455 --> 00:27:34.610
<v Speaker 0>Rust stuff. But here we have some Python

00:27:34.610 --> 00:27:36.710
<v Speaker 0>stuff. And if you are working in data,

00:27:36.850 --> 00:27:38.450
<v Speaker 0>these are gonna be some great fixes for

00:27:38.450 --> 00:27:45.169
<v Speaker 0>you. So, several significant enhancements over three point

00:27:45.169 --> 00:27:48.025
<v Speaker 0>one two, apparently. So it it revamped interactive

00:27:48.085 --> 00:27:51.125
<v Speaker 0>shell, experimental support for running without a global

00:27:51.125 --> 00:27:53.445
<v Speaker 0>interpreter lock. So I was reading about this.

00:27:53.845 --> 00:27:58.265
<v Speaker 0>It was something about, being able to use

00:27:58.325 --> 00:28:00.965
<v Speaker 0>threads or something. So I would be more

00:28:00.965 --> 00:28:02.460
<v Speaker 0>interested in reading a a little bit more

00:28:02.460 --> 00:28:08.140
<v Speaker 0>about that, what that means. So that was

00:28:08.140 --> 00:28:10.460
<v Speaker 0>three point one three. So release this is

00:28:10.460 --> 00:28:12.960
<v Speaker 0>the release context. Sorry. I am skipping ahead.

00:28:13.020 --> 00:28:15.100
<v Speaker 0>I'm getting ahead of myself. Let's just start

00:28:15.100 --> 00:28:17.725
<v Speaker 0>that section over. What led to three point

00:28:17.725 --> 00:28:21.245
<v Speaker 0>one three point five release context? Python three

00:28:21.245 --> 00:28:23.645
<v Speaker 0>point one three released on October seventh twenty

00:28:23.645 --> 00:28:28.125
<v Speaker 0>twenty four introduced several oh, excuse me. Several

00:28:28.125 --> 00:28:30.925
<v Speaker 0>significant enhancements over three point one two, including

00:28:30.925 --> 00:28:34.850
<v Speaker 0>revamped interactive shell, experimental experimental support running without

00:28:34.850 --> 00:28:39.650
<v Speaker 0>a global interpreter lock and global interpreter lock

00:28:39.650 --> 00:28:44.290
<v Speaker 0>and preliminary JIT infrastructure. However, three point one

00:28:44.290 --> 00:28:47.535
<v Speaker 0>three point four, the main tainers discovered several

00:28:47.535 --> 00:28:50.495
<v Speaker 0>serious regressions. Plus three point one, three point

00:28:50.495 --> 00:28:53.775
<v Speaker 0>five was accelerated to correct these before the

00:28:53.775 --> 00:28:56.335
<v Speaker 0>impact of a broader use space. Okay. So,

00:28:56.335 --> 00:28:58.690
<v Speaker 0>and it's just a nice little patch. So

00:28:58.690 --> 00:29:00.690
<v Speaker 0>a little repair release is what they're calling

00:29:00.690 --> 00:29:07.410
<v Speaker 0>it. So they fixed a Windows extension build

00:29:07.410 --> 00:29:13.904
<v Speaker 0>failure. Generator expression type error delay. And random

00:29:13.904 --> 00:29:15.745
<v Speaker 0>dot get ran bits, if you're a user

00:29:15.745 --> 00:29:19.265
<v Speaker 0>of that function, is broken for int like

00:29:19.265 --> 00:29:28.460
<v Speaker 0>types. Okay. So these are still these are

00:29:28.460 --> 00:29:30.540
<v Speaker 0>the one what really drove the update. The

00:29:30.540 --> 00:29:34.300
<v Speaker 0>Windows extension build failure, generator expression type error

00:29:34.300 --> 00:29:37.420
<v Speaker 0>delay, and random dot get random bits broken

00:29:37.420 --> 00:29:40.394
<v Speaker 0>for inline types. Sorry. I didn't get to

00:29:40.394 --> 00:29:42.654
<v Speaker 0>read this article too in-depth at a time.

00:29:43.674 --> 00:29:46.475
<v Speaker 0>So broader enhancements and underlying improvements in the

00:29:46.475 --> 00:29:48.634
<v Speaker 0>three point one three line. Because three point

00:29:48.634 --> 00:29:50.634
<v Speaker 0>one five or three point one three five

00:29:50.634 --> 00:29:54.315
<v Speaker 0>is a maintenance release, it doesn't introduce brand

00:29:54.315 --> 00:29:57.170
<v Speaker 0>new features. But it does carry forward and

00:29:57.170 --> 00:30:00.370
<v Speaker 0>solidify many of the enhancements that distinguish Python

00:30:00.370 --> 00:30:02.130
<v Speaker 0>three point one three from three point one

00:30:02.130 --> 00:30:06.290
<v Speaker 0>two. Here are the most noteworthy. So the

00:30:06.290 --> 00:30:08.690
<v Speaker 0>Repl Shell experience, Python now ships with a

00:30:08.690 --> 00:30:14.285
<v Speaker 0>more capable interactive interpreter inspired part by PyPy.

00:30:14.585 --> 00:30:17.865
<v Speaker 0>The experience includes multiline editing rather than line

00:30:17.865 --> 00:30:21.065
<v Speaker 0>by line, colorized prompts, trace backs, doc test,

00:30:21.065 --> 00:30:24.185
<v Speaker 0>output by default, handy built in commands like

00:30:24.185 --> 00:30:28.640
<v Speaker 0>help, quit, exit without needing parenthesis, a pace

00:30:28.640 --> 00:30:31.520
<v Speaker 0>mode, toggle bolts. Oh, man. I I love

00:30:31.520 --> 00:30:34.960
<v Speaker 0>this for you guys, but just set yourself

00:30:34.960 --> 00:30:37.860
<v Speaker 0>up with a a great Neo Vim config.

00:30:38.400 --> 00:30:40.240
<v Speaker 0>You can get all this set up. You

00:30:40.240 --> 00:30:42.945
<v Speaker 0>can have multiline editing. You can have all

00:30:42.945 --> 00:30:45.505
<v Speaker 0>the cool features that make your your little

00:30:45.505 --> 00:30:48.145
<v Speaker 0>VIM VIM setup look like a, you know,

00:30:48.145 --> 00:30:50.705
<v Speaker 0>like a whole ID. Don't get e max.

00:30:50.705 --> 00:30:57.670
<v Speaker 0>Ignore those people. But I don't know. I've

00:30:57.670 --> 00:31:00.170
<v Speaker 0>never had problems setting up a Python environment,

00:31:01.670 --> 00:31:07.450
<v Speaker 0>on on any machine. So I don't know.

00:31:07.510 --> 00:31:09.610
<v Speaker 0>I I definitely hear that a lot, especially,

00:31:10.595 --> 00:31:13.635
<v Speaker 0>from some of my professors. They'll they'll literally

00:31:13.635 --> 00:31:16.515
<v Speaker 0>say it's, oh, oh, Python's tricky to set

00:31:16.515 --> 00:31:22.675
<v Speaker 0>up, in the environment. So, three words, just

00:31:22.675 --> 00:31:25.870
<v Speaker 0>run Linux. Or if you just can't get

00:31:25.870 --> 00:31:29.470
<v Speaker 0>away from Windows, just run WSL. Make your

00:31:29.470 --> 00:31:37.170
<v Speaker 0>life easier. I guess easier in a sense.

00:31:39.554 --> 00:31:43.495
<v Speaker 0>Ubuntu is a great place to start. But

00:31:43.955 --> 00:31:48.195
<v Speaker 0>back to Python. Prototype JIT compiler. Wait. No.

00:31:48.195 --> 00:31:50.754
<v Speaker 0>Experimental free threaded mode. So, yeah, this is

00:31:50.754 --> 00:31:52.995
<v Speaker 0>this global interpreter lock thing I was talking

00:31:52.995 --> 00:31:55.170
<v Speaker 0>about. One of the most ambitious moves in

00:31:55.170 --> 00:31:57.570
<v Speaker 0>three point one three is introducing an optional

00:31:57.570 --> 00:32:00.790
<v Speaker 0>mode to run c Python without the global

00:32:00.850 --> 00:32:03.490
<v Speaker 0>interpreter lock. So, yes, you can so in

00:32:03.490 --> 00:32:05.970
<v Speaker 0>this mode, threads can execute in parallel more

00:32:05.970 --> 00:32:09.345
<v Speaker 0>freely. The mode is currently experimental and not

00:32:09.345 --> 00:32:13.985
<v Speaker 0>enabled by default. So if you guys know

00:32:13.985 --> 00:32:21.100
<v Speaker 0>about threads, really awesome tool. It's cool to

00:32:21.100 --> 00:32:23.100
<v Speaker 0>see that coming to Python a little bit

00:32:23.100 --> 00:32:28.539
<v Speaker 0>more, easily. I'm sure that we'll start seeing

00:32:28.539 --> 00:32:31.019
<v Speaker 0>some libraries being, I don't know. I'm sure

00:32:31.019 --> 00:32:33.260
<v Speaker 0>there are already some libraries being developed for

00:32:33.260 --> 00:32:41.115
<v Speaker 0>that, but that, that is cool. Just another

00:32:41.415 --> 00:32:44.695
<v Speaker 0>another reason to stop writing in c. No.

00:32:44.695 --> 00:32:50.240
<v Speaker 0>I'm just kidding. Prototype JIT compiler. Minimal just

00:32:50.240 --> 00:32:52.320
<v Speaker 0>in time compiler is bundled in three point

00:32:52.320 --> 00:32:54.419
<v Speaker 0>one three. It's disabled by default and considered

00:32:54.640 --> 00:32:58.080
<v Speaker 0>experimental. Its current performance gains are modest. The

00:32:58.080 --> 00:33:00.020
<v Speaker 0>goal is to lay groundwork for more aggressive

00:33:00.080 --> 00:33:02.745
<v Speaker 0>optimization in future releases. And I love that

00:33:02.745 --> 00:33:04.505
<v Speaker 0>they're just thinking ahead, trying to get this

00:33:04.505 --> 00:33:06.505
<v Speaker 0>thing fast. You know, people have complained for

00:33:06.505 --> 00:33:10.225
<v Speaker 0>a long time. Oh, Python's so slow. And

00:33:10.345 --> 00:33:12.425
<v Speaker 0>yeah. Oh, sure. Yes. I've said it before

00:33:12.425 --> 00:33:16.820
<v Speaker 0>too. I admit Python, I you know? Yes.

00:33:17.120 --> 00:33:19.440
<v Speaker 0>It is so much more work to write

00:33:19.440 --> 00:33:23.120
<v Speaker 0>something in in, ski or c plus plus.

00:33:23.120 --> 00:33:27.440
<v Speaker 0>Yes. However, you get the two of the

00:33:27.440 --> 00:33:29.760
<v Speaker 0>same programs next to each other ten years

00:33:29.760 --> 00:33:32.515
<v Speaker 0>ago, written in Python and c, and you

00:33:32.515 --> 00:33:34.435
<v Speaker 0>press play, and you just watch one just

00:33:34.435 --> 00:33:40.835
<v Speaker 0>sit there. Yeah. It's it's so aggravating. You

00:33:40.835 --> 00:33:43.175
<v Speaker 0>know, you know, it's I feel like especially

00:33:43.635 --> 00:33:46.000
<v Speaker 0>early on, you don't really understand why. You

00:33:46.000 --> 00:33:47.440
<v Speaker 0>just all you all you're worried about is

00:33:47.440 --> 00:33:50.400
<v Speaker 0>speed. Speed. So speed. You know, I feel

00:33:50.400 --> 00:33:52.000
<v Speaker 0>like that's just a complaint they've heard so

00:33:52.000 --> 00:33:53.760
<v Speaker 0>much over the years, so it's always been

00:33:53.760 --> 00:33:56.640
<v Speaker 0>about optimization. Of course, I'm pretty sure Python's

00:33:56.640 --> 00:33:58.960
<v Speaker 0>also just built on c or c plus

00:33:58.960 --> 00:34:02.845
<v Speaker 0>plus. So, it's already got a great infrastructure

00:34:03.065 --> 00:34:08.905
<v Speaker 0>to start. Right? But your minimum Mac OS

00:34:08.905 --> 00:34:12.185
<v Speaker 0>version is now, ten point thirteen high Sierra

00:34:12.185 --> 00:34:14.285
<v Speaker 0>or newer to run three point one three.

00:34:16.960 --> 00:34:20.180
<v Speaker 0>So if you're running Mac, they increase that,

00:34:24.720 --> 00:34:28.765
<v Speaker 0>the the OS requirement. Delaney just came by

00:34:28.765 --> 00:34:31.265
<v Speaker 0>and brought some food. She looks really awesome.

00:34:31.805 --> 00:34:33.725
<v Speaker 0>Woo hoo. I'm gonna eat that right after

00:34:33.725 --> 00:34:35.485
<v Speaker 0>this. You guys are holding me back right

00:34:35.485 --> 00:34:38.605
<v Speaker 0>now. I'm just kidding. I love being here.

00:34:38.605 --> 00:34:39.885
<v Speaker 0>It's kinda fun to read these with you

00:34:39.885 --> 00:34:43.900
<v Speaker 0>guys. Alright. Cloudflare AI team just open source

00:34:43.960 --> 00:34:47.099
<v Speaker 0>Vibe SDK that lets anyone build and deploy

00:34:47.160 --> 00:34:49.880
<v Speaker 0>a full AI Vibe coding platform with a

00:34:49.880 --> 00:34:51.880
<v Speaker 0>single click. Gotta move this back. I keep

00:34:51.880 --> 00:34:56.665
<v Speaker 0>hearing the the whistles. CloudFlare AI team just

00:34:56.665 --> 00:34:59.945
<v Speaker 0>open source Vibe SDK, a full stack Vibe

00:34:59.945 --> 00:35:01.865
<v Speaker 0>coding platform that you can deploy end to

00:35:01.865 --> 00:35:04.605
<v Speaker 0>end with a single click on CloudFlare's network

00:35:04.745 --> 00:35:08.329
<v Speaker 0>or GitHub repo for. It packages code generation,

00:35:08.470 --> 00:35:11.609
<v Speaker 0>safe execution, live preview, and multi tenant deployment

00:35:11.670 --> 00:35:13.670
<v Speaker 0>so teams can run their own internal or

00:35:13.670 --> 00:35:17.509
<v Speaker 0>customer facing AI app builder without stitching together

00:35:17.509 --> 00:35:22.465
<v Speaker 0>infrastructure. So if you guys aren't familiar with

00:35:22.465 --> 00:35:31.985
<v Speaker 0>live coding yeah. Prompts only. Prompts only to

00:35:31.985 --> 00:35:37.090
<v Speaker 0>build you, a software. And, you know, a

00:35:37.090 --> 00:35:38.850
<v Speaker 0>lot of money has been going into this.

00:35:38.850 --> 00:35:41.250
<v Speaker 0>It's one of the big reasons where people

00:35:41.250 --> 00:35:47.905
<v Speaker 0>have been screaming AI bubble. So I know

00:35:48.125 --> 00:35:50.045
<v Speaker 0>there's a lot of businesses right now that

00:35:50.045 --> 00:35:53.885
<v Speaker 0>are that are building AI driven, IDEs for

00:35:53.885 --> 00:35:55.805
<v Speaker 0>for developers and, you know, the the code's

00:35:55.805 --> 00:35:58.285
<v Speaker 0>there too. So it's it's half and half.

00:35:58.285 --> 00:36:00.045
<v Speaker 0>But I I was reading the other day,

00:36:00.045 --> 00:36:02.580
<v Speaker 0>they're finding now that is that the senior

00:36:02.580 --> 00:36:04.660
<v Speaker 0>developers are the ones that benefit from the

00:36:04.660 --> 00:36:06.900
<v Speaker 0>the most from using something like a AI

00:36:06.900 --> 00:36:09.640
<v Speaker 0>tool. Because they they are the most familiar

00:36:09.700 --> 00:36:12.180
<v Speaker 0>with how to operate a system. They're most

00:36:12.180 --> 00:36:15.140
<v Speaker 0>familiar with, you know, the the requirements of

00:36:15.140 --> 00:36:17.625
<v Speaker 0>of, of a project, so to speak, you

00:36:17.625 --> 00:36:22.985
<v Speaker 0>know. And, their scope provides them it's like

00:36:22.985 --> 00:36:26.845
<v Speaker 0>it's like giving, giving them wings, you know.

00:36:27.465 --> 00:36:29.385
<v Speaker 0>They're able to really utilize that a little

00:36:29.385 --> 00:36:33.500
<v Speaker 0>bit easier. Yeah. Because if I mean, if

00:36:33.500 --> 00:36:36.320
<v Speaker 0>you've seen any sort of chatty p t

00:36:36.940 --> 00:36:41.660
<v Speaker 0>generated code, is not optimized. It's not you

00:36:41.660 --> 00:36:43.340
<v Speaker 0>know, if you're copying and pasting that and

00:36:43.340 --> 00:36:46.605
<v Speaker 0>trying to get a really big project going,

00:36:47.065 --> 00:36:49.224
<v Speaker 0>you know, at some point, you you just

00:36:49.224 --> 00:36:51.785
<v Speaker 0>can't it doesn't understand what it's working, what

00:36:51.785 --> 00:36:53.565
<v Speaker 0>it's working on. You know what I mean?

00:36:53.865 --> 00:36:56.825
<v Speaker 0>So it it is kinda crazy to kinda

00:36:56.825 --> 00:36:58.845
<v Speaker 0>see this kinda being built up so fast.

00:37:00.400 --> 00:37:03.540
<v Speaker 0>Vibe SDK is a production oriented reference implementation,

00:37:04.080 --> 00:37:07.440
<v Speaker 0>not a toy UI. The repo MIT license

00:37:07.440 --> 00:37:10.480
<v Speaker 0>ships a React invite front end worker back

00:37:10.720 --> 00:37:13.119
<v Speaker 0>workers back end with durable objects for agent

00:37:13.119 --> 00:37:17.445
<v Speaker 0>coordination. So d one SQLite via drizzle, r

00:37:17.445 --> 00:37:20.185
<v Speaker 0>two for template storage, k v for sessions,

00:37:20.484 --> 00:37:24.185
<v Speaker 0>and deploy to Cloudflare flow. It integrates Cloudflare

00:37:24.484 --> 00:37:28.244
<v Speaker 0>sandboxes slash containers for isolated builds and previews

00:37:28.244 --> 00:37:31.190
<v Speaker 0>and uses workers for platforms to publish each

00:37:31.190 --> 00:37:34.070
<v Speaker 0>generated app as an isolated worker with its

00:37:34.070 --> 00:37:39.349
<v Speaker 0>own URL. You know, really only got that

00:37:39.349 --> 00:37:41.830
<v Speaker 0>last sentence. Integrates Cloud for a sandbox and

00:37:41.830 --> 00:37:45.045
<v Speaker 0>containers for isolated builds, previews, and uses workers

00:37:45.045 --> 00:37:47.045
<v Speaker 0>for platforms to publish each generated app as

00:37:47.045 --> 00:37:51.525
<v Speaker 0>an isolated worker with its own URL. How

00:37:51.525 --> 00:37:54.005
<v Speaker 0>code moves through the system? A user describes

00:37:54.005 --> 00:37:56.405
<v Speaker 0>the app. The agent generates files and writes

00:37:56.405 --> 00:37:59.349
<v Speaker 0>them into a per user sandbox. The sandbox

00:37:59.349 --> 00:38:03.670
<v Speaker 0>installs depths and starts a dev server. The

00:38:03.670 --> 00:38:07.190
<v Speaker 0>SDK exposes a public preview URL. Logs and

00:38:07.190 --> 00:38:09.349
<v Speaker 0>errors string back to the agent for iterative

00:38:09.349 --> 00:38:12.470
<v Speaker 0>fixes. A deployment sandbox runs Wrangler deploy to

00:38:12.470 --> 00:38:14.875
<v Speaker 0>publish the app to a workers for platforms

00:38:15.175 --> 00:38:18.055
<v Speaker 0>dispatch namespace, giving each app its own tenant

00:38:18.055 --> 00:38:24.855
<v Speaker 0>isolated worker. Okay. So, under this whole thing,

00:38:24.855 --> 00:38:28.155
<v Speaker 0>got Google's Gemini two point five plant family

00:38:28.375 --> 00:38:32.400
<v Speaker 0>for planning, cogent, and debugging, but all LLM

00:38:32.400 --> 00:38:36.320
<v Speaker 0>calls go through CloudFlare AI gateway that enables

00:38:36.320 --> 00:38:41.300
<v Speaker 0>unified routing across providers. OpenAI, Anthropic, Google, response,

00:38:44.445 --> 00:38:48.625
<v Speaker 0>Caching for common requests for provider tokens, latency,

00:38:48.845 --> 00:38:53.005
<v Speaker 0>observe observability, and cost tracking. Swapping or mixing

00:38:53.005 --> 00:38:55.345
<v Speaker 0>models is a conflict choice, not an architectural

00:38:55.565 --> 00:38:58.065
<v Speaker 0>rewrite. Okay. So you don't have to use

00:38:58.299 --> 00:39:10.715
<v Speaker 0>Gemini two point five. That's kinda cool. And

00:39:10.715 --> 00:39:12.235
<v Speaker 0>then they have a live demo and a

00:39:12.235 --> 00:39:14.955
<v Speaker 0>one click of deploy button. Once running, users

00:39:14.955 --> 00:39:17.535
<v Speaker 0>can export generated projects to their own CloudFlare

00:39:17.595 --> 00:39:21.355
<v Speaker 0>account or GitHub repo for continued development. Useful

00:39:21.355 --> 00:39:23.275
<v Speaker 0>if you wanna move work off the hosted

00:39:23.275 --> 00:39:32.829
<v Speaker 0>instance or bring your own CI. So, yeah,

00:39:32.829 --> 00:39:36.510
<v Speaker 0>they're starting to really get into, you know

00:39:36.750 --> 00:39:39.890
<v Speaker 0>it's beyond just that copy paste code generation

00:39:40.109 --> 00:39:43.964
<v Speaker 0>now where it has feedback loops, safe code

00:39:43.964 --> 00:39:48.525
<v Speaker 0>execution, and cheap global deployment by using probably

00:39:48.525 --> 00:39:50.685
<v Speaker 0>something like Docker containers, you know, or it's

00:39:50.685 --> 00:39:59.790
<v Speaker 0>just they're just VM contained builds. Yeah. Wow.

00:40:00.010 --> 00:40:03.690
<v Speaker 0>Jeez. I don't really know how I feel

00:40:03.690 --> 00:40:06.010
<v Speaker 0>about all the vibe coding. I've played with

00:40:06.010 --> 00:40:12.224
<v Speaker 0>cloud code, quite a bit. Yeah. Maybe just,

00:40:12.224 --> 00:40:14.305
<v Speaker 0>like, in this past week, really quite a

00:40:14.305 --> 00:40:19.365
<v Speaker 0>bit. But even that's just, like, I I

00:40:20.145 --> 00:40:22.224
<v Speaker 0>I I feel like the control leaves my

00:40:22.224 --> 00:40:23.980
<v Speaker 0>hands to a degree. You know? I I

00:40:23.980 --> 00:40:25.580
<v Speaker 0>don't know what's going on. I don't know

00:40:25.580 --> 00:40:27.180
<v Speaker 0>if I can fix it. Like, it kinda

00:40:27.180 --> 00:40:30.540
<v Speaker 0>becomes Claude's the engineer now, which I I

00:40:30.540 --> 00:40:32.800
<v Speaker 0>really don't know if I like. I don't

00:40:32.860 --> 00:40:38.525
<v Speaker 0>I don't think I do. You know? Especially,

00:40:39.545 --> 00:40:41.464
<v Speaker 0>you lose out on being able to work

00:40:41.464 --> 00:40:46.505
<v Speaker 0>through the problem, figuring it out, and getting

00:40:46.505 --> 00:40:50.425
<v Speaker 0>that, like, satisfying moment of, like, this this

00:40:50.425 --> 00:40:53.430
<v Speaker 0>is the solution right here. You know? So

00:40:53.430 --> 00:40:56.470
<v Speaker 0>I don't know. It's gonna be an interesting

00:40:56.470 --> 00:40:58.630
<v Speaker 0>change. I'm sure that there's gonna be programs

00:40:58.630 --> 00:41:01.590
<v Speaker 0>for this, to learn how to vibe code

00:41:01.590 --> 00:41:08.555
<v Speaker 0>and to be an efficient vibe coder. But

00:41:08.615 --> 00:41:11.175
<v Speaker 0>who knows how fast those, tools are gonna

00:41:11.175 --> 00:41:13.175
<v Speaker 0>really gonna become available. I mean, even in

00:41:13.175 --> 00:41:16.075
<v Speaker 0>the last year or two, we've seen crazy

00:41:16.135 --> 00:41:21.090
<v Speaker 0>changes with the, LLM scene. So be interesting

00:41:21.090 --> 00:41:23.810
<v Speaker 0>to see how that goes. Alright. I think

00:41:23.810 --> 00:41:26.690
<v Speaker 0>that's it for tonight. Thanks so much for

00:41:26.690 --> 00:41:29.170
<v Speaker 0>coming through. I woulda had a couple more

00:41:29.170 --> 00:41:31.330
<v Speaker 0>articles, but this food is tempting me, and

00:41:31.330 --> 00:41:34.545
<v Speaker 0>I just can't just can't justify not eating

00:41:34.545 --> 00:41:36.305
<v Speaker 0>it. Thank you so much for listening. If

00:41:36.305 --> 00:41:39.425
<v Speaker 0>you listen all the way through, if you

00:41:39.425 --> 00:41:41.685
<v Speaker 0>wanna support the show and or the channel,

00:41:44.465 --> 00:41:47.025
<v Speaker 0>subscribe at geek news central dot com slash

00:41:47.025 --> 00:41:49.859
<v Speaker 0>insider. Got it in the, nav bar now.

00:41:49.859 --> 00:41:50.900
<v Speaker 0>So you could just click it if you

00:41:50.900 --> 00:41:53.400
<v Speaker 0>go to the home page too. But support,

00:41:54.099 --> 00:41:56.260
<v Speaker 0>we really appreciate it. Helps keep the site

00:41:56.260 --> 00:42:00.180
<v Speaker 0>online. Otherwise, till next time. Have a great