WEBVTT - We Need Bigger Tubes

0:00:00.160 --> 0:00:07.400
<v Speaker 1>Brought to you by Toyota. Let's go places. Welcome to

0:00:07.560 --> 0:00:14.960
<v Speaker 1>Forward Thinking. Welcome to Forward Thinking, the show that looks

0:00:14.960 --> 0:00:18.480
<v Speaker 1>at the future and says, hey, now you're doing I'm

0:00:18.520 --> 0:00:21.799
<v Speaker 1>Jonathan Strickland. I'm not going after that now. I'm Lauren

0:00:21.880 --> 0:00:24.479
<v Speaker 1>voc Obama, and I'm Joe McCormick. And we wanted to

0:00:24.520 --> 0:00:28.680
<v Speaker 1>talk a bit about communication and speed of communication and

0:00:28.800 --> 0:00:33.159
<v Speaker 1>throughput of information because these are different terms and often

0:00:33.760 --> 0:00:36.159
<v Speaker 1>we can easily confuse them, mostly because of just the

0:00:36.280 --> 0:00:40.200
<v Speaker 1>terminology we tend to use when discussing the stuff casually, like, hey,

0:00:40.280 --> 0:00:44.519
<v Speaker 1>you know, my internet speed is terrible. It's really really slow.

0:00:44.880 --> 0:00:47.080
<v Speaker 1>And what we mean by that usually is that the

0:00:47.120 --> 0:00:49.760
<v Speaker 1>amount of information we are able to get over a

0:00:49.840 --> 0:00:53.120
<v Speaker 1>given span of time is less than what we would like.

0:00:53.560 --> 0:00:56.040
<v Speaker 1>That's that's generally speaking, what we mean when we say

0:00:56.120 --> 0:00:57.800
<v Speaker 1>my internet slow. Yeah, I mean we mean this web

0:00:57.800 --> 0:01:01.400
<v Speaker 1>page is taking forever to load, like four seconds. It's terrible. Though.

0:01:01.400 --> 0:01:03.560
<v Speaker 1>It's funny because there are a lot of different reasons

0:01:04.080 --> 0:01:06.120
<v Speaker 1>web page could be taking forever to load, right, it

0:01:06.120 --> 0:01:08.720
<v Speaker 1>should be a problem. It could be that the server

0:01:08.959 --> 0:01:11.520
<v Speaker 1>is slow, or it could be a problem with the

0:01:11.560 --> 0:01:14.200
<v Speaker 1>information getting from the server. To you, right, there could

0:01:14.240 --> 0:01:17.120
<v Speaker 1>be some problems with switches or routers between the server

0:01:17.240 --> 0:01:24.280
<v Speaker 1>and your computer. It could be problem with your computer. Yeah.

0:01:24.319 --> 0:01:26.280
<v Speaker 1>The one the one thing that you can rest assured

0:01:26.360 --> 0:01:28.720
<v Speaker 1>is that those uh, those ones and zeros are traveling

0:01:28.880 --> 0:01:32.800
<v Speaker 1>as fast as they possibly can through whichever given pathway

0:01:33.000 --> 0:01:36.240
<v Speaker 1>is available to them. So we really want to kind

0:01:36.240 --> 0:01:40.360
<v Speaker 1>of illustrate the difference between speed and through put. And

0:01:40.480 --> 0:01:43.120
<v Speaker 1>I have kind of a an analogy that I'm going

0:01:43.160 --> 0:01:46.600
<v Speaker 1>to try and and and clumsily set up to sort

0:01:46.600 --> 0:01:50.240
<v Speaker 1>of explain this. So let's imagine that the three of

0:01:50.360 --> 0:01:54.680
<v Speaker 1>us live in three different cities, and they're very far apart, uh,

0:01:54.720 --> 0:01:58.240
<v Speaker 1>and we would like to occasionally visit one another. Now,

0:01:58.280 --> 0:02:02.440
<v Speaker 1>in each of our cities, we have these massive highways

0:02:02.480 --> 0:02:06.200
<v Speaker 1>that have maybe there are ten lanes across, and they

0:02:06.520 --> 0:02:10.320
<v Speaker 1>allow thousands of cars on them at any given time,

0:02:10.360 --> 0:02:13.000
<v Speaker 1>and they can all be traveling at top speed safely

0:02:13.480 --> 0:02:15.880
<v Speaker 1>because of the way these highways are designed. They're probably

0:02:15.880 --> 0:02:19.040
<v Speaker 1>autonomous cars then, right, clearly sure. And then but the

0:02:19.040 --> 0:02:22.040
<v Speaker 1>problem is that when you start traveling, when you get about, oh,

0:02:22.080 --> 0:02:25.640
<v Speaker 1>I don't know, maybe a third of the way from

0:02:25.760 --> 0:02:30.359
<v Speaker 1>my city to Lawrence City, that highway suddenly narrows down

0:02:30.440 --> 0:02:33.440
<v Speaker 1>to one lane, and so those ten lanes are now

0:02:33.480 --> 0:02:36.720
<v Speaker 1>compacted into one lane. And it's not that the cars

0:02:36.840 --> 0:02:39.760
<v Speaker 1>have that any individual car would have to move slower

0:02:39.800 --> 0:02:42.040
<v Speaker 1>down that lane. Is that you now have to compress

0:02:42.040 --> 0:02:45.440
<v Speaker 1>all that traffic down into the one lane of traffic.

0:02:45.480 --> 0:02:49.240
<v Speaker 1>And you can't have two cars in super position on

0:02:49.280 --> 0:02:52.600
<v Speaker 1>each other, because physics don't work that way, y'all, and

0:02:52.639 --> 0:02:54.680
<v Speaker 1>you would end up having a big old smash up

0:02:54.680 --> 0:02:57.960
<v Speaker 1>on the highway. So that's a bottleneck. That's where we

0:02:58.200 --> 0:03:01.079
<v Speaker 1>now are going to see traffic slowed down, even though

0:03:01.120 --> 0:03:03.840
<v Speaker 1>that lead car would still be able to continue moving

0:03:03.960 --> 0:03:06.760
<v Speaker 1>at the same speed it was on when the highway

0:03:06.800 --> 0:03:09.079
<v Speaker 1>had ten lanes wide. And if the same thing is

0:03:09.080 --> 0:03:11.600
<v Speaker 1>true between Lauren City and Joe City and Joe City

0:03:11.600 --> 0:03:15.120
<v Speaker 1>and my City, then traveling between the two we would

0:03:15.480 --> 0:03:17.520
<v Speaker 1>experience some slow down, yea, even though we have these

0:03:17.600 --> 0:03:21.080
<v Speaker 1>hyper efficient cars. Yeah there, yeah, well yeah, And we

0:03:21.120 --> 0:03:24.520
<v Speaker 1>can see that difference in terms of information. And I

0:03:24.520 --> 0:03:27.600
<v Speaker 1>don't know if you've heard about this thing called fiber

0:03:27.639 --> 0:03:31.040
<v Speaker 1>to the home, right um, fiber to the home is

0:03:31.120 --> 0:03:35.560
<v Speaker 1>trying to rectify what's a really common bottleneck in in

0:03:35.640 --> 0:03:39.680
<v Speaker 1>the communication grid that it may be that the backbone,

0:03:39.760 --> 0:03:43.560
<v Speaker 1>you know that the public uh wire that if it's

0:03:43.600 --> 0:03:46.360
<v Speaker 1>optical fiber or something like that. The cable, the cable

0:03:46.440 --> 0:03:49.960
<v Speaker 1>that's um carrying the information. It has a lot of throughput,

0:03:50.000 --> 0:03:52.000
<v Speaker 1>but suddenly it needs to branch off and get to

0:03:52.080 --> 0:03:54.520
<v Speaker 1>your house. And you've got some dinky little, you know,

0:03:54.880 --> 0:03:58.760
<v Speaker 1>rolled up piece of tinfoil. It's transmitting from the optical

0:03:58.840 --> 0:04:01.480
<v Speaker 1>fiber to your home. Someone who gets the message and

0:04:01.520 --> 0:04:03.480
<v Speaker 1>walks to your front door and knocks on your door,

0:04:03.560 --> 0:04:05.440
<v Speaker 1>hands you the message. Then you has to wait for

0:04:05.480 --> 0:04:07.640
<v Speaker 1>you to send the reply. They walk back, and in

0:04:07.640 --> 0:04:09.880
<v Speaker 1>that case, it's it's almost like, well, what's the point

0:04:09.880 --> 0:04:12.320
<v Speaker 1>of the you know, right right, you have this incredibly

0:04:12.360 --> 0:04:16.400
<v Speaker 1>fast connection to the node, the network node that's in

0:04:16.520 --> 0:04:19.200
<v Speaker 1>your neighborhood, but then from the node to your home

0:04:19.440 --> 0:04:22.760
<v Speaker 1>it's a much slower connection, so it doesn't really matter. Uh.

0:04:22.920 --> 0:04:25.279
<v Speaker 1>The same thing is true if you have a really

0:04:25.320 --> 0:04:28.960
<v Speaker 1>fast connection to your home, but one of the big

0:04:29.040 --> 0:04:33.520
<v Speaker 1>connections on the internet, the backbone, if it hasn't already

0:04:33.600 --> 0:04:37.919
<v Speaker 1>been outfitted with with fiber, with optic optic fiber or

0:04:37.960 --> 0:04:41.720
<v Speaker 1>fiber optics. I should say, if I brought a cable. Then, uh,

0:04:42.240 --> 0:04:45.560
<v Speaker 1>while you could send things and get things really quickly

0:04:45.680 --> 0:04:47.839
<v Speaker 1>from your node, once it hit that it would start

0:04:47.880 --> 0:04:51.240
<v Speaker 1>to slow down anyway. So really we're looking at the

0:04:51.240 --> 0:04:54.920
<v Speaker 1>Internet as a as an entire unified system. It's kind

0:04:54.960 --> 0:04:57.840
<v Speaker 1>of interesting to me because one of the things that's

0:04:57.880 --> 0:04:59.760
<v Speaker 1>been the news a lot over the last couple of

0:04:59.839 --> 0:05:02.560
<v Speaker 1>years is is that Google in the United States, in

0:05:02.920 --> 0:05:08.200
<v Speaker 1>Kansas City rolled out the Google Fiber hood. So they

0:05:08.200 --> 0:05:11.640
<v Speaker 1>were making these these neighborhoods rolling out this Google Fiber

0:05:12.080 --> 0:05:14.039
<v Speaker 1>that would give you a one gig a bit per

0:05:14.080 --> 0:05:18.200
<v Speaker 1>second download speed and nearly as fast upload speed. In fact,

0:05:18.240 --> 0:05:21.480
<v Speaker 1>the download and upload speeds are almost the same, which

0:05:21.520 --> 0:05:24.720
<v Speaker 1>is unheard of. I mean, in most networks you get

0:05:24.760 --> 0:05:27.279
<v Speaker 1>a fraction of the upload speed that you get with download.

0:05:27.480 --> 0:05:29.840
<v Speaker 1>And part of that is because uh, you know, you're

0:05:29.880 --> 0:05:32.840
<v Speaker 1>you're trying the networks are trying to save this bandwidth.

0:05:32.839 --> 0:05:37.760
<v Speaker 1>This this is for some networks a a limited amount

0:05:37.920 --> 0:05:41.680
<v Speaker 1>of capacity that they have to handle network traffic, and

0:05:41.720 --> 0:05:44.800
<v Speaker 1>this helps cut that down. Because most people don't upload

0:05:45.240 --> 0:05:48.600
<v Speaker 1>that much stuff that if you are a private citizen

0:05:48.720 --> 0:05:51.640
<v Speaker 1>uploading a lot of data, what are you probably doing

0:05:51.880 --> 0:05:55.479
<v Speaker 1>well these days you might be uploading just videos that

0:05:55.520 --> 0:05:57.280
<v Speaker 1>you're taking and you want to put them on Facebook,

0:05:57.560 --> 0:05:59.960
<v Speaker 1>you know, back in back back then, the earlier, it's

0:06:00.160 --> 0:06:04.160
<v Speaker 1>the assumption would be more likely and you were feeding

0:06:04.160 --> 0:06:07.599
<v Speaker 1>on you know, you were here's every metallic album ever made. Yeah,

0:06:07.600 --> 0:06:09.839
<v Speaker 1>to rival the amount of that people are downloading on

0:06:10.600 --> 0:06:13.160
<v Speaker 1>you know, streaming television or something. Sure, yeah, yeah, well

0:06:13.200 --> 0:06:15.719
<v Speaker 1>ten years ago, I would say that pirating would definitely

0:06:15.800 --> 0:06:17.920
<v Speaker 1>be one of the concerns if you're uploading a lot

0:06:17.920 --> 0:06:21.159
<v Speaker 1>of stuff these days, because there's so many options to

0:06:21.279 --> 0:06:26.599
<v Speaker 1>host media from people legitimately that you could have people

0:06:26.640 --> 0:06:28.880
<v Speaker 1>stepping it up, and there's so many products out there

0:06:29.120 --> 0:06:31.960
<v Speaker 1>that allow you to capture video and upload video, and

0:06:32.600 --> 0:06:34.520
<v Speaker 1>you know, YouTube is allowing you to put up as

0:06:34.600 --> 0:06:38.360
<v Speaker 1>much stuff as you like. Then there's really the capacity

0:06:38.400 --> 0:06:40.400
<v Speaker 1>to actually upload a lot more than you used to.

0:06:40.800 --> 0:06:45.280
<v Speaker 1>But unfortunately the actual Internet service providers haven't necessarily caught

0:06:45.400 --> 0:06:47.400
<v Speaker 1>up to that. So still with a lot of I

0:06:47.560 --> 0:06:50.960
<v Speaker 1>s p s you get a pretty decent download speed,

0:06:51.400 --> 0:06:55.400
<v Speaker 1>but a kind of weedy upload speed. In comparison, Google

0:06:55.440 --> 0:06:58.039
<v Speaker 1>Fiber was a little bit different, like this gig a

0:06:58.040 --> 0:07:00.400
<v Speaker 1>bit down. It was matched by all us to gig

0:07:00.400 --> 0:07:04.000
<v Speaker 1>a bit up. So one question people have had is

0:07:04.920 --> 0:07:07.400
<v Speaker 1>what would you use that for? I mean, what that's

0:07:07.560 --> 0:07:11.920
<v Speaker 1>so much data in such a short amount of time. Well, well, yeah,

0:07:12.040 --> 0:07:14.720
<v Speaker 1>right right now, the answer is kind of uh, I

0:07:14.760 --> 0:07:17.800
<v Speaker 1>don't know, but uh, but you know, it's that's not

0:07:17.880 --> 0:07:19.720
<v Speaker 1>to say that that's always going to be the case.

0:07:20.120 --> 0:07:22.280
<v Speaker 1>Just because we can't imagine it now doesn't mean that

0:07:22.320 --> 0:07:24.880
<v Speaker 1>it's going to be like that forever. But there's when

0:07:24.920 --> 0:07:26.960
<v Speaker 1>it comes to technology. I mean, if there's a free launch,

0:07:27.000 --> 0:07:28.400
<v Speaker 1>people are going to find a way to eat it.

0:07:28.560 --> 0:07:31.080
<v Speaker 1>Well and right now. There was an article that was

0:07:31.120 --> 0:07:35.320
<v Speaker 1>on Slate that was written by Farad Manjou who said that,

0:07:35.840 --> 0:07:38.480
<v Speaker 1>you know, in his experience of using it, he actually

0:07:38.480 --> 0:07:42.120
<v Speaker 1>went to Kansas City, um and tried it out. By

0:07:42.160 --> 0:07:44.200
<v Speaker 1>the way, the Kansas Kansas City for those who don't

0:07:44.200 --> 0:07:46.080
<v Speaker 1>know who people who aren't in the United States aren't

0:07:46.120 --> 0:07:49.720
<v Speaker 1>familiar with the geography. It's actually in two There are

0:07:49.720 --> 0:07:52.160
<v Speaker 1>two states that have a Kansas City, and Google has

0:07:52.240 --> 0:07:55.200
<v Speaker 1>rolled out fiber to both of them. So so yeah,

0:07:55.560 --> 0:07:58.440
<v Speaker 1>you're when I say Kansas City, I'm talking about both

0:07:58.520 --> 0:08:03.320
<v Speaker 1>both Kansas cities. But uh uh Manju went to Kansas

0:08:03.360 --> 0:08:05.880
<v Speaker 1>City to try this out and said that he didn't

0:08:05.880 --> 0:08:08.760
<v Speaker 1>have any problem accessing anything like he could he could

0:08:08.920 --> 0:08:11.320
<v Speaker 1>stream several videos all at the same time. But then

0:08:11.680 --> 0:08:14.360
<v Speaker 1>when he went home he had a twenty two megabit

0:08:14.400 --> 0:08:18.080
<v Speaker 1>per second connection, which is far smaller than the one

0:08:18.120 --> 0:08:21.240
<v Speaker 1>gigabit per second, you know, far less throughput, but was

0:08:21.280 --> 0:08:23.680
<v Speaker 1>still not having any trouble with the videos. So he said, well, really,

0:08:24.120 --> 0:08:26.480
<v Speaker 1>everything I would do, I can kind of do already,

0:08:26.520 --> 0:08:30.119
<v Speaker 1>So what what's the advantage unless you're trying to test

0:08:30.120 --> 0:08:32.760
<v Speaker 1>the limits? And and even then again, you are limited

0:08:32.840 --> 0:08:35.640
<v Speaker 1>not just by the speed that's coming into your home,

0:08:35.679 --> 0:08:38.040
<v Speaker 1>but the speed that's going across the core of the network.

0:08:38.679 --> 0:08:42.679
<v Speaker 1>On i triple ease website, there's an article written by

0:08:42.720 --> 0:08:45.839
<v Speaker 1>Dennis Weller and Bill Woodcock that point out that there

0:08:45.880 --> 0:08:49.280
<v Speaker 1>are Internet exchange points. This is like the core of

0:08:49.320 --> 0:08:52.640
<v Speaker 1>the Internet. This is where the major traffic is switching

0:08:52.679 --> 0:08:56.800
<v Speaker 1>across that uh that don't have this fiber optic cable yet.

0:08:56.800 --> 0:08:59.720
<v Speaker 1>That the rollout was going really heavily in the ninety

0:08:59.840 --> 0:09:03.760
<v Speaker 1>nine indies, but then investments started to peter off towards

0:09:03.760 --> 0:09:06.640
<v Speaker 1>the end of the nineteen nineties, and so some parts

0:09:06.679 --> 0:09:10.280
<v Speaker 1>of the core of the Internet never got upgraded. So

0:09:10.640 --> 0:09:12.320
<v Speaker 1>if you if you don't have the core of the

0:09:12.360 --> 0:09:16.239
<v Speaker 1>Internet covered, then uh, you know, again, that's a bottleneck

0:09:16.320 --> 0:09:18.760
<v Speaker 1>that's going to call if there's some traffic that needs

0:09:18.800 --> 0:09:22.079
<v Speaker 1>to go through that point, you don't really benefit from

0:09:22.080 --> 0:09:23.960
<v Speaker 1>that amazing throughput. And in fact, that was one of

0:09:23.960 --> 0:09:27.040
<v Speaker 1>the points that people have made that it's not that

0:09:27.120 --> 0:09:30.440
<v Speaker 1>Google Fiber isn't fast enough, it's that the rest of

0:09:30.520 --> 0:09:33.880
<v Speaker 1>the Internet isn't fast enough to really take advantage of it. However,

0:09:34.120 --> 0:09:36.320
<v Speaker 1>it's a good thing to have sort of as a

0:09:36.400 --> 0:09:39.959
<v Speaker 1>future proofing system. And even then, we know, I mean

0:09:40.000 --> 0:09:41.880
<v Speaker 1>back in the day, I remember when I had a

0:09:41.920 --> 0:09:44.719
<v Speaker 1>two fifty six megabyte hard drive and I thought, well,

0:09:44.720 --> 0:09:49.079
<v Speaker 1>there's no way I would ever fill this. Yeah, I'll

0:09:49.440 --> 0:09:52.280
<v Speaker 1>be upgrade again. But we learned, you know, we will

0:09:52.320 --> 0:09:54.840
<v Speaker 1>find ways of meeting that capacity over time. It just

0:09:54.960 --> 0:09:58.400
<v Speaker 1>might take a while before that happens. But well, I mean,

0:09:58.640 --> 0:10:02.040
<v Speaker 1>it's interesting that we will always find ways to to

0:10:02.200 --> 0:10:06.840
<v Speaker 1>fill capacity. I think because if you think about all

0:10:06.880 --> 0:10:09.800
<v Speaker 1>the ways that we used to send information that are

0:10:09.880 --> 0:10:13.200
<v Speaker 1>really sort of slowly getting transferred to the Internet. That

0:10:13.280 --> 0:10:15.920
<v Speaker 1>we we used to send letters in the mail all

0:10:15.960 --> 0:10:18.240
<v Speaker 1>the time, we still do that some, but a lot

0:10:18.280 --> 0:10:21.440
<v Speaker 1>of that email. Now we used to you know, get

0:10:21.440 --> 0:10:25.480
<v Speaker 1>our TV from cable or from broadcast. Lots of people

0:10:25.520 --> 0:10:27.040
<v Speaker 1>still do that, but a lot of people are just

0:10:27.080 --> 0:10:30.120
<v Speaker 1>watching TV on the internet. Yeah, there's an increasing number

0:10:30.120 --> 0:10:33.040
<v Speaker 1>of people. Yeah, they hit in a December who plus

0:10:33.160 --> 0:10:38.640
<v Speaker 1>hit like thirty million subscribers. Yeah, so it's yeah, just

0:10:38.679 --> 0:10:44.160
<v Speaker 1>quite we're offloading from all these traditional routes of of

0:10:44.240 --> 0:10:49.240
<v Speaker 1>information to to the single grid basically. Yeah, no, that's

0:10:49.280 --> 0:10:52.200
<v Speaker 1>that's a good point, and it's uh, it's interesting to

0:10:52.240 --> 0:10:56.160
<v Speaker 1>me to see what the difference is between the average

0:10:56.600 --> 0:10:59.800
<v Speaker 1>download speed and the Google fiber download speed. So remember

0:10:59.800 --> 0:11:03.439
<v Speaker 1>I talking about the Google fibers one gigabit per second. Now,

0:11:03.440 --> 0:11:07.040
<v Speaker 1>according to the Slate article, uh, it would say that

0:11:07.040 --> 0:11:10.360
<v Speaker 1>that the average American download speed is closer to six

0:11:10.400 --> 0:11:15.000
<v Speaker 1>point seven megabits per second, which, uh is pretty lot.

0:11:15.120 --> 0:11:17.439
<v Speaker 1>I mean, that's incredibly low. I mean it's it's tiny

0:11:17.480 --> 0:11:20.720
<v Speaker 1>little fraction of the one gigabit per second. Other other

0:11:22.160 --> 0:11:26.320
<v Speaker 1>outlets have estimated a different speed. There was one called

0:11:26.400 --> 0:11:29.800
<v Speaker 1>net Index that says it's more like seventeen point seven

0:11:29.880 --> 0:11:32.559
<v Speaker 1>one megabits per second. It all depends on how you

0:11:32.600 --> 0:11:36.480
<v Speaker 1>measure those speeds. It's usually a sampling kind of like

0:11:36.600 --> 0:11:39.400
<v Speaker 1>Nielsen ratings, right, except for Internet speeds. You you take

0:11:39.400 --> 0:11:43.040
<v Speaker 1>the sample of what these computer speeds are, or the

0:11:43.120 --> 0:11:46.160
<v Speaker 1>data transmission rates I guess I should say, and then

0:11:46.200 --> 0:11:49.400
<v Speaker 1>you sort of average that out across the United States. So, um,

0:11:49.720 --> 0:11:53.559
<v Speaker 1>it's interesting to me because the net Index also ranks countries.

0:11:54.320 --> 0:12:00.520
<v Speaker 1>Uh and and uh can you guess where what what? Well,

0:12:01.000 --> 0:12:05.440
<v Speaker 1>they call it a country, but what city? What city

0:12:05.559 --> 0:12:10.640
<v Speaker 1>has the fastest download connection according to net Index, keeping

0:12:10.640 --> 0:12:14.959
<v Speaker 1>in mind that other companies have different links. Wait wait, wait,

0:12:15.760 --> 0:12:22.360
<v Speaker 1>you said it's a city and they're Now the Pope

0:12:22.440 --> 0:12:27.480
<v Speaker 1>does not have a direct line to the internet. You know,

0:12:27.679 --> 0:12:30.120
<v Speaker 1>you have not seen the Pope's chambers. All right, Well

0:12:30.160 --> 0:12:34.319
<v Speaker 1>that's not the one chamber is totally Texas master control

0:12:34.360 --> 0:12:39.920
<v Speaker 1>programs of computers everywhere. Yeah. No, this is Hong Kong.

0:12:40.000 --> 0:12:42.240
<v Speaker 1>I'm taking it, putting out of your misery. It's Hong Kong.

0:12:42.480 --> 0:12:46.840
<v Speaker 1>That's what they listed. So Hong Kong at they have

0:12:46.920 --> 0:12:49.559
<v Speaker 1>an average of forty four point thirty nine megabets per

0:12:49.559 --> 0:12:52.600
<v Speaker 1>second download speed. The others in the top five include

0:12:52.679 --> 0:12:55.800
<v Speaker 1>Singapore with thirty eight point seven five megabets per second

0:12:56.360 --> 0:13:00.280
<v Speaker 1>Lithuania with thirty eight point seven three, Taiwan on with

0:13:00.320 --> 0:13:03.679
<v Speaker 1>thirty four point eight five, and South Korea brings up

0:13:03.760 --> 0:13:06.839
<v Speaker 1>the rear and the top five with thirty four point

0:13:06.880 --> 0:13:09.200
<v Speaker 1>one nine. If you want to round out the sorry

0:13:09.840 --> 0:13:11.559
<v Speaker 1>that seems to make sense. I mean, aren't all those

0:13:11.600 --> 0:13:16.280
<v Speaker 1>places pretty densely populated, Yeah, so that would like it's

0:13:16.320 --> 0:13:20.000
<v Speaker 1>not like they're having to factor in all the farmers

0:13:20.000 --> 0:13:22.280
<v Speaker 1>out in the middle of nowhere who are well and

0:13:22.320 --> 0:13:26.360
<v Speaker 1>they're also smaller than places like the United States, where

0:13:26.800 --> 0:13:28.960
<v Speaker 1>we have some very dense urban areas, but we also

0:13:28.960 --> 0:13:32.720
<v Speaker 1>have some very wide spaces between US and some other

0:13:32.840 --> 0:13:35.880
<v Speaker 1>populations in the United States. So the other the other

0:13:36.400 --> 0:13:42.080
<v Speaker 1>top ten included Luxembourg, Japan, Netherlands, Switzerland, and Sweden. Sweden

0:13:42.200 --> 0:13:45.079
<v Speaker 1>had twenty nine point thirty six megabits per second. United

0:13:45.120 --> 0:13:48.560
<v Speaker 1>States ranked in at thirty one. And uh, then if

0:13:48.600 --> 0:13:51.560
<v Speaker 1>you look at the United States just trying to figure

0:13:51.559 --> 0:13:54.280
<v Speaker 1>out which states have the fastest, well, first of all,

0:13:54.320 --> 0:13:58.440
<v Speaker 1>the state we live in, Georgia ranks twenty second out

0:13:58.480 --> 0:14:01.800
<v Speaker 1>of the fifty states with eighteen point five one megat's

0:14:01.840 --> 0:14:04.760
<v Speaker 1>per second, so we're still over the average. The national

0:14:04.800 --> 0:14:08.840
<v Speaker 1>average Orange. Yes, yes, yes, we are signed to be

0:14:08.880 --> 0:14:11.040
<v Speaker 1>proud of. So can you can you take a guess

0:14:11.520 --> 0:14:16.160
<v Speaker 1>at which state, according to net index, has the the

0:14:16.320 --> 0:14:19.600
<v Speaker 1>fastest bit rate speed. UH. For if we're going to

0:14:19.680 --> 0:14:22.800
<v Speaker 1>go for for small and compact, I would say what

0:14:22.880 --> 0:14:29.119
<v Speaker 1>Rhode Island? Rhode Island, Uh, Tennessee, Tennessee. It was Delaware.

0:14:29.200 --> 0:14:31.040
<v Speaker 1>You were on the right track there, of ok Obama.

0:14:31.040 --> 0:14:34.440
<v Speaker 1>But yeah, Delaware with twenty five point to nine. So

0:14:34.800 --> 0:14:36.760
<v Speaker 1>that that again is coined to net index. So your

0:14:36.760 --> 0:14:41.160
<v Speaker 1>mileage may vary depending upon which which oracle you consult

0:14:41.240 --> 0:14:43.000
<v Speaker 1>when you try to figure out who has the fastest

0:14:43.040 --> 0:14:46.320
<v Speaker 1>data transmission speeds. Oh no, I said Tennessee, because I

0:14:46.360 --> 0:14:48.400
<v Speaker 1>have no idea to what extent this is true. But

0:14:48.480 --> 0:14:51.160
<v Speaker 1>when I go home to my hometown of Chattanooga, the

0:14:51.800 --> 0:14:57.160
<v Speaker 1>local Electric Power Board has been advertising their UH fiber

0:14:57.160 --> 0:15:00.200
<v Speaker 1>optic service and and there's some kind of claim. Don't

0:15:00.200 --> 0:15:02.520
<v Speaker 1>want to misrepresent them, I don't remember exactly, but there's

0:15:02.560 --> 0:15:05.440
<v Speaker 1>some kind of superlative claim they make. You know, this

0:15:05.520 --> 0:15:11.640
<v Speaker 1>is the fastest fiber optic internet access ever UH with asterisk.

0:15:11.680 --> 0:15:14.640
<v Speaker 1>I don't remember exactly what I mean. That may may

0:15:14.640 --> 0:15:16.920
<v Speaker 1>not be fair, but it's something that they claim it's

0:15:16.960 --> 0:15:20.800
<v Speaker 1>really really fast and my parents house really fast internet.

0:15:20.880 --> 0:15:24.000
<v Speaker 1>I will say, yeah, well, and I mean I've lived

0:15:24.000 --> 0:15:27.160
<v Speaker 1>in places where the connections weren't so great and and

0:15:27.600 --> 0:15:30.560
<v Speaker 1>it was a real pain. And then I've the place

0:15:30.560 --> 0:15:33.120
<v Speaker 1>where I live now the connection tends to be really

0:15:33.120 --> 0:15:37.080
<v Speaker 1>really good. Um. So I mean it all depends on

0:15:37.120 --> 0:15:39.320
<v Speaker 1>where you live, what sort of connections are to your house.

0:15:39.960 --> 0:15:42.680
<v Speaker 1>And again, like we're talking the difference between speed and

0:15:42.760 --> 0:15:45.440
<v Speaker 1>through put. When you're talking about speed, depending on depending

0:15:45.600 --> 0:15:48.120
<v Speaker 1>again upon whom you ask, most will say, oh, it's

0:15:48.200 --> 0:15:50.760
<v Speaker 1>essentially the speed of light. Yeah, yeah, that that That's

0:15:50.760 --> 0:15:53.040
<v Speaker 1>one thing I wanted to bring up. So we as

0:15:53.080 --> 0:15:55.280
<v Speaker 1>we established at the beginning, we keep saying speed, but

0:15:55.320 --> 0:15:59.640
<v Speaker 1>we are talking about throughput. Yeah, what is what role

0:16:00.120 --> 0:16:04.680
<v Speaker 1>is the actual physical speed play? I mean, how fast

0:16:04.800 --> 0:16:07.480
<v Speaker 1>are these signals going? And does that part even matter?

0:16:07.800 --> 0:16:11.000
<v Speaker 1>It they're going really really fast, like so fast that

0:16:11.360 --> 0:16:17.160
<v Speaker 1>on Earth it almost doesn't matter what the actual speed

0:16:17.400 --> 0:16:19.840
<v Speaker 1>is because it's it's so fast as to to us

0:16:19.880 --> 0:16:24.640
<v Speaker 1>to seem close to instantaneous. I've read some different figures

0:16:24.640 --> 0:16:26.360
<v Speaker 1>and I don't know which one is correct, but I

0:16:26.360 --> 0:16:30.080
<v Speaker 1>mean some of basically said, I've seen like that, uh,

0:16:30.280 --> 0:16:33.080
<v Speaker 1>signals in fiber optic cable tend to travel at like

0:16:33.160 --> 0:16:35.560
<v Speaker 1>sixty percent of the speed of light, And then I've

0:16:35.600 --> 0:16:38.400
<v Speaker 1>seen others that say it's it's like nineties something percent,

0:16:38.520 --> 0:16:42.520
<v Speaker 1>which is a huge difference. Yeah, exactly, even at it's

0:16:42.520 --> 0:16:45.720
<v Speaker 1>still really fast, but no, thirty difference in claims is

0:16:45.800 --> 0:16:48.080
<v Speaker 1>pretty amazing. Yeah, So I have no idea who to

0:16:48.120 --> 0:16:50.800
<v Speaker 1>trust there, and I don't know how fast that blip

0:16:51.080 --> 0:16:53.480
<v Speaker 1>really goes. Yeah, And again, I think part of that

0:16:53.600 --> 0:16:56.360
<v Speaker 1>is that there's so many places where that blip could

0:16:56.440 --> 0:17:01.080
<v Speaker 1>encounter congestion that it makes it problematic to measure that speed.

0:17:01.120 --> 0:17:03.880
<v Speaker 1>Because if you're talking about just through a fiber optic cable,

0:17:04.640 --> 0:17:07.120
<v Speaker 1>then you know, you would imagine that it would move

0:17:07.160 --> 0:17:10.480
<v Speaker 1>at the speed that light would travel through that medium. Now,

0:17:10.720 --> 0:17:12.679
<v Speaker 1>keep in mind that, of course, light does not travel

0:17:12.720 --> 0:17:15.120
<v Speaker 1>through every medium at the same speed. When we say

0:17:15.119 --> 0:17:17.879
<v Speaker 1>the speed of light, generally, what we're talking about is

0:17:17.920 --> 0:17:21.360
<v Speaker 1>the speed of light through the vacuum of space. But

0:17:21.359 --> 0:17:25.000
<v Speaker 1>but light just is not the vacuum of space exactly right, right,

0:17:25.280 --> 0:17:30.320
<v Speaker 1>So light does travel through different media at different speeds. Right. So,

0:17:31.200 --> 0:17:34.679
<v Speaker 1>but here's an interesting question. Why is fiber optic cable

0:17:35.160 --> 0:17:39.120
<v Speaker 1>so much faster than a traditional cable, because, if I'm

0:17:39.160 --> 0:17:43.720
<v Speaker 1>not wrong, both signals would technically be traveling at something

0:17:43.800 --> 0:17:46.919
<v Speaker 1>like the speed of light. Right that one is sending

0:17:46.960 --> 0:17:49.959
<v Speaker 1>blips of light through a through a tiny glass wire

0:17:50.600 --> 0:17:54.240
<v Speaker 1>and it's being reflected down along the axis of that wire,

0:17:54.560 --> 0:17:58.199
<v Speaker 1>And then the other is sending an electromagnetic pulse along

0:17:59.359 --> 0:18:02.720
<v Speaker 1>electrons through again and and but wouldn't both of those

0:18:03.000 --> 0:18:04.920
<v Speaker 1>essentially be traveling at the speed of light or is

0:18:05.000 --> 0:18:08.320
<v Speaker 1>there a different speed of light in those two media? Well,

0:18:08.600 --> 0:18:11.159
<v Speaker 1>there's I'm guessing that there is a difference in the

0:18:11.200 --> 0:18:13.120
<v Speaker 1>speed of light in those two media. But I think

0:18:13.119 --> 0:18:16.280
<v Speaker 1>the bigger the bigger issue here is again through put

0:18:16.760 --> 0:18:19.199
<v Speaker 1>It's not it's not again, it's not the speed of

0:18:19.240 --> 0:18:22.600
<v Speaker 1>the information traveling along the distance of the cable. It's

0:18:22.640 --> 0:18:26.359
<v Speaker 1>how much of information can that cable accommodate at one time.

0:18:26.760 --> 0:18:29.600
<v Speaker 1>So I've also read that I think the fiber optic

0:18:29.680 --> 0:18:33.400
<v Speaker 1>cable has less interference. That's true. That, uh, it's less

0:18:33.400 --> 0:18:37.000
<v Speaker 1>susceptible to I don't know what, maybe a magnetic field

0:18:37.160 --> 0:18:40.280
<v Speaker 1>or something like that messing up the signal and causing

0:18:40.320 --> 0:18:42.159
<v Speaker 1>you'd have to send it again. Have you ever have

0:18:42.280 --> 0:18:46.560
<v Speaker 1>you ever listened to music over speaker and had a

0:18:46.640 --> 0:18:49.359
<v Speaker 1>phone go off near it and then get that stuttering

0:18:49.359 --> 0:18:52.080
<v Speaker 1>noise to day to day to day? Did it? Did it?

0:18:52.200 --> 0:18:56.080
<v Speaker 1>You know? It sounds like a great premise for a

0:18:56.119 --> 0:18:58.240
<v Speaker 1>sci fi movie, right, You know why are the phones

0:18:58.320 --> 0:19:00.680
<v Speaker 1>doing that? Yeah? Well, yeah, it's it's because of that

0:19:00.720 --> 0:19:05.640
<v Speaker 1>electromagnetic it's the electromagnetic field, and it's because your speakers

0:19:05.680 --> 0:19:10.320
<v Speaker 1>have really lousy shielding around the cables. Because the electromagnetic

0:19:10.359 --> 0:19:15.000
<v Speaker 1>field is interfering with the transmission of signals across those cables,

0:19:15.040 --> 0:19:18.200
<v Speaker 1>and that's why you're picking up this erratic noise that

0:19:18.280 --> 0:19:21.120
<v Speaker 1>shouldn't be there. So if you shield the cables more

0:19:21.200 --> 0:19:23.879
<v Speaker 1>thoroughly than that protects against that same sort of thing.

0:19:23.960 --> 0:19:27.760
<v Speaker 1>You also can get electron leakage through these cables, and

0:19:27.920 --> 0:19:31.639
<v Speaker 1>that can cause errors in in uh transmissions. So if

0:19:31.640 --> 0:19:35.040
<v Speaker 1>I were to send a message over a copper cable

0:19:35.160 --> 0:19:38.119
<v Speaker 1>and there was a lot of leakage along the line,

0:19:38.600 --> 0:19:40.680
<v Speaker 1>you could get errors on the other end of it.

0:19:40.760 --> 0:19:43.240
<v Speaker 1>You know, the file would not would not end up

0:19:43.320 --> 0:19:47.440
<v Speaker 1>loading correctly unless you had really good error protection on there.

0:19:47.600 --> 0:19:51.119
<v Speaker 1>Whereas detection and protection and where they could account for

0:19:51.200 --> 0:19:53.520
<v Speaker 1>the slow it down in anything when you have to

0:19:53.560 --> 0:19:57.000
<v Speaker 1>send the packet again. Yeah, and then, and the Internet's

0:19:57.000 --> 0:19:59.359
<v Speaker 1>designed to allow for that. I mean, that's one of

0:19:59.400 --> 0:20:02.959
<v Speaker 1>the big advantages of the way the Internet works is that, uh,

0:20:03.280 --> 0:20:07.960
<v Speaker 1>you know, the files are broken up into packets. Those

0:20:08.000 --> 0:20:11.240
<v Speaker 1>packets go across the network. They don't all necessarily follow

0:20:11.320 --> 0:20:14.760
<v Speaker 1>the exact same pathway, and there are duplicates that get across,

0:20:15.119 --> 0:20:18.440
<v Speaker 1>so that when the receiving computer starts getting these packets together,

0:20:18.800 --> 0:20:20.879
<v Speaker 1>it just starts putting it together like it's a puzzle.

0:20:21.160 --> 0:20:23.320
<v Speaker 1>But it's a puzzle where you already know where every

0:20:23.400 --> 0:20:26.320
<v Speaker 1>single piece is supposed to go. And once you have

0:20:27.000 --> 0:20:29.320
<v Speaker 1>packet number twelve, you don't need any of the other

0:20:29.359 --> 0:20:31.960
<v Speaker 1>packet number twelves and you just grab the packets that

0:20:32.000 --> 0:20:34.520
<v Speaker 1>you need and put it back together. That's an oversimplification

0:20:34.560 --> 0:20:36.520
<v Speaker 1>of what's going on with packet switching, but that's the

0:20:36.560 --> 0:20:38.880
<v Speaker 1>general idea, and it's to make the Internet more robust

0:20:39.200 --> 0:20:41.840
<v Speaker 1>and to allow for the fact that sometimes you run

0:20:41.880 --> 0:20:43.920
<v Speaker 1>into these problems with congestion, and that's one way to

0:20:43.960 --> 0:20:47.080
<v Speaker 1>get around it. Literally you're going around the congestion to

0:20:47.200 --> 0:20:49.680
<v Speaker 1>go take a different pathway to get your destination. You

0:20:49.720 --> 0:20:53.119
<v Speaker 1>can also compress the files uh down in various ways

0:20:53.200 --> 0:20:54.800
<v Speaker 1>act sure, I mean even you know, not even just

0:20:54.960 --> 0:20:57.040
<v Speaker 1>just like a ZIP file. But it's a process that

0:20:57.119 --> 0:20:59.840
<v Speaker 1>many computers will go through while they are sending information, right,

0:21:00.000 --> 0:21:02.200
<v Speaker 1>And that helps too, because you're actually reducing the amount

0:21:02.240 --> 0:21:04.440
<v Speaker 1>of information that needs to be sent across the network. Thus,

0:21:05.119 --> 0:21:08.040
<v Speaker 1>again you're not making the file move faster, You're just

0:21:08.200 --> 0:21:11.440
<v Speaker 1>making less information so that you don't have to together

0:21:11.520 --> 0:21:15.160
<v Speaker 1>on the other side. Yeah, what about what about microwaves?

0:21:15.200 --> 0:21:17.480
<v Speaker 1>I've heard I've heard that especially on some really really

0:21:17.600 --> 0:21:20.960
<v Speaker 1>high energy trading companies are starting to look at microwaves

0:21:21.000 --> 0:21:23.520
<v Speaker 1>as a method of communication. Well, thirty Rock has taught

0:21:23.600 --> 0:21:27.719
<v Speaker 1>me anything. Microwaves are really important. There's a whole division

0:21:27.760 --> 0:21:30.320
<v Speaker 1>at G where it was am I thinking of the

0:21:30.440 --> 0:21:36.760
<v Speaker 1>right thing I have? Yeah? Microwaves division. Yeah, yeah, No,

0:21:37.040 --> 0:21:39.200
<v Speaker 1>these these these trading firms that are dealing with with

0:21:39.359 --> 0:21:42.720
<v Speaker 1>with trades that are going on, you know, by by computers, Jo,

0:21:42.800 --> 0:21:44.760
<v Speaker 1>you were talking about a little bit earlier. Yeah, they've

0:21:44.800 --> 0:21:47.520
<v Speaker 1>got these these robots that do trades for him right there.

0:21:47.680 --> 0:21:50.959
<v Speaker 1>They're big computer brains and and they're way smarter than

0:21:51.080 --> 0:21:53.400
<v Speaker 1>us or at least, they're way better at way faster

0:21:53.480 --> 0:21:56.439
<v Speaker 1>than us at process. Yeah, they're way better at playing

0:21:56.520 --> 0:21:59.960
<v Speaker 1>this weird game where they make money by just making trade.

0:22:00.000 --> 0:22:03.280
<v Speaker 1>It's faster than anybody else can UM. And so they

0:22:03.359 --> 0:22:06.120
<v Speaker 1>might buy and sell a stock like eight times within

0:22:06.480 --> 0:22:12.119
<v Speaker 1>half a second UM. And the the money they're making

0:22:12.720 --> 0:22:18.040
<v Speaker 1>is directly dependent on how fast they can transmit the signal. Right,

0:22:19.800 --> 0:22:24.200
<v Speaker 1>Like they're responding to market pressures and they have to

0:22:25.000 --> 0:22:28.480
<v Speaker 1>know when there's like a trend in the market. I think, yeah,

0:22:28.520 --> 0:22:31.000
<v Speaker 1>they're they're checking the differences between different markets and I

0:22:31.080 --> 0:22:34.160
<v Speaker 1>think playing off of that. So for them, time really

0:22:34.320 --> 0:22:38.359
<v Speaker 1>is money. Yeah, well well literally, UM. One company, trade

0:22:38.400 --> 0:22:41.199
<v Speaker 1>Works is putting together this microwave network and they say

0:22:41.240 --> 0:22:44.280
<v Speaker 1>that it's going to um shave maybe two point three

0:22:44.320 --> 0:22:48.000
<v Speaker 1>milliseconds off of off of the transfer process. And at

0:22:48.040 --> 0:22:50.959
<v Speaker 1>this two point three milliseconds could save up point oh

0:22:51.080 --> 0:22:54.520
<v Speaker 1>eight cents per share traded, which could be worth like

0:22:54.840 --> 0:22:57.520
<v Speaker 1>like over a thousand bucks a day. To anyone who's

0:22:57.520 --> 0:22:59.600
<v Speaker 1>doing this, this is all crazy to me, like like

0:22:59.680 --> 0:23:01.680
<v Speaker 1>to the to the to the point that the people

0:23:01.720 --> 0:23:04.960
<v Speaker 1>are NASDAC and CEM are putting together a network that

0:23:05.000 --> 0:23:07.960
<v Speaker 1>they're going to be charging like twenty dollars a month

0:23:08.200 --> 0:23:11.400
<v Speaker 1>for people to use your money. Witchcraft frightens me. And well,

0:23:11.480 --> 0:23:15.320
<v Speaker 1>I mean this is a tangent, but it's just it's

0:23:15.320 --> 0:23:17.760
<v Speaker 1>it's fascinating to me that that all of this, all

0:23:17.800 --> 0:23:20.280
<v Speaker 1>of this is just because you know, microwaves, You've got

0:23:20.320 --> 0:23:22.400
<v Speaker 1>these dish networks that are sending signals through the air.

0:23:22.440 --> 0:23:24.800
<v Speaker 1>They don't have to go through cables, they don't have

0:23:24.840 --> 0:23:26.560
<v Speaker 1>to go around curves or bends. You don't have any

0:23:26.640 --> 0:23:29.720
<v Speaker 1>kind of degradation or or or you do have degradation,

0:23:29.800 --> 0:23:31.399
<v Speaker 1>but it's a different kind. But it's like a direct

0:23:31.480 --> 0:23:35.680
<v Speaker 1>line of sight kind of transmission as opposed to whatever

0:23:35.960 --> 0:23:38.320
<v Speaker 1>pathway would have to take in order. It's amazing to

0:23:38.400 --> 0:23:42.359
<v Speaker 1>me that that little could make that difference, that big

0:23:42.359 --> 0:23:46.240
<v Speaker 1>of a difference. Well, it's just cumulative, right, And what

0:23:46.359 --> 0:23:47.800
<v Speaker 1>I was about to say a second ago, it's just

0:23:48.119 --> 0:23:51.520
<v Speaker 1>it's crazy. This is how people are making money. I mean,

0:23:51.640 --> 0:23:53.800
<v Speaker 1>and I think originally a stock market, I think like

0:23:53.960 --> 0:23:56.720
<v Speaker 1>you're investing in a business that you expect to succeed,

0:23:57.359 --> 0:23:59.840
<v Speaker 1>But at this point you're just you're investing in a

0:24:00.000 --> 0:24:03.359
<v Speaker 1>business that you predict will increase in the you know,

0:24:03.440 --> 0:24:06.320
<v Speaker 1>the price of the stock at some amount within the

0:24:06.400 --> 0:24:13.360
<v Speaker 1>next second, right right, Yeah. Micromanaging to that extent does

0:24:13.920 --> 0:24:18.080
<v Speaker 1>fill me with a sense of dread. Hey, you know

0:24:18.240 --> 0:24:21.920
<v Speaker 1>we're so good at it now the roots? Yeah yeah, no,

0:24:22.040 --> 0:24:23.640
<v Speaker 1>no to me. To me, it feels like you're you're

0:24:23.640 --> 0:24:25.719
<v Speaker 1>putting together like like a cheat codes that you can

0:24:25.760 --> 0:24:27.399
<v Speaker 1>press a single button and go how do you can

0:24:27.880 --> 0:24:31.119
<v Speaker 1>rather than just press see here. To me, what this

0:24:31.280 --> 0:24:33.880
<v Speaker 1>tells me is that in the future, not only other

0:24:34.040 --> 0:24:38.320
<v Speaker 1>robots going to get smarter and more capable at destroying us,

0:24:38.400 --> 0:24:41.200
<v Speaker 1>but they will also have all the money. Weren't we

0:24:41.240 --> 0:24:44.720
<v Speaker 1>talking about the speed of communication? Yeah, we were. That's

0:24:44.800 --> 0:24:46.879
<v Speaker 1>that's that's why the robots are the ones who are

0:24:46.880 --> 0:24:49.600
<v Speaker 1>really good. Well, how crazy will this get? I mean,

0:24:50.320 --> 0:24:53.520
<v Speaker 1>so again, if we're not talking about speed, which we

0:24:53.800 --> 0:24:56.040
<v Speaker 1>pretty much know the upper limit there, but what's the

0:24:56.119 --> 0:24:59.640
<v Speaker 1>upper limit on throughput? That's a good question. And I well,

0:24:59.720 --> 0:25:01.520
<v Speaker 1>I was reading about in the research I was doing

0:25:01.680 --> 0:25:05.560
<v Speaker 1>for the episode that uh, some researchers I think it

0:25:05.680 --> 0:25:10.400
<v Speaker 1>was a Dutch Japanese partnership. Um, there were some scientists

0:25:10.440 --> 0:25:14.040
<v Speaker 1>who put together a twelve core optical fiber that could

0:25:14.119 --> 0:25:19.480
<v Speaker 1>deliver one pet a bit per second. That I understand

0:25:19.520 --> 0:25:22.440
<v Speaker 1>that number. That's great. Peat a bit, well, it's a

0:25:22.840 --> 0:25:26.120
<v Speaker 1>it's what is it goes kill a bit, mega bit, big,

0:25:26.200 --> 0:25:29.359
<v Speaker 1>a bit, ter a bit, pet a bit then up

0:25:29.400 --> 0:25:32.520
<v Speaker 1>to xo bit. Yeah, and so this thing could deliver

0:25:33.359 --> 0:25:36.359
<v Speaker 1>it could carry a pet a bit of information across

0:25:36.440 --> 0:25:39.280
<v Speaker 1>I think it was something like fifty kilometers uh in

0:25:39.440 --> 0:25:45.280
<v Speaker 1>one second. Yeah, that's a lot. That's just that, like

0:25:45.440 --> 0:25:49.160
<v Speaker 1>you could transmit the entire Internet back and forth between

0:25:49.280 --> 0:25:52.160
<v Speaker 1>some buildings and I don't know, like five minutes. Essentially

0:25:52.240 --> 0:25:54.400
<v Speaker 1>you could do the Library of Congress in a couple

0:25:54.480 --> 0:25:57.159
<v Speaker 1>of seconds. Yeah, like the entire everything in the Library

0:25:57.160 --> 0:26:01.080
<v Speaker 1>of Congress in a couple of seconds. Yeah, that's that's impressive.

0:26:01.200 --> 0:26:04.000
<v Speaker 1>I mean and again again yeah, we kind of think

0:26:04.080 --> 0:26:07.000
<v Speaker 1>like what would you even use that for? And in

0:26:07.080 --> 0:26:09.240
<v Speaker 1>the future we might we might have answers for that,

0:26:09.359 --> 0:26:13.240
<v Speaker 1>like holograms, right, well, no, exactly. The point I wanted

0:26:13.280 --> 0:26:15.520
<v Speaker 1>to make is we'll find a way. I mean, if

0:26:15.560 --> 0:26:17.760
<v Speaker 1>there's a free launch, somebody's gonna eat it. Yeah, it'll

0:26:17.800 --> 0:26:19.840
<v Speaker 1>be it'll be the first person Shooters of the future

0:26:19.880 --> 0:26:22.359
<v Speaker 1>will be reliant on that. Anyone who does not have

0:26:22.560 --> 0:26:25.400
<v Speaker 1>that pet a bit per second, So sad my Halo

0:26:25.480 --> 0:26:28.119
<v Speaker 1>game is only going to get worse. It's great, like

0:26:28.240 --> 0:26:30.680
<v Speaker 1>by the time, hey, I'm still entering my character's name

0:26:30.800 --> 0:26:33.920
<v Speaker 1>on the screen and you've already kill me fifteen times. Well,

0:26:34.320 --> 0:26:36.240
<v Speaker 1>that's a good discussion. And you know what, I think

0:26:36.400 --> 0:26:39.000
<v Speaker 1>that there's another part of this discussion we need to have,

0:26:39.240 --> 0:26:43.439
<v Speaker 1>which is on Earth speed. We we've kind of cracked

0:26:43.480 --> 0:26:45.400
<v Speaker 1>that nut. I mean, we've got we've got it fast

0:26:45.520 --> 0:26:50.560
<v Speaker 1>enough where the delays in communication are fairly small. I

0:26:50.600 --> 0:26:54.560
<v Speaker 1>mean even if you're for most purposes, they're not speed

0:26:54.720 --> 0:26:58.080
<v Speaker 1>based really like we've been saying they're they're bandwidth based, right, So,

0:26:59.040 --> 0:27:02.480
<v Speaker 1>but there is there is something to say about speed obstacles,

0:27:02.560 --> 0:27:05.320
<v Speaker 1>and that's when we start talking about getting off this

0:27:05.480 --> 0:27:08.400
<v Speaker 1>planet and going somewhere else and then communicating back home.

0:27:08.880 --> 0:27:10.560
<v Speaker 1>So in our next episode, I think we're going to

0:27:10.640 --> 0:27:13.960
<v Speaker 1>focus on that. Uh. In the meantime, guys out there

0:27:14.000 --> 0:27:16.399
<v Speaker 1>who are listening, I would highly recommend you get in

0:27:16.480 --> 0:27:18.800
<v Speaker 1>touch with us, let us know what you think. Let's

0:27:18.840 --> 0:27:20.760
<v Speaker 1>know if you have any topics you think we should

0:27:20.800 --> 0:27:23.760
<v Speaker 1>tackle in future episodes of Forward Thinking, you can get

0:27:23.800 --> 0:27:25.879
<v Speaker 1>in touch with us with our email address. That's f

0:27:26.119 --> 0:27:28.920
<v Speaker 1>w Thinking at Discovery dot com, or you can go

0:27:29.000 --> 0:27:31.840
<v Speaker 1>to f W thinking dot com and check out all

0:27:31.840 --> 0:27:34.000
<v Speaker 1>the videos, the blog posts, you can look at the

0:27:34.040 --> 0:27:37.080
<v Speaker 1>social media stuff we've got there. Come and join the conversation,

0:27:37.119 --> 0:27:39.080
<v Speaker 1>be part of it. We really look forward to speaking

0:27:39.119 --> 0:27:40.720
<v Speaker 1>with you guys, and we will talk to you again

0:27:40.840 --> 0:27:46.720
<v Speaker 1>really soon. For more on this topic and the future

0:27:46.760 --> 0:28:00.080
<v Speaker 1>of technology, visit forward thinking dot com. Brought to you

0:28:00.200 --> 0:28:02.400
<v Speaker 1>by Toyota Let's Go Places