WEBVTT

NOTE
Transcription provided by Deepgram

00:00:00.960 --> 00:00:03.860
<v Speaker 0>Welcome to the Geek News Central podcast, episode

00:00:04.080 --> 00:00:07.919
<v Speaker 0>eighteen fifty two. This is your host, Ray

00:00:07.919 --> 00:00:11.920
<v Speaker 0>Cochran, speaking tonight. It has been a little

00:00:11.920 --> 00:00:14.325
<v Speaker 0>minute. So sorry for the delay on the

00:00:14.325 --> 00:00:17.045
<v Speaker 0>shows, but welcome. If it's your first time

00:00:17.045 --> 00:00:18.805
<v Speaker 0>here, welcome to the show. And for all

00:00:18.805 --> 00:00:21.765
<v Speaker 0>you returnees, welcome back. Got a great show

00:00:21.765 --> 00:00:24.325
<v Speaker 0>lined up for you folks this evening. This

00:00:24.325 --> 00:00:25.765
<v Speaker 0>afternoon for me. I don't know why I

00:00:25.765 --> 00:00:30.359
<v Speaker 0>said evening. Just, But let's, kick it off

00:00:30.359 --> 00:00:33.500
<v Speaker 0>with a really awesome sweet first article. NASA's

00:00:33.720 --> 00:00:37.800
<v Speaker 0>ultra quiet supersonic flying swordfish makes history with

00:00:37.800 --> 00:00:41.425
<v Speaker 0>the first test flight. NASA and Lockheed Martin

00:00:41.425 --> 00:00:44.065
<v Speaker 0>have spent years developing the x fifty nine,

00:00:44.065 --> 00:00:47.025
<v Speaker 0>a long nose experimental aircraft designed to quiet

00:00:47.025 --> 00:00:49.765
<v Speaker 0>the traditional sonic boom into a softer thumb.

00:00:50.385 --> 00:00:52.545
<v Speaker 0>This breakthrough is key to potentially lifting the

00:00:52.545 --> 00:00:55.445
<v Speaker 0>decades old ban on supersonic flight over land.

00:00:55.880 --> 00:00:58.040
<v Speaker 0>The aircraft just completed its first real test

00:00:58.040 --> 00:01:01.079
<v Speaker 0>flight out of Palmdale, California on October twenty

00:01:01.079 --> 00:01:05.800
<v Speaker 0>eighth. So this is a pretty cool story

00:01:05.800 --> 00:01:09.915
<v Speaker 0>on some, aviation innovation that that we haven't

00:01:09.915 --> 00:01:11.275
<v Speaker 0>really covered too much on the show, I

00:01:11.275 --> 00:01:14.555
<v Speaker 0>feel like, in recent times. So really, really

00:01:14.555 --> 00:01:18.315
<v Speaker 0>awesome step forward in the aviation field. NASA

00:01:18.315 --> 00:01:20.475
<v Speaker 0>has officially flown its x fifty nine flying

00:01:20.475 --> 00:01:23.340
<v Speaker 0>swordfish for the first time, marking a major

00:01:23.340 --> 00:01:26.300
<v Speaker 0>step towards the return of commercial supersonic air

00:01:26.300 --> 00:01:29.500
<v Speaker 0>travel. The aircraft didn't go supersonic yet, but

00:01:29.500 --> 00:01:31.900
<v Speaker 0>upcoming tests will push towards Mach speeds as

00:01:31.900 --> 00:01:34.540
<v Speaker 0>NASA prepares to gather noise impact data from

00:01:34.540 --> 00:01:39.545
<v Speaker 0>communities across the country. This is kinda cool.

00:01:39.545 --> 00:01:41.465
<v Speaker 0>I mean, I would be interested to just

00:01:41.465 --> 00:01:44.765
<v Speaker 0>kinda see what might change for commercial aircraft,

00:01:46.345 --> 00:01:49.885
<v Speaker 0>or commercial aircraft travel times, with with technology

00:01:50.025 --> 00:01:52.780
<v Speaker 0>like this. The aircraft flew for about an

00:01:52.780 --> 00:01:55.720
<v Speaker 0>hour at twelve thousand feet, and they didn't

00:01:55.720 --> 00:01:59.980
<v Speaker 0>test any, sound barrier breaking, on this test

00:01:59.980 --> 00:02:02.560
<v Speaker 0>flight. It seems it was just, mostly for

00:02:03.994 --> 00:02:06.575
<v Speaker 0>making sure all the devices were working, configurations

00:02:06.954 --> 00:02:11.275
<v Speaker 0>were correct, fine tuning. I do believe they're

00:02:11.275 --> 00:02:13.675
<v Speaker 0>planning to do some testing. It says here

00:02:13.675 --> 00:02:18.880
<v Speaker 0>in Oklahoma, but really awesome specs. According to

00:02:18.880 --> 00:02:21.280
<v Speaker 0>Lockheed Martin specifications, the x fifty nine has

00:02:21.280 --> 00:02:23.940
<v Speaker 0>a top speed of Mach one point four

00:02:24.320 --> 00:02:27.360
<v Speaker 0>or nine hundred twenty five miles per hour

00:02:27.360 --> 00:02:31.295
<v Speaker 0>or fourteen eighty nine kilometers per hour, which

00:02:31.295 --> 00:02:32.895
<v Speaker 0>is almost twice as fast as a Boeing

00:02:32.895 --> 00:02:36.015
<v Speaker 0>seven forty seven. It's, designed to fly at

00:02:36.015 --> 00:02:40.195
<v Speaker 0>an altitude of fifty five thousand, feet, and

00:02:40.740 --> 00:02:42.580
<v Speaker 0>the aircraft has a wingspan of thirty feet.

00:02:42.580 --> 00:02:44.820
<v Speaker 0>It's fourteen feet high and a whopping a

00:02:44.820 --> 00:02:47.400
<v Speaker 0>hundred feet long, giving it a strong resemblance

00:02:47.540 --> 00:02:50.020
<v Speaker 0>to a swordfish. Let me show a front

00:02:50.020 --> 00:02:52.420
<v Speaker 0>view picture of it here on the article

00:02:52.420 --> 00:02:58.765
<v Speaker 0>that I have. It's just cool. I do

00:02:58.765 --> 00:03:01.885
<v Speaker 0>believe that there's probably some other models like

00:03:01.885 --> 00:03:03.644
<v Speaker 0>this out there. Someone in the comments of

00:03:03.644 --> 00:03:07.665
<v Speaker 0>this article says, boom. It's done something similar.

00:03:10.850 --> 00:03:12.850
<v Speaker 0>Something to look into if you're interested in

00:03:12.850 --> 00:03:19.490
<v Speaker 0>supersonic flight. Let's do some let's step away

00:03:19.490 --> 00:03:21.490
<v Speaker 0>from the article for a second. Welcome back,

00:03:21.490 --> 00:03:25.375
<v Speaker 0>everyone. Sorry for the late delivery on this

00:03:25.375 --> 00:03:29.935
<v Speaker 0>week's episodes, plural. Chris and I have been

00:03:29.935 --> 00:03:31.695
<v Speaker 0>pretty backed up. Chris just picked up a

00:03:31.695 --> 00:03:36.879
<v Speaker 0>new job, and I've been just plunging through

00:03:36.879 --> 00:03:41.120
<v Speaker 0>mid or plowing through midterm season. We're actually

00:03:41.120 --> 00:03:43.280
<v Speaker 0>coming up on the end of my term

00:03:43.280 --> 00:03:45.840
<v Speaker 0>here, in a few weeks, and, man, I

00:03:45.840 --> 00:03:48.329
<v Speaker 0>don't feel like I'm ready at all. I

00:03:48.329 --> 00:03:52.275
<v Speaker 0>think, I got one of my midterms back.

00:03:52.275 --> 00:03:53.955
<v Speaker 0>It's probably one of the lowest scores I

00:03:53.955 --> 00:03:56.595
<v Speaker 0>ever received on a midterm in the last

00:03:56.595 --> 00:03:59.394
<v Speaker 0>few years, so it's definitely really disappointed in

00:03:59.394 --> 00:04:03.555
<v Speaker 0>myself in terms of, performance there. But hoping

00:04:03.555 --> 00:04:07.680
<v Speaker 0>to turn that around and potentially, do better

00:04:07.680 --> 00:04:09.200
<v Speaker 0>on the final. So I've been studying a

00:04:09.200 --> 00:04:11.120
<v Speaker 0>little bit extra, working a little bit more

00:04:11.120 --> 00:04:14.720
<v Speaker 0>on that, to try to keep that. I'm

00:04:14.720 --> 00:04:17.280
<v Speaker 0>trying to compensate for how poorly I did

00:04:17.280 --> 00:04:18.720
<v Speaker 0>the first time around. It's very clear I

00:04:18.720 --> 00:04:24.455
<v Speaker 0>didn't understand the content. But, I wanna take

00:04:24.455 --> 00:04:27.355
<v Speaker 0>a second to thank our amazing sponsor, GoDaddy,

00:04:27.975 --> 00:04:30.055
<v Speaker 0>for their incredible support of this podcast. They

00:04:30.055 --> 00:04:32.295
<v Speaker 0>make it possible for us to keep doing

00:04:32.295 --> 00:04:34.635
<v Speaker 0>what we love and for you to enjoy

00:04:35.255 --> 00:04:39.930
<v Speaker 0>hearing every week. That's that's a little words.

00:04:41.669 --> 00:04:43.350
<v Speaker 0>If you're ready to start your own website

00:04:43.350 --> 00:04:45.990
<v Speaker 0>or even launch a podcast, GoDaddy has you

00:04:45.990 --> 00:04:48.470
<v Speaker 0>covered at geek new central dot com forward

00:04:48.470 --> 00:04:50.870
<v Speaker 0>slash godaddy. You'll find special promo codes that

00:04:50.870 --> 00:04:55.645
<v Speaker 0>make it easy and affordable to get started.

00:04:55.645 --> 00:04:57.885
<v Speaker 0>Economy hosting, just six ninety nine a month.

00:04:57.885 --> 00:04:59.485
<v Speaker 0>It's a full year of hosting with a

00:04:59.485 --> 00:05:02.145
<v Speaker 0>free domain name, professional email, and an SSL

00:05:02.365 --> 00:05:05.485
<v Speaker 0>certificate. WordPress hosting, only twelve ninety nine a

00:05:05.485 --> 00:05:08.160
<v Speaker 0>month, including that same free domain name, email,

00:05:08.160 --> 00:05:11.600
<v Speaker 0>and SSL certificate. And if you just need

00:05:11.600 --> 00:05:13.039
<v Speaker 0>a domain name, you can grab one today

00:05:13.039 --> 00:05:17.360
<v Speaker 0>for eleven ninety nine. And if you're not

00:05:17.360 --> 00:05:19.919
<v Speaker 0>super sick to tech savvy, like, GoDaddy's website

00:05:19.919 --> 00:05:21.680
<v Speaker 0>builder gives you a free thirty day trial

00:05:21.680 --> 00:05:24.225
<v Speaker 0>on personal business and business plus plans, so

00:05:24.225 --> 00:05:26.145
<v Speaker 0>you can get online in no time. Let

00:05:26.145 --> 00:05:29.025
<v Speaker 0>it build the website for you. We use

00:05:29.025 --> 00:05:32.065
<v Speaker 0>GoDaddy, products and services here at Geek News

00:05:32.065 --> 00:05:33.985
<v Speaker 0>Central, and I can definitely tell you their

00:05:33.985 --> 00:05:37.590
<v Speaker 0>reliability is the real deal. I don't know

00:05:37.590 --> 00:05:40.890
<v Speaker 0>if I've ever experienced a website outage personally

00:05:40.950 --> 00:05:44.630
<v Speaker 0>through GoDaddy. But your support of GoDaddy directly

00:05:44.630 --> 00:05:46.970
<v Speaker 0>supports this show, so please use our codes,

00:05:47.030 --> 00:05:49.670
<v Speaker 0>click and save, and help this independent podcast

00:05:49.670 --> 00:05:51.945
<v Speaker 0>going strong. Share those links with friends and

00:05:51.945 --> 00:05:53.945
<v Speaker 0>family every time one's used. It's like writing

00:05:53.945 --> 00:05:59.385
<v Speaker 0>a check to the show. Kinda weird my

00:05:59.385 --> 00:06:03.490
<v Speaker 0>insider portion got cut out here. But if

00:06:03.490 --> 00:06:05.410
<v Speaker 0>you guys do wanna support the show directly

00:06:05.410 --> 00:06:07.890
<v Speaker 0>yourself, we do also have a insider program,

00:06:07.890 --> 00:06:10.850
<v Speaker 0>the at geek news central dot com slash

00:06:10.850 --> 00:06:14.610
<v Speaker 0>insider. Support the show directly today through the

00:06:14.610 --> 00:06:19.125
<v Speaker 0>insider program. We really appreciate those of you

00:06:19.125 --> 00:06:20.985
<v Speaker 0>that do support the show through this program.

00:06:21.604 --> 00:06:23.444
<v Speaker 0>Not everyone needs a website right away, so

00:06:23.444 --> 00:06:26.004
<v Speaker 0>sometimes you can, just contribute what little you

00:06:26.004 --> 00:06:27.444
<v Speaker 0>can to the show. We operate on a

00:06:27.444 --> 00:06:28.884
<v Speaker 0>value for value model. So if you're not

00:06:28.884 --> 00:06:32.780
<v Speaker 0>using, modern podcast apps to, stream sats or

00:06:32.780 --> 00:06:35.180
<v Speaker 0>boost the show, we'd definitely recommend trying that

00:06:35.180 --> 00:06:37.900
<v Speaker 0>out. Check it out at podcast apps dot

00:06:37.900 --> 00:06:41.200
<v Speaker 0>com. I've been recently using Cast O Matic,

00:06:41.660 --> 00:06:43.660
<v Speaker 0>trying that out to see how it, how

00:06:43.660 --> 00:06:46.575
<v Speaker 0>their apps fleshed out and stuff. So, definitely

00:06:46.575 --> 00:06:49.295
<v Speaker 0>something to check out. We truly thank you

00:06:49.295 --> 00:06:51.455
<v Speaker 0>guys for supporting us, and a huge, huge

00:06:51.455 --> 00:06:53.935
<v Speaker 0>thanks to GoDaddy for believing in independent creators

00:06:53.935 --> 00:06:58.255
<v Speaker 0>like us here at Geek News Central. Let's

00:06:58.255 --> 00:07:01.659
<v Speaker 0>get back into the show. I got another

00:07:01.659 --> 00:07:04.560
<v Speaker 0>cool article for you guys tonight. The Phantom

00:07:04.699 --> 00:07:09.580
<v Speaker 0>transparent four k monitor. Virtual Instruments has built

00:07:09.580 --> 00:07:12.060
<v Speaker 0>a prototype twenty four inch transparent four k

00:07:12.060 --> 00:07:15.975
<v Speaker 0>monitor called the Phantom. Using a teleprompter style

00:07:15.975 --> 00:07:19.015
<v Speaker 0>mirror system rather than a transparent OLED, it

00:07:19.015 --> 00:07:21.655
<v Speaker 0>achieves a stunning five thousand nits of brightness

00:07:21.655 --> 00:07:23.735
<v Speaker 0>and allows users to see their environment through

00:07:23.735 --> 00:07:26.395
<v Speaker 0>the screen. Only ten units will be produced

00:07:26.455 --> 00:07:32.830
<v Speaker 0>initially. Ten units. Give me a break. So

00:07:32.830 --> 00:07:35.710
<v Speaker 0>this new prototype display called the Phantom is

00:07:35.710 --> 00:07:37.629
<v Speaker 0>aiming to re reinvent the look of a

00:07:37.629 --> 00:07:40.990
<v Speaker 0>desktop monitor by making it transparent. Despite being

00:07:40.990 --> 00:07:43.569
<v Speaker 0>a concept level device with a limited production,

00:07:43.955 --> 00:07:46.355
<v Speaker 0>it demonstrates where high end display technology may

00:07:46.355 --> 00:07:50.915
<v Speaker 0>be headed with mixed reality style visuals. So

00:07:50.915 --> 00:07:55.235
<v Speaker 0>parent apparently, only ten are being made, which

00:07:55.235 --> 00:07:59.470
<v Speaker 0>is, pretty disappointing, honestly. What the heck? I

00:07:59.470 --> 00:08:01.790
<v Speaker 0>I wish I guess it's just a start

00:08:01.790 --> 00:08:03.310
<v Speaker 0>up, but some of the images on this

00:08:03.310 --> 00:08:06.670
<v Speaker 0>article make it look really cool. Obviously, the

00:08:06.670 --> 00:08:11.310
<v Speaker 0>backgrounds look fake, but definitely looks a little

00:08:11.310 --> 00:08:12.990
<v Speaker 0>bit niche. But I think it's cool to

00:08:12.990 --> 00:08:15.945
<v Speaker 0>just kinda see this starting to, come into

00:08:16.325 --> 00:08:20.825
<v Speaker 0>play, especially with themes like Google Glass coming,

00:08:21.125 --> 00:08:25.605
<v Speaker 0>coming out that came out this year. Seems

00:08:25.605 --> 00:08:29.670
<v Speaker 0>like transparency and opacity is very in. Even

00:08:29.670 --> 00:08:33.450
<v Speaker 0>my own, window manager, I've I've set, opacity

00:08:33.750 --> 00:08:39.110
<v Speaker 0>on, my inactive windows to be a little

00:08:39.110 --> 00:08:41.205
<v Speaker 0>bit more clear so that, you know, you

00:08:41.285 --> 00:08:42.965
<v Speaker 0>kinda see the background through it, and it

00:08:42.965 --> 00:08:45.205
<v Speaker 0>looks like a glass screen. It's it's cool.

00:08:45.205 --> 00:08:47.205
<v Speaker 0>I don't know. I I get it. It's

00:08:47.205 --> 00:08:50.805
<v Speaker 0>cool. But I think this is awesome. If

00:08:50.805 --> 00:08:53.445
<v Speaker 0>you guys wanna check this out, this is

00:08:53.445 --> 00:08:55.520
<v Speaker 0>a cool article from Tom's Hardware. Thank you,

00:08:55.520 --> 00:08:58.720
<v Speaker 0>Hassam Nasir. And I didn't, give some credit

00:08:58.720 --> 00:09:00.240
<v Speaker 0>to the last article. So the the previous

00:09:00.240 --> 00:09:03.360
<v Speaker 0>article is from Live Science, by Damien Pine.

00:09:03.360 --> 00:09:07.935
<v Speaker 0>Thank you very much, Damien Pine. But, yeah,

00:09:07.935 --> 00:09:09.455
<v Speaker 0>I mean, I guess since even though we

00:09:09.455 --> 00:09:11.535
<v Speaker 0>won't see transparent monitors in stores yet, this

00:09:11.535 --> 00:09:13.695
<v Speaker 0>kind of tech is signaling the future of

00:09:13.695 --> 00:09:16.655
<v Speaker 0>workspace screens that blend into your environment. Yeah.

00:09:16.655 --> 00:09:19.555
<v Speaker 0>Right? And then AR displays, I I've recently

00:09:19.695 --> 00:09:22.010
<v Speaker 0>have kind of been more and more of

00:09:22.010 --> 00:09:24.170
<v Speaker 0>a believer of AR, and I think my

00:09:24.170 --> 00:09:26.490
<v Speaker 0>next article will actually kinda convince you of

00:09:26.490 --> 00:09:30.410
<v Speaker 0>that. Now this this next one is is

00:09:30.410 --> 00:09:34.675
<v Speaker 0>still in the realm of, this one's in

00:09:34.675 --> 00:09:37.574
<v Speaker 0>the realm of AI. This is, World Labs

00:09:37.634 --> 00:09:40.194
<v Speaker 0>marble three d world model platform got released.

00:09:41.475 --> 00:09:44.435
<v Speaker 0>If you guys, don't know. So Fei Fei

00:09:44.435 --> 00:09:47.560
<v Speaker 0>Li's startup, World Labs, has released marble, a

00:09:47.560 --> 00:09:50.279
<v Speaker 0>next generation AI model that can generate full

00:09:50.279 --> 00:09:53.079
<v Speaker 0>three d worlds from text, images, video, or

00:09:53.079 --> 00:09:55.720
<v Speaker 0>rough layout sketches. It's part of a major

00:09:55.720 --> 00:09:58.920
<v Speaker 0>industry shift from flat image generation to spatial

00:09:58.920 --> 00:10:01.965
<v Speaker 0>intelligence in three d environments. And I was

00:10:01.965 --> 00:10:04.465
<v Speaker 0>talking about this last night with my partner,

00:10:04.765 --> 00:10:08.685
<v Speaker 0>and it it's really interesting to kinda see

00:10:08.685 --> 00:10:11.485
<v Speaker 0>how this technology is shifting. There was a

00:10:11.485 --> 00:10:17.220
<v Speaker 0>generative, like, AI generated Minecraft game where it

00:10:17.220 --> 00:10:21.140
<v Speaker 0>would generate the scene based on, like, your

00:10:21.140 --> 00:10:23.940
<v Speaker 0>relative scene and and other scenes it's seen

00:10:23.940 --> 00:10:25.300
<v Speaker 0>in the game. So you could walk into

00:10:25.300 --> 00:10:28.185
<v Speaker 0>a dark corner and and back out of

00:10:28.185 --> 00:10:29.785
<v Speaker 0>the corner and actually be in a cave

00:10:29.785 --> 00:10:32.505
<v Speaker 0>now because the context had changed to a

00:10:32.505 --> 00:10:34.425
<v Speaker 0>degree where it was closer to being in

00:10:34.425 --> 00:10:36.845
<v Speaker 0>the cave rather than where you originally were.

00:10:37.305 --> 00:10:40.300
<v Speaker 0>So instead of having it like that where

00:10:40.300 --> 00:10:43.120
<v Speaker 0>they're generating it live, now it's being generated

00:10:43.339 --> 00:10:47.020
<v Speaker 0>with, more of a, how do you put

00:10:47.020 --> 00:10:49.580
<v Speaker 0>it? Like, spatial context. You get more spatial

00:10:49.580 --> 00:10:53.035
<v Speaker 0>context, spatial awareness. If there's a building across

00:10:53.035 --> 00:10:55.515
<v Speaker 0>the way that has, mushrooms all around it,

00:10:55.515 --> 00:10:57.115
<v Speaker 0>then the new building you're gonna make is

00:10:57.115 --> 00:11:00.955
<v Speaker 0>gonna be, mushroom themed as well. If you

00:11:00.955 --> 00:11:02.315
<v Speaker 0>guys don't know who Fei Fei Li is,

00:11:02.315 --> 00:11:03.915
<v Speaker 0>Fei Fei Li is, definitely one of the

00:11:03.915 --> 00:11:07.540
<v Speaker 0>most influential figures in artificial intelligence today and

00:11:07.540 --> 00:11:09.320
<v Speaker 0>and has done a lot of work in,

00:11:09.940 --> 00:11:13.140
<v Speaker 0>visual computing. They were born in Beijing in

00:11:13.140 --> 00:11:15.060
<v Speaker 0>nineteen seventy six and educated here in the

00:11:15.060 --> 00:11:17.380
<v Speaker 0>US. She had her her BA at Princeton,

00:11:17.380 --> 00:11:20.575
<v Speaker 0>her PhD in electrical engineering at Caltech. And

00:11:20.575 --> 00:11:22.895
<v Speaker 0>at Stanford, she's been a professor of computer

00:11:22.895 --> 00:11:25.615
<v Speaker 0>science, founding co director of the Human Centered

00:11:25.615 --> 00:11:28.255
<v Speaker 0>AI Institute, and former director of Stanford's AI

00:11:28.255 --> 00:11:32.015
<v Speaker 0>Lab. Now I think her biggest notable achievement

00:11:32.015 --> 00:11:35.630
<v Speaker 0>is ImageNet. Anyone that does visual computing work

00:11:35.630 --> 00:11:37.950
<v Speaker 0>will know what ImageNet is. It's a large

00:11:37.950 --> 00:11:41.150
<v Speaker 0>scale image database that unlocked, basically, like, modern

00:11:41.150 --> 00:11:44.450
<v Speaker 0>era of deep learning and computer vision. So

00:11:44.750 --> 00:11:47.185
<v Speaker 0>more recently, she's been working on this world

00:11:47.185 --> 00:11:50.305
<v Speaker 0>labs, to pioneer spatial intelligence AI that can

00:11:50.305 --> 00:11:53.605
<v Speaker 0>perceive reason and act within three-dimensional physical environments.

00:11:57.105 --> 00:11:59.105
<v Speaker 0>Because she's a huge ad advocate for human

00:11:59.105 --> 00:12:01.765
<v Speaker 0>centered and ethical AI and a greater diversity

00:12:02.110 --> 00:12:05.010
<v Speaker 0>in the field of AI in general. But,

00:12:05.070 --> 00:12:07.710
<v Speaker 0>yeah, Fei Fei Li is huge right now.

00:12:07.710 --> 00:12:10.110
<v Speaker 0>I would definitely look into her and follow

00:12:10.110 --> 00:12:12.350
<v Speaker 0>her on all the relevant social media if

00:12:12.350 --> 00:12:15.790
<v Speaker 0>you're really into, AI news and and visual

00:12:15.790 --> 00:12:20.235
<v Speaker 0>computing. But let's get back to the article.

00:12:21.015 --> 00:12:23.175
<v Speaker 0>World Labs is launching Marvel, a platform that

00:12:23.175 --> 00:12:25.655
<v Speaker 0>lets creators generate three d scenes in environments

00:12:25.655 --> 00:12:28.935
<v Speaker 0>with simple prompts. It can output meshes, videos,

00:12:28.935 --> 00:12:31.870
<v Speaker 0>or Gaussian splats, and it's designed to plug

00:12:31.870 --> 00:12:35.329
<v Speaker 0>into gaming engines, robotics simulations, and VFX pipelines.

00:12:35.870 --> 00:12:37.870
<v Speaker 0>It's a sign that generative AI is moving

00:12:37.870 --> 00:12:42.110
<v Speaker 0>firmly into three d. With this so this

00:12:42.110 --> 00:12:48.435
<v Speaker 0>is really, really cool. It's they've changed the

00:12:48.435 --> 00:12:50.595
<v Speaker 0>approach, and you can see in some of

00:12:50.595 --> 00:12:55.714
<v Speaker 0>the, graphics they provide, just exactly how it

00:12:55.714 --> 00:13:01.160
<v Speaker 0>works. There was a where was it? There

00:13:01.160 --> 00:13:03.960
<v Speaker 0>was a quote that I wish I had

00:13:03.960 --> 00:13:09.640
<v Speaker 0>saved because it really, like, filled in the

00:13:09.640 --> 00:13:11.880
<v Speaker 0>gaps for me, in terms of how this

00:13:11.880 --> 00:13:13.575
<v Speaker 0>works. Let me see if I can find

00:13:13.575 --> 00:13:19.975
<v Speaker 0>it real quick. Now there is a graphic

00:13:19.975 --> 00:13:22.135
<v Speaker 0>on this, page that I do recommend checking

00:13:22.135 --> 00:13:25.490
<v Speaker 0>out, that kinda shows how it works. And

00:13:25.550 --> 00:13:26.830
<v Speaker 0>I think it kinda makes a little more

00:13:26.830 --> 00:13:28.910
<v Speaker 0>sense in terms of, like, why it's more

00:13:28.910 --> 00:13:34.510
<v Speaker 0>persistent rather than, being live generated and changing

00:13:34.510 --> 00:13:36.430
<v Speaker 0>the context, you know, like I was saying

00:13:36.430 --> 00:13:39.815
<v Speaker 0>with the Minecraft thing. But I definitely recommend

00:13:39.815 --> 00:13:41.735
<v Speaker 0>checking this out. This one's from TechCrunch written

00:13:41.735 --> 00:13:47.435
<v Speaker 0>by Rebecca Belen, and truly, really exciting, news

00:13:47.575 --> 00:13:52.720
<v Speaker 0>in the, I guess, in the world of

00:13:52.720 --> 00:13:56.800
<v Speaker 0>computer vision. Now, hopefully, you know, in terms

00:13:56.800 --> 00:13:59.760
<v Speaker 0>of our concerns of ethical image usage and

00:13:59.760 --> 00:14:02.560
<v Speaker 0>whatnot, a lot of that has been taken

00:14:02.560 --> 00:14:06.274
<v Speaker 0>into account here given Faith Elise's reputation and

00:14:06.274 --> 00:14:12.115
<v Speaker 0>her dedication to ethical AI. But I'm sure

00:14:12.115 --> 00:14:14.355
<v Speaker 0>to some degree there's, you know, some stuff

00:14:14.355 --> 00:14:16.675
<v Speaker 0>that slipped through that should not have. I

00:14:16.675 --> 00:14:20.240
<v Speaker 0>hope not, but, I'm curious to see how

00:14:20.240 --> 00:14:22.959
<v Speaker 0>that is I'll have to look into that

00:14:22.959 --> 00:14:25.839
<v Speaker 0>to see how that's guaranteed. You know? If

00:14:25.839 --> 00:14:27.600
<v Speaker 0>if to make make it so that people

00:14:27.600 --> 00:14:30.079
<v Speaker 0>wanna use the model, especially because a big

00:14:30.079 --> 00:14:32.480
<v Speaker 0>concern with generative stuff right now is stealing

00:14:32.480 --> 00:14:36.075
<v Speaker 0>the content contents of other people's work to

00:14:36.075 --> 00:14:41.675
<v Speaker 0>create this new amalgamation. But on the other

00:14:41.675 --> 00:14:43.195
<v Speaker 0>hand, this, this tech this kind of tech

00:14:43.195 --> 00:14:44.795
<v Speaker 0>would dramatically show the time it takes to

00:14:44.795 --> 00:14:47.490
<v Speaker 0>build, like, virtual worlds. So if you guys

00:14:47.570 --> 00:14:52.690
<v Speaker 0>are into gaming, simulations, even possible, like, AR

00:14:52.690 --> 00:14:56.529
<v Speaker 0>training routines and digital content creation, it it

00:14:56.529 --> 00:15:00.695
<v Speaker 0>could probably help with, a lot of filling

00:15:00.695 --> 00:15:02.455
<v Speaker 0>in the gaps in terms of, you know,

00:15:02.455 --> 00:15:06.455
<v Speaker 0>even just creating scenes for your podcast or

00:15:06.455 --> 00:15:08.055
<v Speaker 0>something. You know, like, you could generate a

00:15:08.055 --> 00:15:11.995
<v Speaker 0>background scene for your, Elgato camera, which could

00:15:12.215 --> 00:15:15.015
<v Speaker 0>use that as your, you know, green screen

00:15:15.015 --> 00:15:17.730
<v Speaker 0>image, which is kinda cool. That was something

00:15:17.730 --> 00:15:19.650
<v Speaker 0>I was thinking about trying out, but I

00:15:19.650 --> 00:15:20.930
<v Speaker 0>haven't been too much doing too much of

00:15:20.930 --> 00:15:23.810
<v Speaker 0>the recording, so it didn't really seem too

00:15:23.810 --> 00:15:26.770
<v Speaker 0>important at the time, currently at this point

00:15:26.770 --> 00:15:28.210
<v Speaker 0>in time. But if I do start doing

00:15:28.210 --> 00:15:30.995
<v Speaker 0>more recording, hopefully, I can set up, a

00:15:30.995 --> 00:15:34.274
<v Speaker 0>nice, background instead of just, like, my my

00:15:34.274 --> 00:15:40.435
<v Speaker 0>bedroom. But, yeah, I I definitely recommend checking

00:15:40.435 --> 00:15:42.834
<v Speaker 0>this article out. I think this is gonna

00:15:42.834 --> 00:15:48.720
<v Speaker 0>be some really groundbreaking stuff. And now if

00:15:48.720 --> 00:15:51.920
<v Speaker 0>any of you are into programming or keep

00:15:51.920 --> 00:15:55.040
<v Speaker 0>up with software development news, this next article

00:15:55.040 --> 00:15:58.720
<v Speaker 0>is from the GitHub blog, TypeScript's rise in

00:15:58.720 --> 00:16:02.715
<v Speaker 0>the AI era, insights from lead architect Anders

00:16:04.055 --> 00:16:10.375
<v Speaker 0>Heilsberg. Hopefully I said that right. Now a

00:16:10.375 --> 00:16:14.375
<v Speaker 0>bit of context. Gabe's latest, developer data shows

00:16:14.375 --> 00:16:17.380
<v Speaker 0>that TypeScript has kinda overtaken both JavaScript and

00:16:17.380 --> 00:16:20.180
<v Speaker 0>Python as the most used programming language on

00:16:20.180 --> 00:16:22.580
<v Speaker 0>the platform. Much of this growth is tied

00:16:22.580 --> 00:16:25.700
<v Speaker 0>to AI assisted coding, which benefits heavily from

00:16:25.700 --> 00:16:29.975
<v Speaker 0>typed languages that reduce errors at scale. Now

00:16:29.975 --> 00:16:33.495
<v Speaker 0>I wonder if this is, you know, if

00:16:33.495 --> 00:16:36.455
<v Speaker 0>we're talking how AI assisted coding are we

00:16:36.455 --> 00:16:38.855
<v Speaker 0>talking about that we're gonna that that it

00:16:38.855 --> 00:16:43.700
<v Speaker 0>requires us to strongly type to reduce errors,

00:16:43.700 --> 00:16:48.980
<v Speaker 0>you know, and I I don't know. I

00:16:48.980 --> 00:16:50.100
<v Speaker 0>I I guess I would have to look

00:16:50.100 --> 00:16:51.940
<v Speaker 0>into this more to kinda understand how this

00:16:51.940 --> 00:16:55.160
<v Speaker 0>works. But I assume it helps on a,

00:16:56.195 --> 00:17:01.075
<v Speaker 0>in terms of, generative code and enforcing, you

00:17:01.075 --> 00:17:06.115
<v Speaker 0>know, type rules for specific objects in your

00:17:06.115 --> 00:17:10.990
<v Speaker 0>system. But I wonder if it's just that

00:17:10.990 --> 00:17:14.590
<v Speaker 0>having those types built into the language makes

00:17:14.590 --> 00:17:20.910
<v Speaker 0>the the generative model more, like, it makes

00:17:20.910 --> 00:17:23.230
<v Speaker 0>it more implicit rather than using a very

00:17:23.230 --> 00:17:26.635
<v Speaker 0>broad language like Python, which can you you

00:17:26.775 --> 00:17:31.434
<v Speaker 0>have to be specific or be good about,

00:17:32.375 --> 00:17:34.375
<v Speaker 0>you know, your your type context. I don't

00:17:34.375 --> 00:17:41.710
<v Speaker 0>know. I wonder. So in twenty twenty five,

00:17:41.710 --> 00:17:44.450
<v Speaker 0>TypeScript became the most used language on GitHub.

00:17:45.389 --> 00:17:48.269
<v Speaker 0>More than a million developers began contributing in

00:17:48.269 --> 00:17:51.009
<v Speaker 0>TypeScript this year alone, which is a sixty

00:17:51.070 --> 00:17:56.495
<v Speaker 0>six percent jump. So it this is due

00:17:56.495 --> 00:17:59.235
<v Speaker 0>to its mix of strong typing, the JavaScript

00:17:59.295 --> 00:18:02.915
<v Speaker 0>compatibility, and synergy with AI code generation tools.

00:18:03.055 --> 00:18:05.315
<v Speaker 0>It's a notable shift in the programming landscape.

00:18:05.779 --> 00:18:08.519
<v Speaker 0>And I think, if I remember correctly, TypeScript

00:18:08.980 --> 00:18:14.980
<v Speaker 0>compiles to JavaScript. So it's almost like safe

00:18:14.980 --> 00:18:18.825
<v Speaker 0>setup and clean knockdown. Right? Because, you know,

00:18:18.825 --> 00:18:21.065
<v Speaker 0>most of the Internet's already using JavaScript. I

00:18:21.065 --> 00:18:23.804
<v Speaker 0>think this is, TypeScript's the superset of JavaScript.

00:18:23.945 --> 00:18:31.350
<v Speaker 0>Right? But so, I wonder. I've never, how

00:18:31.350 --> 00:18:32.390
<v Speaker 0>do I put it? I don't know if

00:18:32.390 --> 00:18:35.190
<v Speaker 0>I've ever consciously used TypeScript, but if it's

00:18:35.190 --> 00:18:37.270
<v Speaker 0>a superset of JavaScript, I I wonder if

00:18:37.270 --> 00:18:40.470
<v Speaker 0>it's just, more specific JavaScript. I'll have to

00:18:40.470 --> 00:18:43.144
<v Speaker 0>look into this a little bit more. But

00:18:43.144 --> 00:18:45.385
<v Speaker 0>if you're in tech or aspiring to be

00:18:45.385 --> 00:18:48.904
<v Speaker 0>in tech, I mean, I'm sure you know,

00:18:48.904 --> 00:18:51.465
<v Speaker 0>this is the first time in years Python's

00:18:51.465 --> 00:18:55.225
<v Speaker 0>been overtaken, especially with the AI boom going

00:18:55.225 --> 00:18:58.580
<v Speaker 0>on right now, and how much support there

00:18:58.580 --> 00:19:02.440
<v Speaker 0>is in Python. It's crazy to see that

00:19:04.100 --> 00:19:08.100
<v Speaker 0>we see this shift because generative AI is

00:19:08.100 --> 00:19:11.860
<v Speaker 0>able to write cleaner code with, with strongly

00:19:11.860 --> 00:19:17.155
<v Speaker 0>typed languages. So, yeah, we'll see how this

00:19:17.155 --> 00:19:21.095
<v Speaker 0>goes in the next few years. Even as

00:19:21.155 --> 00:19:23.395
<v Speaker 0>we're seeing more of these code generative tools

00:19:23.395 --> 00:19:27.770
<v Speaker 0>come up and more people shifting away from

00:19:27.770 --> 00:19:31.610
<v Speaker 0>the classic IDE and into things like cursor

00:19:31.610 --> 00:19:38.590
<v Speaker 0>based IDs, which have more of an agentic

00:19:38.650 --> 00:19:41.135
<v Speaker 0>feel to them. At least it's for from

00:19:41.135 --> 00:19:42.895
<v Speaker 0>what I've read. I actually really need to

00:19:42.895 --> 00:19:44.735
<v Speaker 0>try the cursor ID because I've heard a

00:19:44.735 --> 00:19:47.455
<v Speaker 0>lot of good stuff about it, and some

00:19:47.455 --> 00:19:51.455
<v Speaker 0>of the other, you know, auto context protocol

00:19:51.455 --> 00:19:57.970
<v Speaker 0>based generative AI coding tools now. I really

00:19:57.970 --> 00:19:59.990
<v Speaker 0>haven't tried too much of it at all.

00:20:00.289 --> 00:20:02.130
<v Speaker 0>And even just seeing the tip of the

00:20:02.130 --> 00:20:04.289
<v Speaker 0>iceberg with the use of chatbots, like, that's

00:20:04.289 --> 00:20:06.530
<v Speaker 0>only the beginning. The agents is is where

00:20:06.530 --> 00:20:09.295
<v Speaker 0>it's at, you know, really dialing down the

00:20:09.295 --> 00:20:14.175
<v Speaker 0>context in which you're using it. This next

00:20:14.175 --> 00:20:22.510
<v Speaker 0>article, also really cool. Kinda crazy. Let's go

00:20:22.510 --> 00:20:27.570
<v Speaker 0>with it. World's first mass humanoid robot delivery

00:20:27.870 --> 00:20:31.970
<v Speaker 0>begins as UbiTech sends walker s two units.

00:20:32.910 --> 00:20:36.174
<v Speaker 0>So Chinese company UbiTech or Chinese robotics company

00:20:36.174 --> 00:20:38.975
<v Speaker 0>UbiTech has delivered hundreds of its Walker s

00:20:38.975 --> 00:20:42.575
<v Speaker 0>two humanoid robots to factories and manufacturers, including

00:20:42.575 --> 00:20:46.830
<v Speaker 0>major names like BYD and Foxconn. This marks

00:20:46.830 --> 00:20:49.070
<v Speaker 0>the first time humanoid robots have been developed

00:20:49.070 --> 00:20:56.510
<v Speaker 0>at scale in real world industry environments. I

00:20:56.510 --> 00:20:58.110
<v Speaker 0>I wonder if this is what the robots

00:20:58.110 --> 00:21:00.295
<v Speaker 0>actually look like because the front page image

00:21:00.295 --> 00:21:03.735
<v Speaker 0>here on interesting engineering of this article written

00:21:03.735 --> 00:21:06.875
<v Speaker 0>by Sujita Sinha. Hope I said that right.

00:21:10.775 --> 00:21:15.240
<v Speaker 0>The the image here is is kinda crazy.

00:21:16.740 --> 00:21:18.179
<v Speaker 0>I I don't know. I was just talking

00:21:18.179 --> 00:21:19.780
<v Speaker 0>about this with one of my coworkers actually

00:21:19.780 --> 00:21:23.080
<v Speaker 0>the other day. And, you know, in terms

00:21:23.460 --> 00:21:25.720
<v Speaker 0>of AI assisted tools, like, do you need

00:21:25.940 --> 00:21:29.195
<v Speaker 0>a whole human robot body to help you

00:21:29.195 --> 00:21:31.595
<v Speaker 0>wash your dishes or whatever we're gonna have

00:21:31.595 --> 00:21:36.635
<v Speaker 0>this thing do? I'd rather have a device

00:21:36.635 --> 00:21:38.635
<v Speaker 0>that works in sink that washes the dishes,

00:21:38.635 --> 00:21:42.570
<v Speaker 0>you know, rather than have a robot walk

00:21:42.570 --> 00:21:44.890
<v Speaker 0>over to my sink and and and do

00:21:44.890 --> 00:21:46.410
<v Speaker 0>it there. I I don't know. I I

00:21:46.410 --> 00:21:48.510
<v Speaker 0>feel like to a degree we also personify

00:21:48.730 --> 00:21:51.690
<v Speaker 0>or put these put our human emotions on

00:21:51.690 --> 00:21:58.165
<v Speaker 0>them, and develop some sort of hopeful belief

00:21:58.165 --> 00:22:02.265
<v Speaker 0>that they also have feelings too regardless of

00:22:03.125 --> 00:22:05.765
<v Speaker 0>what we're told or what we're led or

00:22:05.765 --> 00:22:11.160
<v Speaker 0>or what science says. Right? And I think

00:22:11.160 --> 00:22:13.400
<v Speaker 0>just seeing them as humanoid robots is gonna

00:22:13.400 --> 00:22:15.799
<v Speaker 0>make us feel bad for them to a

00:22:15.799 --> 00:22:19.480
<v Speaker 0>degree, trying to making someone do all that

00:22:19.480 --> 00:22:22.299
<v Speaker 0>work. But I wonder. Who knows? We'll see

00:22:22.360 --> 00:22:25.645
<v Speaker 0>we'll see how common this becomes. Ubitec says

00:22:25.645 --> 00:22:28.045
<v Speaker 0>it's completed the first world world's first large

00:22:28.045 --> 00:22:31.085
<v Speaker 0>scale shipment of human humanoid robots to active

00:22:31.085 --> 00:22:33.965
<v Speaker 0>factories, marking a milestone in the industry. These

00:22:33.965 --> 00:22:35.805
<v Speaker 0>units are designed to take on human like

00:22:35.805 --> 00:22:39.059
<v Speaker 0>tasks on manufacturing floors, reflecting a shift from

00:22:39.059 --> 00:22:45.940
<v Speaker 0>robotics demos to real factory integration. Oh my

00:22:45.940 --> 00:22:48.580
<v Speaker 0>goodness. Some major companies are driving eight hundred

00:22:48.580 --> 00:22:53.465
<v Speaker 0>million yuan orders in orders for UbiTech's humanoid

00:22:53.605 --> 00:22:56.245
<v Speaker 0>robots. So a lot of companies are already

00:22:56.245 --> 00:23:01.605
<v Speaker 0>saying I want this, which honestly could be

00:23:01.605 --> 00:23:04.325
<v Speaker 0>pretty concerning for the Chinese labor force, you

00:23:04.325 --> 00:23:06.505
<v Speaker 0>know, if they all get rep replaced by

00:23:07.310 --> 00:23:09.070
<v Speaker 0>robots and what are what are they gonna

00:23:09.070 --> 00:23:13.710
<v Speaker 0>do for work? Are we just gonna keep

00:23:13.710 --> 00:23:18.110
<v Speaker 0>giving them that money? You know? I I

00:23:18.110 --> 00:23:22.195
<v Speaker 0>wouldn't think so. So that's also a major

00:23:22.195 --> 00:23:25.235
<v Speaker 0>concern in terms of their economy too would

00:23:25.235 --> 00:23:28.035
<v Speaker 0>be the what happens with all the workers

00:23:28.035 --> 00:23:31.415
<v Speaker 0>that are gonna be replaced by these robots.

00:23:35.670 --> 00:23:39.190
<v Speaker 0>But we'll see. This is a new major

00:23:39.190 --> 00:23:41.510
<v Speaker 0>new phase of automation. Even if you don't

00:23:41.510 --> 00:23:43.990
<v Speaker 0>work in manufacturing, the presence of humanoid robots

00:23:43.990 --> 00:23:48.085
<v Speaker 0>in factories will influence job markets. Supply chains

00:23:48.085 --> 00:23:50.645
<v Speaker 0>and public conversation about robotics and labor is

00:23:50.645 --> 00:23:52.405
<v Speaker 0>gonna be a huge thing in the next

00:23:52.405 --> 00:23:56.805
<v Speaker 0>few years because we have to think ethically

00:23:56.805 --> 00:23:59.490
<v Speaker 0>about the people that we're replacing here and

00:23:59.490 --> 00:24:01.810
<v Speaker 0>the jobs that are gonna be taken up

00:24:01.810 --> 00:24:04.130
<v Speaker 0>by these robots. And, yes, it's one less

00:24:04.130 --> 00:24:05.410
<v Speaker 0>job that has to be done, but it's

00:24:05.410 --> 00:24:07.730
<v Speaker 0>also one less person that gets paid. We

00:24:07.730 --> 00:24:09.570
<v Speaker 0>we don't really operate in a system that

00:24:09.570 --> 00:24:11.970
<v Speaker 0>provides for people that get their jobs replaced

00:24:11.970 --> 00:24:15.755
<v Speaker 0>by robots. So I wonder I wonder how

00:24:15.755 --> 00:24:20.155
<v Speaker 0>that might, affect their their public and their

00:24:20.155 --> 00:24:28.290
<v Speaker 0>population. Well, let's move on. I got one

00:24:28.290 --> 00:24:29.890
<v Speaker 0>last one for you folks today. This one's

00:24:29.890 --> 00:24:34.850
<v Speaker 0>from Emerge, decrypt dot co. So it looks

00:24:34.850 --> 00:24:36.850
<v Speaker 0>like it's a decrypt article. I didn't realize,

00:24:36.850 --> 00:24:40.805
<v Speaker 0>but, hey yo. This is by Jose Antonio

00:24:41.825 --> 00:24:44.065
<v Speaker 0>Lance. Running your own local open source AI

00:24:44.065 --> 00:24:48.465
<v Speaker 0>model is easy. Here's how. Now recently, I've

00:24:48.465 --> 00:24:50.485
<v Speaker 0>definitely been doing a lot of searches into

00:24:50.625 --> 00:24:53.365
<v Speaker 0>getting a new computer, getting some new parts.

00:24:53.899 --> 00:24:59.279
<v Speaker 0>Man, prices have skyrocketed. Kill me. Kill me.

00:24:59.820 --> 00:25:04.059
<v Speaker 0>Those prices have skyrocketed. I think the fifty

00:25:04.059 --> 00:25:07.664
<v Speaker 0>seventy went from eight hundred. The GPU went

00:25:07.664 --> 00:25:10.385
<v Speaker 0>from eight hundred on average to about thirteen

00:25:10.385 --> 00:25:15.345
<v Speaker 0>or fourteen I'm seeing right now. So give

00:25:15.345 --> 00:25:19.590
<v Speaker 0>me a break. Right? But here's a little

00:25:19.590 --> 00:25:21.670
<v Speaker 0>bit of context into this article. Powerful open

00:25:21.670 --> 00:25:24.790
<v Speaker 0>source AI models like Llama, Mistral, and Fi

00:25:24.790 --> 00:25:26.710
<v Speaker 0>are now efficient enough to run on personal

00:25:26.710 --> 00:25:29.510
<v Speaker 0>computers. New tools such as Ollama and LM

00:25:29.510 --> 00:25:31.910
<v Speaker 0>Studios make setup simple, allowing people to use

00:25:31.910 --> 00:25:34.845
<v Speaker 0>AI locally without cloud services or subscription fees.

00:25:35.804 --> 00:25:39.025
<v Speaker 0>Now one of the biggest concerns about using

00:25:39.085 --> 00:25:42.385
<v Speaker 0>these models, from these big providers like Anthropic

00:25:42.605 --> 00:25:48.800
<v Speaker 0>and OpenAI is that you are basically agreeing

00:25:48.800 --> 00:25:50.880
<v Speaker 0>to allowing to have your data taken and

00:25:50.880 --> 00:25:57.200
<v Speaker 0>trained. Not everyone wants that. And a lot

00:25:57.200 --> 00:25:59.040
<v Speaker 0>of people would love to run these tools

00:25:59.040 --> 00:26:03.295
<v Speaker 0>privately. And it's kinda cool to kinda see

00:26:03.295 --> 00:26:05.935
<v Speaker 0>this. I I wanna do that. So that's

00:26:05.935 --> 00:26:07.775
<v Speaker 0>why I'm looking into new PCs and stuff

00:26:07.775 --> 00:26:10.895
<v Speaker 0>and getting something ready, hopefully so I can

00:26:10.895 --> 00:26:15.055
<v Speaker 0>get that all nice and launched and have

00:26:15.055 --> 00:26:18.419
<v Speaker 0>a little private LLM running from this bad

00:26:18.419 --> 00:26:21.299
<v Speaker 0>boy that I can prompt from anywhere. Like,

00:26:21.299 --> 00:26:25.299
<v Speaker 0>that would be cool. So that's in the

00:26:25.299 --> 00:26:27.299
<v Speaker 0>works, but something to think about if you,

00:26:27.539 --> 00:26:29.059
<v Speaker 0>have a nice setup at home and you

00:26:29.059 --> 00:26:31.705
<v Speaker 0>can run a little something. But a growing

00:26:31.705 --> 00:26:33.144
<v Speaker 0>wave of tools is making it easy for

00:26:33.144 --> 00:26:35.404
<v Speaker 0>anyone to run their own AI model entirely

00:26:35.544 --> 00:26:38.424
<v Speaker 0>offline. With just a standard PC, users can

00:26:38.424 --> 00:26:41.065
<v Speaker 0>load open source models and work privately without

00:26:41.065 --> 00:26:43.465
<v Speaker 0>paying per request cost or sharing data with

00:26:43.465 --> 00:26:48.460
<v Speaker 0>cloud providers. Local AI monitors offer local AI

00:26:48.460 --> 00:26:51.419
<v Speaker 0>models offer privacy and zero subscription costs, letting

00:26:51.419 --> 00:26:56.460
<v Speaker 0>you run powerful models completely offline. So, some

00:26:56.460 --> 00:26:58.860
<v Speaker 0>of the models are called Lama, Mishra, or

00:26:58.860 --> 00:27:01.315
<v Speaker 0>Phy. It can be run privately, and you

00:27:01.315 --> 00:27:05.715
<v Speaker 0>can run those through, tools like Ollama. So

00:27:05.715 --> 00:27:07.155
<v Speaker 0>that was the one I was looking into

00:27:07.155 --> 00:27:08.755
<v Speaker 0>and planning to use, but there's another one

00:27:08.755 --> 00:27:11.555
<v Speaker 0>here that's mentioned called LM Studio. And if

00:27:11.555 --> 00:27:14.195
<v Speaker 0>you're a heavy user that that works with

00:27:14.195 --> 00:27:17.600
<v Speaker 0>private data, I definitely recommend that you shift

00:27:17.660 --> 00:27:20.300
<v Speaker 0>in this direction and and put put that

00:27:20.300 --> 00:27:24.380
<v Speaker 0>data into, your own computer instead of providing

00:27:24.380 --> 00:27:27.580
<v Speaker 0>that to a cloud provider. I think that

00:27:27.580 --> 00:27:29.020
<v Speaker 0>just makes sense. You know? It's a little

00:27:29.020 --> 00:27:33.075
<v Speaker 0>bit ridiculous to allow someone to take all

00:27:33.075 --> 00:27:36.195
<v Speaker 0>your stuff and train their own, machine on

00:27:36.195 --> 00:27:40.515
<v Speaker 0>it, further their own profits. You know? Keep

00:27:40.515 --> 00:27:46.020
<v Speaker 0>that stuff private. But I'm sure we're gonna

00:27:46.020 --> 00:27:47.460
<v Speaker 0>see more and more of these tools come

00:27:47.460 --> 00:27:51.700
<v Speaker 0>out that make it easier and easier. The

00:27:51.700 --> 00:27:53.940
<v Speaker 0>shift is gonna give a lot of users

00:27:53.940 --> 00:27:59.240
<v Speaker 0>more control on their, LLM usage, lower costs,

00:27:59.815 --> 00:28:03.675
<v Speaker 0>better privacy, no reliance on big tech infrastructure

00:28:03.975 --> 00:28:08.375
<v Speaker 0>or a massive cloud server. And I think

00:28:08.375 --> 00:28:10.295
<v Speaker 0>that this is kind of hinting that it

00:28:10.295 --> 00:28:13.760
<v Speaker 0>it is possible to have your AI tools

00:28:13.900 --> 00:28:17.900
<v Speaker 0>locally and running at, on your own, you

00:28:17.900 --> 00:28:24.620
<v Speaker 0>know, dime, basically, without having the, requirement for

00:28:24.620 --> 00:28:27.020
<v Speaker 0>a data center to be available to run

00:28:27.020 --> 00:28:30.115
<v Speaker 0>your models and boiling some water. You know?

00:28:30.115 --> 00:28:34.435
<v Speaker 0>So let's see. We'll see. I'm excited about

00:28:34.435 --> 00:28:35.955
<v Speaker 0>this one. This is something I've been definitely

00:28:35.955 --> 00:28:37.795
<v Speaker 0>been looking into a lot recently and have

00:28:37.795 --> 00:28:41.575
<v Speaker 0>been excited to get running on myself. But,

00:28:44.470 --> 00:28:47.590
<v Speaker 0>yeah, you know, cost constraints and whatnot, tend

00:28:47.590 --> 00:28:50.230
<v Speaker 0>to be the number one reason to start

00:28:50.230 --> 00:28:52.950
<v Speaker 0>or to to prevent you from even starting.

00:28:52.950 --> 00:28:55.049
<v Speaker 0>So that's in the works, but we'll see,

00:28:56.345 --> 00:28:58.585
<v Speaker 0>especially with the current prices being as they

00:28:58.585 --> 00:29:02.105
<v Speaker 0>are. I wanna thank you guys again for

00:29:02.105 --> 00:29:04.105
<v Speaker 0>tuning in for the show, folks. That's really

00:29:04.105 --> 00:29:07.145
<v Speaker 0>all I got for you tonight. Sorry again

00:29:07.145 --> 00:29:09.325
<v Speaker 0>for the long delay on the new episodes.

00:29:09.385 --> 00:29:12.790
<v Speaker 0>I'm recording this on Sunday, November twenty third.

00:29:14.530 --> 00:29:16.770
<v Speaker 0>I just celebrated a birthday, so if you

00:29:16.770 --> 00:29:21.890
<v Speaker 0>guys wanna send me a happy birthday, drop

00:29:21.890 --> 00:29:23.330
<v Speaker 0>it in the comments or something. I don't

00:29:23.330 --> 00:29:26.785
<v Speaker 0>know. But we'll try to be a little

00:29:26.785 --> 00:29:28.465
<v Speaker 0>more consistent about the shows. I really do

00:29:28.465 --> 00:29:31.425
<v Speaker 0>have to talk to Chris about nailing down

00:29:31.425 --> 00:29:34.085
<v Speaker 0>which days of the week. We have initially

00:29:34.145 --> 00:29:35.985
<v Speaker 0>thought it thought that we wanted to do

00:29:35.985 --> 00:29:41.440
<v Speaker 0>Monday and Thursday. But I'm I just am

00:29:41.440 --> 00:29:46.180
<v Speaker 0>completely unavailable right now during the week. And

00:29:46.560 --> 00:29:48.560
<v Speaker 0>Saturday or Sunday mornings just seem like the

00:29:48.560 --> 00:29:49.920
<v Speaker 0>best time for me to be able to

00:29:49.920 --> 00:29:52.914
<v Speaker 0>record a show. So I'm gonna be leaning

00:29:52.914 --> 00:29:54.274
<v Speaker 0>a little bit closer to that. If you

00:29:54.274 --> 00:29:55.875
<v Speaker 0>guys would still want me to post it

00:29:55.875 --> 00:29:57.875
<v Speaker 0>on Monday and just record on Saturday or

00:29:57.875 --> 00:30:00.195
<v Speaker 0>Sunday, that could that could totally be do

00:30:00.355 --> 00:30:02.835
<v Speaker 0>doable too. But my idea is if I

00:30:02.835 --> 00:30:04.514
<v Speaker 0>already have it recorded, why are we holding

00:30:04.514 --> 00:30:06.034
<v Speaker 0>back? You guys might as well be able

00:30:06.034 --> 00:30:09.690
<v Speaker 0>to listen to it. So let me know

00:30:09.690 --> 00:30:11.210
<v Speaker 0>what you think. Send us an email at

00:30:11.210 --> 00:30:13.370
<v Speaker 0>geek at geek news central dot com or

00:30:13.370 --> 00:30:16.090
<v Speaker 0>geek news at g mail dot com. Definitely

00:30:16.090 --> 00:30:21.625
<v Speaker 0>wanna hear your feedback, and drop us some,

00:30:21.865 --> 00:30:23.865
<v Speaker 0>comments. Let us know what you guys think

00:30:23.865 --> 00:30:26.825
<v Speaker 0>of the episode. If you guys wanna hear

00:30:26.825 --> 00:30:31.625
<v Speaker 0>more, AI stuff, more space stuff, we're happy

00:30:31.625 --> 00:30:33.545
<v Speaker 0>to to kinda lean into the feedback and

00:30:33.545 --> 00:30:35.465
<v Speaker 0>look for more articles leaning into the direction

00:30:35.465 --> 00:30:38.130
<v Speaker 0>that you guys want to see. So let

00:30:38.130 --> 00:30:40.130
<v Speaker 0>us know. Thanks again for tuning in. You

00:30:40.130 --> 00:30:42.770
<v Speaker 0>guys have a phenomenal night, and we'll catch