WEBVTT - TechStuff Reviews 2016 Part One

0:00:04.160 --> 0:00:07.480
<v Speaker 1>Get in touch with technology with tech Stuff from stuff

0:00:07.520 --> 0:00:14.320
<v Speaker 1>works dot com. Hey there, and welcome to tex Stuff.

0:00:14.360 --> 0:00:18.279
<v Speaker 1>I'm your host, Jonathan Strickland, and today we're going to

0:00:18.440 --> 0:00:23.079
<v Speaker 1>start our yearly look back on the previous twelve months.

0:00:23.120 --> 0:00:25.400
<v Speaker 1>I'm gonna talk about some of the big tech news

0:00:25.400 --> 0:00:28.479
<v Speaker 1>stories of and there were a lot of them. So

0:00:28.520 --> 0:00:31.160
<v Speaker 1>I'm dividing this up into two episodes. Today we're gonna

0:00:31.160 --> 0:00:34.120
<v Speaker 1>look at January through May. And I know that's not

0:00:34.920 --> 0:00:37.599
<v Speaker 1>fully half a year, but some of these stories are

0:00:37.600 --> 0:00:41.000
<v Speaker 1>really heavily front loaded. So instead of just saying, hey,

0:00:41.040 --> 0:00:44.320
<v Speaker 1>the story began in say, February, and then in September

0:00:44.400 --> 0:00:47.760
<v Speaker 1>this happened, and then in December this happened. For for

0:00:47.840 --> 0:00:50.520
<v Speaker 1>big stories, I'm doing it all at the front. So

0:00:50.600 --> 0:00:54.720
<v Speaker 1>the second half is a little more sparse. I don't

0:00:54.760 --> 0:00:58.960
<v Speaker 1>go back and recover stories I had already talked about. Also,

0:00:59.520 --> 0:01:04.200
<v Speaker 1>let's get out there was kind of crappy for lots

0:01:04.200 --> 0:01:07.880
<v Speaker 1>of reasons, and I'm going to talk about some of them,

0:01:07.959 --> 0:01:11.800
<v Speaker 1>and yeah, you can't get it around it. I mean,

0:01:12.280 --> 0:01:17.319
<v Speaker 1>you just gotta accept it and move on, I guess.

0:01:17.560 --> 0:01:24.360
<v Speaker 1>So we're gonna start in January with what set the

0:01:24.400 --> 0:01:26.360
<v Speaker 1>tone for the rest of the year. I am, of

0:01:26.400 --> 0:01:30.119
<v Speaker 1>course talking about c e S. And this is where

0:01:30.200 --> 0:01:33.839
<v Speaker 1>my producer Dylan gets to feel a sense of dread

0:01:34.000 --> 0:01:37.759
<v Speaker 1>creep into his very bones, because he will be going

0:01:37.840 --> 0:01:41.679
<v Speaker 1>to c e S ten along with several of us

0:01:41.720 --> 0:01:45.760
<v Speaker 1>here at How Stuff Works. So Dylan, I'm sorry, you're

0:01:45.760 --> 0:01:49.880
<v Speaker 1>gonna have to hear this man he's he's just grinning

0:01:49.960 --> 0:01:53.400
<v Speaker 1>at me, but but his eyes are dead, all right.

0:01:53.520 --> 0:01:57.320
<v Speaker 1>So it was my eighth time attending c e S

0:01:57.400 --> 0:02:01.000
<v Speaker 1>and it was a bit different. Three other people from

0:02:01.040 --> 0:02:03.520
<v Speaker 1>How Stuff Works went with me, and I got to

0:02:03.520 --> 0:02:06.400
<v Speaker 1>see ce S through their eyes, and they were excited

0:02:06.960 --> 0:02:11.080
<v Speaker 1>and impressed by something that I had really begun to

0:02:11.120 --> 0:02:14.240
<v Speaker 1>feel like it was old and stale and and therefore

0:02:15.400 --> 0:02:17.440
<v Speaker 1>it was something to dread. It was actually a little

0:02:17.480 --> 0:02:19.480
<v Speaker 1>fun to see it through the eyes of people who

0:02:19.480 --> 0:02:22.320
<v Speaker 1>had never been there and then just kind of slowly

0:02:22.360 --> 0:02:26.280
<v Speaker 1>shake your head and just say, these children, but what

0:02:26.320 --> 0:02:28.520
<v Speaker 1>was going on there? While VR was a big hit

0:02:29.200 --> 0:02:31.560
<v Speaker 1>at c e S and at that time, the Oculus,

0:02:31.680 --> 0:02:35.080
<v Speaker 1>the HTC Vibe, and the PlayStation VR had yet to

0:02:35.160 --> 0:02:39.800
<v Speaker 1>make their debut, everyone was anticipating that the year was

0:02:39.840 --> 0:02:42.440
<v Speaker 1>going to be the year for virtual reality, but more

0:02:42.480 --> 0:02:44.680
<v Speaker 1>on that a little bit later. We also saw a

0:02:44.720 --> 0:02:48.560
<v Speaker 1>lot of drones, including ones that have ultra high definition

0:02:48.639 --> 0:02:51.840
<v Speaker 1>camera systems, and that blew my mind because just a

0:02:51.840 --> 0:02:55.320
<v Speaker 1>few years ago, buying just an ultra high definition camera

0:02:55.720 --> 0:02:59.560
<v Speaker 1>would cost somewhere in the neighborhood of thirty dollars, and

0:02:59.639 --> 0:03:02.600
<v Speaker 1>now today, for less than a grand, you can buy

0:03:02.639 --> 0:03:05.480
<v Speaker 1>a remote controlled drone that flies through the air and

0:03:05.639 --> 0:03:08.280
<v Speaker 1>has a u h D camera on it, which is

0:03:09.120 --> 0:03:13.919
<v Speaker 1>crazy to me. It also really shows how electronics can

0:03:14.120 --> 0:03:19.160
<v Speaker 1>can drop dramatically in cost. Also, drones can drop dramatically

0:03:19.320 --> 0:03:21.840
<v Speaker 1>from the air when I have the controls in my hands.

0:03:22.280 --> 0:03:25.160
<v Speaker 1>That's a different story. Over in the auto world, it

0:03:25.240 --> 0:03:29.000
<v Speaker 1>was all about AI and connected cars. Nearly every auto

0:03:29.040 --> 0:03:32.400
<v Speaker 1>maker at CS had something to show off in those arenas,

0:03:33.000 --> 0:03:35.320
<v Speaker 1>and uh I was at CS covering a lot of stuff,

0:03:35.360 --> 0:03:40.040
<v Speaker 1>including Toyota's press event. Full disclosure, Toyota is the sponsor

0:03:40.280 --> 0:03:43.840
<v Speaker 1>of the show I host called Forward Thinking, and their

0:03:43.880 --> 0:03:48.160
<v Speaker 1>big announcement revolved around the company's billion dollar investment into

0:03:48.280 --> 0:03:50.960
<v Speaker 1>research and development of AI, and I think we're gonna

0:03:51.000 --> 0:03:54.640
<v Speaker 1>hear a lot more about that in seventeen, so stay

0:03:54.640 --> 0:03:57.680
<v Speaker 1>tuned to Forward Thinking to find out more about that

0:03:57.760 --> 0:04:01.520
<v Speaker 1>in the near future. Over at Intel, the emphasis was

0:04:01.560 --> 0:04:04.760
<v Speaker 1>on small processors that can track various points of data

0:04:04.800 --> 0:04:08.280
<v Speaker 1>and other products. So Intel makes the chips that go

0:04:08.400 --> 0:04:11.840
<v Speaker 1>into other things, and they they explored this with a

0:04:11.840 --> 0:04:16.599
<v Speaker 1>lot of different applications. One was a an electronic bracelet

0:04:16.600 --> 0:04:18.840
<v Speaker 1>you would wear that would allow you to interact with

0:04:19.680 --> 0:04:23.039
<v Speaker 1>giant display and control elements on the display by waving

0:04:23.080 --> 0:04:26.600
<v Speaker 1>your hand around. Another was a mountain bike, and the

0:04:26.680 --> 0:04:30.360
<v Speaker 1>processors had things like accelerometers and and gyroscopes that could

0:04:30.360 --> 0:04:34.479
<v Speaker 1>track movement and orientation and give real time feedback to

0:04:34.839 --> 0:04:38.479
<v Speaker 1>another device. So you could have a smartphone open with

0:04:38.560 --> 0:04:42.600
<v Speaker 1>the appropriate app and get real time information about the

0:04:42.640 --> 0:04:47.159
<v Speaker 1>forces that were being uh felt by a rider on

0:04:47.200 --> 0:04:50.039
<v Speaker 1>one of these bicycles, and uh so you do like

0:04:50.080 --> 0:04:54.520
<v Speaker 1>a crazy you know, flip or or some other trick

0:04:54.600 --> 0:04:56.640
<v Speaker 1>on these bikes and you would get the real time

0:04:56.720 --> 0:04:59.800
<v Speaker 1>data feedback, which was kind of neat to actually see

0:04:59.800 --> 0:05:03.840
<v Speaker 1>this working in real time. One item over at Intel

0:05:03.920 --> 0:05:07.960
<v Speaker 1>was the Segue Advanced Personal Robot, which was a project

0:05:08.040 --> 0:05:12.320
<v Speaker 1>that was formed from a partnership between Segue, Intel and

0:05:12.520 --> 0:05:17.359
<v Speaker 1>a company called shoo Me, and it's part Segue device

0:05:17.520 --> 0:05:22.400
<v Speaker 1>you know, like the personalized mobile devices and part Butler,

0:05:22.800 --> 0:05:25.240
<v Speaker 1>so you could write it around kind of like a hoverboard.

0:05:25.720 --> 0:05:27.640
<v Speaker 1>I know those are terrible names for those things because

0:05:27.680 --> 0:05:29.760
<v Speaker 1>they don't hover, but you know what I'm talking about

0:05:29.800 --> 0:05:33.039
<v Speaker 1>those electronic scooters that are kind of like skateboards in

0:05:33.040 --> 0:05:35.920
<v Speaker 1>a way. Uh. They were all really popular for a

0:05:35.960 --> 0:05:39.360
<v Speaker 1>while until they started catching fire. But anyway, this one

0:05:39.560 --> 0:05:41.200
<v Speaker 1>was like a hoverboard, but you could also attach a

0:05:41.240 --> 0:05:42.880
<v Speaker 1>screen to it, and the screen would have like a

0:05:42.880 --> 0:05:45.159
<v Speaker 1>little simple face and turn it into an assistant robot.

0:05:45.200 --> 0:05:48.040
<v Speaker 1>It's really cute. It could respond to commands and talk

0:05:48.080 --> 0:05:51.360
<v Speaker 1>to you, and it was adorable. Didn't get a chance

0:05:51.400 --> 0:05:53.440
<v Speaker 1>to write on it, though. Actually I think I'd feel

0:05:53.480 --> 0:05:56.800
<v Speaker 1>a little conflicted stepping on something that was that adorable

0:05:57.279 --> 0:06:00.279
<v Speaker 1>and then commanding it to take me places. Uh. I

0:06:00.320 --> 0:06:02.880
<v Speaker 1>don't know how. I probably have a complicated relationship with

0:06:02.920 --> 0:06:07.360
<v Speaker 1>that kind of technology. Another thing that our team in

0:06:07.400 --> 0:06:11.880
<v Speaker 1>particular was interested in was a new Super eight camera

0:06:12.000 --> 0:06:14.760
<v Speaker 1>from Kodak. In fact, two of the guys who went

0:06:14.800 --> 0:06:17.400
<v Speaker 1>with me are from the video team, and both of them,

0:06:17.480 --> 0:06:19.719
<v Speaker 1>as soon as they saw it, thought we have to

0:06:19.720 --> 0:06:22.280
<v Speaker 1>shoot a video about this thing because it reminded us

0:06:22.279 --> 0:06:24.520
<v Speaker 1>all of our childhood and how we got into film

0:06:24.680 --> 0:06:27.559
<v Speaker 1>when we were kids, and it shoots both on film

0:06:27.600 --> 0:06:32.120
<v Speaker 1>and digital form formats, which is really neat. Also, this

0:06:32.200 --> 0:06:36.160
<v Speaker 1>gave me the opportunity to eat some crow because my

0:06:36.400 --> 0:06:39.520
<v Speaker 1>friend i As and I had done an episode of

0:06:39.560 --> 0:06:43.120
<v Speaker 1>Tech Stuff where we talked about obsolete technology, and one

0:06:43.160 --> 0:06:45.520
<v Speaker 1>of the things we talked about was eight millimeter film.

0:06:45.600 --> 0:06:47.480
<v Speaker 1>And there I was at c e S looking at

0:06:47.480 --> 0:06:52.720
<v Speaker 1>a brand new super eight camera. So that was awkward

0:06:53.000 --> 0:06:55.360
<v Speaker 1>but super cool. I really liked the design of it.

0:06:55.360 --> 0:06:58.240
<v Speaker 1>It definitely had that retro look and yet included a

0:06:58.279 --> 0:07:01.200
<v Speaker 1>lot of modern conveniences that you would find in digital

0:07:01.240 --> 0:07:04.880
<v Speaker 1>cameras these days. So it was neat. Uh. But that's

0:07:04.960 --> 0:07:06.919
<v Speaker 1>enough about ce S. There was tons of other stuff

0:07:06.960 --> 0:07:09.840
<v Speaker 1>going on. Those were the things we were specifically looking at,

0:07:09.880 --> 0:07:13.080
<v Speaker 1>but we also saw a lot of focus on wearables,

0:07:13.080 --> 0:07:16.720
<v Speaker 1>on health tech, on mental health tech, a lot of

0:07:16.760 --> 0:07:20.400
<v Speaker 1>technology meant to help you try and relax or relieve

0:07:20.480 --> 0:07:23.800
<v Speaker 1>stress or anxiety. Lots of stuff in that realm. I'm

0:07:23.800 --> 0:07:26.080
<v Speaker 1>betting we're gonna see a lot more of that this

0:07:26.200 --> 0:07:30.360
<v Speaker 1>coming year. But January seen also saw some rough news

0:07:30.440 --> 0:07:33.560
<v Speaker 1>for Twitter, which would pretty much follow throughout the rest

0:07:33.560 --> 0:07:36.040
<v Speaker 1>of the year for that company, top executives began to

0:07:36.120 --> 0:07:39.960
<v Speaker 1>jump ship and Twitter stock price struggled throughout twenty sixteen

0:07:40.000 --> 0:07:42.640
<v Speaker 1>and rallied briefly when there was talk of Twitter looking

0:07:42.720 --> 0:07:46.680
<v Speaker 1>for a buyer, but then no one stepped forward to

0:07:46.840 --> 0:07:49.680
<v Speaker 1>buy it, and the stock price began to struggle again.

0:07:49.840 --> 0:07:53.440
<v Speaker 1>So it's been pretty rough. We don't know what Twitter's

0:07:53.480 --> 0:07:57.200
<v Speaker 1>long term prospects are at this point. It's crazy because

0:07:57.240 --> 0:07:59.880
<v Speaker 1>it's still a huge platform that a lot of people

0:08:00.120 --> 0:08:02.160
<v Speaker 1>use and a lot of people depend upon it in

0:08:02.280 --> 0:08:05.920
<v Speaker 1>order to maintain their brand. But at the same time,

0:08:05.920 --> 0:08:08.640
<v Speaker 1>it's still not really a revenue generator, so it may

0:08:08.640 --> 0:08:14.120
<v Speaker 1>be that it's living on borrowed time. We'll see. Also

0:08:14.280 --> 0:08:18.440
<v Speaker 1>in January, Uber, which is always a controversial company, saw

0:08:18.560 --> 0:08:22.080
<v Speaker 1>resistance in several markets as it tried to expand services

0:08:22.120 --> 0:08:26.680
<v Speaker 1>into various countries. For example, in France, cab drivers began

0:08:26.720 --> 0:08:32.000
<v Speaker 1>to set fire to tires in protest. So yeah, Uber

0:08:32.480 --> 0:08:38.520
<v Speaker 1>definitely has seen a lot of resistance, particularly among cab

0:08:38.600 --> 0:08:42.840
<v Speaker 1>driving unions and companies in various regions where it's tried

0:08:42.880 --> 0:08:47.680
<v Speaker 1>to move in. And uh, I mean, it's it's the

0:08:47.720 --> 0:08:51.160
<v Speaker 1>sign of progress. You could argue it may not be

0:08:51.240 --> 0:08:54.160
<v Speaker 1>progress for the cab drivers, but for consumers who want

0:08:54.200 --> 0:08:57.680
<v Speaker 1>to have that choice. UH, it frequently is viewed as

0:08:57.720 --> 0:09:01.440
<v Speaker 1>progress and an early example of a problem that would

0:09:01.480 --> 0:09:04.679
<v Speaker 1>pop up throughout the year. Hackers managed to take down

0:09:04.720 --> 0:09:09.480
<v Speaker 1>power plants in the Ukraine through malware. That particular threat

0:09:09.520 --> 0:09:13.800
<v Speaker 1>was relatively easy to thwart. It wasn't something that was catastrophic,

0:09:14.360 --> 0:09:18.960
<v Speaker 1>but it certainly got people's attention. The idea that malware

0:09:19.080 --> 0:09:24.200
<v Speaker 1>could affect critical infrastructure. I mean, it's something we've known about,

0:09:24.720 --> 0:09:29.120
<v Speaker 1>but to see it actually happened was pretty sobering. Also

0:09:29.120 --> 0:09:32.120
<v Speaker 1>in January, Time Warner suffered one of the earliest security

0:09:32.120 --> 0:09:36.360
<v Speaker 1>breaches of UH. You might remember I think I called

0:09:37.160 --> 0:09:39.839
<v Speaker 1>the Year of security breaches. Well seen gave it a

0:09:39.920 --> 0:09:42.880
<v Speaker 1>run for the money. According to a Reuter's report, up

0:09:42.920 --> 0:09:46.839
<v Speaker 1>to three twenty thousand Time Warner customers had their email

0:09:46.880 --> 0:09:53.000
<v Speaker 1>passwords stolen in an attack. Lenovo in January officially ditched

0:09:53.080 --> 0:09:57.760
<v Speaker 1>the Motorola name. Lenovo had acquired Motorola Mobile from Google.

0:09:58.360 --> 0:10:01.360
<v Speaker 1>It kept the brand name motto for high end phones,

0:10:01.840 --> 0:10:05.920
<v Speaker 1>along with that bat wing m logo that Motorola made famous,

0:10:06.080 --> 0:10:11.480
<v Speaker 1>but Motorola as a mobile brand is a no more.

0:10:13.120 --> 0:10:16.000
<v Speaker 1>Early rumors in January stated that the next iPhone would

0:10:16.040 --> 0:10:20.079
<v Speaker 1>not have a headphone jack, and as we learned later

0:10:20.120 --> 0:10:22.680
<v Speaker 1>on the year, those turned out to be absolutely true.

0:10:22.760 --> 0:10:27.000
<v Speaker 1>But I'll talk about the iPhone more in the next episode,

0:10:27.280 --> 0:10:32.440
<v Speaker 1>since that did not debut until late Nielsen put out

0:10:32.520 --> 0:10:36.760
<v Speaker 1>it's twenty fifteen year in report on digital music, and

0:10:37.000 --> 0:10:40.920
<v Speaker 1>it showed that sales of digital music were down, but

0:10:41.040 --> 0:10:45.079
<v Speaker 1>streaming service subscriptions were way up, and more people were

0:10:45.200 --> 0:10:48.840
<v Speaker 1>using streaming services to access music than ever before. This

0:10:48.920 --> 0:10:53.160
<v Speaker 1>would continue to be a big story in twos and

0:10:53.280 --> 0:10:57.800
<v Speaker 1>on January, Oh man, I'm gonna have to do this

0:10:57.880 --> 0:11:01.840
<v Speaker 1>so many times. In this episode January tenth, David Bowie

0:11:01.840 --> 0:11:04.880
<v Speaker 1>passed away. So you might wonder why I talk about

0:11:04.920 --> 0:11:07.960
<v Speaker 1>David Bowie when I'm talking about technology. Well, he his

0:11:08.040 --> 0:11:12.040
<v Speaker 1>influence in popular music is tangential to technology, but he

0:11:12.120 --> 0:11:16.400
<v Speaker 1>was also heavily influenced by and subsequently became an influencer

0:11:16.600 --> 0:11:19.880
<v Speaker 1>of science fiction, which in turn has a very close

0:11:19.920 --> 0:11:25.320
<v Speaker 1>relationship with technology. So seeing the news about him passing

0:11:25.360 --> 0:11:30.440
<v Speaker 1>away so shortly after his final album came out was

0:11:30.640 --> 0:11:36.400
<v Speaker 1>really sobering and would become one of many stories of

0:11:36.800 --> 0:11:41.400
<v Speaker 1>beloved figures in pop culture as well as technology who

0:11:41.600 --> 0:11:46.360
<v Speaker 1>we lost in So let's move on to February, which,

0:11:46.960 --> 0:11:50.000
<v Speaker 1>at least, if nothing else, has the benefit of being

0:11:50.040 --> 0:11:54.760
<v Speaker 1>the shortest month in the tech world. Was a buzz

0:11:54.840 --> 0:11:58.920
<v Speaker 1>in February about startups competing to bring Elon Musk's hyper

0:11:58.960 --> 0:12:04.840
<v Speaker 1>loop proposal, which he first unveiled back in a Reality Now.

0:12:04.880 --> 0:12:09.240
<v Speaker 1>One of those companies was called hyper Loop Technologies and

0:12:09.320 --> 0:12:12.840
<v Speaker 1>later hyper Loop One, and that became ground zero for

0:12:13.040 --> 0:12:17.280
<v Speaker 1>serious drama among its co founders. One of those co founders,

0:12:17.640 --> 0:12:22.040
<v Speaker 1>formerly named Kevin Brogan now known as Brogan Bam Brogan

0:12:23.160 --> 0:12:26.760
<v Speaker 1>and no, that's not a joke, would be forced out

0:12:26.800 --> 0:12:29.880
<v Speaker 1>of the company. He was essentially ousted from the company

0:12:29.920 --> 0:12:33.880
<v Speaker 1>he co founded, and he would later on sue that company.

0:12:34.280 --> 0:12:38.800
<v Speaker 1>The company would then counter sue Brogan bam Brogan, saying

0:12:38.800 --> 0:12:43.240
<v Speaker 1>that he was passing off untruths that he was slandering

0:12:43.400 --> 0:12:46.679
<v Speaker 1>the company. Uh. For one thing, Bam Brogan said that

0:12:46.800 --> 0:12:50.880
<v Speaker 1>another executive at the company had at one point attempted

0:12:50.920 --> 0:12:55.440
<v Speaker 1>to intimidate him by laying a noose on his desk.

0:12:56.800 --> 0:13:01.200
<v Speaker 1>Doesn't sound like a very healthy corporate culture if true. Uh.

0:13:01.600 --> 0:13:05.559
<v Speaker 1>Eventually those lawsuits were settled out of court. So look

0:13:05.600 --> 0:13:07.800
<v Speaker 1>forward to a future tech Stuff episode where I'm going

0:13:07.840 --> 0:13:11.040
<v Speaker 1>to look at that whole story in much greater detail

0:13:11.080 --> 0:13:14.880
<v Speaker 1>in the future. I think it's too crazy not to.

0:13:15.120 --> 0:13:19.400
<v Speaker 1>It's something that I really want to explore. Also in February,

0:13:19.800 --> 0:13:23.199
<v Speaker 1>Nature dot Com ran an article stating that the semiconductor

0:13:23.240 --> 0:13:27.800
<v Speaker 1>industry would formally announce it would no longer strive to

0:13:27.880 --> 0:13:30.680
<v Speaker 1>keep up with Moore's Law. Now. I know most of

0:13:30.679 --> 0:13:32.600
<v Speaker 1>you know this, but just in case some of you

0:13:32.640 --> 0:13:36.960
<v Speaker 1>aren't unfamiliar, Moore's Laws really about an observation that a

0:13:36.960 --> 0:13:39.960
<v Speaker 1>man named Gordon Moore made. He's a co founder of Intel.

0:13:40.040 --> 0:13:44.560
<v Speaker 1>He made it several decades ago about the tendency for

0:13:44.679 --> 0:13:48.559
<v Speaker 1>the number of discrete components on a semiconductor chip to

0:13:48.800 --> 0:13:52.520
<v Speaker 1>double every two years or so. And by discrete components,

0:13:52.520 --> 0:13:56.480
<v Speaker 1>we're really talking about transistors. Now. The important thing to

0:13:56.480 --> 0:13:59.480
<v Speaker 1>remember about this, as always, is that this was more

0:13:59.559 --> 0:14:04.000
<v Speaker 1>or less observation about the financial viability of adding more

0:14:04.040 --> 0:14:08.240
<v Speaker 1>transistors to a semiconductor. It wasn't that there was some

0:14:08.400 --> 0:14:12.880
<v Speaker 1>magical law dictating this, but rather that the economy of

0:14:12.920 --> 0:14:18.000
<v Speaker 1>scale and the improvement in UH in manufacturing technologies would

0:14:18.000 --> 0:14:19.920
<v Speaker 1>allow for this to happen, and that there would be

0:14:19.960 --> 0:14:25.600
<v Speaker 1>a demand for more powerful semiconductors and microprocessors um and

0:14:25.720 --> 0:14:28.640
<v Speaker 1>as a result, uh, well not as a result. But

0:14:28.880 --> 0:14:31.000
<v Speaker 1>it turns out this has been a true observation and

0:14:31.040 --> 0:14:33.160
<v Speaker 1>a lot of companies have been striving to keep it

0:14:33.240 --> 0:14:37.760
<v Speaker 1>true over the years, and we've sort of fudged with

0:14:37.800 --> 0:14:41.240
<v Speaker 1>the definition a bit. Looking at it more as every

0:14:41.240 --> 0:14:46.560
<v Speaker 1>two years microprocessors essentially double in processing power, maybe not

0:14:46.680 --> 0:14:50.280
<v Speaker 1>necessarily in components or transistors, but in the ability to

0:14:50.400 --> 0:14:56.680
<v Speaker 1>actually process information. According to this report, however, the semiconductor

0:14:56.720 --> 0:14:59.400
<v Speaker 1>industry is essentially ready to give up on that, saying

0:14:59.440 --> 0:15:03.200
<v Speaker 1>it is no longer feasible to try and keep Moore's

0:15:03.280 --> 0:15:07.400
<v Speaker 1>law active. And this is because of two different things.

0:15:08.760 --> 0:15:12.160
<v Speaker 1>One of the factors that is a problem when you're

0:15:12.160 --> 0:15:15.720
<v Speaker 1>talking about sustaining More's law is that the smaller the

0:15:15.720 --> 0:15:19.880
<v Speaker 1>components get, the more they're affected by quantum mechanics. One

0:15:19.920 --> 0:15:23.440
<v Speaker 1>of the aspects of quantum mechanics is something called electron tunneling,

0:15:23.720 --> 0:15:25.960
<v Speaker 1>and you can really think of it in this way.

0:15:26.080 --> 0:15:30.520
<v Speaker 1>Electrons have a probability to exist in any given location

0:15:30.680 --> 0:15:34.240
<v Speaker 1>around uh, kind of like a cloud. Think of it like,

0:15:34.760 --> 0:15:37.240
<v Speaker 1>you can't really dictate exactly where the electron is going

0:15:37.280 --> 0:15:39.280
<v Speaker 1>to be. It's gonna be within a cloud, and there's

0:15:39.280 --> 0:15:42.040
<v Speaker 1>a probability for it to be anywhere inside that cloud.

0:15:42.800 --> 0:15:46.000
<v Speaker 1>If that cloud were to overlap a gate like a

0:15:46.040 --> 0:15:50.320
<v Speaker 1>transistor gate, then that means there is a probability, however small,

0:15:50.920 --> 0:15:53.560
<v Speaker 1>that the electron could be on the opposite side of

0:15:53.560 --> 0:15:56.000
<v Speaker 1>the gate that it's supposed to be on. And if

0:15:56.000 --> 0:15:59.520
<v Speaker 1>there is a probability, that means sometimes it happens that way.

0:15:59.560 --> 0:16:03.440
<v Speaker 1>So when you make these components smaller and smaller and smaller,

0:16:03.440 --> 0:16:06.320
<v Speaker 1>it becomes more challenging to figure out the materials you

0:16:06.360 --> 0:16:09.560
<v Speaker 1>need and the architecture you need to prevent electron tunneling

0:16:09.600 --> 0:16:11.800
<v Speaker 1>from becoming a big problem, because if you can't control

0:16:11.800 --> 0:16:15.200
<v Speaker 1>the flow of electrons, you can't really have logic gates.

0:16:15.800 --> 0:16:19.080
<v Speaker 1>Otherwise you're gonna have errors passed through and then you

0:16:19.200 --> 0:16:23.640
<v Speaker 1>just keep having mistakes pop up and your programs won't run.

0:16:25.080 --> 0:16:27.840
<v Speaker 1>The other issue is that the more components you cram

0:16:27.880 --> 0:16:31.160
<v Speaker 1>onto a chip, the more heat it generates, and in general,

0:16:31.200 --> 0:16:35.120
<v Speaker 1>heat and electronics don't work so well together, so trying

0:16:35.120 --> 0:16:39.800
<v Speaker 1>to manage heat becomes a bigger and bigger challenge. Anyway,

0:16:40.160 --> 0:16:43.120
<v Speaker 1>it looks like we're getting towards the end of Moore's

0:16:43.200 --> 0:16:47.320
<v Speaker 1>law using conventional semiconductor chips. That doesn't mean we won't

0:16:47.320 --> 0:16:50.200
<v Speaker 1>come up with some alternative, but it may mean that

0:16:50.560 --> 0:16:54.200
<v Speaker 1>we'll see progress slow in the short term as we

0:16:54.240 --> 0:17:01.000
<v Speaker 1>start to explore other ways of increasing that processing power. Now,

0:17:01.040 --> 0:17:05.280
<v Speaker 1>one of the biggest stories of in tech began in February.

0:17:06.160 --> 0:17:09.560
<v Speaker 1>That's when the FBI and Apple got into a real

0:17:09.640 --> 0:17:13.160
<v Speaker 1>tiff with one another. In February, a court case made

0:17:13.200 --> 0:17:16.800
<v Speaker 1>headlines when the FBI pursued an order against Apple to

0:17:16.960 --> 0:17:20.320
<v Speaker 1>force the company to deactivate a feature on the iPhone

0:17:20.320 --> 0:17:23.760
<v Speaker 1>five C, and the key point was the FBI wanted

0:17:23.800 --> 0:17:28.200
<v Speaker 1>to be able to deactivate the feature that would erase

0:17:28.400 --> 0:17:32.679
<v Speaker 1>and an encryption key after ten failed password attempts. In

0:17:32.720 --> 0:17:37.600
<v Speaker 1>other words, you lock your iPhone, use a password to

0:17:37.680 --> 0:17:40.320
<v Speaker 1>unlock it. If someone else gets hold of your phone

0:17:40.880 --> 0:17:44.560
<v Speaker 1>and tries brute force attacks to unlock your phone after

0:17:44.960 --> 0:17:50.240
<v Speaker 1>ten failed attempts, the key that would decrypt all the

0:17:50.280 --> 0:17:53.440
<v Speaker 1>information on your phone would delete itself, and then you

0:17:53.440 --> 0:17:57.160
<v Speaker 1>would have an even harder time being able to decrypt

0:17:57.240 --> 0:17:59.359
<v Speaker 1>that information like you could you might be able to

0:17:59.359 --> 0:18:03.040
<v Speaker 1>finally get access to it, but it would all be gibberish,

0:18:03.040 --> 0:18:05.120
<v Speaker 1>and then you would have to go through the process

0:18:05.119 --> 0:18:09.560
<v Speaker 1>of trying to decrypt the information. Now, the phone in

0:18:09.720 --> 0:18:13.640
<v Speaker 1>question belonged to a couple that committed the December two

0:18:13.680 --> 0:18:17.520
<v Speaker 1>thousand and fifteen attack in San Bernardino, California, which resulted

0:18:17.520 --> 0:18:21.560
<v Speaker 1>in fourteen deaths and twenty two serious injuries. So there

0:18:21.600 --> 0:18:25.720
<v Speaker 1>was a very emotional case and very politically charged, and

0:18:25.760 --> 0:18:29.119
<v Speaker 1>it also brought up serious questions about security, privacy and

0:18:29.160 --> 0:18:34.359
<v Speaker 1>the boundaries of law. Apple resisted the FBI's requests, and

0:18:34.440 --> 0:18:37.360
<v Speaker 1>later in March, the FBI claimed it had found another

0:18:37.400 --> 0:18:42.080
<v Speaker 1>way to reach the security without Apple's participation. The Washington

0:18:42.160 --> 0:18:46.520
<v Speaker 1>Post would later report in April that professional hackers had

0:18:46.560 --> 0:18:50.359
<v Speaker 1>sold a zero day exploit to the FBI in order

0:18:50.359 --> 0:18:53.359
<v Speaker 1>to unlock the phone. But for that month and a

0:18:53.440 --> 0:18:56.720
<v Speaker 1>half in February and and March, everyone chimed in on

0:18:56.760 --> 0:19:00.680
<v Speaker 1>the case, including representatives from Google and Microsoft and Bill

0:19:00.720 --> 0:19:04.760
<v Speaker 1>Gates himself. Now, some of them felt the FBI's request

0:19:04.359 --> 0:19:08.359
<v Speaker 1>constitute a back door into a secure system, which is

0:19:08.400 --> 0:19:11.639
<v Speaker 1>a terrible idea. It's always a terrible idea because if

0:19:11.640 --> 0:19:14.720
<v Speaker 1>you create a backdoor into a secure system, you've created

0:19:14.720 --> 0:19:19.159
<v Speaker 1>a potential vulnerability that others can exploit. Other people, however,

0:19:19.320 --> 0:19:23.840
<v Speaker 1>felt that the FBI's request was specific for one particular

0:19:23.920 --> 0:19:26.719
<v Speaker 1>phone and that nothing more would come of it, and

0:19:26.760 --> 0:19:29.240
<v Speaker 1>so therefore it would have made more sense for Apple

0:19:29.280 --> 0:19:34.560
<v Speaker 1>to acquiesce to the FBI's demands. Uh. But it ended

0:19:34.640 --> 0:19:36.840
<v Speaker 1>up being a moot point because the FBI eventually was

0:19:36.880 --> 0:19:42.439
<v Speaker 1>able to access the phone without Apple's participation. Also in February,

0:19:42.840 --> 0:19:46.240
<v Speaker 1>HTC would open up pre orders for the Vibe headset.

0:19:46.520 --> 0:19:49.879
<v Speaker 1>It's a virtual reality headset and had the goal of

0:19:49.880 --> 0:19:55.240
<v Speaker 1>shipping headsets out starting April one, and the headsets cost seven,

0:19:55.760 --> 0:19:58.680
<v Speaker 1>which does not include the beefy computer you would need

0:19:58.720 --> 0:20:02.280
<v Speaker 1>to run the software the HTC Vibe uses at a

0:20:02.359 --> 0:20:05.280
<v Speaker 1>decent clip. But the Vibe is pretty cool and he

0:20:05.400 --> 0:20:09.439
<v Speaker 1>uses external sensors called lighthouses to provide additional tracking and

0:20:09.520 --> 0:20:13.520
<v Speaker 1>orientation station data, which means you can actually move around

0:20:14.200 --> 0:20:18.880
<v Speaker 1>inside a physical space while the the things you see

0:20:18.920 --> 0:20:22.600
<v Speaker 1>and here would be within a virtual space. And that's

0:20:22.640 --> 0:20:24.800
<v Speaker 1>pretty neat. I actually like it a lot. I got

0:20:24.840 --> 0:20:27.240
<v Speaker 1>to try it out not too long ago, and I

0:20:27.359 --> 0:20:33.119
<v Speaker 1>really like the htc vive experience in UH In February,

0:20:33.200 --> 0:20:37.880
<v Speaker 1>Joshua Browder would launch a bot that can contest parking

0:20:37.880 --> 0:20:41.440
<v Speaker 1>tickets in the United Kingdom. So Browner has created a

0:20:41.440 --> 0:20:45.560
<v Speaker 1>few algorithms that work really well within structured environments, things

0:20:45.600 --> 0:20:49.480
<v Speaker 1>where you have a limited number of choices and there

0:20:49.520 --> 0:20:51.560
<v Speaker 1>are you know, different pathways. You can almost think of

0:20:51.560 --> 0:20:55.320
<v Speaker 1>it as choose your own adventure, and online forms like

0:20:55.400 --> 0:20:57.560
<v Speaker 1>the ones you would use to contest a parking ticket

0:20:57.760 --> 0:21:02.479
<v Speaker 1>in the UK fit that bill. So the AI can

0:21:02.480 --> 0:21:05.879
<v Speaker 1>actually argue on behalf of the person ticketed, and they

0:21:06.080 --> 0:21:09.600
<v Speaker 1>actually has a decent chance of success for contesting tickets

0:21:09.640 --> 0:21:15.840
<v Speaker 1>assuming that you have a valid case. So essentially, people

0:21:15.840 --> 0:21:17.840
<v Speaker 1>who would receive a parking ticket that they felt was

0:21:17.920 --> 0:21:22.200
<v Speaker 1>unfair could go through use this AI. The AI would

0:21:22.200 --> 0:21:25.399
<v Speaker 1>fill out all of the paperwork necessary based on a

0:21:25.400 --> 0:21:27.919
<v Speaker 1>few questions that would ask the person to fill in

0:21:27.960 --> 0:21:30.080
<v Speaker 1>a little bit of information and then it would take

0:21:30.119 --> 0:21:32.320
<v Speaker 1>care of all the forms, send the forms to the

0:21:32.520 --> 0:21:36.280
<v Speaker 1>appropriate office, and often that was enough to get the

0:21:36.280 --> 0:21:40.000
<v Speaker 1>ticket thrown out. So pretty cool use of AI, and

0:21:40.040 --> 0:21:45.040
<v Speaker 1>it shows that if you have a very structured system,

0:21:45.119 --> 0:21:49.080
<v Speaker 1>AI can navigate it pretty well. The more unstructured the

0:21:49.080 --> 0:21:51.520
<v Speaker 1>system is the more challenging it is for AI to

0:21:51.600 --> 0:21:55.760
<v Speaker 1>be able to complete a task successfully. But something like

0:21:55.840 --> 0:22:00.760
<v Speaker 1>a government bureaucracy is, by its very nature very a structured,

0:22:01.080 --> 0:22:02.600
<v Speaker 1>so it turned out to be a good use for

0:22:02.680 --> 0:22:08.200
<v Speaker 1>AI around that time. In February, consumer advocacy groups, advertisers,

0:22:08.200 --> 0:22:12.919
<v Speaker 1>and content companies began to butt heads over online advertising

0:22:13.000 --> 0:22:16.720
<v Speaker 1>and ad blockers, and since then we've seen cases of

0:22:16.760 --> 0:22:21.800
<v Speaker 1>advocacy groups arguing that anti ad blocking strategies amount to

0:22:21.800 --> 0:22:25.800
<v Speaker 1>an invasion of privacy, meaning that if a web browser

0:22:26.160 --> 0:22:28.440
<v Speaker 1>or a website rather is telling you, hey, I see

0:22:28.480 --> 0:22:33.359
<v Speaker 1>that you're using ad blocking software, then the advocacy groups

0:22:33.480 --> 0:22:35.720
<v Speaker 1>argue that's an invasion of privacy on the part of

0:22:35.760 --> 0:22:39.720
<v Speaker 1>the person browsing that web page. Uh. Content creators, on

0:22:39.760 --> 0:22:41.960
<v Speaker 1>the other hand, say well, we have to make money

0:22:42.080 --> 0:22:45.840
<v Speaker 1>or else we can't create content. If we don't make money,

0:22:45.960 --> 0:22:48.440
<v Speaker 1>then we can't afford to pay people to make the content,

0:22:48.600 --> 0:22:50.600
<v Speaker 1>we can't afford to pay people to host the content,

0:22:51.400 --> 0:22:54.399
<v Speaker 1>and the content goes away. So it's a complicated issue,

0:22:55.520 --> 0:22:56.919
<v Speaker 1>and there are a lot of people who have valid

0:22:56.920 --> 0:23:00.280
<v Speaker 1>points on both sides. Um and a lot of people

0:23:00.320 --> 0:23:03.399
<v Speaker 1>are making very emotional arguments in order to try and

0:23:03.440 --> 0:23:06.840
<v Speaker 1>support their side of it um. But as for my

0:23:06.880 --> 0:23:10.040
<v Speaker 1>own personal opinion, it's complicated. I work in a in

0:23:10.119 --> 0:23:14.520
<v Speaker 1>an industry where I want to make a living, which

0:23:14.560 --> 0:23:18.720
<v Speaker 1>means I want to have revenue coming in so that

0:23:18.760 --> 0:23:23.760
<v Speaker 1>I can, you know, get get paid. So on certain levels,

0:23:23.760 --> 0:23:26.959
<v Speaker 1>I definitely think online advertising is necessary. I think there

0:23:26.960 --> 0:23:29.199
<v Speaker 1>are good ways and bad ways to implement it, and

0:23:29.240 --> 0:23:32.320
<v Speaker 1>I've seen plenty of bad ways, and I much prefer

0:23:32.640 --> 0:23:36.879
<v Speaker 1>the non intrusive good ways. But it is a complicated landscape.

0:23:38.200 --> 0:23:41.720
<v Speaker 1>At the end of February, Microsoft began taking pre orders

0:23:41.840 --> 0:23:45.600
<v Speaker 1>for the Hollow Lens, it's augmented reality headset. Now these

0:23:45.600 --> 0:23:49.439
<v Speaker 1>were for developer editions of the headset, so they weren't

0:23:49.440 --> 0:23:51.680
<v Speaker 1>meant to be a consumer product, which is a good

0:23:51.680 --> 0:23:56.160
<v Speaker 1>thing because they cost three thousand dollars a pop, expensive

0:23:56.320 --> 0:23:59.560
<v Speaker 1>for an augmented reality headset. But again it was more

0:23:59.640 --> 0:24:03.159
<v Speaker 1>meant as a developer tool, not as something for the

0:24:03.200 --> 0:24:06.520
<v Speaker 1>average consumer, and in fact, we may never see a

0:24:06.560 --> 0:24:09.760
<v Speaker 1>consumer version of the Hollow Lens ever offered. It may

0:24:09.760 --> 0:24:14.280
<v Speaker 1>be that the augmented reality applications that the Hollow Lens

0:24:14.359 --> 0:24:17.639
<v Speaker 1>can support will end up finding their way into other products,

0:24:18.000 --> 0:24:21.320
<v Speaker 1>but not specifically a consumer version of the hollow lens.

0:24:21.359 --> 0:24:24.760
<v Speaker 1>That's a possibility. All Right, We've got a lot more

0:24:24.760 --> 0:24:27.800
<v Speaker 1>to talk about with two thousand and sixteen, but before

0:24:27.800 --> 0:24:30.520
<v Speaker 1>we jump into that, let's take a quick break to

0:24:30.600 --> 0:24:42.440
<v Speaker 1>thank our sponsor. Alright, we're back, and that means we're

0:24:42.480 --> 0:24:46.560
<v Speaker 1>moving into March two thousand and sixteen. That's when south

0:24:46.600 --> 0:24:50.320
<v Speaker 1>By Southwest happened and how Stuff Works was there. We

0:24:50.440 --> 0:24:53.159
<v Speaker 1>ended up having several panels at south By Southwest. We

0:24:53.760 --> 0:24:57.320
<v Speaker 1>hosted several events in a house that was rented by

0:24:57.840 --> 0:25:00.840
<v Speaker 1>the Atlanta Chamber of Commerce, and it was a pretty

0:25:00.880 --> 0:25:03.760
<v Speaker 1>interesting experience. We also got to see a lot of

0:25:03.840 --> 0:25:09.520
<v Speaker 1>cool companies talk about really cutting edge ideas, particularly in

0:25:09.640 --> 0:25:13.359
<v Speaker 1>areas like artificial intelligence and autonomous cars and lots of

0:25:13.400 --> 0:25:20.800
<v Speaker 1>other uh tangential technological areas. Shortly after south By Southwest ended,

0:25:21.280 --> 0:25:24.919
<v Speaker 1>the city of Austin made some demands of Uber and Left,

0:25:25.520 --> 0:25:29.400
<v Speaker 1>specifically about background checks and some other issues that affect

0:25:29.480 --> 0:25:36.879
<v Speaker 1>drivers now. Uber and Left weren't really keen on those demands,

0:25:37.880 --> 0:25:39.679
<v Speaker 1>and as a result, there was kind of a stalemate

0:25:39.760 --> 0:25:44.040
<v Speaker 1>between the companies and Austin, and eventually the company said

0:25:44.040 --> 0:25:47.840
<v Speaker 1>all right, we're leaving and gave their drivers about forty

0:25:47.880 --> 0:25:52.080
<v Speaker 1>eight hours notice before they left town. UH So, Uber

0:25:52.320 --> 0:25:55.880
<v Speaker 1>and Lift, we're both left without support in the city

0:25:55.880 --> 0:25:58.679
<v Speaker 1>of Austin, Texas. A lot of people say this was

0:25:58.720 --> 0:26:01.600
<v Speaker 1>a move specifically to a pressure on the state of

0:26:01.600 --> 0:26:06.560
<v Speaker 1>Texas as a whole to create a rules and regulations

0:26:06.600 --> 0:26:10.199
<v Speaker 1>that that governed the entire state, rather than having to

0:26:10.240 --> 0:26:12.879
<v Speaker 1>go through this and do it for city by city

0:26:13.000 --> 0:26:16.359
<v Speaker 1>or region by region, which would be complicated for a

0:26:16.400 --> 0:26:21.200
<v Speaker 1>company that spans multiple states to have to manage. UH.

0:26:21.240 --> 0:26:23.760
<v Speaker 1>But it made a lot of people really upset. I

0:26:23.840 --> 0:26:27.760
<v Speaker 1>listened to podcasts from folks who record out in Austin, Texas,

0:26:27.880 --> 0:26:30.879
<v Speaker 1>and while they saw both sides of the issue, the

0:26:30.920 --> 0:26:34.760
<v Speaker 1>personal impact on their lives was very apparent. Near the

0:26:34.880 --> 0:26:38.560
<v Speaker 1>end of March, the Oculus Rift was released with a

0:26:38.720 --> 0:26:43.359
<v Speaker 1>US price tag of six hundred dollars, which, again, like

0:26:43.480 --> 0:26:47.280
<v Speaker 1>the HTC Vibe, doesn't include the beefy computer. You actually

0:26:47.280 --> 0:26:50.199
<v Speaker 1>need to run the VR software at a level that's acceptable.

0:26:51.119 --> 0:26:55.480
<v Speaker 1>A new VR system with headset is closer to about

0:26:55.920 --> 0:26:59.160
<v Speaker 1>one thousand, nine hundred dollars as a as a starting point,

0:26:59.600 --> 0:27:05.919
<v Speaker 1>So about PC with the six D dollar headset. Uh,

0:27:06.000 --> 0:27:07.919
<v Speaker 1>there are those who argue you could get away with

0:27:08.320 --> 0:27:12.359
<v Speaker 1>a less expensive PC. You don't necessarily need the cutting

0:27:12.440 --> 0:27:17.920
<v Speaker 1>edge GPUs to run VR, but many people advocate for

0:27:18.920 --> 0:27:21.960
<v Speaker 1>close to cutting edge technology so that you don't run

0:27:21.960 --> 0:27:25.280
<v Speaker 1>into any choppiness or problems when it's rendering to the

0:27:25.359 --> 0:27:30.879
<v Speaker 1>virtual reality headset. And Uh that high price and a

0:27:30.920 --> 0:27:34.800
<v Speaker 1>limited game library would keep VR and kind of a

0:27:34.920 --> 0:27:39.040
<v Speaker 1>niche market for most often. Same thing is true for

0:27:39.240 --> 0:27:43.800
<v Speaker 1>HTC VIVE. I mean, these systems are expensive, and I

0:27:43.880 --> 0:27:47.680
<v Speaker 1>don't think that the killer app has been created yet

0:27:48.080 --> 0:27:51.000
<v Speaker 1>for virtual reality. Not something that's going to convince people

0:27:51.440 --> 0:27:54.639
<v Speaker 1>that it is a must have piece of technology in

0:27:54.680 --> 0:27:58.639
<v Speaker 1>their homes. Maybe we'll see that in Seen, but it

0:27:58.720 --> 0:28:03.000
<v Speaker 1>hasn't happened yet. In When He's Sixteen. Also in March,

0:28:03.160 --> 0:28:07.440
<v Speaker 1>Ray Tomlinson, who is credited as the inventor of email

0:28:07.600 --> 0:28:12.720
<v Speaker 1>passed Away. It was Tomlinson who decided that email addresses

0:28:12.760 --> 0:28:16.679
<v Speaker 1>would consist of a person's name or handle, and then

0:28:16.880 --> 0:28:20.280
<v Speaker 1>the name of the machine that they were using, and

0:28:20.320 --> 0:28:22.560
<v Speaker 1>that the two would be separated from each other with

0:28:22.720 --> 0:28:26.000
<v Speaker 1>the AT symbol. Tomlinson said it was the only preposition

0:28:26.080 --> 0:28:31.160
<v Speaker 1>on the keyboard, so that's kind of interesting. In March,

0:28:31.320 --> 0:28:35.479
<v Speaker 1>Deep Minds Alpha Go AI would end up going up

0:28:35.520 --> 0:28:41.240
<v Speaker 1>against Go Champion player Human Go Champion player Lee C

0:28:41.480 --> 0:28:44.880
<v Speaker 1>Doll in a series of five games, and the AI

0:28:45.040 --> 0:28:48.800
<v Speaker 1>won four out of the five matches. So Go was

0:28:48.800 --> 0:28:51.480
<v Speaker 1>one of those holdout games in which humans were still

0:28:52.160 --> 0:28:56.880
<v Speaker 1>better than machines at least championship level. Humans were better

0:28:56.920 --> 0:29:01.040
<v Speaker 1>than machines. But it's no Go, no Mo. Machines are

0:29:01.080 --> 0:29:05.760
<v Speaker 1>beating us at everything, Dylan smirked, in case you could

0:29:05.800 --> 0:29:09.360
<v Speaker 1>hear it. The FCC created new rules in March limiting

0:29:09.400 --> 0:29:13.280
<v Speaker 1>the data Internet service providers can use for marketing purposes.

0:29:13.600 --> 0:29:18.760
<v Speaker 1>The telecom companies objected to that ruling, of course, and

0:29:18.880 --> 0:29:22.360
<v Speaker 1>said that that would limit their ability way beyond what

0:29:22.440 --> 0:29:24.840
<v Speaker 1>other companies could do. So what they were saying the

0:29:24.880 --> 0:29:28.880
<v Speaker 1>I s p s were saying, hey, brow web web services.

0:29:28.920 --> 0:29:34.560
<v Speaker 1>Web sites like Google or Amazon can gather a lot

0:29:34.600 --> 0:29:38.360
<v Speaker 1>of information about people through their behaviors, So why are

0:29:38.360 --> 0:29:42.479
<v Speaker 1>we being punished when companies like Google and Amazon aren't

0:29:42.560 --> 0:29:46.600
<v Speaker 1>being punished? And the f c C said, well, that's

0:29:46.640 --> 0:29:50.400
<v Speaker 1>because we don't govern what companies like Google and Amazon do.

0:29:50.520 --> 0:29:54.280
<v Speaker 1>They're overseen by the Federal Trade commission the f TC,

0:29:55.160 --> 0:29:57.680
<v Speaker 1>but we oversee what you do. We're the f c C,

0:29:58.760 --> 0:30:05.720
<v Speaker 1>so sorry. Sony would announce that the PlayStation VR would

0:30:05.800 --> 0:30:11.680
<v Speaker 1>launch in October with the price tag of three dollars.

0:30:12.360 --> 0:30:16.280
<v Speaker 1>If you wanted to also supplement that with the other

0:30:16.440 --> 0:30:19.040
<v Speaker 1>materials needed to make a full system, you would need

0:30:19.200 --> 0:30:22.600
<v Speaker 1>a ps camera and move controllers, which we mean you

0:30:22.600 --> 0:30:23.920
<v Speaker 1>had to pay a little bit more. I think they

0:30:23.920 --> 0:30:26.880
<v Speaker 1>had a bundle for five dollars for to move controllers,

0:30:27.280 --> 0:30:31.640
<v Speaker 1>the camera, and the PSVR headset, and in addition to that,

0:30:31.720 --> 0:30:35.080
<v Speaker 1>of course, you would also need a PlayStation four. However,

0:30:35.200 --> 0:30:38.360
<v Speaker 1>have a lot of people saying that PlayStation was ahead

0:30:38.400 --> 0:30:40.600
<v Speaker 1>of the game because even though the specs for the

0:30:40.640 --> 0:30:44.800
<v Speaker 1>ps VR are not as powerful as those on the

0:30:44.960 --> 0:30:48.880
<v Speaker 1>HTC Vibe or the Oculus Rift, lots of people already

0:30:48.920 --> 0:30:52.680
<v Speaker 1>own a PlayStation four, and since that's all you need

0:30:52.960 --> 0:30:56.960
<v Speaker 1>on the computing end to run the headset, it gave

0:30:57.240 --> 0:30:59.480
<v Speaker 1>those consumers an advantage they didn't have to go out

0:30:59.520 --> 0:31:03.160
<v Speaker 1>and buy a new gaming rig in order to run

0:31:03.280 --> 0:31:08.000
<v Speaker 1>VR programs. But on the flip side, people argued while

0:31:08.040 --> 0:31:13.480
<v Speaker 1>the experiences wouldn't be necessarily as uh as innovative or

0:31:13.520 --> 0:31:16.320
<v Speaker 1>immersive as what you would see on Oculus or Vive.

0:31:16.880 --> 0:31:20.480
<v Speaker 1>Turns out, everybody was kind of a a loser this

0:31:20.560 --> 0:31:22.920
<v Speaker 1>year in Steen when it comes to VR, no one

0:31:23.040 --> 0:31:28.200
<v Speaker 1>was able to really make great sales in including the

0:31:28.200 --> 0:31:33.960
<v Speaker 1>ps VR, so it's been a rough year for virtual reality.

0:31:34.720 --> 0:31:37.480
<v Speaker 1>Towards the end of the month, Oculus Rift headsets began

0:31:37.560 --> 0:31:41.440
<v Speaker 1>to actually ship to consumers, but there were some manufacturing

0:31:41.480 --> 0:31:45.000
<v Speaker 1>problems and some component shortages which meant a lot of

0:31:45.040 --> 0:31:48.000
<v Speaker 1>people had to wait a really long time to get

0:31:48.000 --> 0:31:52.240
<v Speaker 1>their promised gear. And more on that in a little bit. Uh.

0:31:52.400 --> 0:31:56.280
<v Speaker 1>One of my favorite stories from Sten happened in March.

0:31:56.880 --> 0:32:01.400
<v Speaker 1>That's when Microsoft launched a chat bought aimed Tay. Do

0:32:01.400 --> 0:32:05.680
<v Speaker 1>you remember Tay, Dylan? You remember Tay, right, Dylan's nodding.

0:32:06.440 --> 0:32:12.760
<v Speaker 1>Tay was not long for this world unfortunately. Uh. Tay

0:32:13.000 --> 0:32:15.840
<v Speaker 1>was kind of kind of presented in the way of

0:32:15.880 --> 0:32:22.160
<v Speaker 1>like a like a teenage female PERSONA and Ta could

0:32:22.160 --> 0:32:26.160
<v Speaker 1>communicate on various social media platforms like Twitter and a

0:32:26.160 --> 0:32:30.320
<v Speaker 1>couple of others. Within twenty four hours, Microsoft would take

0:32:30.360 --> 0:32:35.200
<v Speaker 1>Tay offline because Tay or in a little cray cray.

0:32:35.840 --> 0:32:37.400
<v Speaker 1>Part of the problem was that you could tell Tay

0:32:37.480 --> 0:32:40.320
<v Speaker 1>to parrot what you said, so you can get Tay

0:32:40.400 --> 0:32:42.720
<v Speaker 1>to repeat what you said, and Tay would end up

0:32:42.760 --> 0:32:46.440
<v Speaker 1>adding little, little quirky elements to whatever you said. But

0:32:46.520 --> 0:32:49.080
<v Speaker 1>that meant that they ended up making some really awful,

0:32:49.200 --> 0:32:53.400
<v Speaker 1>awful statements, things that were racist or sexist or just

0:32:53.600 --> 0:32:58.520
<v Speaker 1>playing ugly, and then Tay would eventually start to incorporate

0:32:58.560 --> 0:33:03.680
<v Speaker 1>those into other responses is and became an incredibly absurd

0:33:03.880 --> 0:33:07.560
<v Speaker 1>internet troll within twenty four hours, and Microsoft pulled the

0:33:07.560 --> 0:33:12.040
<v Speaker 1>plug on Ta. There's a valuable lesson teaching us that

0:33:12.160 --> 0:33:15.120
<v Speaker 1>people are terrible and you should never give them anything.

0:33:16.400 --> 0:33:19.760
<v Speaker 1>Pebble would announce that it would lay off forty employees

0:33:20.080 --> 0:33:22.920
<v Speaker 1>in March. That's a big deal for Pebble because that

0:33:22.960 --> 0:33:27.720
<v Speaker 1>was about of its staff. And spoiler alert for December.

0:33:27.760 --> 0:33:29.640
<v Speaker 1>I'm gonna go ahead and tell you the Pebble story

0:33:29.680 --> 0:33:33.520
<v Speaker 1>for so this is what I mean by front loading

0:33:33.520 --> 0:33:37.560
<v Speaker 1>this episode. At the end of the year, Fitbit announced

0:33:37.600 --> 0:33:42.400
<v Speaker 1>it would acquire Pebble's software assets, so Pebble owners were

0:33:42.520 --> 0:33:46.760
<v Speaker 1>told that over time there'd be less and less support

0:33:46.920 --> 0:33:50.120
<v Speaker 1>for their devices. If you had ordered a Pebble two

0:33:50.240 --> 0:33:54.320
<v Speaker 1>or any other Pebble device after this, moment then they

0:33:54.360 --> 0:33:59.720
<v Speaker 1>were Pebbles going to refund your money. Um you Otherwise

0:33:59.760 --> 0:34:02.920
<v Speaker 1>if you if you had bought something before December seven,

0:34:03.040 --> 0:34:05.800
<v Speaker 1>you could get a refund, but army after December seven

0:34:05.840 --> 0:34:08.320
<v Speaker 1>you could get a refund, but not before. Uh. Yeah,

0:34:08.840 --> 0:34:12.960
<v Speaker 1>rough time for Pebble. So Fitbit was acquiring Pebble because

0:34:12.960 --> 0:34:18.040
<v Speaker 1>Pebbles company just couldn't support itself through sales anymore. Their

0:34:18.080 --> 0:34:20.440
<v Speaker 1>sales were not strong enough for them to be a

0:34:20.520 --> 0:34:25.880
<v Speaker 1>viable company. So uh. They were also having an issue

0:34:26.320 --> 0:34:30.080
<v Speaker 1>trying to move smart watches, which was a crowded market

0:34:30.440 --> 0:34:34.840
<v Speaker 1>in and it's not good when you have a crowded

0:34:34.880 --> 0:34:38.600
<v Speaker 1>market and you pair that with consumer apathy. There's just

0:34:38.640 --> 0:34:41.759
<v Speaker 1>not a lot of compelling reasons to go out and

0:34:41.800 --> 0:34:44.360
<v Speaker 1>buy a smart watch. If you want one, you probably

0:34:44.360 --> 0:34:48.239
<v Speaker 1>went out and bought one. But there's probably not a

0:34:48.239 --> 0:34:51.160
<v Speaker 1>lot of reasons out there that would convince someone, oh,

0:34:51.280 --> 0:34:54.200
<v Speaker 1>I need one of these if they didn't already want it.

0:34:54.600 --> 0:34:56.680
<v Speaker 1>And I say this as someone who owns a Pebble,

0:34:57.880 --> 0:35:00.960
<v Speaker 1>I I'm sad to see this news. On top of that,

0:35:01.080 --> 0:35:06.240
<v Speaker 1>Fitbit has had a really rough year. They have consistently

0:35:06.280 --> 0:35:10.400
<v Speaker 1>seen their stock price dropped throughout the year they had

0:35:10.400 --> 0:35:12.600
<v Speaker 1>a high of around fifty dollars a share and now

0:35:12.600 --> 0:35:15.239
<v Speaker 1>it's somewhere close to eight dollars a share. So it's

0:35:15.280 --> 0:35:20.280
<v Speaker 1>been rough And in fact, some people argue that Fitbit

0:35:20.360 --> 0:35:25.080
<v Speaker 1>acquiring Pebbles software assets is really the sign of two

0:35:25.239 --> 0:35:31.759
<v Speaker 1>sinking ships lashing themselves together and then sinking slightly slower. Um.

0:35:31.840 --> 0:35:34.080
<v Speaker 1>That's some of the more cynical people in the tech world.

0:35:34.120 --> 0:35:36.680
<v Speaker 1>Others say, well, maybe this is the right fit. Maybe

0:35:36.960 --> 0:35:42.239
<v Speaker 1>Fitbit using Pebble software can create really compelling wearables that

0:35:42.320 --> 0:35:45.279
<v Speaker 1>are able to turn the prospects around and maybe make

0:35:45.719 --> 0:35:49.440
<v Speaker 1>a compelling case for people who haven't bought a wearable

0:35:49.520 --> 0:35:53.000
<v Speaker 1>device to go out and do so. But it was

0:35:53.000 --> 0:35:56.880
<v Speaker 1>a really rough time for both companies. Uh, not a

0:35:56.920 --> 0:36:00.680
<v Speaker 1>great year for either Fitbit or Pebble. Maybe twin seventeen

0:36:00.920 --> 0:36:05.680
<v Speaker 1>will be different, although it's it's an odd world. I mean,

0:36:05.719 --> 0:36:08.920
<v Speaker 1>the the CEO, the founder of Pebble will not be

0:36:09.000 --> 0:36:12.280
<v Speaker 1>going with Pebble employees who are moving over to Fitbit.

0:36:12.400 --> 0:36:15.480
<v Speaker 1>He will instead be going over to an incubator company

0:36:15.520 --> 0:36:20.640
<v Speaker 1>to work on other startups. So um, rough end, especially

0:36:21.080 --> 0:36:24.520
<v Speaker 1>for someone like me who really believed in the company

0:36:24.760 --> 0:36:30.440
<v Speaker 1>and purchased a smart watch. I bought a Pebble shortly

0:36:30.560 --> 0:36:33.560
<v Speaker 1>after the Kickstarter campaign had ended. I pre ordered one

0:36:33.680 --> 0:36:36.160
<v Speaker 1>after seeing one in person at c ES a couple

0:36:36.160 --> 0:36:38.719
<v Speaker 1>of years ago, and the company was kind enough to

0:36:38.760 --> 0:36:43.640
<v Speaker 1>send me a red Kickstarter edition Pebble watch. Um, so,

0:36:43.680 --> 0:36:47.800
<v Speaker 1>I guess that's a collector's item. Now. Moving into April,

0:36:49.239 --> 0:36:53.399
<v Speaker 1>April first rolled around, and boy, oh boy, we saw

0:36:53.520 --> 0:36:58.360
<v Speaker 1>lots of gags, pranks, jokes, and attempts at humor and

0:36:58.440 --> 0:37:01.719
<v Speaker 1>people either loved it or they hated it. I know

0:37:01.800 --> 0:37:05.680
<v Speaker 1>it's a lot of tech journalists despise April Fool's Day,

0:37:05.960 --> 0:37:08.640
<v Speaker 1>largely because you can't really trust any news that gets

0:37:08.640 --> 0:37:12.600
<v Speaker 1>published on April Fool's Day, and tech journalists hate that.

0:37:13.560 --> 0:37:16.839
<v Speaker 1>I think that if you can make a fun joke,

0:37:17.440 --> 0:37:21.040
<v Speaker 1>it's great and it shows some lightheartedness. And no, not

0:37:21.160 --> 0:37:23.080
<v Speaker 1>all the jokes are a big hit. Some of them

0:37:23.080 --> 0:37:28.160
<v Speaker 1>are dorky or corny, and I think those are fine too. Uh.

0:37:28.239 --> 0:37:31.560
<v Speaker 1>Some of them are misjudged and those are more problematic,

0:37:31.600 --> 0:37:34.720
<v Speaker 1>And in fact, we saw one of those in Google

0:37:35.560 --> 0:37:41.839
<v Speaker 1>included a feature called Google's Send with in Gmail, and

0:37:41.880 --> 0:37:44.040
<v Speaker 1>that ended up being backfiring in a big way. The

0:37:44.120 --> 0:37:47.560
<v Speaker 1>send with button would send a message and include an

0:37:47.560 --> 0:37:51.120
<v Speaker 1>animated gift of a minion from the Despicable Me franchise

0:37:51.239 --> 0:37:55.160
<v Speaker 1>dropping a microphone. But some people were hitting send with

0:37:55.160 --> 0:37:58.920
<v Speaker 1>without realizing that it wasn't truly a replacement for the

0:37:58.960 --> 0:38:03.640
<v Speaker 1>send button, and so then you had folks sending messages

0:38:03.719 --> 0:38:07.160
<v Speaker 1>that really did not need to have an animated character

0:38:07.200 --> 0:38:11.680
<v Speaker 1>dropping a microphone attached to them. Imagine sending something of

0:38:12.440 --> 0:38:18.120
<v Speaker 1>sensitive nature to somebody, or you're consoling a friend who

0:38:18.200 --> 0:38:20.640
<v Speaker 1>is having a particularly rough time for one reason or another,

0:38:20.960 --> 0:38:25.560
<v Speaker 1>having a mic drop moment probably was not the most

0:38:25.600 --> 0:38:29.000
<v Speaker 1>appropriate of actions, and in fact, Google removed the feature

0:38:29.120 --> 0:38:32.640
<v Speaker 1>and even wrote that they must have they accidentally pranked

0:38:32.680 --> 0:38:40.000
<v Speaker 1>themselves in The HTC Vibe was released as promised in

0:38:40.080 --> 0:38:44.799
<v Speaker 1>early April, and uh so it started to to make

0:38:44.840 --> 0:38:49.000
<v Speaker 1>some sales and started to arrive at uh the homes

0:38:49.000 --> 0:38:51.759
<v Speaker 1>of folks who preordered it. Meanwhile, the Oculus was still

0:38:51.800 --> 0:38:57.080
<v Speaker 1>having issues with their their supply chain, so they were

0:38:57.080 --> 0:39:00.640
<v Speaker 1>still very slowly trickling out to the folks who had

0:39:00.719 --> 0:39:07.040
<v Speaker 1>ordered it. US Senators Richard Burr and Diane Feinstein drafted

0:39:07.040 --> 0:39:10.160
<v Speaker 1>a bill that would force tech companies to build in

0:39:10.360 --> 0:39:14.000
<v Speaker 1>systems allowing them to decrypt information on their own devices

0:39:14.480 --> 0:39:18.120
<v Speaker 1>that allow for encryption. So, in other words, this would

0:39:18.160 --> 0:39:23.800
<v Speaker 1>require smartphone companies that have encryption built into their phones

0:39:24.400 --> 0:39:28.279
<v Speaker 1>to have a back door for law enforcement to decrypt

0:39:28.320 --> 0:39:33.480
<v Speaker 1>a phone if necessary. Uh I mentioned earlier that backdoors

0:39:33.520 --> 0:39:36.880
<v Speaker 1>are a terrible idea. I wanna double down on that

0:39:37.000 --> 0:39:40.600
<v Speaker 1>right here. Back Doors are a terrible idea. You might

0:39:40.640 --> 0:39:44.000
<v Speaker 1>as well not have encryption at all if you are

0:39:44.000 --> 0:39:48.080
<v Speaker 1>building in back doors, because you've created a vulnerability. There's

0:39:48.120 --> 0:39:52.000
<v Speaker 1>a bright, shiny target for every single hacker out there

0:39:52.440 --> 0:39:56.280
<v Speaker 1>to exploit. And at that point, you don't need encryption

0:39:56.880 --> 0:39:59.640
<v Speaker 1>because if you if you have a lock on your door,

0:39:59.719 --> 0:40:01.799
<v Speaker 1>but you give everyone in the world a copy of

0:40:01.840 --> 0:40:06.680
<v Speaker 1>the key, what's the point of the lock. So um,

0:40:06.840 --> 0:40:15.560
<v Speaker 1>I understand that there is a political motivation to reducing

0:40:15.800 --> 0:40:21.600
<v Speaker 1>the impact of encryption, but it's I think it's misplaced

0:40:22.800 --> 0:40:27.040
<v Speaker 1>by may. This particular bill, this this version of that

0:40:27.080 --> 0:40:30.839
<v Speaker 1>bill had fizzled out. It did not get passed into law,

0:40:31.239 --> 0:40:36.400
<v Speaker 1>but in September burn Feinstein began crafting an updated version

0:40:36.960 --> 0:40:40.759
<v Speaker 1>with a narrower scope and refined language that was a

0:40:40.760 --> 0:40:44.840
<v Speaker 1>little sneaky in my opinion, Ultimately, it still requires companies

0:40:44.880 --> 0:40:47.840
<v Speaker 1>to have what amounts to a backdoor to bypass encryption,

0:40:48.760 --> 0:40:55.200
<v Speaker 1>and I still think that's completely misguided. Uh. It was

0:40:55.200 --> 0:40:57.839
<v Speaker 1>such a huge story throughout that you can really think

0:40:57.880 --> 0:40:59.720
<v Speaker 1>of that year as being the one in which lots

0:40:59.760 --> 0:41:03.960
<v Speaker 1>of lawmakers were looking for ways to make encryption effectively

0:41:04.120 --> 0:41:11.359
<v Speaker 1>illegal or at least unnecessary or irrelevant. And uh, it's

0:41:11.360 --> 0:41:17.480
<v Speaker 1>something that we continue to see happen right now. All right,

0:41:17.520 --> 0:41:20.440
<v Speaker 1>we've had another one of those dates, folks. On April one,

0:41:21.280 --> 0:41:25.320
<v Speaker 1>that's when we lost Prince. So, like David Bowie, Prince

0:41:25.400 --> 0:41:28.080
<v Speaker 1>was a huge influence in popular music. He was also

0:41:29.239 --> 0:41:33.760
<v Speaker 1>he had a very complicated relationship with technology and the internet,

0:41:33.800 --> 0:41:37.120
<v Speaker 1>in particular, in two thousand seven, he became the first

0:41:37.400 --> 0:41:43.200
<v Speaker 1>artist to release an album exclusively online. However, he also

0:41:43.760 --> 0:41:48.320
<v Speaker 1>was famous for battling lots of online platforms like YouTube

0:41:48.400 --> 0:41:54.160
<v Speaker 1>and others, uh, specifically for sharing music what he felt

0:41:54.239 --> 0:41:58.560
<v Speaker 1>was robbing him and robbing other artists of their livelihood.

0:41:59.120 --> 0:42:02.520
<v Speaker 1>He didn't want users to have the ability to upload

0:42:03.320 --> 0:42:08.040
<v Speaker 1>videos that featured music without an artist's permission, which is understandable,

0:42:08.840 --> 0:42:15.239
<v Speaker 1>but it meant that he took very powerful movements like

0:42:15.280 --> 0:42:17.880
<v Speaker 1>he made made it his mission to make sure his

0:42:17.960 --> 0:42:21.760
<v Speaker 1>music was not easily available online. He fought it tooth

0:42:21.840 --> 0:42:27.320
<v Speaker 1>and nail um. All that being said, the tech world

0:42:27.960 --> 0:42:32.279
<v Speaker 1>very much mourned his passing once news broke out about it.

0:42:33.400 --> 0:42:37.040
<v Speaker 1>Very complicated personally. Also, in declared the Internet to be dead,

0:42:38.360 --> 0:42:41.480
<v Speaker 1>but I think that's largely misinterpreted. I don't think Prince

0:42:41.560 --> 0:42:44.680
<v Speaker 1>was actually saying the Internet itself was a dead medium,

0:42:44.680 --> 0:42:49.080
<v Speaker 1>but rather for artists who want to make a living

0:42:49.480 --> 0:42:55.080
<v Speaker 1>using the Internet, as that means was not really a

0:42:55.200 --> 0:42:58.600
<v Speaker 1>viable approach. I think that's really what he was intending

0:42:59.040 --> 0:43:04.800
<v Speaker 1>by that statement. That's my own interpretation. However, in late April,

0:43:04.840 --> 0:43:07.640
<v Speaker 1>we learned that Google was creating a startup incubator in

0:43:07.760 --> 0:43:12.040
<v Speaker 1>house to help retain employees. Google had seen employees leave

0:43:12.120 --> 0:43:14.759
<v Speaker 1>the company in order to pursue their own ideas and

0:43:14.800 --> 0:43:19.680
<v Speaker 1>their create their own companies, sort of leaving with their

0:43:19.719 --> 0:43:25.040
<v Speaker 1>own personal projects. You know. Google gives every employee, or

0:43:25.040 --> 0:43:30.120
<v Speaker 1>at least used to, of their time to develop projects

0:43:30.120 --> 0:43:34.040
<v Speaker 1>that aren't directly related to their normal work, and by

0:43:34.080 --> 0:43:37.520
<v Speaker 1>creating the startup incubator, it was sort of an attempt

0:43:37.600 --> 0:43:41.080
<v Speaker 1>to keep those folks in the Google family rather than

0:43:41.320 --> 0:43:44.359
<v Speaker 1>encourage them to go out and strike out on their own,

0:43:44.400 --> 0:43:50.920
<v Speaker 1>and thus Google is bereft of their talent. Uh. Also

0:43:50.960 --> 0:43:54.840
<v Speaker 1>in April, music streaming service Title land and ex landed

0:43:54.880 --> 0:43:58.920
<v Speaker 1>an exclusive deal would Beyonce to feature her album Lemonade

0:43:58.960 --> 0:44:02.239
<v Speaker 1>for one weekend before became available on iTunes and Amazon.

0:44:03.120 --> 0:44:07.600
<v Speaker 1>This was another big story throughout not Beyonce's Lemonade in particular,

0:44:07.640 --> 0:44:09.959
<v Speaker 1>although that did make quite the stir when it came out,

0:44:10.480 --> 0:44:14.440
<v Speaker 1>but rather the way that streaming music services were trying

0:44:14.440 --> 0:44:19.400
<v Speaker 1>to differentiate themselves, largely through exclusive deals with artists. UH.

0:44:19.480 --> 0:44:22.160
<v Speaker 1>These exclusive deals tend to last a certain amount of

0:44:22.160 --> 0:44:25.640
<v Speaker 1>time and then the exclusivity ends. But Title is not

0:44:25.680 --> 0:44:27.759
<v Speaker 1>the only one that did it. Apple Music has done

0:44:27.760 --> 0:44:32.760
<v Speaker 1>it several times in sixteen, and we would see revenue

0:44:32.800 --> 0:44:37.080
<v Speaker 1>from streaming services out performing revenue from digital downloads for

0:44:37.120 --> 0:44:41.600
<v Speaker 1>the first time ever. So, in other words, more people

0:44:41.800 --> 0:44:46.600
<v Speaker 1>are subscribing to music streaming services paying for a subscription

0:44:47.080 --> 0:44:52.640
<v Speaker 1>to streaming music services than they are purchasing music online. UH.

0:44:52.840 --> 0:44:58.040
<v Speaker 1>So iTunes is seeing much lower numbers for people buying music,

0:44:58.280 --> 0:45:01.279
<v Speaker 1>but higher numbers for people using Apple Music and subscribing

0:45:01.320 --> 0:45:05.120
<v Speaker 1>to that service. I also saw a really interesting article

0:45:05.840 --> 0:45:11.120
<v Speaker 1>um that claimed at least that artists aren't really suffering

0:45:11.200 --> 0:45:15.239
<v Speaker 1>because of this, that the numbers generated through streaming are

0:45:15.320 --> 0:45:18.759
<v Speaker 1>pretty much the same as what they would be for

0:45:18.960 --> 0:45:23.879
<v Speaker 1>digital sales of that same music. So even though there's

0:45:23.920 --> 0:45:27.160
<v Speaker 1>some artists like Taylor Swift who have famously said that

0:45:27.280 --> 0:45:30.920
<v Speaker 1>streaming is robbing artists of revenue and that it's a

0:45:31.040 --> 0:45:36.560
<v Speaker 1>terrible thing, the numbers appear to not support that argument.

0:45:36.600 --> 0:45:41.360
<v Speaker 1>They they seem to say, it's it's the same amount

0:45:41.360 --> 0:45:45.080
<v Speaker 1>of money. It's a different delivery system, but artists, or

0:45:45.120 --> 0:45:49.080
<v Speaker 1>at least music labels should be making the same amount. Now,

0:45:49.120 --> 0:45:51.520
<v Speaker 1>if an artist is making less because of their agreement

0:45:51.560 --> 0:45:54.880
<v Speaker 1>with their music label, that's a different issue. That's not

0:45:54.960 --> 0:45:59.880
<v Speaker 1>so much the delivery system that's allows the contract towards

0:45:59.880 --> 0:46:03.000
<v Speaker 1>the Into April, the Supreme Court approved a change to

0:46:03.080 --> 0:46:06.960
<v Speaker 1>the federal rule of criminal procedure, and it would allow

0:46:07.000 --> 0:46:10.520
<v Speaker 1>the FBI to get permission to search computers and drives remotely.

0:46:11.120 --> 0:46:14.759
<v Speaker 1>In other words, it gave the FBI greater authority to

0:46:14.880 --> 0:46:18.360
<v Speaker 1>hack into machines. And the logic behind this decision was

0:46:18.440 --> 0:46:23.400
<v Speaker 1>that a suspect might be within one jurisdiction, but because

0:46:23.440 --> 0:46:26.480
<v Speaker 1>of the nature of the Internet. The suspect might be

0:46:26.600 --> 0:46:30.160
<v Speaker 1>using machines that are in totally different jurisdictions or entirely

0:46:30.160 --> 0:46:34.760
<v Speaker 1>different countries in some cases, and it would be impossible

0:46:35.160 --> 0:46:39.080
<v Speaker 1>for some law enforcement to get access to those machines

0:46:39.760 --> 0:46:43.120
<v Speaker 1>because they're outside of the jurisdiction. So the only alternative

0:46:43.680 --> 0:46:46.960
<v Speaker 1>is to hack into the service and look for evidence

0:46:47.040 --> 0:46:51.840
<v Speaker 1>that way. But the a c l U and companies

0:46:51.840 --> 0:46:55.239
<v Speaker 1>like Google argued against it, saying it amounts to unreasonable

0:46:55.280 --> 0:46:59.080
<v Speaker 1>search and seizure because it affects not only a suspect,

0:46:59.360 --> 0:47:02.520
<v Speaker 1>but also innocent people as well, or or not the

0:47:02.560 --> 0:47:06.000
<v Speaker 1>suspect could be innocent. It affects people not related to

0:47:06.040 --> 0:47:10.640
<v Speaker 1>the to the the investigation. And uh so this is

0:47:10.680 --> 0:47:13.640
<v Speaker 1>a complicated matter that I'm sure we will see pop

0:47:13.719 --> 0:47:18.920
<v Speaker 1>up again in all Right, we're getting close to the end.

0:47:19.120 --> 0:47:21.000
<v Speaker 1>We have one more month to get through. There's a

0:47:21.040 --> 0:47:24.440
<v Speaker 1>lot of information in it. But before I jump into May,

0:47:24.960 --> 0:47:35.839
<v Speaker 1>let's take another break to thank our sponsor. All Right,

0:47:36.360 --> 0:47:42.560
<v Speaker 1>home stretch. May. On May seven, a man named Joshua

0:47:42.640 --> 0:47:46.560
<v Speaker 1>Brown died in a car accident. He was driving a

0:47:46.719 --> 0:47:52.680
<v Speaker 1>Tesla Models and reportedly the autopilot driver assist system was

0:47:52.800 --> 0:47:57.520
<v Speaker 1>engaged and also reportedly he was traveling at nine miles

0:47:57.520 --> 0:47:59.920
<v Speaker 1>over the speed limit for the highway he was on.

0:48:01.320 --> 0:48:03.520
<v Speaker 1>The car he was in collided with the side of

0:48:03.560 --> 0:48:07.600
<v Speaker 1>a tractor trailer. Now, initial reports suggested the autopilot system

0:48:07.680 --> 0:48:11.920
<v Speaker 1>was unable to distinguish the trailer from the bright sky

0:48:11.960 --> 0:48:15.120
<v Speaker 1>that was present that day, and the car failed to

0:48:15.160 --> 0:48:18.360
<v Speaker 1>break as it should have because it didn't recognize that

0:48:18.400 --> 0:48:20.680
<v Speaker 1>there was an obstacle in the way. The radar and

0:48:20.719 --> 0:48:25.880
<v Speaker 1>the cameras didn't pick anything up. Other accidents, including another

0:48:25.920 --> 0:48:29.360
<v Speaker 1>fatal one, would follow later in the year that involved

0:48:29.680 --> 0:48:34.920
<v Speaker 1>or allegedly involved Tesla autopilot being in play. Now, Tesla's

0:48:34.960 --> 0:48:38.560
<v Speaker 1>autopilot feature is meant to be a driver augmented experience,

0:48:38.600 --> 0:48:43.440
<v Speaker 1>a driver assist feature, not a replacement for drivers, and

0:48:43.480 --> 0:48:46.520
<v Speaker 1>to enable it, drivers have to acknowledge they understand this.

0:48:46.640 --> 0:48:50.520
<v Speaker 1>They read a warning message saying as much. But this

0:48:50.719 --> 0:48:54.600
<v Speaker 1>was a rough rough year for Tesla because of that.

0:48:56.200 --> 0:49:00.080
<v Speaker 1>Later in May, a University of Michigan survey revealed that

0:49:00.200 --> 0:49:05.200
<v Speaker 1>the vast majority of people don't really want a driverless

0:49:05.239 --> 0:49:08.160
<v Speaker 1>car or want to ride in a driverless car that

0:49:08.239 --> 0:49:12.399
<v Speaker 1>doesn't have at least some sort of manual override system.

0:49:12.520 --> 0:49:14.120
<v Speaker 1>Many said they were afraid to be in a self

0:49:14.200 --> 0:49:18.719
<v Speaker 1>driving car at all, said they'd rather have control themselves,

0:49:18.760 --> 0:49:24.640
<v Speaker 1>manual control and and no self driving car elements included. Now, personally,

0:49:25.640 --> 0:49:29.239
<v Speaker 1>I hate the idea of having manual override controls in

0:49:29.280 --> 0:49:32.080
<v Speaker 1>an autonomous car. And I've said this before because it

0:49:32.120 --> 0:49:34.520
<v Speaker 1>amounts to the same thing as someone saying in the

0:49:34.520 --> 0:49:36.960
<v Speaker 1>passenger seat and reaching over and grabbing your steering wheel

0:49:37.160 --> 0:49:40.560
<v Speaker 1>or stomping on your foot to hit the accelerator or

0:49:40.600 --> 0:49:44.840
<v Speaker 1>the break. Uh, it's not safe. It's much more safe

0:49:44.880 --> 0:49:49.040
<v Speaker 1>to have a fully autonomous car, assuming that the system

0:49:49.080 --> 0:49:52.560
<v Speaker 1>has been designed properly. Obviously, you make a really crappy

0:49:52.600 --> 0:49:56.320
<v Speaker 1>autonomous car, then it's not safe. But if you're following

0:49:56.320 --> 0:50:00.279
<v Speaker 1>the best practices, it's much more safe to give troll

0:50:00.360 --> 0:50:03.680
<v Speaker 1>to the vehicle and not struggle with it. But I

0:50:03.719 --> 0:50:06.640
<v Speaker 1>also say that as someone who doesn't drive, so perhaps

0:50:06.680 --> 0:50:11.040
<v Speaker 1>I'm heavily biased. In fact, I am heavily biased. I mean,

0:50:11.040 --> 0:50:15.719
<v Speaker 1>there's no no perhaps about it. Another big story in

0:50:15.760 --> 0:50:20.120
<v Speaker 1>May um a crazy story, was that there was an

0:50:20.160 --> 0:50:24.800
<v Speaker 1>Australian businessman named Craig Wright who came forward and claimed

0:50:24.880 --> 0:50:30.680
<v Speaker 1>he was Satoshi Nakamoto a k a. The creator of bitcoin,

0:50:32.040 --> 0:50:37.640
<v Speaker 1>and well, the media essentially said, say, what can you

0:50:37.719 --> 0:50:41.400
<v Speaker 1>prove it? And Craig Wright said, boy, how do I

0:50:41.440 --> 0:50:44.839
<v Speaker 1>can prove it? Here's some cryptography for you. And then

0:50:44.880 --> 0:50:49.359
<v Speaker 1>the cryptography community said this is really lousy. And then

0:50:49.400 --> 0:50:53.439
<v Speaker 1>eventually Craig Wright removed the posts he had that quote

0:50:53.520 --> 0:50:58.760
<v Speaker 1>unquote contained the proof of his identity. A London Review

0:50:58.800 --> 0:51:02.360
<v Speaker 1>of Books investigation concluded that Right was making a baseless

0:51:02.400 --> 0:51:06.000
<v Speaker 1>claim and went so far as to suggest perhaps the

0:51:06.040 --> 0:51:10.319
<v Speaker 1>motivation for claiming to be Nakamoto was that he was

0:51:10.400 --> 0:51:15.640
<v Speaker 1>trying to make money through selling patents related to bitcoin

0:51:16.160 --> 0:51:19.040
<v Speaker 1>in order to cover other debts that he had amassed

0:51:19.200 --> 0:51:24.760
<v Speaker 1>through various business ventures. Uh. It was not a pretty

0:51:24.840 --> 0:51:30.120
<v Speaker 1>story at all, but kind of crazy. Also in May,

0:51:30.160 --> 0:51:33.120
<v Speaker 1>Oculus announced that it had it was going to create

0:51:33.160 --> 0:51:37.080
<v Speaker 1>a limited number of Oculus Rift headsets for sale at

0:51:37.560 --> 0:51:41.719
<v Speaker 1>brick and mortar Best Buy stores. They were gonna make

0:51:41.840 --> 0:51:46.360
<v Speaker 1>just a limited number available for physical purchase at these stores,

0:51:47.120 --> 0:51:52.080
<v Speaker 1>and that drove some preorder customers absolutely bonkers because they

0:51:52.080 --> 0:51:55.640
<v Speaker 1>still had not received their sets that they had pre ordered.

0:51:56.520 --> 0:52:00.200
<v Speaker 1>Oculus solution to this problem was to say, hey, if

0:52:00.239 --> 0:52:02.520
<v Speaker 1>you go and buy it at the best Buy, we

0:52:02.560 --> 0:52:06.239
<v Speaker 1>will preserve the preorder perks that come along with the

0:52:06.280 --> 0:52:09.040
<v Speaker 1>preorder set, so you'll you'll still get the perks that

0:52:09.120 --> 0:52:11.799
<v Speaker 1>you should have, but you can go and get your

0:52:11.800 --> 0:52:14.920
<v Speaker 1>set this way rather than wait for it. That did

0:52:14.920 --> 0:52:19.120
<v Speaker 1>not go over very well. Uh. I think describing the

0:52:19.160 --> 0:52:25.440
<v Speaker 1>Oculus Riffs launch as rocky or problematic is probably being generous.

0:52:25.680 --> 0:52:30.280
<v Speaker 1>It did not. It did not go very smoothly. Um,

0:52:30.320 --> 0:52:34.160
<v Speaker 1>and not all of that was necessarily Oculus's fault, but

0:52:34.239 --> 0:52:36.640
<v Speaker 1>it did not reflect well in the company when these

0:52:36.640 --> 0:52:41.680
<v Speaker 1>sort of things happened. Also in May, Radiohead fans began

0:52:41.719 --> 0:52:44.759
<v Speaker 1>to scratch their heads because the band was doing some

0:52:44.840 --> 0:52:48.520
<v Speaker 1>odd stuff. The entire Twitter and Facebook history of the

0:52:48.520 --> 0:52:52.359
<v Speaker 1>band got deleted and their web page was replaced with

0:52:52.440 --> 0:52:55.400
<v Speaker 1>a blank white page. Now all of that ended up

0:52:55.440 --> 0:52:57.360
<v Speaker 1>being part of a campaign to promote a new album,

0:52:57.400 --> 0:53:01.800
<v Speaker 1>but at the time people were wondering exactly what was up. Also,

0:53:02.160 --> 0:53:07.000
<v Speaker 1>a ten year old kid in Finland earned ten thousand

0:53:07.280 --> 0:53:12.160
<v Speaker 1>dollars because he found a flaw in Instagram's app, and

0:53:12.239 --> 0:53:15.600
<v Speaker 1>that flaw would allow him to delete any comments left

0:53:15.840 --> 0:53:20.200
<v Speaker 1>on Instagram. He alerted Facebook. He said, hey, I found

0:53:20.200 --> 0:53:24.200
<v Speaker 1>this this flaw, you need to fix it, and Facebook

0:53:24.239 --> 0:53:28.640
<v Speaker 1>said thanks and then paid him ten grand for the discovery.

0:53:29.080 --> 0:53:34.640
<v Speaker 1>So good for that kid, Ice creams on him. IBM

0:53:34.680 --> 0:53:38.479
<v Speaker 1>opened up it's quantum computing platform to researchers in May

0:53:38.640 --> 0:53:41.160
<v Speaker 1>of twenty sixteen, saying that if you want to run

0:53:41.400 --> 0:53:44.960
<v Speaker 1>quantum computing experiments on our equipment, you can. You can

0:53:45.040 --> 0:53:48.359
<v Speaker 1>use the online portal and do that. They just had

0:53:48.400 --> 0:53:50.880
<v Speaker 1>to request an invite to create experiments to run on

0:53:50.960 --> 0:53:54.719
<v Speaker 1>quantum logic gates, which is pretty cool. We still don't

0:53:54.719 --> 0:53:59.680
<v Speaker 1>know what the full potential for quantum computing is. We

0:53:59.760 --> 0:54:06.720
<v Speaker 1>know that it could absolutely transform cryptography and encryption and

0:54:06.719 --> 0:54:11.520
<v Speaker 1>and related fields, but beyond that, it's uh. There's still

0:54:11.520 --> 0:54:13.960
<v Speaker 1>a lot of questions about what quantum computing will be

0:54:14.000 --> 0:54:18.240
<v Speaker 1>great for. The Wall Street Journal would publish an article

0:54:18.280 --> 0:54:21.520
<v Speaker 1>that said LIFT and GM had entered a partnership to

0:54:21.520 --> 0:54:25.280
<v Speaker 1>start testing autonomous Chevy Bolt cars as a cab service,

0:54:26.440 --> 0:54:32.560
<v Speaker 1>aiming for a a soft launch in and Google published

0:54:32.560 --> 0:54:36.280
<v Speaker 1>a blog post explaining that researchers had been feeding romance

0:54:36.400 --> 0:54:40.440
<v Speaker 1>novels along with other materials, to artificial intelligence to help

0:54:40.640 --> 0:54:45.640
<v Speaker 1>its ability to understand conversational language. And lots of bodices

0:54:45.680 --> 0:54:49.960
<v Speaker 1>began ripping all over the place in AI Land. Actually, uh,

0:54:50.160 --> 0:54:52.359
<v Speaker 1>it makes sense when you really look into it. First

0:54:52.360 --> 0:54:55.279
<v Speaker 1>of all, it wasn't just romance novels, but that's how

0:54:55.320 --> 0:54:58.320
<v Speaker 1>it was widely reported because it was the the most

0:54:58.440 --> 0:55:01.879
<v Speaker 1>amusing part of the story. The real way to think

0:55:01.920 --> 0:55:04.879
<v Speaker 1>about this is that we humans tend to have lots

0:55:04.880 --> 0:55:07.520
<v Speaker 1>of different ways to say the same thing. Like you

0:55:07.560 --> 0:55:11.040
<v Speaker 1>can use different turns of phrase or figures of speech

0:55:11.080 --> 0:55:15.320
<v Speaker 1>in order to express the same idea a hundred different ways,

0:55:15.400 --> 0:55:19.560
<v Speaker 1>and this is difficult for computers to parse. So by

0:55:19.680 --> 0:55:26.080
<v Speaker 1>feeding romance novels, which are largely formulaic, to AI, it

0:55:26.239 --> 0:55:28.280
<v Speaker 1>kind of shows that there are lots of different ways

0:55:28.320 --> 0:55:32.400
<v Speaker 1>to say basically the same thing. If most romance novels

0:55:32.680 --> 0:55:36.640
<v Speaker 1>follow a particular formula, but they each contain their own

0:55:36.680 --> 0:55:41.200
<v Speaker 1>specific language, as created by the author, then you know

0:55:41.239 --> 0:55:44.480
<v Speaker 1>their own way of expressing these same basic ideas. It's

0:55:44.480 --> 0:55:46.359
<v Speaker 1>a good way to teach computers, Hey, there's all these

0:55:46.360 --> 0:55:49.920
<v Speaker 1>different ways to get across the same basic notion. So

0:55:49.960 --> 0:55:51.680
<v Speaker 1>it made sense if you looked at it from a

0:55:52.480 --> 0:55:55.560
<v Speaker 1>little further back than just saying, hey, they're reading a

0:55:55.560 --> 0:56:01.200
<v Speaker 1>lot of Harlequin romance books. And around that same time,

0:56:01.520 --> 0:56:05.319
<v Speaker 1>a former Facebook employee made big waves out in the

0:56:05.360 --> 0:56:08.480
<v Speaker 1>tech world by saying that Facebook as a rule was

0:56:08.560 --> 0:56:13.239
<v Speaker 1>suppressing conservative news stories from the Trending news section on Facebook,

0:56:14.480 --> 0:56:19.400
<v Speaker 1>which is partly curated by Facebook employees. Now. Facebook denied

0:56:19.640 --> 0:56:22.640
<v Speaker 1>the allegations, saying the company worked very hard to avoid

0:56:22.680 --> 0:56:27.120
<v Speaker 1>bias or prioritization of any news or philosophy over any other.

0:56:28.200 --> 0:56:32.479
<v Speaker 1>But that definitely made headlines for quite some time in

0:56:32.480 --> 0:56:38.320
<v Speaker 1>in May sixteen. Also in that time, Amazon Video Direct

0:56:38.400 --> 0:56:42.600
<v Speaker 1>launched and that allows professional content creators to use Amazon

0:56:42.640 --> 0:56:45.320
<v Speaker 1>as a video platform, and one of the launch partners

0:56:46.000 --> 0:56:49.799
<v Speaker 1>was a scrappy little company called how Stuff Works. So

0:56:49.840 --> 0:56:51.520
<v Speaker 1>if you go to Amazon Video and you search for

0:56:51.520 --> 0:56:54.000
<v Speaker 1>how Stuff Works, you'll find videos that have me and

0:56:54.040 --> 0:56:57.240
<v Speaker 1>my co workers in them. Kind of neat. You should

0:56:57.239 --> 0:57:00.960
<v Speaker 1>do that thing. If you have Amazon Video, you go

0:57:01.120 --> 0:57:06.719
<v Speaker 1>check it out. I'm on brain stuff. Instagram updated its

0:57:06.760 --> 0:57:10.319
<v Speaker 1>logo and people went nuts and ridiculed it, and now

0:57:10.600 --> 0:57:12.520
<v Speaker 1>I bet you can't even remember what the old logo

0:57:12.560 --> 0:57:17.720
<v Speaker 1>looked like. So there. Disney would close down its video

0:57:17.800 --> 0:57:21.480
<v Speaker 1>game division in May, including the Disney Infinity line of games.

0:57:21.480 --> 0:57:25.840
<v Speaker 1>And collectibles. The company decided instead that it would license

0:57:25.920 --> 0:57:30.040
<v Speaker 1>intellectual property out to other video game developers and then

0:57:30.080 --> 0:57:36.240
<v Speaker 1>they would just avoid building stuff in house Mouse House. Now,

0:57:36.320 --> 0:57:39.920
<v Speaker 1>towards the end of May, Google would have its big

0:57:39.920 --> 0:57:43.480
<v Speaker 1>event and start announcing stuff like crazy, including the Google

0:57:43.560 --> 0:57:46.840
<v Speaker 1>Home device. Google Home is Google's take on a smart

0:57:46.920 --> 0:57:51.520
<v Speaker 1>speaker with a personal digital audio assistant similar to Amazon's Echo,

0:57:52.400 --> 0:57:55.480
<v Speaker 1>and the company also introduced a messaging service called l O,

0:57:56.040 --> 0:58:00.640
<v Speaker 1>a l l O that incorporates the personal digit assistant

0:58:01.120 --> 0:58:05.440
<v Speaker 1>the audio assistant, just like Google Home does. So you

0:58:05.480 --> 0:58:08.360
<v Speaker 1>could have a text message with somebody else, a real,

0:58:08.440 --> 0:58:14.200
<v Speaker 1>live human being, and Aloe could help. Let's say that

0:58:14.240 --> 0:58:16.479
<v Speaker 1>you start having a discussion with someone about a place

0:58:16.520 --> 0:58:18.800
<v Speaker 1>you want to go and eat. Aloe might end up

0:58:18.840 --> 0:58:21.320
<v Speaker 1>pulling up open table so that you can make a reservation.

0:58:21.440 --> 0:58:25.560
<v Speaker 1>That sort of thing. It's a little creepy, can feel

0:58:25.560 --> 0:58:29.560
<v Speaker 1>a little invasive, maybe if you aren't really in the

0:58:29.600 --> 0:58:33.120
<v Speaker 1>mind to have a digital assistant kind of button and say, hey,

0:58:33.160 --> 0:58:35.080
<v Speaker 1>I see you're talking about this thing. Let me help

0:58:35.080 --> 0:58:39.400
<v Speaker 1>you out with that. But fortunately, this is a dedicated app.

0:58:39.600 --> 0:58:42.000
<v Speaker 1>It's not like it's built into all of Google services,

0:58:42.000 --> 0:58:44.520
<v Speaker 1>so you can just not download it and use it

0:58:44.560 --> 0:58:48.080
<v Speaker 1>if you'd rather avoid that sort of stuff. Google would

0:58:48.120 --> 0:58:51.040
<v Speaker 1>also show off day Dream. It's a it's a virtual

0:58:51.120 --> 0:58:54.800
<v Speaker 1>reality platform, so that makes that VR crowded space even

0:58:54.840 --> 0:58:58.920
<v Speaker 1>more crowded. And Google debuted Magenta, which is an AI

0:58:59.000 --> 0:59:01.520
<v Speaker 1>program that explores deep learning to create art in a

0:59:01.560 --> 0:59:06.280
<v Speaker 1>real trippy way. Pretty cool and weird. Um not something

0:59:06.320 --> 0:59:11.840
<v Speaker 1>I would typically associate with engineers. Towards the end of

0:59:11.880 --> 0:59:15.280
<v Speaker 1>a the Pittsburgh Tribune confirmed that Uber had begun testing

0:59:15.320 --> 0:59:20.560
<v Speaker 1>autonomous cars in Pittsburgh. Now, in those cases, you still

0:59:20.600 --> 0:59:24.560
<v Speaker 1>had someone writing in the driver's seat. They weren't completely

0:59:24.760 --> 0:59:27.320
<v Speaker 1>without a driver, but the driver. The driver was meant

0:59:27.320 --> 0:59:32.840
<v Speaker 1>to be passive unless absolutely necessary. And Uber has made

0:59:32.920 --> 0:59:37.000
<v Speaker 1>no secret that it intends to adopt autonomous car technology

0:59:37.040 --> 0:59:41.360
<v Speaker 1>as soon as that technology is mature and legal. And

0:59:42.280 --> 0:59:45.240
<v Speaker 1>that's tough because if you're a company and your employees

0:59:45.240 --> 0:59:48.880
<v Speaker 1>are largely drivers, and you're telling them, hey, your job

0:59:49.120 --> 0:59:52.760
<v Speaker 1>is limited, You've you've got a limited time span. Eventually

0:59:52.760 --> 0:59:55.720
<v Speaker 1>we're gonna replace you with a robot. It's got to

0:59:55.760 --> 1:00:00.080
<v Speaker 1>hurt employee morale, I would think. And that is it

1:00:00.720 --> 1:00:04.280
<v Speaker 1>for the first half of a little less than first half,

1:00:04.840 --> 1:00:07.720
<v Speaker 1>So join me next week for the exciting conclusion to

1:00:08.800 --> 1:00:12.280
<v Speaker 1>when I look at these stories from June through as

1:00:12.360 --> 1:00:14.320
<v Speaker 1>much of December as we are through by the time

1:00:14.360 --> 1:00:20.280
<v Speaker 1>I record it, and we'll talk about more interesting stories, triumphs,

1:00:20.320 --> 1:00:23.560
<v Speaker 1>tragedies and everything in between. If you guys have any

1:00:23.600 --> 1:00:26.640
<v Speaker 1>suggestions for future episodes, or if there's a story that

1:00:26.680 --> 1:00:28.440
<v Speaker 1>I skipped over that you think I really should have

1:00:28.440 --> 1:00:32.000
<v Speaker 1>talked about, write me let me know. The email address

1:00:32.080 --> 1:00:35.120
<v Speaker 1>is tech stuff at how stuff works dot com, or

1:00:35.160 --> 1:00:37.440
<v Speaker 1>you can drop me a line on Facebook or Twitter,

1:00:37.480 --> 1:00:39.480
<v Speaker 1>or the handle at both of those is tech Stuff

1:00:39.800 --> 1:00:43.480
<v Speaker 1>H s W. And I'll talk to you again really

1:00:43.520 --> 1:00:51.040
<v Speaker 1>soon for more on this and thousands of other topics.

1:00:51.280 --> 1:01:00.400
<v Speaker 1>Is that how stuff works dot com. Eight