WEBVTT - What's Up With DARPA?

0:00:00.160 --> 0:00:07.080
<v Speaker 1>Brought to you by Toyota. Let's go places. Welcome to

0:00:07.280 --> 0:00:14.760
<v Speaker 1>Forward Thinking. Hey there, and welcome to Forward Thinking, the

0:00:14.920 --> 0:00:17.680
<v Speaker 1>podcast that looks at the future and says, but there's

0:00:17.680 --> 0:00:21.360
<v Speaker 1>no danger. It's a professional career. I'm Jonathan Strickland, I'm Lauren,

0:00:21.960 --> 0:00:24.000
<v Speaker 1>and I'm Joe McCormick. And today we're going to be

0:00:24.040 --> 0:00:28.159
<v Speaker 1>dealing with another listener request topic. This is awesome. We

0:00:28.280 --> 0:00:31.440
<v Speaker 1>love doing these and we love that you guys are listening.

0:00:31.840 --> 0:00:36.520
<v Speaker 1>So keep keep listening and keep requesting. Ah yeah, Joe,

0:00:36.600 --> 0:00:39.040
<v Speaker 1>do you want to read it for sure? Well? Our listener,

0:00:39.120 --> 0:00:42.080
<v Speaker 1>Nate wrote in via our email address, w thinking at

0:00:42.120 --> 0:00:45.040
<v Speaker 1>how stuff works dot Com? Say it again, f W

0:00:45.120 --> 0:00:47.080
<v Speaker 1>thinking at how stuff works dot Com. Wait are you

0:00:47.080 --> 0:00:50.240
<v Speaker 1>sure it wasn't f X thinking. No, it's f W

0:00:50.640 --> 0:00:54.040
<v Speaker 1>thinking at how stuff works dot Com. That sounds it's

0:00:54.080 --> 0:00:57.640
<v Speaker 1>just music to my years. Okay, Nate wrote in, saying

0:00:58.160 --> 0:01:01.400
<v Speaker 1>good show on the five G topic. Thank you, Nate, uh,

0:01:01.480 --> 0:01:04.240
<v Speaker 1>he said, thanks for making podcasts that are technical nature

0:01:04.240 --> 0:01:07.360
<v Speaker 1>but not so full of techno jargon that I can't

0:01:07.480 --> 0:01:11.720
<v Speaker 1>understand it possible. Show topic DARPA, the future of the

0:01:11.720 --> 0:01:15.279
<v Speaker 1>world's most advanced military in the world speculated about the future,

0:01:15.440 --> 0:01:18.560
<v Speaker 1>or review some of the groundbreaking ideas inventions that have

0:01:18.640 --> 0:01:22.000
<v Speaker 1>come out of DARPA. Thanks much, Well, thank you, Nate,

0:01:22.080 --> 0:01:25.880
<v Speaker 1>because we do talk about DARPA an awful lot on

0:01:26.040 --> 0:01:31.959
<v Speaker 1>this show. DARPA is responsible for so many technicals. Well,

0:01:32.160 --> 0:01:35.880
<v Speaker 1>it's not because we love DARPA. It's just because you

0:01:35.920 --> 0:01:39.680
<v Speaker 1>trace the money back when you're talking about the technology,

0:01:40.040 --> 0:01:44.120
<v Speaker 1>and somewhere along the line you'll find DARPA. Yequently a

0:01:44.160 --> 0:01:47.040
<v Speaker 1>couple of guys in dark suits and sunglasses with a

0:01:47.040 --> 0:01:50.480
<v Speaker 1>briefcase and saying just keep going. But it all sounds

0:01:50.560 --> 0:01:56.680
<v Speaker 1>so silly slash sinister and a lot of sists. But anyway,

0:01:56.720 --> 0:01:59.920
<v Speaker 1>what is DARPA. Let's go back and look at DARPA

0:02:00.080 --> 0:02:04.400
<v Speaker 1>as an organization and figure out why so many technological

0:02:04.600 --> 0:02:10.680
<v Speaker 1>historical roads lead to this strange military shadow organizations or

0:02:10.720 --> 0:02:14.400
<v Speaker 1>have led out from there. Well, let's start by saying,

0:02:14.800 --> 0:02:18.079
<v Speaker 1>because we love saying it the even though no one

0:02:18.120 --> 0:02:20.600
<v Speaker 1>ever calls DARPA by its full name, it is the

0:02:20.639 --> 0:02:24.639
<v Speaker 1>Defense Advanced Research Projects Agency. Yes, and uh, well, let's

0:02:24.680 --> 0:02:27.959
<v Speaker 1>also say that as shadowy government organizations go, this is

0:02:28.000 --> 0:02:31.639
<v Speaker 1>a really forward facing one. Yeah. Yeah, they put their

0:02:32.040 --> 0:02:34.600
<v Speaker 1>like their press releases and their call for proposals on

0:02:34.600 --> 0:02:37.080
<v Speaker 1>the Internet. Yeah, they've worked with a lot of people

0:02:37.080 --> 0:02:40.680
<v Speaker 1>who went on to work for other massive companies like Google.

0:02:41.560 --> 0:02:43.440
<v Speaker 1>But we're getting hut of ourselves. So this is the

0:02:43.440 --> 0:02:47.359
<v Speaker 1>research and development arm of the US military, specifically part

0:02:47.360 --> 0:02:49.799
<v Speaker 1>of the Department of Defense. Well that sounds scary, Well

0:02:49.840 --> 0:02:53.160
<v Speaker 1>it's it's not. Kind of is it can be. I

0:02:53.160 --> 0:02:56.160
<v Speaker 1>mean some of the because a lot of the technology

0:02:56.200 --> 0:03:00.880
<v Speaker 1>they're looking into our specifically for military applications, it makes sense.

0:03:00.880 --> 0:03:03.320
<v Speaker 1>It's a it's part of the Department of Defense. It's

0:03:03.400 --> 0:03:09.360
<v Speaker 1>very important that uh technology play a role in military applications. Sure,

0:03:09.520 --> 0:03:11.760
<v Speaker 1>but so much of the technology that we're talking about

0:03:11.840 --> 0:03:14.720
<v Speaker 1>that where those roads lead back to DARPA has nothing

0:03:14.760 --> 0:03:17.119
<v Speaker 1>to do with weapons in the end. Yeah, it may

0:03:17.160 --> 0:03:19.960
<v Speaker 1>be that it's in lots of other ways, um supporting

0:03:20.240 --> 0:03:25.720
<v Speaker 1>military roles and ends up in filtering down into civilian

0:03:25.760 --> 0:03:28.600
<v Speaker 1>technology that we all stand to benefit from. So it's

0:03:28.600 --> 0:03:32.600
<v Speaker 1>not like this is all uh super secret ray guns

0:03:32.919 --> 0:03:35.920
<v Speaker 1>and stuff like that and that that's the only thing

0:03:35.960 --> 0:03:38.680
<v Speaker 1>they work in. This is all sorts of technology that

0:03:38.720 --> 0:03:41.800
<v Speaker 1>could support the military in multiple ways and often ends

0:03:41.880 --> 0:03:46.080
<v Speaker 1>up becoming part of other types of tech right, because

0:03:46.280 --> 0:03:48.840
<v Speaker 1>I would argue that the that the really key word

0:03:49.600 --> 0:03:54.240
<v Speaker 1>in the DARPA acronym is not defense, it's rather advanced.

0:03:54.640 --> 0:03:57.120
<v Speaker 1>Part part of the agency's mission statement is to go

0:03:57.240 --> 0:04:01.440
<v Speaker 1>after these high risk, high reward research and development projects

0:04:01.480 --> 0:04:05.600
<v Speaker 1>as often they're pushing four main areas of strategy, and

0:04:05.640 --> 0:04:12.080
<v Speaker 1>those are rethinking complex military systems to being not just

0:04:12.280 --> 0:04:16.680
<v Speaker 1>reactive but proactive about the speed with which information technology

0:04:16.760 --> 0:04:23.000
<v Speaker 1>is changing these days. Uh three, harnessing biotechnology, oh boy,

0:04:23.080 --> 0:04:25.320
<v Speaker 1>and four is missing, and I forgot to write the

0:04:25.360 --> 0:04:29.200
<v Speaker 1>fourth one down and the Know such a good podcast.

0:04:29.279 --> 0:04:31.080
<v Speaker 1>And the fourth one is on a need to know

0:04:31.160 --> 0:04:36.520
<v Speaker 1>basic three, which is putting backpacks on beatles and getting

0:04:36.520 --> 0:04:39.120
<v Speaker 1>them fly around the room where you want. That's what

0:04:39.279 --> 0:04:41.200
<v Speaker 1>let's hold for a second to find the fourth one

0:04:42.000 --> 0:04:44.520
<v Speaker 1>and four. I'm going to quote this one because it's

0:04:44.520 --> 0:04:47.960
<v Speaker 1>a little bit less uh fourth, right, than than the

0:04:48.000 --> 0:04:56.000
<v Speaker 1>rest of them. Expanding the technological frontier. And also we

0:04:56.000 --> 0:04:59.279
<v Speaker 1>should point out that DARPA is not dark as nine

0:04:59.360 --> 0:05:04.960
<v Speaker 1>organization that has an enormous secret underground scientific laboratory. No.

0:05:05.080 --> 0:05:07.760
<v Speaker 1>In a lot of ways, DARPA is money. Yeah, DARPA

0:05:07.960 --> 0:05:11.040
<v Speaker 1>is I think of it kind of like um Like

0:05:11.560 --> 0:05:14.000
<v Speaker 1>they're almost like a consulting firm for the government in

0:05:14.040 --> 0:05:17.960
<v Speaker 1>a way, Like they put out a request for proposal saying,

0:05:18.279 --> 0:05:21.600
<v Speaker 1>here's the thing that we want done. We have this

0:05:21.680 --> 0:05:24.120
<v Speaker 1>is our goal, we need to have this thing happen,

0:05:24.600 --> 0:05:26.680
<v Speaker 1>and then they put that request for a proposal out

0:05:26.720 --> 0:05:29.800
<v Speaker 1>and they wait for the various organizations, usually things like

0:05:29.920 --> 0:05:33.400
<v Speaker 1>universities and research centers to respond to that and say

0:05:33.680 --> 0:05:36.680
<v Speaker 1>we're going to attempt to do this thing that you

0:05:36.760 --> 0:05:39.960
<v Speaker 1>have put a request out for, and then it goes

0:05:40.040 --> 0:05:43.000
<v Speaker 1>from there and it all depends upon the actual technology.

0:05:43.040 --> 0:05:45.800
<v Speaker 1>You know. Sometimes we're talking about massive companies like Boeing

0:05:46.800 --> 0:05:51.760
<v Speaker 1>being involved. Sometimes we're talking about labs. Yeah, there, there's

0:05:51.839 --> 0:05:55.320
<v Speaker 1>um plenty. Like Stanford has had a long association with

0:05:55.400 --> 0:05:59.640
<v Speaker 1>doing some DARPA projects, particularly in the robotics field. So uh,

0:06:00.520 --> 0:06:04.800
<v Speaker 1>don't think of DARPA as those secret labs. These are

0:06:04.800 --> 0:06:08.240
<v Speaker 1>the guys who fund the secret labs. Were not the

0:06:08.279 --> 0:06:14.599
<v Speaker 1>agents of Shield. No there there, that's that's fair. That's fair.

0:06:14.640 --> 0:06:17.359
<v Speaker 1>So yeah, like we said before, it is part of

0:06:17.360 --> 0:06:20.560
<v Speaker 1>the Department of Defense, huh. And the current director is

0:06:20.720 --> 0:06:25.160
<v Speaker 1>a woman named dr Addati Propaka who came up through

0:06:25.240 --> 0:06:29.200
<v Speaker 1>DARPA's offices from being a program manager in six to

0:06:29.720 --> 0:06:32.600
<v Speaker 1>leading a whole bunch of semi conductor programs to being

0:06:32.640 --> 0:06:37.640
<v Speaker 1>the founding director of their Microelectronics Technology Office. So I'm

0:06:37.680 --> 0:06:40.480
<v Speaker 1>not saying that she oversaw nano box, but she probably

0:06:40.800 --> 0:06:43.560
<v Speaker 1>oversaw some nano box. And to be fair, you could

0:06:43.560 --> 0:06:45.719
<v Speaker 1>be overseeing nano bots and never even know it because

0:06:45.760 --> 0:06:48.080
<v Speaker 1>that's how small they are, right, you can kind of

0:06:48.120 --> 0:06:51.520
<v Speaker 1>only oversee them. Yeah, you can't really undersee. No, you

0:06:51.520 --> 0:06:53.560
<v Speaker 1>can't really. I mean have you ever tried to get

0:06:53.600 --> 0:06:56.480
<v Speaker 1>under a nano bot? It is like impossible. So as

0:06:57.480 --> 0:07:01.960
<v Speaker 1>DARPA had a two point nine billion dollar budget, they

0:07:01.960 --> 0:07:06.960
<v Speaker 1>employ only two hundred nineteen like official full time government employees.

0:07:07.120 --> 0:07:11.000
<v Speaker 1>Salaries must be on though and world two point nine billion, right,

0:07:11.320 --> 0:07:14.720
<v Speaker 1>and they but they oversee two hundred and fifty programs

0:07:15.000 --> 0:07:18.960
<v Speaker 1>and they have some two thousand collaborations with universities, private companies,

0:07:19.000 --> 0:07:22.880
<v Speaker 1>and other governmental entities. Right. Yeah, So this is uh,

0:07:22.960 --> 0:07:25.200
<v Speaker 1>I mean, this is a big deal where we're having

0:07:25.240 --> 0:07:27.520
<v Speaker 1>a lot of fun discussing this. But you know, it's

0:07:27.560 --> 0:07:28.960
<v Speaker 1>kind of because it has a little bit of the

0:07:29.000 --> 0:07:34.120
<v Speaker 1>cloak and dagger kind of reputation and also mad science reputation,

0:07:34.400 --> 0:07:36.640
<v Speaker 1>So those lend themselves to that. But when I'm sure

0:07:36.640 --> 0:07:38.280
<v Speaker 1>the stuff they don't want you to know, kids could

0:07:38.280 --> 0:07:40.800
<v Speaker 1>come in here and talk a big game about various

0:07:40.960 --> 0:07:44.280
<v Speaker 1>DARPA alternatives. Sure, I'm sure we could bring them in

0:07:44.360 --> 0:07:46.880
<v Speaker 1>for that. But the cool thing to me is that

0:07:47.440 --> 0:07:50.680
<v Speaker 1>this is also an organization that has been responsible in

0:07:50.800 --> 0:07:57.520
<v Speaker 1>a very direct way for incredible leaps in technological capabilities

0:07:57.720 --> 0:08:02.600
<v Speaker 1>in various fields. Jonathan, Yeah, tell me the story of DARPA. Well,

0:08:02.600 --> 0:08:05.520
<v Speaker 1>it wasn't always DARPA, for one thing, that's true. It

0:08:05.680 --> 0:08:11.160
<v Speaker 1>was ARFA ARCA so close of course. Yeah, they only

0:08:11.240 --> 0:08:16.400
<v Speaker 1>dropped the letter. Actually they gained a letter afterward. But yeah,

0:08:16.400 --> 0:08:20.280
<v Speaker 1>it was originally ARPA, just the Advanced Research Projects Agency.

0:08:20.600 --> 0:08:25.720
<v Speaker 1>And yeah, there was a specific event in history that

0:08:26.320 --> 0:08:31.000
<v Speaker 1>that prodded the United States and de forming this organization. Right, Well,

0:08:31.040 --> 0:08:36.400
<v Speaker 1>it was formed in oh less than a year after

0:08:36.520 --> 0:08:41.280
<v Speaker 1>the uss are launched Sputnik. Yeah, the thing what beeped,

0:08:41.640 --> 0:08:45.400
<v Speaker 1>as my my old colleague Chris Palette would say, yeah, well,

0:08:45.400 --> 0:08:48.079
<v Speaker 1>of course, put Nick was the first artificial satellite ever

0:08:48.120 --> 0:08:51.000
<v Speaker 1>put into orbit by humans. Right, It wasn't the fact

0:08:51.080 --> 0:08:55.280
<v Speaker 1>that it was beeping that really disturbed anyone. It was

0:08:55.320 --> 0:08:58.000
<v Speaker 1>the fact that it was beeping and anyone in the

0:08:58.040 --> 0:09:00.320
<v Speaker 1>world contune and in here it and further that they

0:09:00.360 --> 0:09:03.200
<v Speaker 1>had launched it into space. Yeah. So if you are

0:09:03.240 --> 0:09:06.240
<v Speaker 1>the United States and the Soviet Union has just put

0:09:06.480 --> 0:09:10.280
<v Speaker 1>something into space, and you are part of the Department

0:09:10.320 --> 0:09:14.160
<v Speaker 1>of Defense, you're going to be thinking some pretty serious thoughts.

0:09:14.240 --> 0:09:16.600
<v Speaker 1>One is that if the Soviet Union can put something

0:09:16.600 --> 0:09:20.199
<v Speaker 1>into space, it can potentially put something here in the US,

0:09:20.240 --> 0:09:22.760
<v Speaker 1>all the way from the Soviet Union. Yes, not into

0:09:22.800 --> 0:09:25.520
<v Speaker 1>space over the US, but just into the US. Yes,

0:09:25.600 --> 0:09:30.000
<v Speaker 1>so essentially intercontinental ballistic missile kind of thing. Secondly, if

0:09:30.000 --> 0:09:32.559
<v Speaker 1>they can put something into space, sure, right now, all

0:09:32.600 --> 0:09:34.880
<v Speaker 1>it's doing is sending out a signal that you could

0:09:34.880 --> 0:09:36.880
<v Speaker 1>pick up if you're a you have a ham radio

0:09:37.000 --> 0:09:39.000
<v Speaker 1>or something, which is you know, kind of interesting in

0:09:39.600 --> 0:09:44.160
<v Speaker 1>neat but potentially further down the line, yeah, it might

0:09:44.200 --> 0:09:46.439
<v Speaker 1>be able to do other stuff than just beep. It

0:09:46.520 --> 0:09:48.840
<v Speaker 1>might be able to take pictures, it might be able

0:09:48.880 --> 0:09:51.959
<v Speaker 1>to take video or stream video. I mean, obviously this

0:09:52.040 --> 0:09:56.440
<v Speaker 1>is talking further years in advance, but the potential was there,

0:09:56.440 --> 0:09:59.959
<v Speaker 1>and so clearly there was a need for the United

0:10:00.120 --> 0:10:03.160
<v Speaker 1>States to get on the ball as far as technology

0:10:03.240 --> 0:10:05.800
<v Speaker 1>is concerned. And so that's where the government said, all right,

0:10:05.800 --> 0:10:09.319
<v Speaker 1>we're going to we're going to found an organization whose

0:10:09.360 --> 0:10:15.360
<v Speaker 1>purpose is to develop science and technology specifically for defense. Yeah. Yeah,

0:10:15.559 --> 0:10:18.720
<v Speaker 1>so that was the that was the reason for ARPA

0:10:18.760 --> 0:10:21.200
<v Speaker 1>to come into being. And in fact, in the earliest

0:10:21.280 --> 0:10:24.760
<v Speaker 1>days of the United States Space Program, ARPA oversaw a

0:10:24.760 --> 0:10:29.240
<v Speaker 1>lot of those operations that would eventually transfer over to NASA,

0:10:29.320 --> 0:10:32.200
<v Speaker 1>but originally it was ARPA that was overseeing those early

0:10:32.679 --> 0:10:36.960
<v Speaker 1>uh space programs. Yeah, a lot of the projects that

0:10:36.960 --> 0:10:39.960
<v Speaker 1>they were that they were working on during their early

0:10:40.200 --> 0:10:44.320
<v Speaker 1>days would wind up being really important to the state

0:10:44.360 --> 0:10:47.760
<v Speaker 1>of technology as we know it today. For for example,

0:10:47.880 --> 0:10:51.640
<v Speaker 1>ARPA hired on J. C. R. Lick Lighter as their

0:10:51.720 --> 0:10:56.120
<v Speaker 1>director of the Information Processing Techniques Office. And if you

0:10:56.160 --> 0:10:58.840
<v Speaker 1>haven't heard about this dude before, his vision of computers

0:10:58.880 --> 0:11:04.480
<v Speaker 1>as communication asian devices, not not just information information processing devices,

0:11:04.480 --> 0:11:07.360
<v Speaker 1>which they were generally thought of back in that time.

0:11:08.640 --> 0:11:11.960
<v Speaker 1>His vision is a big part of why we have

0:11:12.440 --> 0:11:15.960
<v Speaker 1>computers right now, right, I mean the kind of computers

0:11:16.040 --> 0:11:18.439
<v Speaker 1>that we talk into and you know, can play but

0:11:18.520 --> 0:11:20.400
<v Speaker 1>jeweled on and all of that kind of right, because

0:11:20.440 --> 0:11:25.000
<v Speaker 1>before that you're talking about massive machines that were self contained, right.

0:11:25.440 --> 0:11:29.640
<v Speaker 1>They were. Often they were purposed for specific applications and

0:11:29.640 --> 0:11:34.080
<v Speaker 1>couldn't do very much outside of those. So computers were useful,

0:11:34.200 --> 0:11:36.400
<v Speaker 1>but they were also very limited, and it was his

0:11:36.520 --> 0:11:41.880
<v Speaker 1>vision that really helped push that beyond those early limitations. Yeah,

0:11:41.920 --> 0:11:44.800
<v Speaker 1>so they hired him on in the nineteen sixties and

0:11:45.040 --> 0:11:48.480
<v Speaker 1>that led to a whole bunch of developments, including well,

0:11:48.520 --> 0:11:51.760
<v Speaker 1>first the Arbannett so Arbet. Often people will call that

0:11:51.840 --> 0:11:54.720
<v Speaker 1>like the predecessor to the Internet, which that's that's fair.

0:11:54.760 --> 0:11:58.680
<v Speaker 1>It was the first computer network that was a wide

0:11:58.720 --> 0:12:03.400
<v Speaker 1>scale computer network nected uh initially just three computers, although

0:12:03.440 --> 0:12:06.360
<v Speaker 1>more would join on later, and they were separated by

0:12:06.600 --> 0:12:10.360
<v Speaker 1>vast regions of geography, so it wasn't like three computers

0:12:10.360 --> 0:12:12.160
<v Speaker 1>that were saying next to each other that then we're

0:12:12.200 --> 0:12:17.559
<v Speaker 1>wired together there. This was a true accomplishment, and it's

0:12:17.600 --> 0:12:21.679
<v Speaker 1>hard to explain to someone who now can plug into

0:12:21.760 --> 0:12:24.800
<v Speaker 1>the Internet wirelessly pretty much wherever they happened to be

0:12:25.000 --> 0:12:27.880
<v Speaker 1>how hard this was at the time because they had

0:12:27.920 --> 0:12:31.240
<v Speaker 1>to build the infrastructure, as in the actual physical infrastructure,

0:12:31.280 --> 0:12:34.360
<v Speaker 1>the things that would plug into the various machines. They

0:12:34.400 --> 0:12:37.200
<v Speaker 1>also had to create a means for these machines to

0:12:37.240 --> 0:12:40.560
<v Speaker 1>communicate with each other, because the other issue about computers

0:12:40.600 --> 0:12:42.920
<v Speaker 1>back in those days is that if you had two

0:12:42.960 --> 0:12:47.480
<v Speaker 1>different computers, they essentially spoke two different languages. So you

0:12:47.520 --> 0:12:50.439
<v Speaker 1>had to create a common form of communication for these

0:12:50.440 --> 0:12:53.840
<v Speaker 1>computers to be able to work together in any meaningful way.

0:12:54.240 --> 0:12:58.160
<v Speaker 1>And that became the purpose of several of the researchers

0:12:58.160 --> 0:13:02.040
<v Speaker 1>there to develop the protocols that would allow information to

0:13:02.120 --> 0:13:05.720
<v Speaker 1>be passed across this network and to be accepted and

0:13:05.800 --> 0:13:10.760
<v Speaker 1>interpreted properly on either side. So this would end up

0:13:10.800 --> 0:13:14.319
<v Speaker 1>leading into the technologies that we now use in the Internet.

0:13:14.400 --> 0:13:18.640
<v Speaker 1>A lot of them have evolved into that role. So, uh,

0:13:18.720 --> 0:13:20.679
<v Speaker 1>while the ARPA net you might argue, was just a

0:13:20.679 --> 0:13:24.679
<v Speaker 1>computer network, the Internet was a network of networks which

0:13:25.280 --> 0:13:27.360
<v Speaker 1>incorporate lots of stuff you need. You need some networks

0:13:27.360 --> 0:13:30.600
<v Speaker 1>first in order to really get off the ground, exactly. So,

0:13:30.600 --> 0:13:33.920
<v Speaker 1>so we can thank DARPA for the fact that the

0:13:33.920 --> 0:13:36.800
<v Speaker 1>Internet is a thing. I mean, it's again, a lot

0:13:36.800 --> 0:13:40.600
<v Speaker 1>of the technologies will talk about you could argue would

0:13:40.600 --> 0:13:45.720
<v Speaker 1>eventually come to being eventually anyway, but the keyword there's eventually.

0:13:46.000 --> 0:13:49.520
<v Speaker 1>The reason they happened when they happened is largely because

0:13:49.600 --> 0:13:52.840
<v Speaker 1>DARPA was funding the research that made it possible. Sort

0:13:52.880 --> 0:13:56.080
<v Speaker 1>of side question, has anybody ever put a date on

0:13:56.200 --> 0:14:00.040
<v Speaker 1>the time that the Internet became the Internet? Yeah, I

0:14:01.080 --> 0:14:05.559
<v Speaker 1>don't have the date in front of me, but essentially, yes,

0:14:05.679 --> 0:14:08.600
<v Speaker 1>there is a record. There is a record of that thing. Yeah,

0:14:08.640 --> 0:14:10.640
<v Speaker 1>because if you're talking about the Internet. One other things

0:14:10.640 --> 0:14:12.840
<v Speaker 1>to remember, of course, and I mean, I'm sure our

0:14:12.880 --> 0:14:15.000
<v Speaker 1>listeners are really aware of this, that the Internet and

0:14:15.040 --> 0:14:17.080
<v Speaker 1>the Worldwide Web are two different things. Right. The World

0:14:17.080 --> 0:14:19.400
<v Speaker 1>Wide Web exists on top of the Internet, So you're

0:14:19.400 --> 0:14:22.480
<v Speaker 1>talking about the Internet probably wasn't really the Internet until

0:14:22.520 --> 0:14:26.160
<v Speaker 1>there was an x files fan site, so so in

0:14:26.200 --> 0:14:27.760
<v Speaker 1>other words, you had to wait for the x files.

0:14:27.840 --> 0:14:29.560
<v Speaker 1>So the Web had been around for a little bit,

0:14:29.880 --> 0:14:33.600
<v Speaker 1>but no one cared, right, it didn't have any x files. Really,

0:14:33.680 --> 0:14:37.680
<v Speaker 1>I would argue that it didn't really become the Internet

0:14:37.760 --> 0:14:42.880
<v Speaker 1>until because that's when cats were invented, and that would

0:14:42.920 --> 0:14:47.280
<v Speaker 1>be when when the Internet really tell I think so,

0:14:47.400 --> 0:14:51.520
<v Speaker 1>and finally made all those hieroglyphs make sense. That was retroactively.

0:14:51.560 --> 0:14:53.720
<v Speaker 1>It was rhet conning is what we call that. Anyway,

0:14:54.360 --> 0:14:57.320
<v Speaker 1>It's not the only technology that DARPA had a hand

0:14:57.400 --> 0:15:01.520
<v Speaker 1>in developing. It also was largely responsible for the funding

0:15:01.560 --> 0:15:05.440
<v Speaker 1>of research that led to the Global Positioning System or GPS,

0:15:06.440 --> 0:15:09.560
<v Speaker 1>another technology that got a big boost from spotne going

0:15:09.600 --> 0:15:13.600
<v Speaker 1>into space absolutely so. The Navy first tested a system

0:15:13.640 --> 0:15:17.280
<v Speaker 1>called Transit back in nineteen sixty They used five orbiting

0:15:17.280 --> 0:15:21.200
<v Speaker 1>satellites that would allow ships to fix their exact position UH.

0:15:21.200 --> 0:15:25.560
<v Speaker 1>A successor to that was called Timation in nineteen sixty seven.

0:15:26.120 --> 0:15:29.479
<v Speaker 1>The interesting thing was that the military used the satellites

0:15:29.520 --> 0:15:35.160
<v Speaker 1>for a very long time and civilians only got partial

0:15:35.200 --> 0:15:40.040
<v Speaker 1>access to this data. It was specifically degraded on purpose

0:15:40.560 --> 0:15:43.160
<v Speaker 1>so that you would not get an accurate reading of

0:15:43.200 --> 0:15:46.360
<v Speaker 1>your position because it was considered too valuable for military

0:15:46.440 --> 0:15:50.440
<v Speaker 1>use to allow civilians to really get that information, right.

0:15:50.480 --> 0:15:53.360
<v Speaker 1>That's why that's why some of the first GPS systems

0:15:53.440 --> 0:15:56.440
<v Speaker 1>were so crappy in comparison to the ones that we

0:15:56.480 --> 0:15:59.400
<v Speaker 1>have today. It wasn't because there was something lacking in

0:15:59.440 --> 0:16:02.640
<v Speaker 1>the technolo pology. It was because it had been purposefully restricted.

0:16:02.880 --> 0:16:05.960
<v Speaker 1>It was called selective availability. And you if you look

0:16:06.000 --> 0:16:10.120
<v Speaker 1>at the there were forums that were dedicated to GPS,

0:16:10.160 --> 0:16:11.920
<v Speaker 1>Like the people who are really into this kind of

0:16:11.960 --> 0:16:14.480
<v Speaker 1>stuff less like any other technology. There were people who

0:16:14.520 --> 0:16:17.280
<v Speaker 1>really thought it was super cool, like the early adopters

0:16:18.280 --> 0:16:22.160
<v Speaker 1>radio enthusiasts. They might talk about, oh, this one has

0:16:22.680 --> 0:16:25.880
<v Speaker 1>a precision of up to five hundred feet, so you'd

0:16:25.880 --> 0:16:28.400
<v Speaker 1>be somewhere within five hundred feet of like you knew

0:16:28.440 --> 0:16:30.640
<v Speaker 1>your position was within five feet of what you were

0:16:30.640 --> 0:16:33.600
<v Speaker 1>being told. It made geo cashing a lot trickier. Yeah,

0:16:33.600 --> 0:16:37.840
<v Speaker 1>and in fact, geo cashing really took off because Bill

0:16:37.840 --> 0:16:42.080
<v Speaker 1>Clinton got rid of the policy of selected availability, and

0:16:42.160 --> 0:16:46.800
<v Speaker 1>once that was eliminated and these GPS receivers could suddenly

0:16:47.240 --> 0:16:50.360
<v Speaker 1>get much more accurate readings, people were more interested in

0:16:50.400 --> 0:16:53.240
<v Speaker 1>buying them and using them, And the the enthusiasts were

0:16:53.240 --> 0:16:55.000
<v Speaker 1>the ones who were saying, hey, why don't we use

0:16:55.080 --> 0:16:57.960
<v Speaker 1>this to have a game? And you you know, I

0:16:58.000 --> 0:17:00.440
<v Speaker 1>did a whole article on how geo cashing works where

0:17:00.440 --> 0:17:02.520
<v Speaker 1>I talked about the history of it. It actually is

0:17:02.560 --> 0:17:06.160
<v Speaker 1>really fascinating. It became this this means of hunting treasure

0:17:06.280 --> 0:17:09.760
<v Speaker 1>using these online forums. And again DARPA is largely responsible

0:17:09.760 --> 0:17:12.680
<v Speaker 1>for the research and development of that technology. Yeah. Then,

0:17:12.720 --> 0:17:15.119
<v Speaker 1>of course there are all kinds of DARPER projects that

0:17:15.160 --> 0:17:17.400
<v Speaker 1>we've talked about on the podcast before. We've talked about

0:17:17.440 --> 0:17:20.280
<v Speaker 1>the ones where they where they were trying to control

0:17:20.400 --> 0:17:23.560
<v Speaker 1>the flight of beatles and stuff with little backpacks that

0:17:23.720 --> 0:17:27.080
<v Speaker 1>they put on them. We've talked about of course they're

0:17:27.160 --> 0:17:34.520
<v Speaker 1>the DARPA contracted Boston Dynamics robots there, we'll legged walking.

0:17:34.840 --> 0:17:38.199
<v Speaker 1>We we've talked about autonomous cars. Yeah, yeah, the Grand

0:17:38.359 --> 0:17:41.600
<v Speaker 1>Challenges those were those are a really big deal with

0:17:41.680 --> 0:17:46.240
<v Speaker 1>DARPA's past, where DARPA had created these challenges for teams

0:17:46.280 --> 0:17:48.879
<v Speaker 1>to create autonomous vehicles that would have to complete a

0:17:48.920 --> 0:17:52.440
<v Speaker 1>course within a certain amount of time. Uh. And um,

0:17:52.480 --> 0:17:55.199
<v Speaker 1>the very first one, there were no winners. None of

0:17:55.200 --> 0:17:58.399
<v Speaker 1>the cars were able to complete the course successfully. The

0:17:58.440 --> 0:18:01.040
<v Speaker 1>second year they had I think five or six teams

0:18:01.080 --> 0:18:03.560
<v Speaker 1>successfully complete the course and the one that had the

0:18:03.560 --> 0:18:07.639
<v Speaker 1>lowest time one. And then they decided to make it harder.

0:18:08.400 --> 0:18:11.440
<v Speaker 1>So the original course was like a desert course, right.

0:18:11.480 --> 0:18:13.960
<v Speaker 1>It was pretty wide open space, and it was you

0:18:14.040 --> 0:18:15.520
<v Speaker 1>had to go from point A to point B, and

0:18:15.560 --> 0:18:17.639
<v Speaker 1>it did require turns and stuff. It wasn't like a

0:18:17.680 --> 0:18:23.000
<v Speaker 1>straight shot, but it wasn't having to navigate through like traffic. Uh.

0:18:23.240 --> 0:18:26.200
<v Speaker 1>They they made it tougher by setting it in a

0:18:26.359 --> 0:18:29.320
<v Speaker 1>simulated urban environment I think. I think they used essentially

0:18:29.359 --> 0:18:33.639
<v Speaker 1>in an old army base, and they set it up

0:18:33.680 --> 0:18:36.719
<v Speaker 1>as if it were a town, and they included actual

0:18:36.800 --> 0:18:40.440
<v Speaker 1>traffic in the streets, and I think even pedestrian traffic,

0:18:40.920 --> 0:18:44.320
<v Speaker 1>and the vehicles had to be able to autonomously plot

0:18:44.359 --> 0:18:47.679
<v Speaker 1>a path from a starting position to a destination. They

0:18:47.680 --> 0:18:49.679
<v Speaker 1>were not told what it was going to be beforehand,

0:18:50.200 --> 0:18:52.920
<v Speaker 1>and then the cars had to navigate through that, obeying

0:18:52.920 --> 0:18:56.480
<v Speaker 1>all traffic laws as well. So a much more difficult

0:18:56.480 --> 0:18:58.680
<v Speaker 1>task than just going from point A to point B.

0:18:59.440 --> 0:19:02.720
<v Speaker 1>And we've seen that continue to the most recent robotics challenge,

0:19:02.760 --> 0:19:05.000
<v Speaker 1>the one that's going on right now and will conclude.

0:19:05.160 --> 0:19:10.040
<v Speaker 1>We're recording this in April. In the summer, there's going

0:19:10.080 --> 0:19:13.760
<v Speaker 1>to be the Robotics challenge that requires teams to create

0:19:13.800 --> 0:19:17.000
<v Speaker 1>a robot that can get into a vehicle, drive the

0:19:17.119 --> 0:19:20.639
<v Speaker 1>vehicle to a location, get out of the vehicle, go

0:19:20.720 --> 0:19:25.400
<v Speaker 1>into said location, navigate a set upstairs, go over possibly

0:19:25.440 --> 0:19:31.040
<v Speaker 1>some rubble, breakthrough a wall, connects some wires together, operate

0:19:31.119 --> 0:19:35.680
<v Speaker 1>some control systems, and do something secret that has yet

0:19:35.720 --> 0:19:39.800
<v Speaker 1>to be revealed to the teams. And the purpose of

0:19:39.840 --> 0:19:41.639
<v Speaker 1>this is to create a robot that can respond to

0:19:41.680 --> 0:19:46.800
<v Speaker 1>emergency situations. It was specifically inspired by the Fukushima disaster.

0:19:47.800 --> 0:19:51.920
<v Speaker 1>I'm really sorry, guys, but the second that you got

0:19:51.920 --> 0:19:54.439
<v Speaker 1>to breaking through a wall, I could think of in

0:19:54.520 --> 0:19:57.840
<v Speaker 1>my head was like a like slim Ninja version of

0:19:57.880 --> 0:20:01.920
<v Speaker 1>the kool Aid Man. See, that's interesting. My first thought

0:20:02.040 --> 0:20:04.359
<v Speaker 1>was that it's it's a robot that turns into the

0:20:04.440 --> 0:20:07.720
<v Speaker 1>Incredible Hulk. That was my version of smashing through the wall.

0:20:07.760 --> 0:20:10.720
<v Speaker 1>But Cooley man, is that's good too. It would be

0:20:10.800 --> 0:20:13.320
<v Speaker 1>hilarious if it actually did get shout out oh yeah

0:20:13.400 --> 0:20:17.320
<v Speaker 1>when it does that. Um yeah. And I'm sure at

0:20:17.359 --> 0:20:19.199
<v Speaker 1>least one team is going to have to do it

0:20:19.240 --> 0:20:23.000
<v Speaker 1>that way. I really hope that someone does. Yeah. So anyway,

0:20:23.040 --> 0:20:25.919
<v Speaker 1>that's that one is going on right now, and I

0:20:26.000 --> 0:20:29.760
<v Speaker 1>look forward to following the the progress of the various

0:20:29.760 --> 0:20:32.240
<v Speaker 1>teams and kind of also, I'm very curious to find

0:20:32.240 --> 0:20:35.680
<v Speaker 1>out what the secret objective is that has yet to

0:20:35.720 --> 0:20:38.440
<v Speaker 1>be revealed, And the idea is it's supposed to test

0:20:38.480 --> 0:20:42.399
<v Speaker 1>the robot's ability to deal with um changing situations that

0:20:42.480 --> 0:20:46.800
<v Speaker 1>are difficult, if not impossible, to predict. Yeah, but of

0:20:46.840 --> 0:20:50.159
<v Speaker 1>course there are lots of new DARPA proposals going on

0:20:50.400 --> 0:20:52.800
<v Speaker 1>all the time. Yeah, and we should preface this. We're

0:20:52.800 --> 0:20:54.880
<v Speaker 1>going to be talking and some of these we will

0:20:54.880 --> 0:20:56.880
<v Speaker 1>not be covering in depth. And the reason for that

0:20:57.600 --> 0:21:00.800
<v Speaker 1>is that the proposals are in various state ages right now.

0:21:00.840 --> 0:21:03.240
<v Speaker 1>Some of them are so early and so vague as

0:21:03.280 --> 0:21:07.200
<v Speaker 1>to be impossible to go into depth about because there's

0:21:07.240 --> 0:21:09.359
<v Speaker 1>nothing to talk about yet. Yeah, there's no science to

0:21:09.400 --> 0:21:12.440
<v Speaker 1>talk about because no one has done the science yet. Yeah,

0:21:12.480 --> 0:21:15.120
<v Speaker 1>but that's where science comes from from, no one having

0:21:15.160 --> 0:21:18.920
<v Speaker 1>done it yet exactly. So. Yeah, and this, this first

0:21:18.920 --> 0:21:21.639
<v Speaker 1>one that I'm going to mention, is one of those things.

0:21:21.760 --> 0:21:26.240
<v Speaker 1>The press release for this was only put out on April,

0:21:27.119 --> 0:21:31.920
<v Speaker 1>I believe. And uh, this is for Project the Darpest,

0:21:31.960 --> 0:21:37.360
<v Speaker 1>calling and zero. They love acronyms, you guys. Oh yeah,

0:21:37.400 --> 0:21:41.560
<v Speaker 1>a whole bunch. They are metal gear solid. I've got

0:21:41.560 --> 0:21:43.879
<v Speaker 1>a feeling, hey, call back. I've got a feeling that

0:21:44.000 --> 0:21:47.679
<v Speaker 1>uh uh, that we're going to see like there's a

0:21:47.840 --> 0:21:50.600
<v Speaker 1>there's gotta be a department in DARPA that's just like,

0:21:50.800 --> 0:21:53.120
<v Speaker 1>all right, you gotta come up with a really awesome

0:21:53.560 --> 0:21:56.560
<v Speaker 1>project name that could be a cool acronyms. Just keep

0:21:56.600 --> 0:22:00.280
<v Speaker 1>on tweaking it until the acronym makes sense. Yeah, So

0:22:00.280 --> 0:22:03.320
<v Speaker 1>so end zero that's near zero power r F and

0:22:03.400 --> 0:22:08.800
<v Speaker 1>sensor operations. And this project is currently seeking proposals and

0:22:08.840 --> 0:22:13.640
<v Speaker 1>it's it's looking to develop low energy, wireless sensors that

0:22:13.680 --> 0:22:17.200
<v Speaker 1>can wake up and take action when a particular event

0:22:17.320 --> 0:22:21.720
<v Speaker 1>triggers them, like, for example, infrastructure damage. If a crack

0:22:22.080 --> 0:22:26.879
<v Speaker 1>appears in a dam, for example, then these these sleeping

0:22:27.160 --> 0:22:29.800
<v Speaker 1>sensors could could wake up and phone home, or if

0:22:29.840 --> 0:22:34.560
<v Speaker 1>there's a forest fire or etcetera, an earthquake or an earthquake. Yeah,

0:22:34.600 --> 0:22:37.960
<v Speaker 1>that makes sense to me actually, because one thing we've

0:22:38.000 --> 0:22:41.520
<v Speaker 1>talked about before is imagine we're going into the world

0:22:41.520 --> 0:22:44.080
<v Speaker 1>of the Internet of things, and one of the primary

0:22:44.119 --> 0:22:47.320
<v Speaker 1>components of the Internet of things as we've imagined it

0:22:47.520 --> 0:22:51.840
<v Speaker 1>at least, is sensors, right, you know, ubiquitous sensors. Sensors

0:22:51.880 --> 0:22:55.119
<v Speaker 1>on everything that let you know when something's going on

0:22:55.320 --> 0:22:58.080
<v Speaker 1>that needs attention, or they give you data that you

0:22:58.119 --> 0:23:02.160
<v Speaker 1>can use somehow to to decisions or have your environment

0:23:02.280 --> 0:23:05.720
<v Speaker 1>changed for you, or whatever it may be. You're going

0:23:05.760 --> 0:23:08.399
<v Speaker 1>to have sensors everywhere, yeah, Yeah, so that you don't

0:23:08.440 --> 0:23:11.200
<v Speaker 1>have to be in a place watching a thing personally,

0:23:12.200 --> 0:23:15.880
<v Speaker 1>your your place can monitor that for you. Sure, but

0:23:17.359 --> 0:23:20.400
<v Speaker 1>you don't want those sensors to be a big power drain,

0:23:20.480 --> 0:23:22.959
<v Speaker 1>of course, and you don't want them to have just

0:23:23.000 --> 0:23:25.320
<v Speaker 1>sort of like little batteries that you'd have to replace

0:23:25.400 --> 0:23:28.400
<v Speaker 1>or recharge all the time. So this makes a lot

0:23:28.400 --> 0:23:29.919
<v Speaker 1>of sense to me if you can come up with

0:23:29.960 --> 0:23:33.720
<v Speaker 1>ways of of having sensors that are basically not draining

0:23:33.800 --> 0:23:37.200
<v Speaker 1>power or somehow inactive when they're not in use, so

0:23:37.280 --> 0:23:39.800
<v Speaker 1>essentially they can go into some form of sleep mode

0:23:40.320 --> 0:23:44.520
<v Speaker 1>and thus prolong the life of their power source. Also, uh,

0:23:44.560 --> 0:23:47.520
<v Speaker 1>it's attractive or another reason, that reason being that I

0:23:47.560 --> 0:23:50.439
<v Speaker 1>think most of us would prefer a world where the

0:23:50.520 --> 0:23:53.200
<v Speaker 1>sensors are active when they need to be and not

0:23:53.359 --> 0:23:57.760
<v Speaker 1>always monitoring everything we do all the time always, or

0:23:58.960 --> 0:24:01.239
<v Speaker 1>the sort of compliment that is that the sensors are

0:24:01.320 --> 0:24:04.280
<v Speaker 1>largely invisible. Yeah, you know, you don't want them like

0:24:04.640 --> 0:24:08.199
<v Speaker 1>activating all the time when they're not doing anything, Like

0:24:08.240 --> 0:24:10.719
<v Speaker 1>a smoke alarm that goes off every time you you

0:24:10.920 --> 0:24:13.880
<v Speaker 1>fry a piece of chicken in a pan. Sure, that's

0:24:13.880 --> 0:24:16.520
<v Speaker 1>why you out so frequently. So I mean the smoke

0:24:16.560 --> 0:24:19.960
<v Speaker 1>alarm that does that, I must point out is operating correctly.

0:24:20.280 --> 0:24:24.720
<v Speaker 1>It's your cooking, that's what we're saying. No, that's fair,

0:24:25.080 --> 0:24:29.280
<v Speaker 1>really terrible cook This podcast has actually been an elaborate intervention,

0:24:29.520 --> 0:24:37.200
<v Speaker 1>and it's led up to this point. I congratulations, guys.

0:24:37.240 --> 0:24:39.120
<v Speaker 1>I would slow clap, but I don't want to set

0:24:39.160 --> 0:24:41.320
<v Speaker 1>off the audio. But I guess it doesn't matter since

0:24:41.320 --> 0:24:44.399
<v Speaker 1>we're not really making an audio podcast. Well, you know,

0:24:44.600 --> 0:24:47.600
<v Speaker 1>I've always tried to stick with baking more than cooking,

0:24:47.640 --> 0:24:50.159
<v Speaker 1>but now this is we are just kidding, Lauren. I

0:24:50.520 --> 0:24:53.720
<v Speaker 1>must say I've seen you bring leftovers before that look delicious.

0:24:53.880 --> 0:24:56.080
<v Speaker 1>Oh well, thank you, thank you, Joe. I appreciate that

0:24:56.119 --> 0:24:59.280
<v Speaker 1>most of them are from takeout. So what else has

0:24:59.359 --> 0:25:02.240
<v Speaker 1>DARPA been up to besides making these low inner or

0:25:02.600 --> 0:25:05.040
<v Speaker 1>sending out a proposal for these low energy sensors. Well

0:25:05.080 --> 0:25:07.919
<v Speaker 1>here's another call for proposals I was reading about that

0:25:08.040 --> 0:25:12.840
<v Speaker 1>I am fascinated by because of the vagueness. Yeah, this

0:25:12.920 --> 0:25:15.400
<v Speaker 1>was one that the proposal and and it leads your

0:25:15.440 --> 0:25:18.159
<v Speaker 1>your brain down a bunch of strange directions. When you

0:25:18.160 --> 0:25:20.919
<v Speaker 1>when you told me about this one, I was so perplexed,

0:25:21.000 --> 0:25:23.320
<v Speaker 1>and honestly I still am because I haven't had a

0:25:23.400 --> 0:25:25.479
<v Speaker 1>chance to dive into it to a point where I

0:25:25.520 --> 0:25:27.199
<v Speaker 1>feel like I really have a grasp on it. So

0:25:27.240 --> 0:25:31.840
<v Speaker 1>why don't you walk me through what this is? Okay,

0:25:31.880 --> 0:25:35.960
<v Speaker 1>So this is known as BRASS and BRASS stands for

0:25:36.600 --> 0:25:41.720
<v Speaker 1>building resource adaptive software systems, And so they are currently

0:25:41.760 --> 0:25:46.119
<v Speaker 1>seeking proposals um and the idea behind this is that

0:25:46.200 --> 0:25:49.120
<v Speaker 1>they want to or at least as we understand it,

0:25:49.200 --> 0:25:53.239
<v Speaker 1>is that they want to create software or frameworks for

0:25:53.480 --> 0:26:00.320
<v Speaker 1>creating software that sort of eliminate the need for updates, right,

0:26:00.400 --> 0:26:06.040
<v Speaker 1>the costernal updates, right, that can dynamically adapt to all

0:26:06.080 --> 0:26:09.200
<v Speaker 1>the software and hardware around them. Right. So, so we're

0:26:09.240 --> 0:26:11.639
<v Speaker 1>all familiar with the need for software to update. You know,

0:26:11.720 --> 0:26:16.000
<v Speaker 1>computers are incredibly powerful, but they interface with us through

0:26:16.040 --> 0:26:19.920
<v Speaker 1>software that has very little resilience. Just think about how

0:26:20.000 --> 0:26:24.040
<v Speaker 1>easy it is to just completely break and ruin the

0:26:24.080 --> 0:26:28.640
<v Speaker 1>operational software profile of your amazing piece of hardware computer. Well,

0:26:28.800 --> 0:26:31.439
<v Speaker 1>or just the fact that, uh, let's say that you

0:26:31.560 --> 0:26:35.200
<v Speaker 1>get anyone who's ever done an operating system upgrade where

0:26:35.200 --> 0:26:38.400
<v Speaker 1>they've upgraded from one version to another and then realize

0:26:38.440 --> 0:26:42.720
<v Speaker 1>that some other programs no longer work properly. That's a problem,

0:26:42.840 --> 0:26:45.440
<v Speaker 1>and it's a problem that DARBA has identified as being

0:26:45.480 --> 0:26:51.040
<v Speaker 1>a serious issue, particularly in military applications where downtime could

0:26:51.280 --> 0:26:54.199
<v Speaker 1>put people's lives at risk. Yeah. Another side of this

0:26:54.280 --> 0:26:56.199
<v Speaker 1>is if you hear the stories about like, you know,

0:26:56.240 --> 0:26:59.439
<v Speaker 1>the missile command systems that are still running on like

0:26:59.560 --> 0:27:03.640
<v Speaker 1>Cobal all operated, you know, just these ancient software systems.

0:27:04.359 --> 0:27:07.160
<v Speaker 1>But anyway, so DARPA announced this was also this month,

0:27:07.240 --> 0:27:11.120
<v Speaker 1>so April, that it would launch a four year research

0:27:11.160 --> 0:27:14.320
<v Speaker 1>project to find out what it would take to create

0:27:14.440 --> 0:27:21.160
<v Speaker 1>software that remains robust for a hundred years without updates.

0:27:22.520 --> 0:27:26.040
<v Speaker 1>So I think they're not necessarily saying like time to

0:27:26.080 --> 0:27:29.240
<v Speaker 1>create that software. They're saying, let's do research to figure

0:27:29.280 --> 0:27:32.800
<v Speaker 1>out what it would take to create software like that. Yeah,

0:27:32.880 --> 0:27:37.240
<v Speaker 1>let's let's identify the requirements and then start to identify

0:27:37.359 --> 0:27:39.840
<v Speaker 1>how those requirements could be met. Yeah. So this is

0:27:39.880 --> 0:27:43.320
<v Speaker 1>a quote from their call for proposals, so brass quote

0:27:43.400 --> 0:27:48.880
<v Speaker 1>seeks to realize foundational advances in the design and implementation

0:27:49.119 --> 0:27:54.000
<v Speaker 1>of long lived software systems that can dynamically adapt to

0:27:54.240 --> 0:27:58.159
<v Speaker 1>changes in the resources they depend upon and environments in

0:27:58.200 --> 0:28:03.320
<v Speaker 1>which they operate. So that's really interesting. And and again

0:28:03.480 --> 0:28:07.080
<v Speaker 1>this is something where it's just a call for proposals UM,

0:28:07.280 --> 0:28:10.280
<v Speaker 1>so we don't know everything about what they mean yet,

0:28:10.320 --> 0:28:14.240
<v Speaker 1>but there have been different interpretations of what this means.

0:28:15.000 --> 0:28:17.720
<v Speaker 1>One of them is sort of that, Okay, so all

0:28:17.800 --> 0:28:22.200
<v Speaker 1>software lives on what this uh, this release called an ecosystem,

0:28:22.280 --> 0:28:24.919
<v Speaker 1>and that sort of makes sense. There's an ecosystem of

0:28:25.400 --> 0:28:28.200
<v Speaker 1>other software out there. There's other software in the world

0:28:28.240 --> 0:28:32.080
<v Speaker 1>that has to share and trade information with UM. There's

0:28:32.119 --> 0:28:35.200
<v Speaker 1>the hardware that it runs on, you know, the physical

0:28:35.280 --> 0:28:39.440
<v Speaker 1>stuff that allows the software to execute. There are protocols,

0:28:39.520 --> 0:28:42.000
<v Speaker 1>and you know, that's like the language the software uses

0:28:42.040 --> 0:28:44.720
<v Speaker 1>to communicate with other pieces of software. One example would

0:28:44.760 --> 0:28:49.960
<v Speaker 1>be HTTP, the protocol of Web traffic. UM. Of course,

0:28:50.000 --> 0:28:52.800
<v Speaker 1>the users that operate it could be considered part of

0:28:52.800 --> 0:28:57.400
<v Speaker 1>the ecosystem, possibly the libraries that supported the data that

0:28:57.440 --> 0:28:59.680
<v Speaker 1>goes into it, right, yeah, yeah, So libraries you can

0:28:59.720 --> 0:29:02.840
<v Speaker 1>think of as like imported tools that are used in software.

0:29:02.840 --> 0:29:05.600
<v Speaker 1>So you might have like the Windows Control library, which

0:29:05.640 --> 0:29:09.320
<v Speaker 1>would include like Windows buttons and stuff like that, or subroutines.

0:29:10.320 --> 0:29:14.680
<v Speaker 1>And of course for any program, this ecosystem is constantly

0:29:14.760 --> 0:29:17.160
<v Speaker 1>changing all around and around it, and this is why

0:29:17.280 --> 0:29:19.760
<v Speaker 1>we have to have software updates. I mean, sometimes you'll

0:29:19.800 --> 0:29:22.960
<v Speaker 1>realize there's a vulnerability or something like that they need

0:29:23.040 --> 0:29:26.600
<v Speaker 1>to patch. Other times it needs a compatibility update, it

0:29:26.600 --> 0:29:30.920
<v Speaker 1>needs to be updated to work with something else, or well, well,

0:29:30.920 --> 0:29:34.280
<v Speaker 1>because I was going to say, uh when like Firefox

0:29:34.360 --> 0:29:37.240
<v Speaker 1>updates and all of a sudden, Adobe Flash is like, oh,

0:29:37.320 --> 0:29:40.520
<v Speaker 1>I don't work with this version of Firefox anymore. Let's

0:29:40.520 --> 0:29:43.400
<v Speaker 1>get on writing some new code to patch that up, right.

0:29:43.560 --> 0:29:45.280
<v Speaker 1>Or you might be saying, well, I want to port

0:29:45.400 --> 0:29:48.360
<v Speaker 1>this piece of software to a totally different environment. So

0:29:48.840 --> 0:29:50.920
<v Speaker 1>it used to run on my web browser, now I

0:29:50.960 --> 0:29:53.200
<v Speaker 1>want to make it an Android app that does exactly

0:29:53.200 --> 0:29:58.280
<v Speaker 1>the same thing. Uh okay, well that's usually not so easy.

0:29:58.360 --> 0:30:01.400
<v Speaker 1>You've got to like actually have some developers go in

0:30:01.440 --> 0:30:05.480
<v Speaker 1>there and make some changes. If I'm interpreting this correctly,

0:30:05.520 --> 0:30:08.520
<v Speaker 1>what it sounds like they want to get into is

0:30:08.560 --> 0:30:13.440
<v Speaker 1>the idea of self adapting code for software programs like

0:30:13.480 --> 0:30:18.320
<v Speaker 1>the like, how can you create software that is itself

0:30:18.400 --> 0:30:22.680
<v Speaker 1>sort of uh, mainly just driven by its goal, Like

0:30:22.720 --> 0:30:25.440
<v Speaker 1>it has a function that it performs and it adapts

0:30:25.560 --> 0:30:29.840
<v Speaker 1>when its conditions change. Sure so so kind of rather

0:30:29.920 --> 0:30:33.800
<v Speaker 1>than having software updates that have to be written by

0:30:33.840 --> 0:30:38.680
<v Speaker 1>a team and installed either manually or automatically when the

0:30:38.720 --> 0:30:42.280
<v Speaker 1>team sends them out. You would have software that's essentially

0:30:42.560 --> 0:30:48.680
<v Speaker 1>updating all the time. Yeah, yeah, yeah, I that might

0:30:48.760 --> 0:30:52.280
<v Speaker 1>be the case, or it may be something that could

0:30:52.320 --> 0:30:55.520
<v Speaker 1>potentially be I hesitate to use the words simpler, because

0:30:55.560 --> 0:30:59.120
<v Speaker 1>this would still be incredibly difficult. But the development of

0:30:59.400 --> 0:31:04.560
<v Speaker 1>a new form of software platform that could perpetually do

0:31:04.640 --> 0:31:07.320
<v Speaker 1>what it's supposed to do no matter what kind of

0:31:07.360 --> 0:31:09.920
<v Speaker 1>equipment it's running on. You know, let's say that the

0:31:10.120 --> 0:31:12.160
<v Speaker 1>because I mean, obviously, if you if you assume that

0:31:12.200 --> 0:31:15.560
<v Speaker 1>Moore's law holds true at least for a while, then

0:31:15.600 --> 0:31:18.000
<v Speaker 1>the computers of ten years from now are going to

0:31:18.040 --> 0:31:20.680
<v Speaker 1>be so much faster than what we're using today that

0:31:20.920 --> 0:31:25.120
<v Speaker 1>running today's software on them would seem ridiculous. It certainly

0:31:25.160 --> 0:31:28.840
<v Speaker 1>wouldn't be optimized for that equipment. This sounds like it's

0:31:28.840 --> 0:31:31.640
<v Speaker 1>a proposal to try and create a type of software

0:31:32.000 --> 0:31:36.200
<v Speaker 1>that would consistently be able to adapt so that it

0:31:36.320 --> 0:31:42.200
<v Speaker 1>is running at the appropriate efficiency for whatever conditions happened

0:31:42.240 --> 0:31:45.160
<v Speaker 1>to be there. In other words, if you're using it

0:31:45.200 --> 0:31:48.719
<v Speaker 1>in the future, it should be just as efficient on

0:31:48.800 --> 0:31:51.880
<v Speaker 1>that future equipment as it is on today's equipment. Which

0:31:51.920 --> 0:31:54.960
<v Speaker 1>is an incredibly difficult thing to do. Yeah, yeah, it's

0:31:55.000 --> 0:31:57.240
<v Speaker 1>sort of. That would be like if you took a

0:31:57.480 --> 0:32:00.520
<v Speaker 1>copy of I don't know, we were is talking about

0:32:00.520 --> 0:32:04.680
<v Speaker 1>Silent Hill, a Silent Hill one for the PlayStation and

0:32:04.720 --> 0:32:07.880
<v Speaker 1>being able to plug it right into a PS three

0:32:08.000 --> 0:32:10.200
<v Speaker 1>and have it look like a PS three game or

0:32:10.240 --> 0:32:13.680
<v Speaker 1>at least run we can see. That's the other thing

0:32:13.680 --> 0:32:15.880
<v Speaker 1>about That's the other thing about legacy systems, right, is

0:32:15.920 --> 0:32:19.959
<v Speaker 1>thatwards compatibility isn't always considered and built in exactly if

0:32:19.960 --> 0:32:22.160
<v Speaker 1>we look if we just look at the brief history

0:32:22.160 --> 0:32:25.200
<v Speaker 1>of computers already, which have not been around that long.

0:32:25.240 --> 0:32:28.400
<v Speaker 1>In the grand scheme of things, there there's a host

0:32:28.680 --> 0:32:31.800
<v Speaker 1>of different forms of media that we no longer have

0:32:31.880 --> 0:32:35.360
<v Speaker 1>access to that you know, we don't have the devices

0:32:35.400 --> 0:32:37.360
<v Speaker 1>that read that media, or there are very few of

0:32:37.360 --> 0:32:41.040
<v Speaker 1>them in existence these days. So, uh, this is also

0:32:41.080 --> 0:32:43.200
<v Speaker 1>supposed to be a system that's going to have a

0:32:43.320 --> 0:32:46.560
<v Speaker 1>centuries worth of longevity to it, meaning that the stuff

0:32:46.560 --> 0:32:49.120
<v Speaker 1>that's created at the beginning should still be just as

0:32:49.160 --> 0:32:51.760
<v Speaker 1>accessible in a hundred years. That's not even true for

0:32:51.800 --> 0:32:55.000
<v Speaker 1>the stuff we build right now. That is in itself

0:32:55.080 --> 0:32:58.120
<v Speaker 1>is a huge task, right, I mean, the stuff that

0:32:58.160 --> 0:33:01.280
<v Speaker 1>the stuff that was made back on punch cards. You're

0:33:01.320 --> 0:33:04.120
<v Speaker 1>not gonna I doubt any of our listeners have access

0:33:04.160 --> 0:33:06.880
<v Speaker 1>to that. Yeah, So, I mean it sounds like you're

0:33:06.880 --> 0:33:09.120
<v Speaker 1>talking about the same kind of thing I am, from

0:33:09.120 --> 0:33:12.080
<v Speaker 1>what I can tell, more or less. I mean, the

0:33:12.120 --> 0:33:16.520
<v Speaker 1>only thing I because I've seen interpretations that suggest that

0:33:16.520 --> 0:33:21.440
<v Speaker 1>that every implementation of this would adapt on its own

0:33:21.600 --> 0:33:24.560
<v Speaker 1>to a point where like some people have in some

0:33:24.640 --> 0:33:27.320
<v Speaker 1>of the stories I've read, have have equated this to

0:33:28.480 --> 0:33:33.120
<v Speaker 1>artificial intelligence and the potential rise of sentience sentience from

0:33:33.200 --> 0:33:37.320
<v Speaker 1>sentience sentience from from artificial intelligence, which is a totally

0:33:37.320 --> 0:33:40.280
<v Speaker 1>different thing, right, It's not. It's not that the software

0:33:40.640 --> 0:33:46.280
<v Speaker 1>is intelligently adapting itself so that it will be the better, faster,

0:33:46.360 --> 0:33:52.480
<v Speaker 1>and stronger on that hardware. It's just saying, oh, I have,

0:33:53.200 --> 0:33:56.240
<v Speaker 1>uh this much more memory, now let's use it. Or

0:33:58.240 --> 0:34:00.719
<v Speaker 1>you know this, this other program has changed and so

0:34:00.800 --> 0:34:03.200
<v Speaker 1>I need to change in order to use it. Something

0:34:03.200 --> 0:34:06.600
<v Speaker 1>along those lines. I mean, that's again, the vague descriptions

0:34:06.640 --> 0:34:09.680
<v Speaker 1>make it difficult for us to really come down on this,

0:34:09.760 --> 0:34:14.839
<v Speaker 1>and also the responses to this request for proposal could

0:34:14.960 --> 0:34:18.359
<v Speaker 1>end up having a limited response or it could end

0:34:18.400 --> 0:34:22.560
<v Speaker 1>up being a response that that the response says, yes,

0:34:22.560 --> 0:34:25.200
<v Speaker 1>we're gonna meet all of these requirements, but the reality

0:34:25.239 --> 0:34:29.200
<v Speaker 1>may shape out totally differently. It's it's impossible to say

0:34:29.239 --> 0:34:32.400
<v Speaker 1>this is the very dawn of this research for this

0:34:32.480 --> 0:34:36.440
<v Speaker 1>particular project. So it'll be really interesting to see what

0:34:36.560 --> 0:34:40.080
<v Speaker 1>happens for years from now when this this kind of

0:34:40.120 --> 0:34:42.560
<v Speaker 1>research project comes to an end and see where we're

0:34:42.600 --> 0:34:46.600
<v Speaker 1>at and what has actually taken place, because right now

0:34:46.640 --> 0:34:49.839
<v Speaker 1>it's very hard for me to envision what the end

0:34:49.840 --> 0:34:52.920
<v Speaker 1>product is going to be. Like. Another project that is

0:34:53.000 --> 0:34:57.799
<v Speaker 1>in those early beginning stages is called four Is it Mighty?

0:34:57.840 --> 0:35:01.239
<v Speaker 1>It is the Mighty Thore? Yes, it is Technologies for

0:35:01.360 --> 0:35:07.719
<v Speaker 1>Host Resilience, and it is currently it is currently reviewing proposals.

0:35:07.719 --> 0:35:10.359
<v Speaker 1>So they so they had a proposal acceptance round, They've

0:35:10.360 --> 0:35:14.919
<v Speaker 1>received a bunch and they are presumably looking at them

0:35:15.040 --> 0:35:18.960
<v Speaker 1>um and and this this project is trying to discover

0:35:19.440 --> 0:35:24.400
<v Speaker 1>how disease tolerance works in various creatures and various systems

0:35:24.400 --> 0:35:28.680
<v Speaker 1>of creatures and to then identify ways to make organisms,

0:35:29.160 --> 0:35:33.200
<v Speaker 1>uh presumably mostly humans stronger against infection. That makes so

0:35:33.280 --> 0:35:35.719
<v Speaker 1>much more sense than what I thought Technologies for Host

0:35:35.760 --> 0:35:37.120
<v Speaker 1>Resilience was going to be. I thought it was going

0:35:37.160 --> 0:35:39.280
<v Speaker 1>to be about how you know, when you have a party,

0:35:39.560 --> 0:35:42.680
<v Speaker 1>and like you've invited different people to come to your party,

0:35:42.719 --> 0:35:45.080
<v Speaker 1>and you know that one of those people really hates

0:35:45.120 --> 0:35:46.719
<v Speaker 1>the other ones, You've got to figure out how you

0:35:46.719 --> 0:35:48.719
<v Speaker 1>can position them at the party so that you don't

0:35:48.760 --> 0:35:50.839
<v Speaker 1>have any of those awkward social situations. I thought that's

0:35:50.840 --> 0:35:54.440
<v Speaker 1>what this was about. And then fortunately none of them arrive. Anyway,

0:35:54.239 --> 0:35:57.360
<v Speaker 1>that's my party to a t Joe, You've just described

0:35:57.400 --> 0:36:00.560
<v Speaker 1>every party I've ever tried to throw. Um the you

0:36:00.560 --> 0:36:05.360
<v Speaker 1>know what? Getting back into this the proposal here. I

0:36:05.440 --> 0:36:09.160
<v Speaker 1>love this idea because to me, this this sounds like

0:36:09.200 --> 0:36:13.440
<v Speaker 1>a proposal. Let's look into alternatives for things like antibiotics,

0:36:13.960 --> 0:36:17.760
<v Speaker 1>right exactly. Yeah, And so it's flipping the common system

0:36:17.760 --> 0:36:20.560
<v Speaker 1>on its head. Of of figuring out how to attack better,

0:36:20.640 --> 0:36:23.680
<v Speaker 1>this is learning how to defend better, which is so

0:36:23.719 --> 0:36:27.080
<v Speaker 1>cool medically speaking. And yeah, especially with all the problems

0:36:27.160 --> 0:36:32.440
<v Speaker 1>that we've talked about having with the overuse of antibiotics.

0:36:32.520 --> 0:36:35.879
<v Speaker 1>And did we do did we do? Yeah? I thought

0:36:35.960 --> 0:36:38.040
<v Speaker 1>we had. Yeah, So yeah, we we talked about that

0:36:38.120 --> 0:36:42.080
<v Speaker 1>at length, about the various issues which I mean, this

0:36:42.120 --> 0:36:44.560
<v Speaker 1>would be a really cool kind of technology that could

0:36:44.600 --> 0:36:48.960
<v Speaker 1>stand to benefit millions of people, well beyond military applications.

0:36:49.960 --> 0:36:53.520
<v Speaker 1>So here's hoping that that pans out. Well, they're also

0:36:53.800 --> 0:36:58.239
<v Speaker 1>darpest looking at alternatives to GPS. Yeah, after creating this

0:36:58.320 --> 0:37:03.640
<v Speaker 1>amazing satellite global UH positioning satellite system, they they're like,

0:37:03.880 --> 0:37:06.759
<v Speaker 1>you know, this isn't working so great? Yeah, or rather

0:37:06.800 --> 0:37:09.920
<v Speaker 1>there are there are there are some limitations. Like one

0:37:09.920 --> 0:37:12.200
<v Speaker 1>of the limitations is that, well, if you don't have

0:37:12.239 --> 0:37:16.200
<v Speaker 1>satellite coverage, then you don't get them the data needed

0:37:16.239 --> 0:37:18.200
<v Speaker 1>to tell you where you are. And sometimes you don't

0:37:18.200 --> 0:37:21.319
<v Speaker 1>have satellite coverage because it can be blocked. Yeah, and

0:37:21.360 --> 0:37:24.240
<v Speaker 1>it might be blocked by a physical structure. So example,

0:37:24.280 --> 0:37:26.600
<v Speaker 1>you might be in a city that has laws of

0:37:26.640 --> 0:37:28.840
<v Speaker 1>tall buildings and you're not getting a clear signal, and

0:37:28.920 --> 0:37:31.560
<v Speaker 1>that might be it. Sometimes you might be in a

0:37:31.600 --> 0:37:34.480
<v Speaker 1>really deeply wooded area that might be it. Sometimes you

0:37:34.560 --> 0:37:38.799
<v Speaker 1>might have UH an opponent of some sort jamming signals,

0:37:39.000 --> 0:37:41.960
<v Speaker 1>so you cannot get a clear signal from a satellite,

0:37:42.280 --> 0:37:46.040
<v Speaker 1>and thus your device cannot determine what your position is. Um.

0:37:46.080 --> 0:37:47.839
<v Speaker 1>So there are a lot of reasons why you might

0:37:47.880 --> 0:37:49.440
<v Speaker 1>want to look into this, or you know, it may

0:37:49.520 --> 0:37:51.480
<v Speaker 1>be that the environment you're in, Like if you are

0:37:51.480 --> 0:37:53.759
<v Speaker 1>in an underground facility, you're not going to get a

0:37:53.800 --> 0:37:58.440
<v Speaker 1>strong signal, you know. So what what are some alternatives? Uh?

0:37:58.440 --> 0:38:00.600
<v Speaker 1>And there are a lot of different proposed was on this.

0:38:00.680 --> 0:38:04.319
<v Speaker 1>One of them is called the All Source Positioning and

0:38:04.400 --> 0:38:09.400
<v Speaker 1>Navigation Project or ASPEN, and UH, this one is interesting.

0:38:09.440 --> 0:38:12.799
<v Speaker 1>It it's supposed to make use of all available signals

0:38:13.000 --> 0:38:17.560
<v Speaker 1>in an area, everything that is being transmitted, including things

0:38:17.560 --> 0:38:20.239
<v Speaker 1>that are not being transmitted by humans. And by that

0:38:20.320 --> 0:38:22.720
<v Speaker 1>I mean it will pick up radio signals, television signals,

0:38:22.760 --> 0:38:25.279
<v Speaker 1>cell tower signals, all to try and position itself, but

0:38:25.400 --> 0:38:31.200
<v Speaker 1>also naturally occurring phenomenon like lightning, because if you know

0:38:31.200 --> 0:38:35.040
<v Speaker 1>where the lightning strike is and your your system detects

0:38:35.080 --> 0:38:38.480
<v Speaker 1>the lightning strike as well, it can coordinate that information

0:38:38.520 --> 0:38:43.600
<v Speaker 1>to help locate your fixed position. UM. And because this

0:38:43.640 --> 0:38:47.440
<v Speaker 1>would be a passive system, you wouldn't without shutting down everything,

0:38:47.520 --> 0:38:50.279
<v Speaker 1>you wouldn't be able to jam it. Uh. So that's

0:38:50.320 --> 0:38:52.799
<v Speaker 1>the you know, one of the ideas, and it's not

0:38:52.840 --> 0:38:56.080
<v Speaker 1>the only alternative GPS that DARP is looking into, but

0:38:56.120 --> 0:38:59.440
<v Speaker 1>it's the one that I can find the most information on. UM.

0:38:59.480 --> 0:39:04.879
<v Speaker 1>Also there looking at maybe looking backward at computer models. Right,

0:39:05.000 --> 0:39:09.200
<v Speaker 1>the computers we have today are digital computers. The computers

0:39:09.200 --> 0:39:11.680
<v Speaker 1>of the past were analog, and they're like, hey, you

0:39:11.719 --> 0:39:14.239
<v Speaker 1>know those analog computers were actually pretty cool. Yeah, this

0:39:14.280 --> 0:39:16.000
<v Speaker 1>is ah, this is going to make a lot of

0:39:16.080 --> 0:39:19.120
<v Speaker 1>sense to all the musicians out there. The difference between

0:39:19.120 --> 0:39:23.320
<v Speaker 1>digital and analog. So digital deals with discrete measurements. You know, essentially,

0:39:23.320 --> 0:39:25.239
<v Speaker 1>when you get down to it, a bit is either

0:39:25.320 --> 0:39:28.120
<v Speaker 1>a zero or a one. It can't be any other value, right,

0:39:28.400 --> 0:39:30.880
<v Speaker 1>unless you're talking about quantum bits, which are technically zero,

0:39:30.960 --> 0:39:34.560
<v Speaker 1>one and everything in between. Um, So your classic bit

0:39:34.640 --> 0:39:37.120
<v Speaker 1>is either a zero or a one, and that leads

0:39:37.200 --> 0:39:41.520
<v Speaker 1>to the ability to make discreete measurements with incredible precision.

0:39:41.600 --> 0:39:45.279
<v Speaker 1>But as far as dynamic, changing complicated systems go, it's

0:39:45.360 --> 0:39:51.040
<v Speaker 1>not ideal. So something like a really complex fluid system

0:39:51.040 --> 0:39:54.920
<v Speaker 1>would be difficult to simulate with classical computers without using

0:39:55.040 --> 0:40:00.919
<v Speaker 1>a huge amount of of computational power. That's why when

0:40:00.920 --> 0:40:03.640
<v Speaker 1>we talk about things like these really dynamic systems like

0:40:03.719 --> 0:40:08.080
<v Speaker 1>climates and weather, it's difficult to simulate. It's why it

0:40:08.120 --> 0:40:11.400
<v Speaker 1>needs so much processor power. But what DARPA says is

0:40:11.440 --> 0:40:15.960
<v Speaker 1>that if we look at more of an analog method computation,

0:40:16.440 --> 0:40:21.040
<v Speaker 1>we could potentially make these sort of simulations using much

0:40:21.200 --> 0:40:26.239
<v Speaker 1>less computational power comparatively speaking, make it more efficient, so

0:40:26.280 --> 0:40:29.560
<v Speaker 1>we're not constantly having to build the next great supercomputer

0:40:29.640 --> 0:40:33.359
<v Speaker 1>in order to to simulate these systems. Uh. And when

0:40:33.400 --> 0:40:37.080
<v Speaker 1>we talk about analog, they're not talking about like mechanical

0:40:37.200 --> 0:40:39.839
<v Speaker 1>switches or anything like that. They're talking about some pretty

0:40:39.880 --> 0:40:43.560
<v Speaker 1>high tech stuff like DNA computing models or photonic systems

0:40:43.560 --> 0:40:47.040
<v Speaker 1>that you're using optical uh, you know, fiber optic wires

0:40:47.040 --> 0:40:50.800
<v Speaker 1>instead of instead of electricity. So it would be still

0:40:50.880 --> 0:40:53.719
<v Speaker 1>kind of a sci fi high tech computer, and it

0:40:53.719 --> 0:40:57.759
<v Speaker 1>would be really really good at dealing with certain computational problems,

0:40:58.239 --> 0:41:03.120
<v Speaker 1>not necessarily faster than classical supercomputer for other types of problems, however,

0:41:03.600 --> 0:41:05.440
<v Speaker 1>very much like quantum computers. We talked about that in

0:41:05.480 --> 0:41:08.439
<v Speaker 1>the past two how quantum computers could be amazing at

0:41:08.520 --> 0:41:11.759
<v Speaker 1>particular applications. But it doesn't mean you're going to be

0:41:11.840 --> 0:41:15.319
<v Speaker 1>able to run the next version of Skyrim, like the

0:41:15.360 --> 0:41:18.600
<v Speaker 1>next Elder Scrolls game at the highest frame rate. That's

0:41:18.600 --> 0:41:22.359
<v Speaker 1>not what a quantum computer, but it probably would make

0:41:22.360 --> 0:41:26.560
<v Speaker 1>those mods even more interesting. Now there's a particular office

0:41:27.120 --> 0:41:32.240
<v Speaker 1>within DARPA called the Technical Technology Office, which looks at quote,

0:41:32.239 --> 0:41:36.840
<v Speaker 1>military capabilities that create an asymmetric technological advantage and provide

0:41:36.920 --> 0:41:40.760
<v Speaker 1>US forces with decisive superiority and the ability to overwhelm

0:41:40.800 --> 0:41:45.719
<v Speaker 1>our opponents end quote. So that's your moral fashioned just

0:41:45.760 --> 0:41:48.920
<v Speaker 1>straight up military technology. Yeah, this is the stuff that

0:41:48.920 --> 0:41:54.040
<v Speaker 1>would give our side technical advantage over anyone else's side.

0:41:54.239 --> 0:41:56.200
<v Speaker 1>That's essentially what it comes down to. And what what

0:41:56.320 --> 0:41:59.120
<v Speaker 1>I love is that says an asymmetric technical advantage, Like

0:41:59.160 --> 0:42:02.680
<v Speaker 1>technical advantage isn't good enough, it has to be asymmetrical.

0:42:03.040 --> 0:42:06.040
<v Speaker 1>What they're saying is we're investigating how to make war

0:42:06.200 --> 0:42:09.880
<v Speaker 1>more unfair. Yeah. Yeah, and uh and so here are

0:42:09.920 --> 0:42:11.880
<v Speaker 1>some of them. And the first one I can't believe

0:42:11.920 --> 0:42:14.759
<v Speaker 1>they took this name. I mean, I really can't they

0:42:14.880 --> 0:42:18.640
<v Speaker 1>They have a project called Hydra hale Hydra hale Hydra.

0:42:18.840 --> 0:42:21.560
<v Speaker 1>So that's like a y'all have to help me here,

0:42:21.560 --> 0:42:25.160
<v Speaker 1>because as we've established, I'm sort of a casual comics fan. Alright,

0:42:25.200 --> 0:42:28.279
<v Speaker 1>So two of the three members of four thinking now

0:42:28.360 --> 0:42:30.080
<v Speaker 1>know that the third one is not one of us.

0:42:32.080 --> 0:42:35.000
<v Speaker 1>Hydra is is that some sort of like weird Nazi

0:42:35.120 --> 0:42:38.279
<v Speaker 1>thing in Captain America. It's an evil organization that's set

0:42:38.320 --> 0:42:41.040
<v Speaker 1>up in the Marvel universe that uh, yeah, it's an

0:42:41.040 --> 0:42:43.759
<v Speaker 1>offshoot of the well because you know the Captain Mark

0:42:43.960 --> 0:42:47.560
<v Speaker 1>Captain America rather comics started during World War Two, and

0:42:47.600 --> 0:42:52.399
<v Speaker 1>so the Hydra originally was an offshoot of the Nazis. Yeah,

0:42:52.480 --> 0:42:56.719
<v Speaker 1>and now now exists as its own totalitarian secret organization

0:42:57.040 --> 0:43:00.799
<v Speaker 1>that is attempting to bring the world under one world order.

0:43:01.160 --> 0:43:05.440
<v Speaker 1>So hopefully that's not what this Defense initiative is trying

0:43:05.440 --> 0:43:08.600
<v Speaker 1>to evoke. Yeah, as far as I know, they don't

0:43:08.719 --> 0:43:13.680
<v Speaker 1>use the Marvel Hydra symbol as their logo or anything. Now,

0:43:13.680 --> 0:43:17.280
<v Speaker 1>this is a project that is specifically dedicated to adding

0:43:17.480 --> 0:43:21.920
<v Speaker 1>unmanned support in naval operations as in the Navy, not

0:43:22.040 --> 0:43:26.520
<v Speaker 1>as in belly buttons. Uh So, manned ships can't be everywhere,

0:43:26.800 --> 0:43:29.319
<v Speaker 1>right like you if you if there's a conflict and

0:43:29.719 --> 0:43:32.440
<v Speaker 1>the Navy has to be involved, uh, you know, you

0:43:32.480 --> 0:43:34.960
<v Speaker 1>have to just like with any military resource, you have

0:43:35.040 --> 0:43:38.839
<v Speaker 1>to be very strategic about where you're you are locating

0:43:38.920 --> 0:43:42.160
<v Speaker 1>your resources and how they can respond in any given situation,

0:43:42.480 --> 0:43:45.959
<v Speaker 1>and they can't be everywhere at once. So this would

0:43:46.000 --> 0:43:51.000
<v Speaker 1>actually be a program that would UH augment the Navy's

0:43:51.040 --> 0:43:55.520
<v Speaker 1>operations by creating unmanned platforms. And platforms in this sense

0:43:55.600 --> 0:44:01.319
<v Speaker 1>mean a method of uh attaching whatever tools you need

0:44:01.360 --> 0:44:04.200
<v Speaker 1>to accomplish your mission. So if it's surveillance, it might

0:44:04.239 --> 0:44:10.440
<v Speaker 1>be various sensors, cameras, that kind of thing, microphones, etcetera.

0:44:10.640 --> 0:44:14.640
<v Speaker 1>And you would deploy these with Navy ships and ideally

0:44:14.680 --> 0:44:17.200
<v Speaker 1>they would be able to remain operational for months at

0:44:17.200 --> 0:44:20.200
<v Speaker 1>a time without the need of having to be recharged

0:44:20.320 --> 0:44:23.799
<v Speaker 1>or maintained in any way. Uh So, really, in a way,

0:44:23.800 --> 0:44:27.520
<v Speaker 1>it's it's like saying, let's let's have lots of ways

0:44:27.600 --> 0:44:32.760
<v Speaker 1>of listening in and paying attention, so that it's almost

0:44:32.800 --> 0:44:36.120
<v Speaker 1>as if we can be everywhere. But in reality, it's

0:44:36.120 --> 0:44:40.200
<v Speaker 1>because we have these unmanned um platforms in order to

0:44:40.440 --> 0:44:44.680
<v Speaker 1>gain that that or to gather that information underwater drones. Yeah,

0:44:44.920 --> 0:44:46.960
<v Speaker 1>it could be, I mean that could certainly be part

0:44:47.000 --> 0:44:49.840
<v Speaker 1>of it. Because again, this is sort of the definition

0:44:49.880 --> 0:44:52.719
<v Speaker 1>of what their goal is. It's not the explanation of

0:44:52.719 --> 0:44:55.640
<v Speaker 1>how they achieve that goal, right, So they use lots

0:44:55.680 --> 0:44:59.560
<v Speaker 1>of vague terms like platform and payload because it's better

0:44:59.600 --> 0:45:03.279
<v Speaker 1>to go had to be vague and not predefined. What

0:45:03.520 --> 0:45:05.920
<v Speaker 1>it is, because you may come up with a solution

0:45:05.920 --> 0:45:10.719
<v Speaker 1>that didn't meet that predefinition but still is totally applicable. UM,

0:45:11.239 --> 0:45:15.400
<v Speaker 1>then you got vulture. Okay, I like that. They're picking

0:45:15.640 --> 0:45:21.720
<v Speaker 1>lots of commonly feared, mythological and real animals. The Armies

0:45:21.760 --> 0:45:26.160
<v Speaker 1>of Hell burst forth under Defense Department funding. It's not

0:45:26.160 --> 0:45:28.839
<v Speaker 1>not the case in this one either. But the next

0:45:28.880 --> 0:45:34.839
<v Speaker 1>one is called Cerberus. All right, so let's Chiron here

0:45:34.880 --> 0:45:37.520
<v Speaker 1>we get No, it's a This is a project to

0:45:37.560 --> 0:45:41.160
<v Speaker 1>develop an unmanned aerial vehicle you a v that would

0:45:41.200 --> 0:45:43.640
<v Speaker 1>be capable of remaining in flight for up to five

0:45:43.719 --> 0:45:47.040
<v Speaker 1>years without the need for maintenance or refueling. So we're

0:45:47.040 --> 0:45:50.320
<v Speaker 1>talking about like using solar cells and fuel cells that

0:45:50.400 --> 0:45:52.839
<v Speaker 1>kind of stuff. Uh. The idea being that you could

0:45:52.880 --> 0:45:54.920
<v Speaker 1>put this up in the air, it could have a

0:45:54.960 --> 0:45:59.799
<v Speaker 1>surveillance role UM or reconnaissance role, and you wouldn't need

0:45:59.840 --> 0:46:02.760
<v Speaker 1>to have it come down after because most most drones

0:46:02.800 --> 0:46:05.120
<v Speaker 1>that are used to have a very limited flying time.

0:46:05.760 --> 0:46:07.960
<v Speaker 1>This would be something that would be used for long

0:46:08.120 --> 0:46:12.239
<v Speaker 1>term UM. And that project, actually I believe is now

0:46:12.320 --> 0:46:15.920
<v Speaker 1>concluded and they've they're they kind of transitioned into looking

0:46:15.960 --> 0:46:21.239
<v Speaker 1>into ways of UM accelerating the advancement of solar cell

0:46:21.280 --> 0:46:25.480
<v Speaker 1>technology because it's a very important component of this. Next,

0:46:25.560 --> 0:46:30.279
<v Speaker 1>you have the extreme accuracy tasked ordinance or exact to

0:46:31.080 --> 0:46:33.080
<v Speaker 1>which I have to feel like they're going to get

0:46:33.120 --> 0:46:39.000
<v Speaker 1>into copyright anyway. Yeah, if you're if you're exact. Oh,

0:46:39.040 --> 0:46:41.360
<v Speaker 1>I'm not sure that you go after the Department's defense,

0:46:41.440 --> 0:46:45.120
<v Speaker 1>but maybe. Um so, this is technology for military snipers

0:46:45.160 --> 0:46:49.319
<v Speaker 1>that could also be a deterrent. Sure. Uh. And this

0:46:49.360 --> 0:46:51.240
<v Speaker 1>one's been in the news a lot over the past

0:46:51.280 --> 0:46:53.880
<v Speaker 1>couple of days since we've been we we are recording

0:46:53.880 --> 0:46:58.360
<v Speaker 1>this podcast episode Look Behind the curtainet on the April,

0:46:58.880 --> 0:47:01.400
<v Speaker 1>and I've been seeing this pop up a whole bunch. Yeah. So,

0:47:01.400 --> 0:47:06.800
<v Speaker 1>so exact though, this would be guided small caliber bullets.

0:47:07.360 --> 0:47:10.440
<v Speaker 1>And by small caliber, I mean fifty caliber, so small

0:47:10.560 --> 0:47:15.440
<v Speaker 1>for a given definition. And by guided, what do you

0:47:15.440 --> 0:47:18.440
<v Speaker 1>mean guided? So they're developing bullets that would be capable

0:47:18.480 --> 0:47:22.839
<v Speaker 1>of changing pathways in midflight. So let's say that you

0:47:22.920 --> 0:47:25.279
<v Speaker 1>are a sniper and you've lined up a shot on

0:47:25.320 --> 0:47:28.080
<v Speaker 1>a target. You've identified the target, so there'd have to

0:47:28.080 --> 0:47:31.920
<v Speaker 1>be some way for this targeting system to communicate with

0:47:31.920 --> 0:47:36.240
<v Speaker 1>the bullet, essentially saying this is where we're shooting. You fire,

0:47:36.320 --> 0:47:39.120
<v Speaker 1>but let's say the wind changes direction. If you're a

0:47:39.200 --> 0:47:44.000
<v Speaker 1>truly gifted sniper and you're firing from a very far distance,

0:47:44.719 --> 0:47:47.000
<v Speaker 1>a change in wind could be all that it takes

0:47:47.120 --> 0:47:49.759
<v Speaker 1>for a hit to turn into a miss. And if

0:47:49.800 --> 0:47:53.719
<v Speaker 1>you miss, you've also given away potentially your position and

0:47:53.840 --> 0:47:58.280
<v Speaker 1>endangered your mission. So this would be a means of

0:47:58.360 --> 0:48:02.200
<v Speaker 1>having a system that could allow for corrections in bullet

0:48:02.320 --> 0:48:05.360
<v Speaker 1>flight so that the bullet actually hits the intended target.

0:48:05.760 --> 0:48:09.600
<v Speaker 1>Now you'll notice I'm using a lot of terminology that

0:48:09.760 --> 0:48:14.759
<v Speaker 1>dehumanizes the purpose of snipers. That's not by accident. That's

0:48:14.800 --> 0:48:18.200
<v Speaker 1>the way DARPA defines these things too, because once you

0:48:18.239 --> 0:48:20.319
<v Speaker 1>start talking about this is a way for you to

0:48:20.400 --> 0:48:24.680
<v Speaker 1>kill people more efficiently, it gets super grim, super fast.

0:48:25.120 --> 0:48:28.120
<v Speaker 1>This is kind of a strange reminder and wake up

0:48:28.160 --> 0:48:32.000
<v Speaker 1>call on this because while DARPA is coming up with

0:48:32.040 --> 0:48:35.200
<v Speaker 1>lots of wonderful technologies that do filter down to the

0:48:35.200 --> 0:48:37.640
<v Speaker 1>the everyday level, and if we partially have them to

0:48:37.760 --> 0:48:41.480
<v Speaker 1>thank for the Internet, you can see them as a

0:48:41.560 --> 0:48:45.239
<v Speaker 1>very positive organization in a lot of ways. But their

0:48:45.280 --> 0:48:49.759
<v Speaker 1>funding technology technology, But we also have to remember, yeah,

0:48:49.800 --> 0:48:52.840
<v Speaker 1>they're they're gonna make bullets and stuff too write and

0:48:53.360 --> 0:48:55.160
<v Speaker 1>you know, you could even argue that, you know, the

0:48:55.239 --> 0:48:59.640
<v Speaker 1>responsible use of that technology can still be positive in

0:48:59.680 --> 0:49:02.359
<v Speaker 1>the overall scheme of things, But should you get down

0:49:02.400 --> 0:49:05.680
<v Speaker 1>to particulars, it's it's it's hard to talk about, Okay, Yeah,

0:49:05.680 --> 0:49:07.120
<v Speaker 1>I mean, I mean, and you just you just can't

0:49:07.160 --> 0:49:12.080
<v Speaker 1>forget that when they say engage targets faster, what they

0:49:12.160 --> 0:49:15.560
<v Speaker 1>genuinely mean is is kill a bunch of people, yeah,

0:49:15.800 --> 0:49:19.040
<v Speaker 1>more efficiently. Yeah. Yeah, So, I mean, that's that's just

0:49:19.080 --> 0:49:21.960
<v Speaker 1>the reality of the situation. Now that technology may end

0:49:22.080 --> 0:49:25.920
<v Speaker 1>up affecting other things that end up being in civilian

0:49:25.920 --> 0:49:29.640
<v Speaker 1>technology down the road that we can't necessarily anticipate right now.

0:49:29.719 --> 0:49:32.560
<v Speaker 1>Oh sure, I can imagine, for for example, going back

0:49:32.560 --> 0:49:36.960
<v Speaker 1>to autonomous vehicles, guiding systems being useful for for that

0:49:37.040 --> 0:49:41.240
<v Speaker 1>kind of right or even for some forms of autonomous flight.

0:49:41.560 --> 0:49:44.440
<v Speaker 1>It could be important, and you know, lots of different

0:49:44.480 --> 0:49:48.000
<v Speaker 1>other robotics. Really clearly, if if you're if your room

0:49:48.000 --> 0:49:51.919
<v Speaker 1>book can target the pile of of escaped kitty litterle

0:49:51.960 --> 0:49:54.640
<v Speaker 1>better sure, just not thinking about being in fear of

0:49:54.640 --> 0:49:57.640
<v Speaker 1>my room, but my room is able to pick me

0:49:57.719 --> 0:50:01.520
<v Speaker 1>off from across the house. Um So, the next one

0:50:01.960 --> 0:50:04.719
<v Speaker 1>is one that we've already kind of referenced earlier in

0:50:04.760 --> 0:50:08.680
<v Speaker 1>this episode, the Legged Squad Support System or l S three.

0:50:08.880 --> 0:50:12.120
<v Speaker 1>This is the one that includes the technology that was

0:50:12.200 --> 0:50:15.840
<v Speaker 1>developed by Boston Dynamics, the big dog technology, the legged

0:50:16.440 --> 0:50:20.000
<v Speaker 1>robotic units. And the purpose for these isn't to fulfill

0:50:20.160 --> 0:50:23.280
<v Speaker 1>the enemy with fear when they see this for legged

0:50:23.320 --> 0:50:27.120
<v Speaker 1>monstrosity marching towards them at a style change their hearts

0:50:27.160 --> 0:50:29.799
<v Speaker 1>and make them collapse into a puddle of Oh it's

0:50:29.840 --> 0:50:32.279
<v Speaker 1>so cute. Yeah, it's not neither of those things. It's

0:50:32.280 --> 0:50:36.560
<v Speaker 1>specifically to serve as like a mule. It's it's designed

0:50:36.560 --> 0:50:41.120
<v Speaker 1>to carry cargo because soldiers can carry a lot of stuff.

0:50:41.160 --> 0:50:43.200
<v Speaker 1>Some of them might be carrying upwards of a hundred

0:50:43.200 --> 0:50:46.240
<v Speaker 1>pounds of gear. That's like forty five kilos of gear.

0:50:47.000 --> 0:50:50.040
<v Speaker 1>That's that's heavy, and to think that, you know, you

0:50:50.120 --> 0:50:53.839
<v Speaker 1>often will end up also having to walk a very

0:50:53.920 --> 0:50:57.200
<v Speaker 1>great distance while carrying that. You know, you're you're already

0:50:57.400 --> 0:51:00.640
<v Speaker 1>talking about a huge physical demand on a soldier, and

0:51:00.680 --> 0:51:03.680
<v Speaker 1>that's before there's any sort of combat that might take

0:51:03.680 --> 0:51:05.839
<v Speaker 1>a point. Yeah, and that kind of physical strain can

0:51:05.920 --> 0:51:10.680
<v Speaker 1>absolutely affect your performance in the field. Sure. So this

0:51:10.680 --> 0:51:14.719
<v Speaker 1>this project is about finding means of creating a robotic

0:51:15.400 --> 0:51:19.320
<v Speaker 1>uh systems that could carry gear on behalf of soldiers.

0:51:19.760 --> 0:51:21.759
<v Speaker 1>It could keep pace with soldiers, So it has to

0:51:21.760 --> 0:51:26.480
<v Speaker 1>be able to go across different types of terrain, including

0:51:26.520 --> 0:51:30.440
<v Speaker 1>difficult terrain, and to remain safe around those soldiers. So,

0:51:30.480 --> 0:51:32.200
<v Speaker 1>in other words, you have to create a robot that

0:51:32.320 --> 0:51:34.719
<v Speaker 1>not only keeps pace and can travel the same sort

0:51:34.760 --> 0:51:37.319
<v Speaker 1>of ground that the soldiers do, but doesn't tread on

0:51:37.360 --> 0:51:40.279
<v Speaker 1>their feet or bump into them or you know other

0:51:40.360 --> 0:51:42.799
<v Speaker 1>things that we've talked about with robots, things that you

0:51:42.880 --> 0:51:45.720
<v Speaker 1>have to consider anytime you have a robot and human

0:51:46.480 --> 0:51:50.480
<v Speaker 1>potentially interacting with one another. So that's what that system

0:51:50.560 --> 0:51:53.200
<v Speaker 1>is all about. Uh So yeah, I mean those are

0:51:53.200 --> 0:51:55.680
<v Speaker 1>just that's just a kind of an overview of some

0:51:55.800 --> 0:51:58.600
<v Speaker 1>of the projects that DARPA has in various stages of

0:51:58.640 --> 0:52:01.440
<v Speaker 1>development right now. There are tons of other ones that

0:52:01.480 --> 0:52:04.080
<v Speaker 1>we didn't even touch upon. Oh of course. Yeah, there

0:52:04.120 --> 0:52:06.719
<v Speaker 1>are many, many, many things that they're always working on.

0:52:07.239 --> 0:52:10.280
<v Speaker 1>If you guys have heard about one that you would

0:52:10.320 --> 0:52:12.880
<v Speaker 1>like us to take a deeper look at, we would

0:52:12.880 --> 0:52:15.000
<v Speaker 1>love to hear from you. Yeah, you should send us

0:52:15.040 --> 0:52:18.360
<v Speaker 1>an email and say, hey, there's the specific DARPA initiative

0:52:18.400 --> 0:52:21.360
<v Speaker 1>that we would love to hear more about. We will

0:52:21.400 --> 0:52:24.480
<v Speaker 1>happily take a look at least as far as DARPA

0:52:24.560 --> 0:52:27.359
<v Speaker 1>will allow us to and and report back on that.

0:52:27.840 --> 0:52:30.279
<v Speaker 1>You can contact us by just sending an email to

0:52:30.400 --> 0:52:33.160
<v Speaker 1>FW thinking at how Stuff Works dot com. I think

0:52:33.200 --> 0:52:36.560
<v Speaker 1>I may have mentioned that email address before, uh but

0:52:36.719 --> 0:52:38.560
<v Speaker 1>FW thinking at how stuff Works dot com in case

0:52:38.560 --> 0:52:42.919
<v Speaker 1>you missed it the first five times. Um So, this

0:52:43.000 --> 0:52:45.760
<v Speaker 1>is one of those things where you know, I am

0:52:45.840 --> 0:52:50.160
<v Speaker 1>overall happy that DARPA exists. Actually, I'm really happy that

0:52:50.239 --> 0:52:52.520
<v Speaker 1>DARPA exists, because as as flippant as I can be

0:52:52.600 --> 0:52:57.799
<v Speaker 1>about this, national defense is incredibly important. And you know,

0:52:57.840 --> 0:52:59.919
<v Speaker 1>we would not be here if it weren't for nash

0:53:00.000 --> 0:53:03.480
<v Speaker 1>Old events, like our lives would be if they were,

0:53:03.520 --> 0:53:07.240
<v Speaker 1>in fact, our lives would be significantly different. Um So,

0:53:07.480 --> 0:53:09.360
<v Speaker 1>it's it's one of those things. But I'm also thankful

0:53:09.400 --> 0:53:11.799
<v Speaker 1>for the technology that has come out of it that

0:53:11.800 --> 0:53:15.960
<v Speaker 1>has benefited us in a consumer fashion. Again, the three

0:53:16.040 --> 0:53:17.640
<v Speaker 1>of us would not be in this room right now

0:53:17.680 --> 0:53:21.040
<v Speaker 1>if it weren't for the Internet. We wouldn't have jobs,

0:53:21.400 --> 0:53:25.200
<v Speaker 1>not here anyway. Well, I mean, in that parallel universe,

0:53:25.280 --> 0:53:27.520
<v Speaker 1>we might all wind up sitting in a small room

0:53:27.560 --> 0:53:30.279
<v Speaker 1>talking together. Anyway, to be in this room trying to

0:53:30.320 --> 0:53:32.759
<v Speaker 1>create a fire, I think. I think two out of

0:53:32.800 --> 0:53:34.640
<v Speaker 1>the three of us would be trying to induct the

0:53:34.680 --> 0:53:40.080
<v Speaker 1>third one into hydra. Joe, I have an interesting business

0:53:40.080 --> 0:53:42.799
<v Speaker 1>opportunity for you. Well, I have a rat on a

0:53:42.840 --> 0:53:46.080
<v Speaker 1>skewer to cook. I want to get this fire going.

0:53:46.719 --> 0:53:49.960
<v Speaker 1>That's fair, all right? So at any rate, Uh, As

0:53:49.960 --> 0:53:52.799
<v Speaker 1>far as what the future holds for DARPA, it's really

0:53:52.840 --> 0:53:56.440
<v Speaker 1>going to be a continuation of developing technologies that will

0:53:56.880 --> 0:54:01.160
<v Speaker 1>benefit military operations in some way, whether it's directly for

0:54:01.320 --> 0:54:05.480
<v Speaker 1>combat roles or support roles. That's its purpose. It's going

0:54:05.520 --> 0:54:09.799
<v Speaker 1>to continue doing that, and as a result those technologies,

0:54:09.840 --> 0:54:12.880
<v Speaker 1>many of them will filter down to benefit our lives

0:54:12.960 --> 0:54:15.640
<v Speaker 1>in ways that are very difficult for us to anticipate

0:54:15.719 --> 0:54:19.640
<v Speaker 1>right now. I'm sure when when DARPA was first formed,

0:54:19.640 --> 0:54:23.720
<v Speaker 1>back when it was ARPA, no one had really thought

0:54:23.800 --> 0:54:27.680
<v Speaker 1>about the possibility of something as incredible as the Internet, right,

0:54:27.760 --> 0:54:31.680
<v Speaker 1>and so it's when you think about that there, it's

0:54:31.680 --> 0:54:34.600
<v Speaker 1>impossible for us to predict what's going to come out next,

0:54:34.760 --> 0:54:38.719
<v Speaker 1>and There are plenty of research and development UH departments

0:54:39.000 --> 0:54:44.080
<v Speaker 1>in in UM companies and in universities that depends very

0:54:44.080 --> 0:54:47.440
<v Speaker 1>heavily upon DARPA's investment in order for them to do

0:54:47.480 --> 0:54:50.719
<v Speaker 1>the work they do, so it'll be interesting to see

0:54:50.760 --> 0:54:57.240
<v Speaker 1>what comes next. Any predictions, Joe, I think that the

0:54:57.239 --> 0:55:00.840
<v Speaker 1>the controlling of large flying beetles is really going to

0:55:00.920 --> 0:55:05.520
<v Speaker 1>be key to the next stage of of how stuff works,

0:55:05.520 --> 0:55:08.840
<v Speaker 1>in particular because we're going to be moving away from

0:55:08.880 --> 0:55:13.759
<v Speaker 1>like web video podcasting and into disseminating leaflets that are

0:55:13.800 --> 0:55:17.040
<v Speaker 1>carried out by beatles controlled by computers. I think that

0:55:17.080 --> 0:55:21.800
<v Speaker 1>the beatles could actually be carrying our microphones and video cameras,

0:55:21.840 --> 0:55:25.040
<v Speaker 1>like like swarms of microphones and video cameras. I think

0:55:25.080 --> 0:55:28.520
<v Speaker 1>they already do now. There are only two remaining beatles,

0:55:29.080 --> 0:55:33.600
<v Speaker 1>but I think they're fully capable of carrying cameras and microphones.

0:55:33.760 --> 0:55:36.839
<v Speaker 1>My prediction is that the next big thing coming out

0:55:36.840 --> 0:55:41.239
<v Speaker 1>of DARPA will be a pun generating computer. And then

0:55:41.239 --> 0:55:45.359
<v Speaker 1>you can post exactly that. We can sit in Jonathan's

0:55:45.440 --> 0:55:48.479
<v Speaker 1>chair and it will just take whatever the last word

0:55:48.520 --> 0:55:52.160
<v Speaker 1>we said was and turn it into something horrific. I

0:55:52.200 --> 0:55:54.400
<v Speaker 1>think the important thing for us to remember is that

0:55:54.480 --> 0:55:56.960
<v Speaker 1>all you need is love. So if you guys have

0:55:57.000 --> 0:56:01.040
<v Speaker 1>any suggestions for future episodes a Forward Thinking again, write us.

0:56:01.080 --> 0:56:03.080
<v Speaker 1>I'm not going to repeat the email address again. That

0:56:03.200 --> 0:56:06.319
<v Speaker 1>joke is long since dead, but please get in touch

0:56:06.360 --> 0:56:08.880
<v Speaker 1>with us. You can also touch based with us on Twitter,

0:56:09.000 --> 0:56:11.960
<v Speaker 1>Google Plus or Facebook. At Twitter and Google Plus, we

0:56:12.000 --> 0:56:14.960
<v Speaker 1>are f W Thinking. Search f W Thinking and Facebook

0:56:15.000 --> 0:56:17.200
<v Speaker 1>will pop right up. Leave us a message, tell us

0:56:17.239 --> 0:56:19.279
<v Speaker 1>what you think, give us you know your requests for

0:56:19.400 --> 0:56:21.759
<v Speaker 1>future episodes. We would love to hear from you, and

0:56:21.800 --> 0:56:29.480
<v Speaker 1>you'll hear from us again really soon. For more on

0:56:29.520 --> 0:56:32.760
<v Speaker 1>this topic in the future of technology, visit forward thinking

0:56:32.840 --> 0:56:45.920
<v Speaker 1>dot com, brought to you by Toyota. Let's Go Places,