WEBVTT

00:00:00.630 --> 00:00:03.490
Today's tech news moves fast, but understanding

00:00:03.490 --> 00:00:06.710
it shouldn't be hard. That's why Snarful Solutions

00:00:06.710 --> 00:00:09.310
Group brings you Connecting the Dots, where we

00:00:09.310 --> 00:00:11.830
break down what's happening in tech and why it

00:00:11.830 --> 00:00:14.890
matters to you. Now, let's dive in with your

00:00:14.890 --> 00:00:17.870
hosts. Welcome to Connecting the Dots, broadcasting

00:00:17.870 --> 00:00:20.170
live from the Snarful Solutions Group in sunny

00:00:20.170 --> 00:00:22.670
Sacramento, California. I'm Alex. And I'm Morgan.

00:00:23.070 --> 00:00:27.399
And today is Monday, September 21, 2026. So before

00:00:27.399 --> 00:00:29.940
we get into our deep dive today, let's get you

00:00:29.940 --> 00:00:32.939
prepped for the day. Looking at the weather right

00:00:32.939 --> 00:00:34.920
here in Sacramento, it is just a gorgeous one

00:00:34.920 --> 00:00:37.119
out there. Yeah, really perfect fall weather.

00:00:37.219 --> 00:00:39.960
It is. We are mostly sunny, sitting right at

00:00:39.960 --> 00:00:42.780
82 degrees with a nice light breeze. Winds are

00:00:42.780 --> 00:00:45.640
like five to nine miles per hour, but. You know,

00:00:45.719 --> 00:00:47.219
if you're traveling, definitely double check

00:00:47.219 --> 00:00:49.119
your local listing. Oh, for sure. Things are

00:00:49.119 --> 00:00:50.659
pretty chaotic in other parts of the country

00:00:50.659 --> 00:00:53.539
right now. Yeah, we are currently tracking 335

00:00:53.539 --> 00:00:57.439
active U .S. weather alerts and 88 of those are

00:00:57.439 --> 00:00:59.619
actually overland. So keep an eye out. Right.

00:00:59.799 --> 00:01:02.640
Those inland systems can shift incredibly fast.

00:01:02.700 --> 00:01:04.980
So you just really can't be too careful if you're

00:01:04.980 --> 00:01:07.599
on the move. Exactly. So pivoting over to the

00:01:07.599 --> 00:01:09.379
financial markets, things are holding pretty

00:01:09.379 --> 00:01:11.939
steady to start the week. The Dow Jones closed

00:01:11.939 --> 00:01:16.379
slightly up, gaining 52 .68 points to land at

00:01:16.379 --> 00:01:20.480
51 ,989 .44. A nice little bump to start the

00:01:20.480 --> 00:01:23.359
day. And the S &P 500 remained mostly flat. I

00:01:23.359 --> 00:01:26.079
mean, it's just inched up 3 .22 points to close

00:01:26.079 --> 00:01:30.900
at 7 ,696 .05. But the real story. I mean, the

00:01:30.900 --> 00:01:32.719
thing everyone is talking about is in crypto.

00:01:33.180 --> 00:01:35.280
Oh, yeah. Bitcoin is just tearing it up right

00:01:35.280 --> 00:01:37.140
now. It really is. It's having a massive day,

00:01:37.239 --> 00:01:40.200
surging over 4 .6 % to edge right up near that

00:01:40.200 --> 00:01:45.040
$85 ,000 mark. It's sitting at $84 ,937 .76 right

00:01:45.040 --> 00:01:48.540
now. I mean, there has just been a lot of significant

00:01:48.540 --> 00:01:50.840
institutional movement driving that momentum

00:01:50.840 --> 00:01:53.780
lately, you know? Totally. Fine, let's do a quick

00:01:53.780 --> 00:01:56.060
check on the diamond. The SF Giants dropped their

00:01:56.060 --> 00:01:59.260
game to the Los Angeles Dodgers 1 -3. Chris Bubick

00:01:59.260 --> 00:02:01.219
took the win on the mound for LA. Tough break

00:02:01.219 --> 00:02:03.040
for the Giants. Yeah, and tough luck for the

00:02:03.040 --> 00:02:05.060
Athletics too, dropping a really tight one to

00:02:05.060 --> 00:02:07.819
the Cleveland Guardians 0 -1. Gavin Williams

00:02:07.819 --> 00:02:09.580
picked up the win for Cleveland. Just a rough

00:02:09.580 --> 00:02:11.620
day for the local teams all around, I guess.

00:02:12.000 --> 00:02:13.819
Yeah, pretty much. All right, well today's episode

00:02:13.819 --> 00:02:16.379
is brought to you by Strong Coffee, the premium

00:02:16.379 --> 00:02:18.180
instant coffee that tastes like a traditional

00:02:18.180 --> 00:02:20.979
brew, but is packed with 15 grams of protein,

00:02:21.219 --> 00:02:24.800
MCTs, and adaptogens like ashwagandha. Get clean,

00:02:25.039 --> 00:02:27.979
sustained energy without the jitters. Use promo

00:02:27.979 --> 00:02:31.639
code SNARFL for 20 % off at strongcoffeecompany

00:02:31.639 --> 00:02:34.539
.com. And honestly, clean energy is definitely

00:02:34.539 --> 00:02:37.080
required for the sheer scale of the engineering

00:02:37.080 --> 00:02:39.979
we are looking at today. Oh, no kidding. So welcome

00:02:39.979 --> 00:02:42.560
to the Morning Star Report. Our mission for this

00:02:42.560 --> 00:02:44.840
segment is pretty simple. We take the day's top

00:02:44.840 --> 00:02:47.240
tech developments and we just strip away the

00:02:47.240 --> 00:02:49.340
heavy, confusing jargon. Right, because nobody

00:02:49.340 --> 00:02:51.719
has time for all that developer speak. Exactly.

00:02:52.280 --> 00:02:54.620
We focus on the real world impact for you, whether

00:02:54.620 --> 00:02:56.680
you're a working professional managing a remote

00:02:56.680 --> 00:02:59.300
team or, you know, a busy parent just trying

00:02:59.300 --> 00:03:01.479
to keep the family's digital life organized.

00:03:02.000 --> 00:03:04.400
And today is a big one. We are looking at a massive

00:03:04.400 --> 00:03:07.400
shift in how our everyday devices talk to each

00:03:07.400 --> 00:03:10.069
other. Yeah, let's unpack this. Google has officially

00:03:10.069 --> 00:03:12.330
unveiled Google Books, which is a brand new line

00:03:12.330 --> 00:03:15.169
of premium laptops launching on October 4th,

00:03:15.169 --> 00:03:18.969
starting at $899. And we really need to clarify

00:03:18.969 --> 00:03:21.090
right out of the gate here. These are not those

00:03:21.090 --> 00:03:23.430
cheap plastic Chromebooks you see handed out

00:03:23.430 --> 00:03:25.430
in elementary schools. Oh, not at all. I mean,

00:03:25.669 --> 00:03:28.080
these things are gorgeous. Right. What we are

00:03:28.080 --> 00:03:31.900
witnessing is a massive, deliberate pivot in

00:03:31.900 --> 00:03:34.360
Google's hardware strategy. They aren't just

00:03:34.360 --> 00:03:36.780
releasing one device, they've actually partnered

00:03:36.780 --> 00:03:39.580
with the absolute heavyweights of the PC world.

00:03:39.659 --> 00:03:43.020
Yeah, we're talking Acer, Asus, Dell, HP, and

00:03:43.020 --> 00:03:46.240
Lenovo. But the catch is that Google has mandated

00:03:46.240 --> 00:03:50.110
a very strict, basically uncompromising standard

00:03:50.110 --> 00:03:52.129
of quality for these. Yeah, they are built using

00:03:52.129 --> 00:03:54.270
premium materials. We're talking machined aluminum,

00:03:54.729 --> 00:03:57.469
magnesium alloy and carbon fiber. And under the

00:03:57.469 --> 00:03:59.729
hood, they're running on Intel Core Ultra Series

00:03:59.729 --> 00:04:03.449
3 or the Qualcomm Snapdragon X Elite chips. Plus

00:04:03.449 --> 00:04:05.669
they have a minimum of 16 gigabytes of RAM across

00:04:05.669 --> 00:04:09.629
the board, up to 2 .8K OLED or LCD screens and

00:04:09.629 --> 00:04:11.810
Dolby Atmos audio. It's a seriously impressive

00:04:11.810 --> 00:04:13.830
spec sheet. It is, but you know, specs are just

00:04:13.830 --> 00:04:16.129
numbers on a box. What actually caught my eye

00:04:16.009 --> 00:04:18.649
is a specific design element. Every single one

00:04:18.649 --> 00:04:20.350
of these Google Books features what they call

00:04:20.350 --> 00:04:24.069
a glow bar on the lid. Ah, yes, the glow bar.

00:04:24.310 --> 00:04:26.250
Yeah, it lights up in Google Colors. When you

00:04:26.250 --> 00:04:28.610
open it, it acts as a visual battery indicator.

00:04:29.050 --> 00:04:30.949
And it even pulses when you're talking to the

00:04:30.949 --> 00:04:34.870
AI. Looking at this glow bar, I mean, it gives

00:04:34.870 --> 00:04:37.810
me serious nostalgia for when Apple laptops had

00:04:37.810 --> 00:04:40.170
the glowing logo on the back. Oh, it definitely

00:04:40.170 --> 00:04:44.620
taps into that exact same iconic energy. It serves

00:04:44.620 --> 00:04:46.920
a much more strategic purpose than just looking

00:04:46.920 --> 00:04:48.579
cool in a coffee shop. Well, let me push you

00:04:48.579 --> 00:04:50.920
on that for a second. Is this GloBar just a flashy

00:04:50.920 --> 00:04:53.300
gimmick to catch your attention? Or is this a

00:04:53.300 --> 00:04:56.240
genuine signal that we're looking at a new unified

00:04:56.240 --> 00:04:59.199
hardware standard for the Android world? It's

00:04:59.199 --> 00:05:01.439
a really good question. Because for years, you

00:05:01.439 --> 00:05:03.800
know, buying an Android tablet or an alternative

00:05:03.800 --> 00:05:07.699
laptop meant navigating just an absolute minefield

00:05:07.699 --> 00:05:10.120
of different qualities and frankly, corners being

00:05:10.120 --> 00:05:12.439
cut. You fit the nail in the head there. It is

00:05:12.439 --> 00:05:15.540
a signal and a highly engineered one. Historically,

00:05:15.639 --> 00:05:18.560
the Android hardware ecosystem has been incredibly

00:05:18.560 --> 00:05:20.959
fractured. Every manufacturer kind of just did

00:05:20.959 --> 00:05:22.860
their own thing. Right. It was a mess. Exactly.

00:05:23.139 --> 00:05:25.740
So the glow bar alongside these super strict

00:05:25.740 --> 00:05:28.540
requirements for premium materials is basically

00:05:28.540 --> 00:05:31.620
Google planting a flag in the ground. OK, I see

00:05:31.620 --> 00:05:33.759
what you mean. They are telling you the consumer.

00:05:34.089 --> 00:05:37.110
If it bears the Google book name and it has the

00:05:37.110 --> 00:05:40.250
specific light bar on the back, you are guaranteed

00:05:40.250 --> 00:05:42.949
a flagship experience. And that's a huge deal

00:05:42.949 --> 00:05:44.589
for you if you're looking to invest in a new

00:05:44.589 --> 00:05:47.949
computer. I mean, starting at $899, it's not

00:05:47.949 --> 00:05:51.189
a budget buy, right? But it provides a high -end

00:05:51.189 --> 00:05:54.250
alternative that finally promises to sync effortlessly

00:05:54.250 --> 00:05:56.350
with the mobile life you probably already have.

00:05:56.509 --> 00:05:58.569
Yeah, and the variety is great. You've got the

00:05:58.569 --> 00:06:01.509
Acer 14 -inch 2 -in -1 Convertible. the super

00:06:01.509 --> 00:06:03.990
light Asus at just two and a half pounds. Oh

00:06:03.990 --> 00:06:06.550
wow, that is incredibly light. Right. Then there's

00:06:06.550 --> 00:06:09.850
the sleek Dell XPS, the 15 inch Lenovo with that

00:06:09.850 --> 00:06:12.490
cool carbon fiber build and the all aluminum

00:06:12.490 --> 00:06:15.089
HP. There's basically a flavor for everyone,

00:06:15.230 --> 00:06:18.410
but the quality floor is remarkably high. And

00:06:18.410 --> 00:06:20.910
because of those specific Intel and Snapdragon

00:06:20.910 --> 00:06:23.769
chips, they aren't just powerful, they are highly

00:06:23.769 --> 00:06:26.620
efficient. I read they're getting up to 14 hours

00:06:26.620 --> 00:06:29.300
of video playback or 16 hours of web browsing.

00:06:29.399 --> 00:06:31.759
Which is fantastic for a work day. Moving on

00:06:31.759 --> 00:06:34.720
to our next story. The hardware is really just

00:06:34.720 --> 00:06:36.699
an empty vessel without the brain running it.

00:06:36.939 --> 00:06:39.220
The reason you need those powerful processors

00:06:39.220 --> 00:06:42.100
brings us directly to the operating system. Right,

00:06:42.139 --> 00:06:44.480
because hardware is absolutely nothing without

00:06:44.480 --> 00:06:48.660
an ecosystem. Which brings us to Google Book

00:06:48.660 --> 00:06:51.279
OS. This is where things get really fascinating

00:06:51.279 --> 00:06:53.759
because it's built on a native Android stack.

00:06:53.879 --> 00:06:56.120
Now let's banish the jargon for a second. Please

00:06:56.120 --> 00:06:58.680
do. When they say a native Android stack, it

00:06:58.680 --> 00:07:01.560
basically means the fundamental foundation of

00:07:01.560 --> 00:07:04.720
this laptop's brain is identical to the brain

00:07:04.720 --> 00:07:08.120
inside an Android smartphone. Furthermore, it

00:07:08.120 --> 00:07:11.100
uses what they call a Material 3 expressive UI.

00:07:11.339 --> 00:07:14.319
Which is another heavy piece of developer jargon.

00:07:14.399 --> 00:07:16.879
Yeah, seriously. Essentially, Material 3 is just

00:07:16.879 --> 00:07:19.319
Google's design language. It dictates the physics

00:07:19.319 --> 00:07:21.959
of the software, like how a button visually presses

00:07:21.959 --> 00:07:24.199
down when you click it, the specific shape of

00:07:24.199 --> 00:07:26.439
the window corners, or how shadows fall on the

00:07:26.439 --> 00:07:29.060
screen. If you've used a recent Pixel phone,

00:07:29.300 --> 00:07:31.259
your brain won't have to learn a new interface

00:07:31.259 --> 00:07:33.600
when you open this laptop. It will instantly

00:07:33.600 --> 00:07:37.019
feel like home. And that familiarity is really

00:07:37.019 --> 00:07:40.189
the entire point. But the real magic happens

00:07:40.189 --> 00:07:42.730
in how deeply they've integrated this with Android

00:07:42.730 --> 00:07:45.629
17. Let's break down what that seamless continuity

00:07:45.629 --> 00:07:47.629
actually looks like, starting with a feature

00:07:47.629 --> 00:07:50.790
called Continue On. Okay, so imagine you're typing

00:07:50.790 --> 00:07:54.790
out a long email or reviewing a complex PDF on

00:07:54.790 --> 00:07:57.569
your phone during your commute on the train.

00:07:57.810 --> 00:08:00.089
Sounds like a typical Tuesday. Right. You walk

00:08:00.089 --> 00:08:02.009
into your office, you open your Google Book,

00:08:02.149 --> 00:08:04.350
and with Continue On, you instantly hand that

00:08:04.350 --> 00:08:07.529
task off from the phone to the laptop. You pick

00:08:07.529 --> 00:08:09.790
up on the exact same sentence, but now you have

00:08:09.790 --> 00:08:12.050
a full keyboard and a mouse. But how does that

00:08:12.050 --> 00:08:14.410
actually work mechanically? Like, it's not just

00:08:14.410 --> 00:08:16.170
uploading to the cloud and downloading again,

00:08:16.389 --> 00:08:18.129
right? Exactly. It's much faster than that. It

00:08:18.129 --> 00:08:21.470
uses a combination of a localized Bluetooth handshake

00:08:21.470 --> 00:08:24.009
to know the devices are near each other, combined

00:08:24.009 --> 00:08:26.329
with real -time state syncing. Oh, that's clever.

00:08:26.569 --> 00:08:28.930
Yeah. The devices are literally whispering to

00:08:28.930 --> 00:08:30.990
each other, passing the baton without you ever

00:08:30.990 --> 00:08:34.549
having to hit save or send. That eliminates so

00:08:34.549 --> 00:08:36.940
much daily friction. But what about apps that

00:08:36.940 --> 00:08:39.559
aren't natively installed on the laptop? Let's

00:08:39.559 --> 00:08:42.240
say I want to order lunch using an app like GrubHub,

00:08:42.559 --> 00:08:45.080
but I really don't want to clutter up my laptop's

00:08:45.080 --> 00:08:47.720
hard drive with a desktop version of a food delivery

00:08:47.720 --> 00:08:50.379
app. That's where AppCast comes into play. You

00:08:50.379 --> 00:08:52.980
just cast the app directly from your phone. Wait,

00:08:52.980 --> 00:08:55.600
really? Yeah. It pops up on your Google Book

00:08:55.600 --> 00:08:58.679
screen in a vertical phone -shaped window. You

00:08:58.679 --> 00:09:00.759
can interact with it using your trackpad and

00:09:00.759 --> 00:09:03.340
keyboard, but all the actual processing, the

00:09:03.340 --> 00:09:06.279
location tracking, the payment data, that is

00:09:06.279 --> 00:09:08.820
all staying securely on your phone. So instead

00:09:08.820 --> 00:09:11.379
of downloading a 500 megabyte app, your laptop

00:09:11.379 --> 00:09:14.769
is... basically acting as a remote control. It's

00:09:14.769 --> 00:09:17.009
streaming the visual output from your phone over

00:09:17.009 --> 00:09:19.649
a local Wi -Fi connection and sending your mouse

00:09:19.649 --> 00:09:21.769
clicks back to it. That is exactly how it works.

00:09:21.850 --> 00:09:23.909
That is brilliant. It also means we can finally

00:09:23.909 --> 00:09:26.269
browse our phone's files directly on the laptop

00:09:26.269 --> 00:09:29.169
without having to awkwardly email photos to ourselves.

00:09:29.389 --> 00:09:32.049
A total game changer for sure. But we cannot

00:09:32.049 --> 00:09:34.970
talk about a 2026 tech launch without talking

00:09:34.970 --> 00:09:39.350
about the AI. Google Book OS has Gemini Nano

00:09:39.350 --> 00:09:42.080
running entirely on device. and they've introduced

00:09:42.080 --> 00:09:44.440
something called Magic Pointer, where you basically

00:09:44.440 --> 00:09:47.299
wiggle your mouse rapidly to trigger AI tasks.

00:09:47.399 --> 00:09:49.480
Yeah, the Magic Pointer. I have to admit, the

00:09:49.480 --> 00:09:52.500
idea of aggressively wiggling my mouse to summon

00:09:52.500 --> 00:09:55.340
an AI feels a little bit like trying to wake

00:09:55.340 --> 00:09:58.580
up a sleeping digital genie by like... furiously

00:09:58.580 --> 00:10:00.639
rubbing the lamp. It does feel a bit theatrical,

00:10:00.639 --> 00:10:02.879
I'll give you that, but the physical action is

00:10:02.879 --> 00:10:04.980
designed to be very intentional. So you don't

00:10:04.980 --> 00:10:07.259
do it by accident. Right, so you don't accidentally

00:10:07.259 --> 00:10:10.120
trigger the AI while just casually moving your

00:10:10.120 --> 00:10:13.039
cursor across a spreadsheet. Fair enough. But

00:10:13.039 --> 00:10:15.039
beyond the wiggling, they've actually replaced

00:10:15.039 --> 00:10:18.090
the traditional caps lock key with a new quick

00:10:18.090 --> 00:10:21.470
insert key you press it and it brings up rambler

00:10:21.470 --> 00:10:23.950
which is this gemini live like a system that

00:10:23.950 --> 00:10:26.549
feature is so useful for fast brainstorming it

00:10:26.549 --> 00:10:29.429
really is you can literally dictate a messy rambling

00:10:29.429 --> 00:10:31.850
stream of consciousness and it just organizes

00:10:31.850 --> 00:10:34.309
it into actual text for an email or a document

00:10:34.309 --> 00:10:37.629
but the feature that blew my mind is create my

00:10:37.629 --> 00:10:40.759
widget Oh, this is a massive leap in generative

00:10:40.759 --> 00:10:43.159
user interfaces. Right. You just type out what

00:10:43.159 --> 00:10:45.220
you want a widget to do in plain English. For

00:10:45.220 --> 00:10:48.080
example, you say, show me my upcoming flight

00:10:48.080 --> 00:10:50.080
times combined with the current weather at my

00:10:50.080 --> 00:10:53.720
destination. And the AI dynamically builds a

00:10:53.720 --> 00:10:56.379
custom widget for your desktop right in front

00:10:56.379 --> 00:10:58.679
of your eyes. It's wild. You aren't just choosing

00:10:58.679 --> 00:11:01.120
from a static list of pre -made widgets anymore.

00:11:01.700 --> 00:11:03.759
The operating system is writing the code for

00:11:03.759 --> 00:11:06.539
a bespoke tool based on your specific explanation

00:11:06.539 --> 00:11:09.700
of what data you need to see. OK, that is undeniably

00:11:09.700 --> 00:11:12.019
cool. But let me push back on something here,

00:11:12.179 --> 00:11:14.639
because the reality of how these apps run on

00:11:14.639 --> 00:11:17.679
Google Book OS sounds like a bit of a mixed bag.

00:11:17.919 --> 00:11:19.710
OK, let's hear it. You have some native Play

00:11:19.710 --> 00:11:21.690
Store apps, right? You have the AppCast mirroring

00:11:21.690 --> 00:11:24.269
thing we just talked about. And then for core

00:11:24.269 --> 00:11:27.370
services like Gmail or Google Calendar, they're

00:11:27.370 --> 00:11:29.730
running as Trusted Web Activities. Right, the

00:11:29.730 --> 00:11:32.870
WebEx. Let's translate that for everyone. A Trusted

00:11:32.870 --> 00:11:34.990
Web Activity is basically a website putting on

00:11:34.990 --> 00:11:37.929
a Halloween costume to look exactly like an app

00:11:37.929 --> 00:11:40.509
on your desktop. It hides the browser search

00:11:40.509 --> 00:11:42.889
bar so it feels native, but it's really just

00:11:42.889 --> 00:11:45.850
a web page. That's a great analogy. So if I'm

00:11:45.850 --> 00:11:48.370
a casual user like a busy parent who just wants

00:11:48.370 --> 00:11:50.990
to buy a laptop and have it work, isn't this

00:11:50.990 --> 00:11:53.309
fractured app experience going to be deeply confusing?

00:11:54.169 --> 00:11:55.850
You don't know if you're getting a phone app

00:11:55.850 --> 00:11:59.909
stretched out, a web page in disguise, or a real

00:11:59.909 --> 00:12:02.940
desktop program. That is the big risk here, and

00:12:02.940 --> 00:12:06.600
it is a very valid concern. When you have multiple

00:12:06.600 --> 00:12:09.639
mechanisms for an app to run, it can absolutely

00:12:09.639 --> 00:12:12.779
lead to a disjointed, frustrating user experience.

00:12:12.840 --> 00:12:14.899
Right, which nobody wants when they drop almost

00:12:14.899 --> 00:12:17.879
a thousand dollars on a machine. Exactly. However,

00:12:18.240 --> 00:12:20.580
Google is attempting to mitigate this by adding

00:12:20.580 --> 00:12:23.070
specific tags in the Play Store. When you go

00:12:23.070 --> 00:12:24.830
to download an app on your Google book, you'll

00:12:24.830 --> 00:12:27.629
see clear upfront labels like made for desktop,

00:12:28.190 --> 00:12:30.110
optimized for desktop, or even better on the

00:12:30.110 --> 00:12:32.789
website. They are actively guiding you to the

00:12:32.789 --> 00:12:35.350
best version of that tool before you even install

00:12:35.350 --> 00:12:37.110
it. So they're acknowledging the mess and at

00:12:37.110 --> 00:12:40.350
least giving you a map to navigate it. Yes. And

00:12:40.350 --> 00:12:42.610
to offset any hesitation you might have about

00:12:42.610 --> 00:12:45.990
adopting a completely new operating system, Google

00:12:45.990 --> 00:12:49.529
is making a massive unprecedented promise. 10

00:12:49.529 --> 00:12:51.889
years of automatic software updates and security

00:12:51.889 --> 00:12:55.769
patches. 10 years. OK, Morgan, a 10 year software

00:12:55.769 --> 00:12:58.690
promise sounds phenomenal in a press release.

00:12:59.179 --> 00:13:01.840
But realistically, is the physical hardware even

00:13:01.840 --> 00:13:05.559
going to survive until 2036? Yeah. I mean, a

00:13:05.559 --> 00:13:07.759
laptop battery from today is not going to hold

00:13:07.759 --> 00:13:10.120
a charge a decade from now and hinges break.

00:13:10.419 --> 00:13:12.100
You're absolutely right that batteries degrade.

00:13:12.240 --> 00:13:14.580
But this 10 year promise isn't about guaranteeing

00:13:14.580 --> 00:13:16.940
the hardware will feel brand new. It's about

00:13:16.940 --> 00:13:19.679
software longevity and security. OK, that makes

00:13:19.679 --> 00:13:21.820
sense. Think about how many laptops end up in

00:13:21.820 --> 00:13:24.100
landfills simply because the manufacturer stops

00:13:24.100 --> 00:13:26.539
issuing security patches after three years, making

00:13:26.539 --> 00:13:29.220
them completely unsafe to use online. Oh, tons

00:13:29.220 --> 00:13:31.299
of them. It's a huge e -waste problem. Right.

00:13:31.820 --> 00:13:33.899
By taking on the responsibility for those updates,

00:13:34.240 --> 00:13:36.399
directly bypassing the hardware manufacturers

00:13:36.399 --> 00:13:39.100
entirely, Google is ensuring that whether you

00:13:39.100 --> 00:13:41.659
buy the ASUS or the Dell, that machine will still

00:13:41.659 --> 00:13:43.840
be secure enough to pass down to a child for

00:13:43.840 --> 00:13:46.700
schoolwork in 2034. That is actually incredible.

00:13:47.080 --> 00:13:49.320
It brings a huge amount of long -term stability

00:13:49.320 --> 00:13:53.100
to anyone investing $900 or $1200 into a computer

00:13:53.100 --> 00:13:55.980
today. It really keeps devices out of the e -waste

00:13:55.980 --> 00:13:58.759
pile. just because of a software bottleneck.

00:13:59.159 --> 00:14:00.740
Yeah. But let's look closer, because the sheer

00:14:00.740 --> 00:14:02.840
scale of what we're talking about is massive.

00:14:02.980 --> 00:14:05.759
All of this constant syncing, this on -device

00:14:05.759 --> 00:14:09.120
AI fetching cloud data, custom widgets pulling

00:14:09.120 --> 00:14:12.399
live flight information, it all requires a massive

00:14:12.399 --> 00:14:15.340
continuous flow of data across the globe. It

00:14:15.340 --> 00:14:18.159
really does take an unbelievable amount of bandwidth.

00:14:18.360 --> 00:14:20.480
Which brings us perfectly to the invisible plumbing

00:14:20.480 --> 00:14:22.860
that makes this entire connected future possible.

00:14:23.340 --> 00:14:25.740
Meta is currently building a brand new subsea

00:14:25.740 --> 00:14:29.039
cable called Pedal. And it is an absolute engineering

00:14:29.039 --> 00:14:31.220
marvel. It really is. We are talking about a

00:14:31.220 --> 00:14:34.000
4 ,300 mile cable that will sit at the bottom

00:14:34.000 --> 00:14:36.460
of the ocean connecting the US and France. It's

00:14:36.460 --> 00:14:39.120
slated to come online by 2029. Just a few years

00:14:39.120 --> 00:14:41.440
away. Yeah. And it's going to use multi -core

00:14:41.440 --> 00:14:44.419
fiber technology to deliver one petabit of data

00:14:44.419 --> 00:14:46.669
per second. Now let's break down how that actually

00:14:46.669 --> 00:14:48.809
works. We hear fiber optics and we generally

00:14:48.809 --> 00:14:52.429
just know it means fast internet. But in standard

00:14:52.429 --> 00:14:55.529
fiber optic cables, you have a single core like

00:14:55.529 --> 00:14:58.149
a tiny glass thread guiding a beam of light.

00:14:58.629 --> 00:15:01.389
Multi -core fiber is entirely different. Imagine

00:15:01.389 --> 00:15:04.389
your current home gigabit internet is a single

00:15:04.389 --> 00:15:06.950
lane tunnel where data cars drive single file.

00:15:07.899 --> 00:15:10.220
Multi -core is like stacking eight tunnels on

00:15:10.220 --> 00:15:12.700
top of each other inside the exact same space.

00:15:12.840 --> 00:15:14.840
Yeah, and bouncing different colored lasers to

00:15:14.840 --> 00:15:17.299
keep all that traffic separated. Exactly, and

00:15:17.299 --> 00:15:19.600
they wrap all this in armored steel and literally

00:15:19.600 --> 00:15:22.259
drop it off the back of a specialized ship, just

00:15:22.259 --> 00:15:24.120
letting it sink to the ocean floor while trying

00:15:24.120 --> 00:15:27.460
to dodge tectonic plates. It is incredibly delicate

00:15:27.460 --> 00:15:30.360
technology wrapped in just brute force industrial

00:15:30.360 --> 00:15:34.080
engineering. and the capacity is staggering.

00:15:34.419 --> 00:15:36.299
It really is hard to wrap your head around. Right,

00:15:36.399 --> 00:15:38.779
so to put some real world context to that number,

00:15:39.460 --> 00:15:41.879
one petabit per second is enough capacity for

00:15:41.879 --> 00:15:45.179
75 % of the entire world's population to stream

00:15:45.179 --> 00:15:47.679
music at the exact same time through this single

00:15:47.679 --> 00:15:50.200
cable. That just completely breaks my brain a

00:15:50.200 --> 00:15:53.340
little bit. Six billion people streaming a song

00:15:53.340 --> 00:15:55.360
simultaneously through a wire sitting in the

00:15:55.360 --> 00:15:56.899
mud at the bottom of the Atlantic. It sounds

00:15:56.899 --> 00:15:59.929
like sci -fi, right? It really does. But here's

00:15:59.929 --> 00:16:02.429
what I want to ask you. As everyday users, we

00:16:02.429 --> 00:16:04.850
never see these cables. We just complain when

00:16:04.850 --> 00:16:08.350
our video call buffers. Why should we care about

00:16:08.350 --> 00:16:10.610
meta laying a cable we'll never look at? That's

00:16:10.610 --> 00:16:13.789
a fair point. How does a massive invisible infrastructure

00:16:13.789 --> 00:16:17.389
project like Petal actually impact the person

00:16:17.389 --> 00:16:20.029
buying a Google Book today? Because the magic

00:16:20.029 --> 00:16:22.629
of that Google Book relies entirely on continuous

00:16:22.629 --> 00:16:26.539
server pings. We look at a shiny new laptop and

00:16:26.539 --> 00:16:29.259
we marvel at how it can use an AI assistant to

00:16:29.259 --> 00:16:32.340
summarize a document in seconds. Right. But while

00:16:32.340 --> 00:16:34.500
Gemini Nano does some processing on the device,

00:16:35.019 --> 00:16:37.139
complex queries often have to travel to a server

00:16:37.139 --> 00:16:39.519
farm, get processed and travel all the way back.

00:16:39.659 --> 00:16:42.779
Now multiply that by billions of users, autonomous

00:16:42.779 --> 00:16:46.000
vehicles, smart cities and AI agents continuously

00:16:46.000 --> 00:16:48.500
talking to each other. So the data load is increasing

00:16:48.500 --> 00:16:51.100
exponentially and the current pipes just aren't

00:16:51.100 --> 00:16:53.440
big enough to handle where we are going. Exactly.

00:16:53.419 --> 00:16:56.340
If we don't lay these new massive multi -core

00:16:56.340 --> 00:16:58.960
cables today, our networks will essentially experience

00:16:58.960 --> 00:17:01.919
digital gridlock. And nobody wants that. No,

00:17:02.100 --> 00:17:06.099
because your premium $1 ,200 laptop would become

00:17:06.099 --> 00:17:08.660
frustratingly slow. Not because the processor

00:17:08.660 --> 00:17:11.740
is bad, but because the global network is congested.

00:17:11.839 --> 00:17:15.839
By building Petal now, Meta and the broader telecom

00:17:15.839 --> 00:17:18.329
industry are future -proofing the internet. They

00:17:18.329 --> 00:17:19.930
are ensuring that when you wiggle your mouse

00:17:19.930 --> 00:17:23.450
to ask an AI a complex question in 2029, the

00:17:23.450 --> 00:17:25.910
answer is still instantaneous, no matter where

00:17:25.910 --> 00:17:28.529
the server processing it happens to be physically

00:17:28.529 --> 00:17:30.750
located. So we're basically building the foundation

00:17:30.750 --> 00:17:33.210
now so that when the real weight of these AI

00:17:33.210 --> 00:17:35.789
tools hits the network, the floor doesn't collapse.

00:17:36.069 --> 00:17:38.440
Precisely. It's the invisible infrastructure

00:17:38.440 --> 00:17:40.779
that makes those magical hardware and software

00:17:40.779 --> 00:17:43.339
experiences even possible. Before we wrap up,

00:17:43.440 --> 00:17:45.819
a quick thanks to Old Glory, an iconic music

00:17:45.819 --> 00:17:48.400
and sports fan merch store. Perfect for the techie

00:17:48.400 --> 00:17:50.920
in your life. Use promo code SNARFL for 15 %

00:17:50.920 --> 00:17:53.740
off at oldglory .com. Always a good spot to check

00:17:53.740 --> 00:17:55.819
out. Definitely. All right, so let's briefly

00:17:55.819 --> 00:17:58.079
recap the relevance of these three stories today.

00:17:58.400 --> 00:18:00.720
We're looking at a tech landscape that is rapidly

00:18:00.720 --> 00:18:03.460
maturing and integrating. We have these shiny,

00:18:03.859 --> 00:18:06.720
powerful premium new hardware devices in the

00:18:06.720 --> 00:18:09.079
form of Google Books, establishing a strict new

00:18:09.079 --> 00:18:11.460
standard of quality. Yeah, and we have Google

00:18:11.460 --> 00:18:15.299
Book OS, a software ecosystem deliberately engineered.

00:18:15.529 --> 00:18:18.789
down to the way apps are mirrored and data is

00:18:18.789 --> 00:18:20.890
synced to completely erase the boundary between

00:18:20.890 --> 00:18:23.829
your mobile phone and your desktop life. And

00:18:23.829 --> 00:18:26.390
all of that is backed by a decade of security

00:18:26.390 --> 00:18:29.509
support. And finally, we have massive underwater

00:18:29.509 --> 00:18:32.089
infrastructure like Meta's pedal cable being

00:18:32.089 --> 00:18:34.769
laid across the ocean floor right now just to

00:18:34.769 --> 00:18:36.930
carry the immense data weight of this connected

00:18:36.930 --> 00:18:39.210
AI driven future we are all sprinting toward.

00:18:39.329 --> 00:18:41.450
It's just a highly cohesive picture of where

00:18:41.450 --> 00:18:43.730
consumer technology is headed and honestly how

00:18:43.730 --> 00:18:45.779
much coordination is required. behind the scenes

00:18:45.779 --> 00:18:47.680
to make it feel effortless for the end user.

00:18:47.880 --> 00:18:50.700
It really is. So we'll leave you with this final

00:18:50.700 --> 00:18:53.460
provocative thought to mull over. We are entering

00:18:53.460 --> 00:18:56.740
an era where a laptop is no longer just a standalone

00:18:56.740 --> 00:18:59.380
machine. It is a literal continuous extension

00:18:59.380 --> 00:19:02.019
of the smartphone you already carry. Absolutely.

00:19:02.539 --> 00:19:04.579
So when it comes time for your next computer

00:19:04.579 --> 00:19:07.220
purchase, will you still be looking at processor

00:19:07.220 --> 00:19:10.200
specs and RAM? Or will your decision be entirely

00:19:10.200 --> 00:19:12.079
dictated by which brand of phone is currently

00:19:12.079 --> 00:19:15.089
sitting in your pocket? We're here to help at

00:19:15.089 --> 00:19:17.049
Snarful, so reach out on our website if you have

00:19:17.049 --> 00:19:23.109
any more questions. That's a wrap on today's

00:19:23.109 --> 00:19:25.869
top stories. Remember, tech doesn't have to be

00:19:25.869 --> 00:19:28.089
complicated and we're here to help connect the

00:19:28.089 --> 00:19:30.869
dots. If you've got questions or want to learn

00:19:30.869 --> 00:19:34.490
more, visit us at snarful .com. Thanks for listening

00:19:34.490 --> 00:19:35.970
and we'll catch you next time.
