WEBVTT - TechStuff and Friends Predict 2017

0:00:04.160 --> 0:00:12.000
<v Speaker 1>Get in touch with technology with tex Stuff from dot Com.

0:00:12.000 --> 0:00:15.680
<v Speaker 1>Happy New Year, everyone, I'm Jonathan Strickland and this is

0:00:15.880 --> 0:00:19.680
<v Speaker 1>tech Stuff. Today's episode is an annual tradition. It's the

0:00:19.720 --> 0:00:23.360
<v Speaker 1>one in which I make predictions about the twelve months

0:00:23.400 --> 0:00:26.480
<v Speaker 1>ahead of us. What do we have in store with

0:00:26.560 --> 0:00:30.000
<v Speaker 1>tech now? Normally I do this with a co host,

0:00:30.520 --> 0:00:32.920
<v Speaker 1>but this year I thought I'd try something a little different.

0:00:33.159 --> 0:00:35.680
<v Speaker 1>I invited a few friends to send me a prediction

0:00:35.800 --> 0:00:38.440
<v Speaker 1>or two an audio format, and so in this show,

0:00:38.640 --> 0:00:41.360
<v Speaker 1>I'll occasionally play a clip from some good friends of

0:00:41.400 --> 0:00:44.639
<v Speaker 1>mine with their insights into what two thousand and seventeen

0:00:44.720 --> 0:00:49.559
<v Speaker 1>may bring us. So let's get started, and I want

0:00:49.560 --> 0:00:51.320
<v Speaker 1>to start things off with a look ahead to c

0:00:51.520 --> 0:00:54.440
<v Speaker 1>E S two thousand seventeen. It is on the mind

0:00:54.640 --> 0:00:57.800
<v Speaker 1>right now for both me and my producer Dylan, who

0:00:57.840 --> 0:01:00.400
<v Speaker 1>is in the room with me. We literally just got

0:01:00.440 --> 0:01:04.200
<v Speaker 1>out of a meeting about c E and the stuff

0:01:04.240 --> 0:01:07.200
<v Speaker 1>what we will bring with us when we go. So

0:01:08.120 --> 0:01:11.960
<v Speaker 1>I'll be sitting through press conferences in Las Vegas by

0:01:12.000 --> 0:01:15.520
<v Speaker 1>the time this particular episode goes live. Actually Dylan might

0:01:15.520 --> 0:01:18.679
<v Speaker 1>be too, and we'll be listening to what companies plan

0:01:18.840 --> 0:01:21.640
<v Speaker 1>to bring to market in the near future, but I

0:01:21.680 --> 0:01:26.200
<v Speaker 1>am recording this episode in December two thousand sixteen, so

0:01:26.319 --> 0:01:29.760
<v Speaker 1>right now it's still a mystery to me. So here

0:01:29.760 --> 0:01:32.080
<v Speaker 1>are some of my predictions of stuff that I will

0:01:32.120 --> 0:01:35.840
<v Speaker 1>see at c E S. First of all, VR and

0:01:35.920 --> 0:01:38.160
<v Speaker 1>A are are gonna be everywhere. There's gonna be a

0:01:38.200 --> 0:01:40.600
<v Speaker 1>whole section for VR and A R at c E S,

0:01:40.640 --> 0:01:42.399
<v Speaker 1>but I would not be surprised to see it pop

0:01:42.480 --> 0:01:45.880
<v Speaker 1>up in booths throughout the show, so there'll be a

0:01:45.880 --> 0:01:50.320
<v Speaker 1>dedicated section. But then big big booths like Intel are

0:01:50.440 --> 0:01:54.000
<v Speaker 1>likely going to have these on display sony, probably with

0:01:54.080 --> 0:01:58.040
<v Speaker 1>the PlayStation VR. We're gonna see that everywhere. Plus we're

0:01:58.040 --> 0:02:01.960
<v Speaker 1>gonna see tons of smart home devices and home automation

0:02:02.320 --> 0:02:05.240
<v Speaker 1>that's also going to be omnipresent at c e S.

0:02:05.720 --> 0:02:09.360
<v Speaker 1>Driverless car technologies and related products are going to have

0:02:09.560 --> 0:02:14.400
<v Speaker 1>a big, strong showing at at c e Drones will

0:02:14.440 --> 0:02:17.560
<v Speaker 1>be everywhere and come in all sorts of shapes and sizes.

0:02:18.200 --> 0:02:20.160
<v Speaker 1>I've been playing with a Star Wars drone for the

0:02:20.240 --> 0:02:23.440
<v Speaker 1>last couple of days, irritating people and ramming it into

0:02:23.480 --> 0:02:27.120
<v Speaker 1>people's faces. It is amazing, and I think we'll also

0:02:27.120 --> 0:02:30.000
<v Speaker 1>see a lot of three sixty degree cameras at the show.

0:02:30.080 --> 0:02:32.679
<v Speaker 1>That seems to be like the new hot tech stuff

0:02:33.160 --> 0:02:36.760
<v Speaker 1>at C E S. I think three sixty degree cameras

0:02:36.800 --> 0:02:39.560
<v Speaker 1>are gonna be at a lot of different booths. We're

0:02:39.600 --> 0:02:42.119
<v Speaker 1>gonna see a lot of different approaches. You're gonna see

0:02:42.120 --> 0:02:44.760
<v Speaker 1>people claiming to have four K or eight K or

0:02:44.800 --> 0:02:49.400
<v Speaker 1>maybe even sixteen kgree cameras, So we'll explore that when

0:02:49.400 --> 0:02:52.680
<v Speaker 1>we're there. Now, I plan on recording an episode of

0:02:52.680 --> 0:02:55.400
<v Speaker 1>tech Stuff while I'm at C E S with a

0:02:55.480 --> 0:02:58.760
<v Speaker 1>certain Mr Ben Bolan as my co host, and I

0:02:58.760 --> 0:03:02.600
<v Speaker 1>think he's gonna have me on an episode of car stuff, uh,

0:03:02.600 --> 0:03:04.320
<v Speaker 1>and I will be his co host for that, So

0:03:04.400 --> 0:03:08.120
<v Speaker 1>we're gonna kind of trade shows while we're there, and

0:03:08.200 --> 0:03:09.960
<v Speaker 1>at that time, we'll see if I'm on track with

0:03:10.000 --> 0:03:14.359
<v Speaker 1>these predictions. So you'll actually hear that in next week's episode.

0:03:15.040 --> 0:03:17.440
<v Speaker 1>It's really weird to say next week's episode because I'm

0:03:17.440 --> 0:03:20.080
<v Speaker 1>recording this on December twenty one, and I won't be

0:03:20.120 --> 0:03:23.640
<v Speaker 1>recording the c S episode until early January. But for

0:03:23.680 --> 0:03:27.320
<v Speaker 1>you guys, it's like only a week past. So hello

0:03:27.440 --> 0:03:31.120
<v Speaker 1>from the past. I guess that's what I'm saying there. Anyway,

0:03:31.160 --> 0:03:33.760
<v Speaker 1>that's the e So let's move on. How about a

0:03:33.760 --> 0:03:38.440
<v Speaker 1>prediction about Apple. So two thousand seventeen, we'll mark the

0:03:38.520 --> 0:03:43.480
<v Speaker 1>tenth anniversary of the debut of the iPhone. Steve Jobs

0:03:43.680 --> 0:03:47.000
<v Speaker 1>debut the iPhone in two thousand seven, So because of that,

0:03:47.240 --> 0:03:50.280
<v Speaker 1>I think the next iPhone, the next generation, whatever it

0:03:50.360 --> 0:03:54.520
<v Speaker 1>might be called, will be a bigger and bolder departure

0:03:54.920 --> 0:03:59.360
<v Speaker 1>from the current design than the last couple of generations were. Um,

0:03:59.400 --> 0:04:02.119
<v Speaker 1>I think Apple really needs to capitalize on this tenth

0:04:02.200 --> 0:04:05.280
<v Speaker 1>year anniversary. So I think we're gonna see some really

0:04:05.320 --> 0:04:08.720
<v Speaker 1>bold choices, hopefully that won't involve getting rid of more

0:04:09.080 --> 0:04:12.520
<v Speaker 1>features like the headphone jack. But I also think that

0:04:12.560 --> 0:04:15.520
<v Speaker 1>two is the year in which Apple gives us at

0:04:15.600 --> 0:04:19.440
<v Speaker 1>least a sneak peek at their autonomous car technology. Now

0:04:19.480 --> 0:04:22.960
<v Speaker 1>they're they're not building autonomous cars from what we understand,

0:04:22.960 --> 0:04:27.159
<v Speaker 1>they're building systems, autonomous car systems that would be or

0:04:27.160 --> 0:04:29.640
<v Speaker 1>at least things that would pair with autonomous car systems.

0:04:30.200 --> 0:04:32.200
<v Speaker 1>Uh So I think we might actually get a sneak

0:04:32.240 --> 0:04:34.320
<v Speaker 1>peek of that next year. That's kind of a long

0:04:34.360 --> 0:04:38.240
<v Speaker 1>shot because Apple is not known for showing their technology early.

0:04:39.160 --> 0:04:41.720
<v Speaker 1>They're much more likely to wait until it's ready to go,

0:04:43.000 --> 0:04:45.560
<v Speaker 1>maybe show it off a month in advance of launching it.

0:04:46.640 --> 0:04:49.120
<v Speaker 1>But I think next year is going to be a

0:04:49.120 --> 0:04:51.880
<v Speaker 1>big year for Apple, or this year for you guys

0:04:51.880 --> 0:04:55.920
<v Speaker 1>listening to this now. Next year from when I'm recording it,

0:04:55.920 --> 0:04:57.800
<v Speaker 1>it's gonna be a huge year for Apple, and I

0:04:57.880 --> 0:05:00.760
<v Speaker 1>think they need to have something that is really going

0:05:00.800 --> 0:05:03.520
<v Speaker 1>to blow people away, and I think autonomous car technology

0:05:03.520 --> 0:05:06.279
<v Speaker 1>would be the way to do it. Unless they finally

0:05:06.320 --> 0:05:09.160
<v Speaker 1>came out with an Apple branded television, that might help too.

0:05:10.120 --> 0:05:14.240
<v Speaker 1>And if they do show their autonomous car technology, then

0:05:14.320 --> 0:05:16.880
<v Speaker 1>that might take some of the sting out. If their

0:05:16.960 --> 0:05:20.880
<v Speaker 1>next generation iPhone is not a huge departure or a

0:05:21.360 --> 0:05:25.200
<v Speaker 1>home run, if it's not totally breathtaking, then they can say,

0:05:25.279 --> 0:05:27.440
<v Speaker 1>but we also have this cool thing that's gonna make

0:05:27.640 --> 0:05:32.120
<v Speaker 1>automas cars more interesting. Speaking of driverless cars, I think

0:05:32.120 --> 0:05:34.440
<v Speaker 1>we're gonna see a lot more states start to draft

0:05:34.600 --> 0:05:38.719
<v Speaker 1>rules and regulations for driverless vehicles. As it stands, Michigan

0:05:38.800 --> 0:05:41.279
<v Speaker 1>is the only state that really has a comprehensive legal

0:05:41.320 --> 0:05:45.040
<v Speaker 1>framework for autonomous vehicles operating on state roads, but expect

0:05:45.120 --> 0:05:48.599
<v Speaker 1>to see more states in the US frame regulations and

0:05:48.640 --> 0:05:53.320
<v Speaker 1>not all states might be particularly welcoming of autonomous car technology.

0:05:53.360 --> 0:05:57.440
<v Speaker 1>We might see a few that specifically prohibit driverless cars.

0:05:58.240 --> 0:06:02.719
<v Speaker 1>We're already seeing some for action in California. That's where Uber,

0:06:03.000 --> 0:06:06.400
<v Speaker 1>the car sharing service, although I don't really think of

0:06:06.440 --> 0:06:09.960
<v Speaker 1>as a car sharing service. Uh. They've been butting heads

0:06:10.120 --> 0:06:13.560
<v Speaker 1>with San Francisco officials over the legality of testing autonomous

0:06:13.560 --> 0:06:17.680
<v Speaker 1>cars within the city limits. So we're probably gonna see

0:06:17.720 --> 0:06:20.560
<v Speaker 1>more of those kind of growing pains in different areas,

0:06:20.560 --> 0:06:24.320
<v Speaker 1>particularly if companies like Uber don't bother to I don't know,

0:06:24.440 --> 0:06:28.239
<v Speaker 1>ask permission before testing an autonomous car on city streets.

0:06:29.000 --> 0:06:31.760
<v Speaker 1>We'll have to see. Uber, by the way, has been

0:06:31.800 --> 0:06:35.679
<v Speaker 1>super aggressive with its move toward autonomous cars. It's weird

0:06:35.720 --> 0:06:40.400
<v Speaker 1>to see a company moving so quickly toward a largely

0:06:40.520 --> 0:06:44.120
<v Speaker 1>unproven technology, and I say unproven as an unproven in

0:06:44.680 --> 0:06:48.880
<v Speaker 1>real world cases as opposed to just test cases, even

0:06:48.920 --> 0:06:51.960
<v Speaker 1>test drives within the city itself. We haven't really seen

0:06:52.640 --> 0:06:55.880
<v Speaker 1>anyone adopt this technology on a level that Uber has

0:06:55.920 --> 0:06:59.880
<v Speaker 1>been attempting to do. Also, it would mean that Uber

0:07:00.000 --> 0:07:02.960
<v Speaker 1>would be replacing a lot of its workforce, or at

0:07:03.040 --> 0:07:05.719
<v Speaker 1>least the the drivers who work on behalf of Uber

0:07:06.080 --> 0:07:09.200
<v Speaker 1>so that also comes across as a little weird. You know,

0:07:09.360 --> 0:07:12.720
<v Speaker 1>they're essentially saying, Hey, we don't want all these people

0:07:12.840 --> 0:07:16.040
<v Speaker 1>driving for us, we want robots driving for us. I

0:07:16.080 --> 0:07:19.560
<v Speaker 1>say that before two thousands seventeen is over, expect Uber

0:07:19.680 --> 0:07:24.520
<v Speaker 1>to at least test a truly driverless vehicle. I said,

0:07:24.600 --> 0:07:27.720
<v Speaker 1>no one is sitting in the driver's seat in a

0:07:27.800 --> 0:07:33.200
<v Speaker 1>major market somewhere. Now, that means there's no human operator

0:07:33.760 --> 0:07:37.000
<v Speaker 1>inside the vehicle as it stands right now. Uber has

0:07:37.040 --> 0:07:40.560
<v Speaker 1>been testing driverless cars in Pittsburgh and San Francisco, but

0:07:40.640 --> 0:07:44.720
<v Speaker 1>they always have a driver in the driver's seat, able

0:07:44.760 --> 0:07:48.640
<v Speaker 1>to take over at any second. So I imagine that

0:07:48.680 --> 0:07:51.440
<v Speaker 1>before the year is out, Uber world test a car

0:07:52.040 --> 0:07:54.600
<v Speaker 1>with no one in the driver's seat. Uh, it may

0:07:54.680 --> 0:07:56.760
<v Speaker 1>be a test in which no member of the public

0:07:56.880 --> 0:07:58.800
<v Speaker 1>is in the vehicle at all, So the vehicle may

0:07:58.840 --> 0:08:02.000
<v Speaker 1>just be empty, or there might be an Uber employee

0:08:02.040 --> 0:08:04.800
<v Speaker 1>inside who's writing as a passenger but not an actual

0:08:04.840 --> 0:08:07.560
<v Speaker 1>member of the public. But I do think Uber is

0:08:07.640 --> 0:08:10.360
<v Speaker 1>so eager to take this step, even if the rest

0:08:10.400 --> 0:08:13.480
<v Speaker 1>of the US isn't prepared for it. I'm guessing there

0:08:13.480 --> 0:08:15.600
<v Speaker 1>will be a lot more news about driverless cars in

0:08:15.760 --> 0:08:18.840
<v Speaker 1>two thousand seventeen from other players in the game as well,

0:08:18.920 --> 0:08:22.800
<v Speaker 1>like Tesla and Google. In fact, Google recently spun off

0:08:22.800 --> 0:08:26.880
<v Speaker 1>its driverless car division within Google Access, the research and

0:08:26.920 --> 0:08:30.880
<v Speaker 1>development branch of Google, into its own subsidiary company called

0:08:30.960 --> 0:08:33.920
<v Speaker 1>way Mo w A Y m O. I think we're

0:08:33.920 --> 0:08:35.800
<v Speaker 1>still a few more years out before we see that

0:08:35.920 --> 0:08:39.120
<v Speaker 1>this blossom into something more than just a test bed technology,

0:08:40.000 --> 0:08:44.760
<v Speaker 1>but expect to hear more about this throughout two thousand seventeen,

0:08:45.240 --> 0:08:47.480
<v Speaker 1>and I wouldn't be surprised to hear about more pilot

0:08:47.480 --> 0:08:51.679
<v Speaker 1>programs or pilotless programs if you prefer in other parts

0:08:51.679 --> 0:08:55.720
<v Speaker 1>of the world, including driverless trucks and driverless shuttle buses.

0:08:56.240 --> 0:08:59.360
<v Speaker 1>We've seen a couple of experiments in that area already.

0:08:59.440 --> 0:09:03.120
<v Speaker 1>I think we're going to see more In other big

0:09:03.120 --> 0:09:07.520
<v Speaker 1>predictions about new technology, I think hyperloop tests will show

0:09:07.559 --> 0:09:11.640
<v Speaker 1>that the concept is basically sound, but requires such an

0:09:11.760 --> 0:09:15.800
<v Speaker 1>enormous investment from both an infrastructure and an operational standpoint

0:09:15.800 --> 0:09:19.600
<v Speaker 1>that it makes it unrealistic. I suspect that, barring any

0:09:19.600 --> 0:09:23.600
<v Speaker 1>phenomenal incentives from state or federal government agencies, it will

0:09:23.640 --> 0:09:27.079
<v Speaker 1>turn out to be financially untenable. So I don't anticipate

0:09:27.120 --> 0:09:31.680
<v Speaker 1>any major engineering fails as companies test out hyperloop designs.

0:09:31.679 --> 0:09:33.599
<v Speaker 1>I don't think we're going to have a catastrophe or

0:09:34.160 --> 0:09:37.240
<v Speaker 1>a massive system failure, but I do think it will

0:09:37.360 --> 0:09:43.720
<v Speaker 1>become increasingly challenging to keep things moving from an investment standpoint. Now,

0:09:44.600 --> 0:09:47.000
<v Speaker 1>I hope that we do see companies push past this

0:09:47.240 --> 0:09:51.079
<v Speaker 1>and create a real hyperloop track that actually functions as

0:09:51.080 --> 0:09:54.040
<v Speaker 1>a transportation method. But I think the odds of that

0:09:54.080 --> 0:09:58.439
<v Speaker 1>are pretty slim. But please prove me wrong, hyper loop companies.

0:09:58.480 --> 0:10:01.280
<v Speaker 1>I don't want to be right about that addiction. It's

0:10:01.320 --> 0:10:04.760
<v Speaker 1>just kind of a gut feeling I have. Now let's

0:10:04.800 --> 0:10:07.360
<v Speaker 1>hear what my friend I as Actar has to say

0:10:07.400 --> 0:10:10.520
<v Speaker 1>about the tech of two thousand seventeen. Hey, they're tech

0:10:10.559 --> 0:10:13.320
<v Speaker 1>stuff listeners, And Jonathan, it's I as actor seen dot

0:10:13.360 --> 0:10:16.400
<v Speaker 1>dot com, gfqu network dot com and other places, And yes,

0:10:16.400 --> 0:10:18.840
<v Speaker 1>I just promoted myself on your show. My tech prediction

0:10:18.880 --> 0:10:21.760
<v Speaker 1>for seventeen is a prediction I keep saying pretty much

0:10:21.840 --> 0:10:24.880
<v Speaker 1>every year. It seems Alphabet will get into the wireless

0:10:24.920 --> 0:10:28.839
<v Speaker 1>internet game. Huge in the division of Alphabet that runs

0:10:28.880 --> 0:10:31.560
<v Speaker 1>Google Fiber Access put a halt to rolling out. It's

0:10:31.600 --> 0:10:34.320
<v Speaker 1>super fast internet service and a lot of cities back

0:10:34.360 --> 0:10:38.200
<v Speaker 1>in August. Now, I think that these divisions of Alphabet

0:10:38.200 --> 0:10:42.480
<v Speaker 1>are reevaluating everything possible to become the biggest deal within Alphabet.

0:10:42.840 --> 0:10:45.800
<v Speaker 1>While the fiber rollout may be paused. Reports have said

0:10:45.840 --> 0:10:49.640
<v Speaker 1>Access is already looking into wireless tech to get into cities.

0:10:49.960 --> 0:10:52.679
<v Speaker 1>Why bother having to drag out physical fiber to holmes

0:10:52.960 --> 0:10:56.280
<v Speaker 1>if you can build transmitters with five G speeds. S

0:10:56.480 --> 0:10:59.000
<v Speaker 1>Net got to try out Verizons five G wireless service

0:10:59.160 --> 0:11:02.120
<v Speaker 1>and it topped out at three point seven seven gigabits

0:11:02.160 --> 0:11:04.600
<v Speaker 1>per second. That's a whole lot of bandwidth, and I

0:11:04.640 --> 0:11:07.480
<v Speaker 1>think that might be enough for Access to invest heavily

0:11:07.559 --> 0:11:11.120
<v Speaker 1>in wireless. That's my prediction. I hope everybody listening has

0:11:11.120 --> 0:11:16.840
<v Speaker 1>a great and crazy fast wireless Internet Access. I think

0:11:16.880 --> 0:11:18.400
<v Speaker 1>i as is right on the money with this one.

0:11:18.440 --> 0:11:21.040
<v Speaker 1>We've seen Google put the brakes on laying out fiber

0:11:21.120 --> 0:11:25.600
<v Speaker 1>infrastructure in the cities that hasn't already committed itself to fully.

0:11:25.679 --> 0:11:27.800
<v Speaker 1>So you know, Google announced that they were going to

0:11:27.920 --> 0:11:29.920
<v Speaker 1>lay down fiber in a lot of different cities, and

0:11:30.120 --> 0:11:33.120
<v Speaker 1>some of them they either have completed their work or

0:11:33.160 --> 0:11:35.160
<v Speaker 1>they're in the middle of it, Like here in Atlanta,

0:11:35.240 --> 0:11:38.960
<v Speaker 1>They're still laying down fiber. Those cities they're still committed

0:11:39.000 --> 0:11:41.760
<v Speaker 1>to do it, but other cities where they experienced they

0:11:41.760 --> 0:11:45.080
<v Speaker 1>expressed an interest, they are no longer going to forward

0:11:45.120 --> 0:11:48.240
<v Speaker 1>with laying down fiber, and I suspect a big reason

0:11:48.320 --> 0:11:50.439
<v Speaker 1>for this is that Google is looking at the economic

0:11:50.480 --> 0:11:53.600
<v Speaker 1>and engineering factors of going with a wireless strategy versus

0:11:53.640 --> 0:11:56.800
<v Speaker 1>going with a wired one, and they're leaning towards wireless

0:11:56.800 --> 0:11:58.839
<v Speaker 1>at this point. And not only that, but as I

0:11:58.920 --> 0:12:01.800
<v Speaker 1>as is predicted in the past, I do think Google

0:12:01.880 --> 0:12:04.880
<v Speaker 1>is seriously thinking about being a bigger player and wireless

0:12:04.920 --> 0:12:08.720
<v Speaker 1>phone infrastructures. Google figh is kind of a first step

0:12:08.760 --> 0:12:11.400
<v Speaker 1>into that world, but that involves partnering with existing cell

0:12:11.400 --> 0:12:14.560
<v Speaker 1>phone carriers and piggybacking off their networks. It would not

0:12:14.640 --> 0:12:17.280
<v Speaker 1>shock me to see Google jump into the game wholeheartedly.

0:12:17.400 --> 0:12:21.679
<v Speaker 1>In and speaking of games, I think two thousands seventeen

0:12:21.760 --> 0:12:24.560
<v Speaker 1>is the make or break year for virtual reality. Consumer

0:12:24.640 --> 0:12:27.280
<v Speaker 1>VR finally really got off the ground in with the

0:12:27.320 --> 0:12:29.920
<v Speaker 1>launch of the Oculus Rift, the h d C five,

0:12:30.080 --> 0:12:33.720
<v Speaker 1>and the ps VR, among others. Google's in the game

0:12:33.760 --> 0:12:36.600
<v Speaker 1>with Daydream. There are dozens of companies that sell headsets

0:12:36.600 --> 0:12:39.960
<v Speaker 1>and apps promising to turn your smartphone into a VR HMD,

0:12:40.640 --> 0:12:43.320
<v Speaker 1>but the fact remains that the gear is still in

0:12:43.400 --> 0:12:47.720
<v Speaker 1>general heavy, clunky, it's not really comfortable to wear for

0:12:47.800 --> 0:12:50.960
<v Speaker 1>really long play sessions, and it doesn't look like anyone

0:12:51.000 --> 0:12:53.400
<v Speaker 1>has come out with a killer app or game to

0:12:53.600 --> 0:12:56.040
<v Speaker 1>sell systems yet, So no one can point to a

0:12:56.080 --> 0:12:59.000
<v Speaker 1>specific game and say you have to have VR because

0:12:59.040 --> 0:13:02.000
<v Speaker 1>you have to play this thing, and it doesn't look

0:13:02.000 --> 0:13:05.240
<v Speaker 1>like anyone um is finding a way to bring that

0:13:05.280 --> 0:13:08.720
<v Speaker 1>price tag down. If you're using a smartphone, then I

0:13:08.720 --> 0:13:10.839
<v Speaker 1>guess the price tag isn't that bad because you're already

0:13:11.080 --> 0:13:14.480
<v Speaker 1>probably already have the phone. But when you're looking at

0:13:14.520 --> 0:13:19.439
<v Speaker 1>the headsets themselves, they're still pretty expensive, particularly for systems

0:13:19.480 --> 0:13:22.720
<v Speaker 1>that rely upon a console or a bf PC to work,

0:13:23.320 --> 0:13:25.840
<v Speaker 1>so that's a high barrier to entry. For example, if

0:13:25.840 --> 0:13:28.120
<v Speaker 1>you don't already own a p S four, then you

0:13:28.160 --> 0:13:30.000
<v Speaker 1>have to buy one of those to have the PSVR.

0:13:30.400 --> 0:13:34.040
<v Speaker 1>If you don't already own a powerful gaming computer, then

0:13:34.040 --> 0:13:35.720
<v Speaker 1>you're gonna have to buy one of those in order

0:13:35.760 --> 0:13:38.240
<v Speaker 1>to play with an Oculus Rift or an HDC five.

0:13:39.000 --> 0:13:42.480
<v Speaker 1>This brings that price way up, and it means that

0:13:42.520 --> 0:13:46.200
<v Speaker 1>fewer people can actually afford to get into this this world.

0:13:47.240 --> 0:13:50.839
<v Speaker 1>So if VR companies can make more comfortable gear, if

0:13:50.840 --> 0:13:52.840
<v Speaker 1>they can offer it at a reasonable price, or at

0:13:52.920 --> 0:13:55.720
<v Speaker 1>least not make it more expensive than it is right now,

0:13:56.559 --> 0:14:00.320
<v Speaker 1>and if developers can create some really compelling experiences and aims,

0:14:00.640 --> 0:14:03.040
<v Speaker 1>I think VR will make it through two thousand seventeen

0:14:03.120 --> 0:14:06.360
<v Speaker 1>just fine. But if not, I fear we'll see VR

0:14:06.480 --> 0:14:08.559
<v Speaker 1>kind of take the same role as in Nintendo. We

0:14:09.920 --> 0:14:13.240
<v Speaker 1>so we'll just become something that gathers dust until you

0:14:13.240 --> 0:14:15.600
<v Speaker 1>have a group of friends or family over and then you,

0:14:15.600 --> 0:14:18.520
<v Speaker 1>you know, dust it off and you show everybody how

0:14:18.520 --> 0:14:21.840
<v Speaker 1>it works, and everyone's like, oh, that's amazing, that's that's phenomenal.

0:14:21.920 --> 0:14:23.360
<v Speaker 1>And then you're done, and then you put it in

0:14:23.360 --> 0:14:26.040
<v Speaker 1>the corner and then you don't touch it again until

0:14:26.080 --> 0:14:29.080
<v Speaker 1>the next big gathering. That's what I'm worried VR will

0:14:29.080 --> 0:14:32.240
<v Speaker 1>turn into. And I think two thousand seventeen is the

0:14:32.320 --> 0:14:37.040
<v Speaker 1>year where it either faces that future or it becomes

0:14:37.080 --> 0:14:40.200
<v Speaker 1>the ubiquitous type of computing everyone wants to have in

0:14:40.240 --> 0:14:43.120
<v Speaker 1>their home. It's one or the other. I don't think

0:14:43.160 --> 0:14:47.160
<v Speaker 1>you can just treadwater for another year. Now. One exception

0:14:47.200 --> 0:14:51.720
<v Speaker 1>to that rule with VR is that I think you're

0:14:51.720 --> 0:14:55.360
<v Speaker 1>going to see more uses of VR in attractions or

0:14:55.360 --> 0:14:58.640
<v Speaker 1>experiences that you pay to have, like an amusement park

0:14:58.920 --> 0:15:02.160
<v Speaker 1>or even the equip plent of a virtual reality arcade,

0:15:02.680 --> 0:15:05.560
<v Speaker 1>if the cost of the hardware and the software is

0:15:05.680 --> 0:15:09.800
<v Speaker 1>on a proprietor, and then you pay the proprietor to

0:15:09.920 --> 0:15:12.440
<v Speaker 1>have access to it, so that way you can have

0:15:12.520 --> 0:15:14.480
<v Speaker 1>the experience, but you don't have to pay to have

0:15:14.600 --> 0:15:19.200
<v Speaker 1>the whole UH technology in your own home taking up space.

0:15:20.000 --> 0:15:21.920
<v Speaker 1>I think people would be willing to do it if

0:15:21.920 --> 0:15:25.600
<v Speaker 1>the experiences are good enough, So I suspect we'll CVR

0:15:25.640 --> 0:15:29.840
<v Speaker 1>incorporated into more amusement park rides and related entertainment purposes.

0:15:30.280 --> 0:15:33.360
<v Speaker 1>It's possible that even where that's where VR will live,

0:15:33.520 --> 0:15:36.640
<v Speaker 1>they will just live in the entertainment world where you

0:15:36.760 --> 0:15:38.680
<v Speaker 1>pay to have access to it, but you don't go

0:15:38.720 --> 0:15:42.000
<v Speaker 1>out and buy one of these systems for home use,

0:15:42.320 --> 0:15:45.680
<v Speaker 1>kind of like roller coasters. You go and you pay

0:15:45.720 --> 0:15:48.200
<v Speaker 1>to get into a park to ride a roller coaster,

0:15:48.280 --> 0:15:50.120
<v Speaker 1>but you don't pay to have a roller coaster bill

0:15:50.160 --> 0:15:52.440
<v Speaker 1>at your house unless you get a whole lot of

0:15:52.520 --> 0:15:56.240
<v Speaker 1>land and an engineering buddy. And if you do, I

0:15:56.320 --> 0:16:00.080
<v Speaker 1>want to ride on your roller coaster. Meanwhile, another a

0:16:00.080 --> 0:16:02.320
<v Speaker 1>friend of mine has a prediction about where the world

0:16:02.360 --> 0:16:05.560
<v Speaker 1>of cable television is headed. Hello, I'm Tom Merritt, host

0:16:05.600 --> 0:16:09.240
<v Speaker 1>of daily tech news show and Chord Killers. So I'm

0:16:09.240 --> 0:16:12.120
<v Speaker 1>gonna make my prediction actually about cord cutting. In the

0:16:12.160 --> 0:16:15.520
<v Speaker 1>next year, we're going to see launches of what they

0:16:15.520 --> 0:16:18.600
<v Speaker 1>call over the top services TV services that are delivered

0:16:18.680 --> 0:16:24.640
<v Speaker 1>over the Internet, from Hulu, from Google through YouTube. We

0:16:24.680 --> 0:16:28.800
<v Speaker 1>will probably see direct tv now underway, in addition to

0:16:28.840 --> 0:16:32.360
<v Speaker 1>PlayStation View and Sling TV. And there's some rumors out

0:16:32.360 --> 0:16:34.720
<v Speaker 1>there that other folks may be getting into the market

0:16:34.760 --> 0:16:38.680
<v Speaker 1>as well. So my prediction for the United States television

0:16:38.720 --> 0:16:46.120
<v Speaker 1>market is that by the end of the combined number

0:16:46.200 --> 0:16:51.440
<v Speaker 1>of subscribers for these new over the top services so View, Hulu, YouTube,

0:16:51.640 --> 0:16:56.760
<v Speaker 1>direct TV Now, Sling will be the number three if

0:16:56.760 --> 0:16:58.520
<v Speaker 1>you if you, if you combine them will be the

0:16:58.640 --> 0:17:04.040
<v Speaker 1>number three. Large are just cable company in the United States,

0:17:04.160 --> 0:17:07.760
<v Speaker 1>so that would put them after Comcast and what is

0:17:07.800 --> 0:17:12.600
<v Speaker 1>being called Spectrum now, the new combination of Charter and

0:17:13.080 --> 0:17:15.200
<v Speaker 1>Time Warner. I think it will put it in front

0:17:15.240 --> 0:17:18.600
<v Speaker 1>of cable vision. That you know, if I wanted to

0:17:18.640 --> 0:17:20.440
<v Speaker 1>be safe, I'd put it behind cable Vision. But I'm

0:17:20.440 --> 0:17:21.960
<v Speaker 1>gonna go out on a limb and I'm going to

0:17:22.080 --> 0:17:27.159
<v Speaker 1>say that the combination of people getting their live television service,

0:17:27.240 --> 0:17:31.439
<v Speaker 1>their channel television service over the Internet will make it.

0:17:31.640 --> 0:17:35.280
<v Speaker 1>The combined will be the number three cable company, if

0:17:35.359 --> 0:17:36.639
<v Speaker 1>you were to call it a cable company in the

0:17:36.680 --> 0:17:39.760
<v Speaker 1>United States of America. And uh, we will start to

0:17:39.800 --> 0:17:44.359
<v Speaker 1>see more of the traditional cable companies offering services or

0:17:44.359 --> 0:17:49.160
<v Speaker 1>at least talking about offering services outside of their normal markets.

0:17:49.840 --> 0:17:51.920
<v Speaker 1>That that's kind of a corollary to this. We'll start

0:17:51.960 --> 0:17:54.120
<v Speaker 1>to see Comcast saying, hey, we haven't over the top

0:17:54.119 --> 0:17:56.359
<v Speaker 1>service of our own, which they already do right now.

0:17:56.440 --> 0:17:59.280
<v Speaker 1>They only offer it to their existing Comcast subscribers. They'll

0:17:59.280 --> 0:18:03.000
<v Speaker 1>start offering in places that aren't Time Warner territory the

0:18:03.080 --> 0:18:07.120
<v Speaker 1>Comcast doesn't operate in anyway. That's my prediction, Jonathan, Thanks

0:18:07.200 --> 0:18:09.480
<v Speaker 1>for inviting me on if you'd like to find out

0:18:09.520 --> 0:18:11.600
<v Speaker 1>more about cord cutting, of course, courd killers dot com

0:18:11.880 --> 0:18:15.080
<v Speaker 1>or Daily Tech News Show. Thanks again, Happy New Year.

0:18:15.480 --> 0:18:18.080
<v Speaker 1>I can't argue with Tom's logic. Over the top or

0:18:18.200 --> 0:18:21.840
<v Speaker 1>o t T services are growing more popular every year plus,

0:18:22.160 --> 0:18:25.760
<v Speaker 1>we're seeing more televisions and entertainment system components that incorporate

0:18:25.840 --> 0:18:29.359
<v Speaker 1>O T T services into the hardware themselves, making it

0:18:29.440 --> 0:18:33.280
<v Speaker 1>easier than ever to get content without actually subscribing to cable.

0:18:33.880 --> 0:18:36.640
<v Speaker 1>In two thousand sixteen, we saw some cable companies kind

0:18:36.640 --> 0:18:39.760
<v Speaker 1>of make a bit of a rally against declining subscriber numbers,

0:18:40.119 --> 0:18:42.679
<v Speaker 1>which suggests that we may have leveled off of the

0:18:42.760 --> 0:18:45.159
<v Speaker 1>number of people who are just jumping ship and cutting

0:18:45.160 --> 0:18:49.560
<v Speaker 1>the court entirely. So maybe we won't see even smaller

0:18:49.640 --> 0:18:53.040
<v Speaker 1>numbers of subscribers in the future, but rather a growing

0:18:53.119 --> 0:18:55.560
<v Speaker 1>number of people with O T T services, many of

0:18:55.600 --> 0:18:58.520
<v Speaker 1>whom may also be cable subscribers in addition to having

0:18:58.520 --> 0:19:02.240
<v Speaker 1>the O T T services. I've got a lot more

0:19:02.280 --> 0:19:05.080
<v Speaker 1>predictions ahead, but first, let's take a quick break to

0:19:05.160 --> 0:19:17.280
<v Speaker 1>thank our sponsor. Okay, now that we're back, let's talk

0:19:17.320 --> 0:19:20.320
<v Speaker 1>about those personal digital assistance that we have out there.

0:19:20.840 --> 0:19:22.760
<v Speaker 1>I'm not talking about p d as in the old

0:19:22.840 --> 0:19:28.119
<v Speaker 1>fashioned sense, but rather the stuff like Sirie Cortana, Alexa,

0:19:28.400 --> 0:19:32.000
<v Speaker 1>Google's assistant who I guess doesn't merit an actual name.

0:19:32.480 --> 0:19:35.560
<v Speaker 1>For a while, those have served primarily as a user

0:19:35.600 --> 0:19:39.440
<v Speaker 1>interface and by that I mean that the early implementations

0:19:39.440 --> 0:19:42.080
<v Speaker 1>have mostly been used as a replacement for like a

0:19:42.160 --> 0:19:45.800
<v Speaker 1>touch screen or keyboard and mouse. They weren't really living

0:19:45.840 --> 0:19:47.800
<v Speaker 1>up to their full potential. It was just a different

0:19:47.840 --> 0:19:51.240
<v Speaker 1>way to access your devices and to make them do stuff.

0:19:51.680 --> 0:19:54.439
<v Speaker 1>But beyond that, there wasn't a whole lot of power

0:19:54.520 --> 0:19:58.000
<v Speaker 1>to them. As time has gone on, that has changed.

0:19:58.040 --> 0:20:01.240
<v Speaker 1>Developers have created more skills for a for example, or

0:20:01.280 --> 0:20:03.800
<v Speaker 1>apps for other services, and we started to see a

0:20:03.840 --> 0:20:06.639
<v Speaker 1>little bit more functionality in two thousand and sixteen. For

0:20:06.720 --> 0:20:10.080
<v Speaker 1>one thing, the companies behind those services are starting to

0:20:10.080 --> 0:20:12.320
<v Speaker 1>collect a lot of data to work with and to

0:20:12.320 --> 0:20:15.480
<v Speaker 1>see how people are using their services. And by looking

0:20:15.480 --> 0:20:18.200
<v Speaker 1>at that data, they can make changes to those services,

0:20:18.280 --> 0:20:21.439
<v Speaker 1>make them work better, make them do more things, and

0:20:21.480 --> 0:20:24.240
<v Speaker 1>we'll likely see those services take a more proactive approach

0:20:24.840 --> 0:20:27.840
<v Speaker 1>where it starts to anticipate our needs as we move

0:20:27.880 --> 0:20:31.399
<v Speaker 1>through our routines. So, in other words, if you do

0:20:31.480 --> 0:20:36.000
<v Speaker 1>the same thing every work day or school day, if

0:20:36.040 --> 0:20:38.720
<v Speaker 1>you have the same kind of routine set up, and

0:20:39.040 --> 0:20:41.199
<v Speaker 1>the systems in your house start to learn what your

0:20:41.280 --> 0:20:44.520
<v Speaker 1>routines are, they can start to prepare things in advance

0:20:44.640 --> 0:20:47.639
<v Speaker 1>of your routine to make it more smooth. That's the

0:20:47.720 --> 0:20:49.359
<v Speaker 1>kind of thing I'm thinking about. By the end of

0:20:49.359 --> 0:20:52.280
<v Speaker 1>two thousand seventeen, I expect to see an enormous increase

0:20:52.280 --> 0:20:55.160
<v Speaker 1>in the number of Internet of Things devices that can

0:20:55.200 --> 0:20:59.399
<v Speaker 1>interoperate with these digital assistants. So we've already seen Amazon

0:20:59.520 --> 0:21:02.440
<v Speaker 1>be very aggressive in this space. Amazon works very hard

0:21:02.480 --> 0:21:05.920
<v Speaker 1>to try and get partnerships with various Internet of things

0:21:05.960 --> 0:21:09.600
<v Speaker 1>companies so that Alexa can also interact with things like

0:21:09.760 --> 0:21:15.240
<v Speaker 1>lighting systems, thermostats, that kind of stuff, electronic locks, cameras,

0:21:15.280 --> 0:21:18.400
<v Speaker 1>everything you can think of, the same thing for Google Home.

0:21:19.240 --> 0:21:21.119
<v Speaker 1>I think we're going to continue to see that grow

0:21:21.240 --> 0:21:26.440
<v Speaker 1>in ten to a huge extent. Now that actually ties

0:21:26.480 --> 0:21:30.080
<v Speaker 1>into another prediction a different friend of mine made. I'm

0:21:30.080 --> 0:21:33.680
<v Speaker 1>talking about my buddy, Shannon Morse, who was a podcaster, hacker,

0:21:34.160 --> 0:21:39.120
<v Speaker 1>and wearer of many hats, both literally and figuratively. Shannon

0:21:39.160 --> 0:21:42.119
<v Speaker 1>made two predictions for me this year, and this is

0:21:42.160 --> 0:21:46.320
<v Speaker 1>actually her second prediction, but I'm gonna play it first.

0:21:46.359 --> 0:21:48.760
<v Speaker 1>I'll play the first one later in the show, but

0:21:48.840 --> 0:21:51.560
<v Speaker 1>it fits better in a different discussion. So for now,

0:21:52.400 --> 0:21:55.199
<v Speaker 1>here's what Shannon has to say about the Internet of

0:21:55.240 --> 0:22:01.040
<v Speaker 1>Things in for my second prediction. I believe if that Mirai,

0:22:01.200 --> 0:22:04.280
<v Speaker 1>which was a really big bot net this year that

0:22:04.760 --> 0:22:07.600
<v Speaker 1>was able to attack Internet of things devices such as

0:22:07.840 --> 0:22:12.840
<v Speaker 1>security cameras and the like, UH will create critical changes

0:22:12.960 --> 0:22:15.919
<v Speaker 1>for the Internet of things manufacturers and is going to

0:22:15.920 --> 0:22:20.360
<v Speaker 1>spot spur more security focus from consumers on IoT devices. So,

0:22:20.440 --> 0:22:23.399
<v Speaker 1>for example, I believe that consumers are going to be

0:22:23.480 --> 0:22:26.240
<v Speaker 1>a lot more aware of what kind of security their

0:22:26.240 --> 0:22:29.440
<v Speaker 1>IoT devices have on them before they actually buy them,

0:22:29.480 --> 0:22:32.119
<v Speaker 1>and I hope that they will start asking the correct

0:22:32.240 --> 0:22:35.840
<v Speaker 1>questions to figure out that security. I also predict that

0:22:35.880 --> 0:22:38.879
<v Speaker 1>we are going to see a more consumer focused software

0:22:38.920 --> 0:22:43.920
<v Speaker 1>program made to detect IoT vulnerabilities and help you patch them. Currently,

0:22:43.960 --> 0:22:46.920
<v Speaker 1>there is nothing that I know of, at least that

0:22:47.000 --> 0:22:51.439
<v Speaker 1>allows consumers to really easily check their IoT devices for

0:22:51.480 --> 0:22:54.520
<v Speaker 1>any kind of vulnerabilities. Yes, we do have things like

0:22:54.720 --> 0:22:58.800
<v Speaker 1>malware um detection and antavirus for computers, but we don't

0:22:58.840 --> 0:23:01.760
<v Speaker 1>have anything like that for OOT devices, for open ports

0:23:01.760 --> 0:23:05.600
<v Speaker 1>and like. So I would love to see somebody create,

0:23:05.880 --> 0:23:08.800
<v Speaker 1>for example, and open source software that can be audited

0:23:09.080 --> 0:23:12.480
<v Speaker 1>that would allow consumers to quickly check their devices, quickly

0:23:12.560 --> 0:23:15.080
<v Speaker 1>check their ports to make sure everything is safe on

0:23:15.119 --> 0:23:18.240
<v Speaker 1>their routers. And given the high concerns that we've had

0:23:18.280 --> 0:23:20.680
<v Speaker 1>with mere I bought net this past year, I can

0:23:20.680 --> 0:23:26.160
<v Speaker 1>see that as a quite a high possibility for now.

0:23:26.160 --> 0:23:28.560
<v Speaker 1>Like I said earlier, I'm recording this episode in December

0:23:28.600 --> 0:23:30.760
<v Speaker 1>twenty one, two thousand and sixteen. I can tell you

0:23:30.840 --> 0:23:33.800
<v Speaker 1>right now that Shannon is on target with this particular prediction.

0:23:34.359 --> 0:23:36.879
<v Speaker 1>The Internet of things is a big focus of the

0:23:36.960 --> 0:23:42.240
<v Speaker 1>upcoming ce SEEN trade show. Again, that's that big electronics

0:23:42.240 --> 0:23:44.720
<v Speaker 1>conference that will be going to in Las Vegas. One

0:23:44.760 --> 0:23:49.080
<v Speaker 1>of the categories of products that I'm seeing concentrates specifically

0:23:49.200 --> 0:23:53.240
<v Speaker 1>on IoT device security IoT stands for Internet of Things.

0:23:53.320 --> 0:23:55.720
<v Speaker 1>Just in case I didn't explain that a few different

0:23:55.720 --> 0:23:58.879
<v Speaker 1>companies are offering up smart home hubs to add in

0:23:59.000 --> 0:24:01.720
<v Speaker 1>kind of a layer of protection between the gadgets in

0:24:01.800 --> 0:24:04.320
<v Speaker 1>your home and the big bad world of people who

0:24:04.320 --> 0:24:07.639
<v Speaker 1>want to exploit your devices. So, if you recall in

0:24:07.680 --> 0:24:10.919
<v Speaker 1>my review episodes of twenty sixteen, I talked about several

0:24:10.960 --> 0:24:14.679
<v Speaker 1>examples of hackers using unsecured devices to attack targets like

0:24:14.720 --> 0:24:17.440
<v Speaker 1>web servers or even the heating system of some apartment

0:24:17.480 --> 0:24:19.960
<v Speaker 1>buildings in Europe. So if nothing else, we're going to

0:24:20.040 --> 0:24:22.880
<v Speaker 1>see a strong push from the electronics industry and various

0:24:22.920 --> 0:24:26.719
<v Speaker 1>agencies within it to employ new strategies to protect COOT

0:24:26.880 --> 0:24:29.840
<v Speaker 1>devices and the people who use them. So I agree

0:24:29.920 --> 0:24:34.360
<v Speaker 1>entirely with Shannon's prediction. In fact, I think security tech

0:24:34.440 --> 0:24:38.840
<v Speaker 1>alone will see enormous growth in tween we saw so

0:24:38.880 --> 0:24:43.119
<v Speaker 1>many accounts of de dos attacks and worse stuff like

0:24:43.200 --> 0:24:46.440
<v Speaker 1>intrusions into what should have been a secure system that

0:24:46.560 --> 0:24:49.560
<v Speaker 1>I suspect the security industry will have the biggest year

0:24:49.680 --> 0:24:53.480
<v Speaker 1>ever in twenty seventeen. All of that won't really matter

0:24:53.600 --> 0:24:56.400
<v Speaker 1>much if people don't learn to practice healthy security, though,

0:24:56.720 --> 0:24:58.960
<v Speaker 1>as we see numerous times, people tend to be the

0:24:58.960 --> 0:25:03.040
<v Speaker 1>weakest link in secure systems. There's no need to brute

0:25:03.040 --> 0:25:05.439
<v Speaker 1>force an attack into a computer system if you can

0:25:05.480 --> 0:25:09.560
<v Speaker 1>convince someone to give you access to it. Switching gears

0:25:09.560 --> 0:25:11.800
<v Speaker 1>over to hardware for a second, I predict that we'll

0:25:11.840 --> 0:25:15.600
<v Speaker 1>see a hardware kind of development level off a little bit.

0:25:16.000 --> 0:25:19.679
<v Speaker 1>I don't think we're gonna see as fast progression in

0:25:19.800 --> 0:25:24.000
<v Speaker 1>hardware capabilities as we have in previous years, or at

0:25:24.080 --> 0:25:25.879
<v Speaker 1>least not an increase in power at the at that

0:25:26.040 --> 0:25:31.080
<v Speaker 1>same rate. So in other words, yes, once again, I'm

0:25:31.119 --> 0:25:33.560
<v Speaker 1>going to predict that Moore's law will become less of

0:25:33.600 --> 0:25:36.439
<v Speaker 1>a factor. I think most companies are now concentrating on

0:25:36.480 --> 0:25:39.280
<v Speaker 1>ways to make more efficient use of their components in

0:25:39.320 --> 0:25:43.639
<v Speaker 1>their microprocessors, rather than dedicate themselves to perpetuating an observation

0:25:43.640 --> 0:25:46.639
<v Speaker 1>that was made half a century ago. As a result,

0:25:46.640 --> 0:25:49.760
<v Speaker 1>I think we're gonna see focus placed on developing software

0:25:50.480 --> 0:25:55.679
<v Speaker 1>rather than pushing hardware. Even if hardware companies try to

0:25:55.720 --> 0:25:58.760
<v Speaker 1>break new barriers, I think most spending will be on

0:25:58.840 --> 0:26:02.880
<v Speaker 1>the software end of things. This is particularly true as

0:26:02.920 --> 0:26:06.359
<v Speaker 1>more companies embraced cloud based services in favor of native

0:26:06.400 --> 0:26:11.120
<v Speaker 1>applications on corporate computers. I also suspect we'll see at

0:26:11.200 --> 0:26:14.720
<v Speaker 1>least one major issue with a cloud based service, perhaps

0:26:14.720 --> 0:26:18.679
<v Speaker 1>even a catastrophic one, before the end of SEEN, and

0:26:18.760 --> 0:26:20.520
<v Speaker 1>that might shake things up for the second half of

0:26:20.560 --> 0:26:23.080
<v Speaker 1>the year. It could cause big companies to reassess the

0:26:23.119 --> 0:26:26.439
<v Speaker 1>strategy of offloading everything to the cloud. If a cloud

0:26:26.480 --> 0:26:30.120
<v Speaker 1>service suffers a terrible failure at some point in SEEN,

0:26:30.640 --> 0:26:33.080
<v Speaker 1>then you're gonna have companies saying, well, maybe we shouldn't

0:26:33.840 --> 0:26:37.359
<v Speaker 1>put all of our eggs into the online basket. Maybe

0:26:37.400 --> 0:26:43.879
<v Speaker 1>we should have localized backups, localized instances of our data

0:26:45.160 --> 0:26:47.400
<v Speaker 1>and a lot of companies still do that, but we've

0:26:47.440 --> 0:26:49.640
<v Speaker 1>been seeing more and more kind of adopt the cloud

0:26:49.840 --> 0:26:53.600
<v Speaker 1>approach over the years because there's a lot of savings involved.

0:26:53.640 --> 0:26:56.680
<v Speaker 1>You don't have to have the physical space to hold

0:26:56.760 --> 0:26:58.840
<v Speaker 1>all the equipment, you don't have to have as many

0:26:58.920 --> 0:27:02.919
<v Speaker 1>people you're paying for a service in that sense, But

0:27:03.200 --> 0:27:07.080
<v Speaker 1>if one of those services fails, it could be huge news.

0:27:07.920 --> 0:27:10.240
<v Speaker 1>And now I'd like to play another prediction, and this

0:27:10.280 --> 0:27:13.160
<v Speaker 1>one comes to us from my buddy Jason Howell over

0:27:13.240 --> 0:27:16.359
<v Speaker 1>at this Weekend Tech. Hey, Jonathan, this is Jason Howell

0:27:16.359 --> 0:27:19.080
<v Speaker 1>Tech News Today for Twitter dot TV. You're no stranger

0:27:19.119 --> 0:27:20.840
<v Speaker 1>to the show. We've had you on many times, but

0:27:20.880 --> 0:27:25.439
<v Speaker 1>thanks for asking for my prediction. For I'm thinking that

0:27:25.600 --> 0:27:29.040
<v Speaker 1>maybe throughout the course of the year, maybe there's a

0:27:29.080 --> 0:27:32.719
<v Speaker 1>little bit of a resistance, a pushback on things like

0:27:32.760 --> 0:27:38.200
<v Speaker 1>social media, things like over sharing everybody's details to technology companies.

0:27:38.480 --> 0:27:41.240
<v Speaker 1>We've gotten to the point to where we've really started

0:27:41.280 --> 0:27:45.400
<v Speaker 1>to give so much of our identities of our lives

0:27:45.520 --> 0:27:49.320
<v Speaker 1>in exchange for conveniences. And I think what we're starting

0:27:49.359 --> 0:27:52.280
<v Speaker 1>to realize is and and many people have realized this

0:27:52.359 --> 0:27:54.879
<v Speaker 1>for a long time, but uh and warned against it,

0:27:54.920 --> 0:27:57.480
<v Speaker 1>But is that as we give away all that information,

0:27:57.560 --> 0:28:00.320
<v Speaker 1>it's really hard to take it back, and there's the

0:28:00.320 --> 0:28:03.199
<v Speaker 1>potential there's a lot of potential for abuse, be it

0:28:03.359 --> 0:28:07.720
<v Speaker 1>weaponized information, be it hacking and security, be it just

0:28:07.920 --> 0:28:12.560
<v Speaker 1>reliance on things. You know, people are worried of the

0:28:12.600 --> 0:28:15.159
<v Speaker 1>thought of, like leaving Facebook, even though they don't like it,

0:28:15.240 --> 0:28:17.960
<v Speaker 1>because that's how I keep in touch with people. Is

0:28:18.000 --> 0:28:22.439
<v Speaker 1>it healthy to make one single, you know, service like

0:28:22.520 --> 0:28:25.359
<v Speaker 1>Facebook or other social networks the one way that you

0:28:25.400 --> 0:28:27.240
<v Speaker 1>get all of your information that you stay in touch

0:28:27.280 --> 0:28:29.840
<v Speaker 1>with people. There's there's potential for abuse there, and I

0:28:29.880 --> 0:28:32.480
<v Speaker 1>think we're starting to realize, uh, you know, starting to

0:28:32.520 --> 0:28:35.360
<v Speaker 1>react to that a little bit. I'm wondering if there

0:28:35.440 --> 0:28:37.720
<v Speaker 1>is a little bit of a pull back, a pull

0:28:37.760 --> 0:28:40.360
<v Speaker 1>away from over sharing, where people kind of start to

0:28:40.360 --> 0:28:43.640
<v Speaker 1>take their digital lives back into their own hands, and uh,

0:28:43.800 --> 0:28:47.480
<v Speaker 1>I don't know, just realize that there there are alternatives

0:28:47.800 --> 0:28:50.440
<v Speaker 1>that they don't have to feel beholden to these companies

0:28:50.480 --> 0:28:52.719
<v Speaker 1>who are really just you know, doing all of this

0:28:52.800 --> 0:28:55.520
<v Speaker 1>in the best interests of themselves and their shareholders, not

0:28:55.640 --> 0:28:58.520
<v Speaker 1>necessarily for the users. I know, maybe that's a pipe

0:28:58.600 --> 0:29:00.960
<v Speaker 1>dream something I've been thinking about a lot lately, and

0:29:01.000 --> 0:29:03.480
<v Speaker 1>I'm kind of hoping that going into twenty seventeen people

0:29:03.520 --> 0:29:05.600
<v Speaker 1>think about that too. Anyways, thanks for asking me to

0:29:05.600 --> 0:29:08.040
<v Speaker 1>do this. There's a lot of fun. I'm really hoping

0:29:08.040 --> 0:29:12.000
<v Speaker 1>for a fantastic seventeen, but that is that happy new year,

0:29:12.480 --> 0:29:15.240
<v Speaker 1>you know. I'd like to think we'll see behavior kind

0:29:15.240 --> 0:29:18.120
<v Speaker 1>of like what Jason predicts, but I'm not sure. I

0:29:18.200 --> 0:29:21.200
<v Speaker 1>definitely saw a lot of people become disenchanted with social

0:29:21.240 --> 0:29:25.600
<v Speaker 1>media over this past year, particularly after events like the

0:29:25.640 --> 0:29:28.600
<v Speaker 1>Brexit vote in the UK and the elections here in

0:29:28.600 --> 0:29:32.360
<v Speaker 1>the United States. But that's purely anecdotal and based upon

0:29:32.480 --> 0:29:35.880
<v Speaker 1>my particular group of friends, and just because several people

0:29:36.040 --> 0:29:38.800
<v Speaker 1>I know decided that they wanted to take a bit

0:29:38.840 --> 0:29:43.000
<v Speaker 1>of a social media sabbatical doesn't mean it's an overall trend.

0:29:43.920 --> 0:29:46.120
<v Speaker 1>But it's also possible that it is a trend, and

0:29:46.160 --> 0:29:48.600
<v Speaker 1>the people I see in my group are just part

0:29:48.640 --> 0:29:52.400
<v Speaker 1>of a smaller part of a much larger movement. Now,

0:29:52.440 --> 0:29:56.360
<v Speaker 1>whether that prediction is true or not, I do hope

0:29:56.920 --> 0:29:59.880
<v Speaker 1>that in tween people give more thought to what they're

0:30:00.000 --> 0:30:03.840
<v Speaker 1>participation on social media really means. And I know you

0:30:03.880 --> 0:30:06.120
<v Speaker 1>guys know this because you've been listening to tech stuff,

0:30:06.160 --> 0:30:09.000
<v Speaker 1>your tech savvy folks. But it means that when you

0:30:09.120 --> 0:30:12.840
<v Speaker 1>participate in social media, you give up some, sometimes a lot,

0:30:13.600 --> 0:30:17.080
<v Speaker 1>of your privacy and security in return for the rewards

0:30:17.120 --> 0:30:21.040
<v Speaker 1>you get with social media. That that level of connection,

0:30:21.200 --> 0:30:26.040
<v Speaker 1>that immediacy of communication, those come into price, and those

0:30:26.080 --> 0:30:29.480
<v Speaker 1>companies like Facebook and Twitter, they all profit off of

0:30:29.480 --> 0:30:32.959
<v Speaker 1>our participation in these systems, Like we're the ones that

0:30:33.040 --> 0:30:36.840
<v Speaker 1>make it valuable. It's not that Facebook is valuable because

0:30:36.880 --> 0:30:39.880
<v Speaker 1>of all of its features. Facebook is valuable because there's

0:30:39.920 --> 0:30:45.080
<v Speaker 1>so many of us on Facebook. We're the part of

0:30:45.120 --> 0:30:49.440
<v Speaker 1>those platforms that make those companies money. And if that's

0:30:49.440 --> 0:30:51.640
<v Speaker 1>all okay with you, well that's totally cool. You know,

0:30:51.680 --> 0:30:54.080
<v Speaker 1>there's nothing wrong with that. If you are aware of

0:30:54.080 --> 0:30:56.920
<v Speaker 1>it and you're okay with it, that's fine. But if

0:30:56.960 --> 0:30:59.760
<v Speaker 1>you're not okay with it, then you should ask yourself

0:30:59.800 --> 0:31:03.960
<v Speaker 1>hard questions about using social media. Now. Personally, I'm going

0:31:04.000 --> 0:31:06.720
<v Speaker 1>to continue to use social media. Even if it were

0:31:06.800 --> 0:31:09.240
<v Speaker 1>not part of my job, I would still use it.

0:31:09.840 --> 0:31:11.400
<v Speaker 1>I don't have a whole lot of time that I

0:31:11.440 --> 0:31:15.960
<v Speaker 1>can spend with my friends in real life, so social

0:31:16.000 --> 0:31:17.960
<v Speaker 1>media remains one of the easiest ways for me to

0:31:18.000 --> 0:31:20.240
<v Speaker 1>stay up to date with what my friends are doing

0:31:20.280 --> 0:31:23.520
<v Speaker 1>and understand what's going on. Also, I can organize events

0:31:23.520 --> 0:31:27.040
<v Speaker 1>really easily with stuff like Facebook. But then if everyone

0:31:27.080 --> 0:31:29.600
<v Speaker 1>else leaves, it's gonna get awful lonely in there for me.

0:31:30.240 --> 0:31:33.080
<v Speaker 1>So I won't obviously won't be nearly as useful if

0:31:33.120 --> 0:31:36.160
<v Speaker 1>everyone else does. So. Will we see people pull back

0:31:36.160 --> 0:31:40.520
<v Speaker 1>from social media? Um? Some Sure. I think we will

0:31:40.520 --> 0:31:45.680
<v Speaker 1>see some people pulled back from social media in I

0:31:45.760 --> 0:31:47.480
<v Speaker 1>just don't know that it's going to be a large

0:31:47.560 --> 0:31:54.040
<v Speaker 1>enough number for the majority to notice. But maybe Jason's right.

0:31:54.280 --> 0:31:58.040
<v Speaker 1>I mean, I don't know. I feel like something is

0:31:58.080 --> 0:32:01.800
<v Speaker 1>going to change. At least awareness is going to change. Now.

0:32:01.880 --> 0:32:04.120
<v Speaker 1>That brings me to a related prediction that I have,

0:32:04.320 --> 0:32:06.360
<v Speaker 1>which is that Twitter is going to have a very

0:32:06.480 --> 0:32:11.000
<v Speaker 1>rough In fact, I worry that if no one steps

0:32:11.080 --> 0:32:14.000
<v Speaker 1>up to acquire Twitter with a serious bid, we could

0:32:14.000 --> 0:32:17.960
<v Speaker 1>see the service completely die. That's hard to imagine considering

0:32:17.960 --> 0:32:20.280
<v Speaker 1>how many people use Twitter as a way to follow

0:32:20.320 --> 0:32:24.400
<v Speaker 1>people and brands they like, or sometimes the people and

0:32:24.520 --> 0:32:28.640
<v Speaker 1>brands they don't like it depending upon their inclinations, or

0:32:28.680 --> 0:32:31.880
<v Speaker 1>the fact that celebrities, politicians, and brands use Twitter to

0:32:31.920 --> 0:32:35.040
<v Speaker 1>reach out directly to an audience, but unless the company

0:32:35.160 --> 0:32:39.560
<v Speaker 1>can make some positive changes soon, it may not be around.

0:32:40.440 --> 0:32:44.280
<v Speaker 1>At the end of complicating that matter is the ongoing

0:32:44.320 --> 0:32:47.720
<v Speaker 1>issue of harassment on Twitter. The company has struggled to

0:32:47.760 --> 0:32:51.760
<v Speaker 1>create and enforce a policy that satisfies users, and some

0:32:51.800 --> 0:32:55.560
<v Speaker 1>people continue to be the targets of online harassment. Now

0:32:55.600 --> 0:32:58.080
<v Speaker 1>that's not helping matters. And all that being said, I

0:32:58.120 --> 0:33:01.480
<v Speaker 1>think it's most likely that someone will buy Twitter before

0:33:01.520 --> 0:33:04.800
<v Speaker 1>the end of seventeen, but I bet they're going to

0:33:04.880 --> 0:33:07.680
<v Speaker 1>buy it for way less than what Twitter was hoping for,

0:33:08.400 --> 0:33:11.920
<v Speaker 1>so significantly less. Like essentially, if Twitter doesn't sell, then

0:33:11.960 --> 0:33:15.080
<v Speaker 1>it's not going to be around. Uh that's my prediction

0:33:15.120 --> 0:33:18.680
<v Speaker 1>for seventeen with Twitter. On a related note, I suspect

0:33:18.720 --> 0:33:22.040
<v Speaker 1>we'll see a renewed attempt to curtail fake news from

0:33:22.120 --> 0:33:27.200
<v Speaker 1>spreading online. Personally, I think that's nearly impossible if you

0:33:27.280 --> 0:33:31.760
<v Speaker 1>go back to the eighteenth century. In seventeen ten, Jonathan Swift,

0:33:32.400 --> 0:33:36.360
<v Speaker 1>another brilliant Jonathan, there's been so many of us wrote,

0:33:37.040 --> 0:33:42.120
<v Speaker 1>falsehood flies and the truth comes limping after it. The

0:33:42.200 --> 0:33:45.960
<v Speaker 1>same thing is true now, more true than ever now

0:33:46.240 --> 0:33:51.480
<v Speaker 1>falsehood flies across the Internet very very quickly, the truth

0:33:52.360 --> 0:33:57.720
<v Speaker 1>stumbling along behind. And you know, Jonathan Swift made this

0:33:58.240 --> 0:34:00.600
<v Speaker 1>observation all the way back in seventeen, you know, back

0:34:00.600 --> 0:34:04.239
<v Speaker 1>when the Internet was super slow because it hadn't been

0:34:04.280 --> 0:34:08.320
<v Speaker 1>invented yet. But Google and Facebook both have recently pledged

0:34:08.360 --> 0:34:11.680
<v Speaker 1>to identify and limit the impact of fake news sites

0:34:12.040 --> 0:34:16.280
<v Speaker 1>to prevent misinformation from spreading so quickly. And here's my prediction.

0:34:16.760 --> 0:34:20.480
<v Speaker 1>If they do a good job of identifying these sites,

0:34:21.640 --> 0:34:25.480
<v Speaker 1>those sites will quickly die off because those sites only

0:34:25.520 --> 0:34:29.919
<v Speaker 1>exist because people are clicking on those links. When people

0:34:29.960 --> 0:34:32.200
<v Speaker 1>click on the links, they drive up the page views

0:34:32.360 --> 0:34:36.320
<v Speaker 1>on those pages. Those page views are linked to ads

0:34:36.520 --> 0:34:39.160
<v Speaker 1>running on those pages, which means the pages start to

0:34:39.200 --> 0:34:41.880
<v Speaker 1>earn money. They earn ad money for the number of

0:34:41.880 --> 0:34:45.640
<v Speaker 1>impressions they get. The more impressions or views they get,

0:34:45.960 --> 0:34:49.680
<v Speaker 1>the more money the sites get. So if Google or

0:34:49.719 --> 0:34:53.880
<v Speaker 1>Facebook refuses to sell ads against those pages, or they

0:34:53.920 --> 0:34:58.839
<v Speaker 1>adjust their algorithms to completely exclude those pages from their services,

0:35:00.040 --> 0:35:03.000
<v Speaker 1>it won't be profitable to operate those sites, and the

0:35:03.080 --> 0:35:06.520
<v Speaker 1>people writing for those sites will go and do something else. Now,

0:35:06.560 --> 0:35:09.360
<v Speaker 1>some of those people might truly believe in whatever message

0:35:09.440 --> 0:35:11.960
<v Speaker 1>they're sending out even if they're sending out fake news,

0:35:12.040 --> 0:35:14.960
<v Speaker 1>they may really believe in the point of view that

0:35:15.000 --> 0:35:19.280
<v Speaker 1>they are stating, but many of them, perhaps even most,

0:35:20.000 --> 0:35:22.200
<v Speaker 1>are just doing it as a way to make money.

0:35:22.360 --> 0:35:26.000
<v Speaker 1>They're not It's not that they particularly hold the viewpoints

0:35:26.040 --> 0:35:31.000
<v Speaker 1>that they espouse in there in their episodes or in

0:35:31.040 --> 0:35:34.960
<v Speaker 1>their in their sites. They're just writing what they think

0:35:34.960 --> 0:35:37.799
<v Speaker 1>people will click on, which is pretty darn cynical. But

0:35:37.920 --> 0:35:40.560
<v Speaker 1>then I'm doing a job I love, and so I'm

0:35:40.560 --> 0:35:43.279
<v Speaker 1>in a position of luxury when it comes to that

0:35:43.360 --> 0:35:46.160
<v Speaker 1>sort of thing. I'd like to think that if I

0:35:46.200 --> 0:35:49.720
<v Speaker 1>didn't have this job, I would not be writing fake news.

0:35:50.360 --> 0:35:52.040
<v Speaker 1>But since I'm not in that position, it's kind of

0:35:52.040 --> 0:35:54.960
<v Speaker 1>hard to say for sure. Maybe i'd be a a

0:35:55.040 --> 0:35:59.600
<v Speaker 1>fake newsmonger. Who's to say, Well, I've got a few

0:35:59.600 --> 0:36:03.239
<v Speaker 1>more action But before I get into those, let's take

0:36:03.239 --> 0:36:14.360
<v Speaker 1>another quick break to thank our sponsor. Okay, we're in

0:36:14.400 --> 0:36:18.400
<v Speaker 1>the homes trench, so how about some doom and gloom.

0:36:18.440 --> 0:36:21.200
<v Speaker 1>So we're gonna see a lot more automation in jobs

0:36:21.360 --> 0:36:25.239
<v Speaker 1>in several industries. In some examples may just be kind

0:36:25.239 --> 0:36:28.920
<v Speaker 1>of test cases, you know, not like a widespread rollout

0:36:28.920 --> 0:36:32.680
<v Speaker 1>of technology, but more prototypes to see how it goes.

0:36:32.719 --> 0:36:36.000
<v Speaker 1>Things like fast food restaurants moving into more automated systems,

0:36:36.080 --> 0:36:39.880
<v Speaker 1>or delivery services relying on more automation like self driving

0:36:39.960 --> 0:36:43.360
<v Speaker 1>vehicles or other shipping methods. Now that's going to prompt

0:36:43.400 --> 0:36:46.919
<v Speaker 1>more discussions about how automation will affect the workforce as

0:36:46.920 --> 0:36:50.160
<v Speaker 1>a whole, and how to prepare people for the jobs

0:36:50.160 --> 0:36:54.680
<v Speaker 1>of tomorrow. As more of today's jobs become automated, I

0:36:54.719 --> 0:36:58.120
<v Speaker 1>suspect we'll also see more people advocate for a universal

0:36:58.239 --> 0:37:03.520
<v Speaker 1>basic income concept, though I cannot imagine the upcoming US

0:37:03.560 --> 0:37:07.600
<v Speaker 1>administration to be at all interested in that. We might

0:37:07.640 --> 0:37:11.320
<v Speaker 1>see examples of it in other countries outside the United States. However,

0:37:12.360 --> 0:37:15.680
<v Speaker 1>something else we might see is an increase in electronics

0:37:15.760 --> 0:37:19.840
<v Speaker 1>prices because I suspect trade relations between the US and

0:37:19.920 --> 0:37:24.440
<v Speaker 1>China could get a little prickly. President elect Donald Trump

0:37:24.520 --> 0:37:27.040
<v Speaker 1>has been really critical of China and has talked about

0:37:27.080 --> 0:37:30.000
<v Speaker 1>imposing tariffs on Chinese goods, so we may see some

0:37:30.080 --> 0:37:33.080
<v Speaker 1>fallout in the consumer market as a result of all this.

0:37:33.440 --> 0:37:36.960
<v Speaker 1>Now it's still early, so this could all change. But

0:37:37.080 --> 0:37:41.600
<v Speaker 1>my bed is that we'll see trade strained in between

0:37:41.640 --> 0:37:43.479
<v Speaker 1>China and the US, and stuff is going to cost

0:37:43.560 --> 0:37:46.440
<v Speaker 1>more than it has for the past few years. On

0:37:46.520 --> 0:37:50.280
<v Speaker 1>a related note, some analysts are saying that it's getting

0:37:50.320 --> 0:37:53.160
<v Speaker 1>more expensive for companies to operate in China, so it's

0:37:53.200 --> 0:37:56.840
<v Speaker 1>actually possible that we might see some of the manufacturing

0:37:56.840 --> 0:38:00.239
<v Speaker 1>companies move out of China entirely and into a friend

0:38:00.239 --> 0:38:04.280
<v Speaker 1>country like Vietnam or the Philippines. Now back in the States,

0:38:06.000 --> 0:38:11.480
<v Speaker 1>we have another concern that's also politically related, and that

0:38:11.560 --> 0:38:15.600
<v Speaker 1>concern is net neutrality. So to talk about net neutrality,

0:38:15.680 --> 0:38:19.840
<v Speaker 1>here's Shannon Morse again with her other prediction, which technically

0:38:19.920 --> 0:38:23.240
<v Speaker 1>was her first prediction, but I saved it until now

0:38:23.840 --> 0:38:26.560
<v Speaker 1>prediction number one. I believe that we are going to

0:38:26.600 --> 0:38:29.840
<v Speaker 1>start seeing some large hits to security and privacy, starting

0:38:29.840 --> 0:38:35.320
<v Speaker 1>with net neutrality in bulk data collection for example. Just recently,

0:38:35.480 --> 0:38:39.160
<v Speaker 1>just last week, net neutrality came under fire due to

0:38:39.200 --> 0:38:42.439
<v Speaker 1>an FCC commissioner wanting to remove some of the regulations

0:38:42.480 --> 0:38:45.920
<v Speaker 1>that it creates under the new newly led government that

0:38:46.000 --> 0:38:50.000
<v Speaker 1>was recently elected in I suspect that other privacy regulations

0:38:50.040 --> 0:38:52.279
<v Speaker 1>such as the us A Freedom Act, which did a

0:38:52.280 --> 0:38:54.360
<v Speaker 1>weigh with a lot of the bulk data collection that

0:38:54.400 --> 0:38:56.880
<v Speaker 1>the government was allowed to do from the Patriot Act

0:38:57.520 --> 0:39:00.680
<v Speaker 1>will also be stripped away to allow for more of

0:39:00.719 --> 0:39:05.040
<v Speaker 1>a surveillance state kind of United States due to fears

0:39:05.040 --> 0:39:08.640
<v Speaker 1>of terrorism. Now, while I do know that this prediction

0:39:08.760 --> 0:39:11.640
<v Speaker 1>is kind of negative, it is something that I'm very

0:39:11.719 --> 0:39:14.440
<v Speaker 1>keenly aware of due to the fact that I'm currently

0:39:14.480 --> 0:39:18.960
<v Speaker 1>studying privacy and security regulations for my own podcast. So

0:39:19.000 --> 0:39:23.160
<v Speaker 1>it's something that I've seen as a growing concern in

0:39:23.280 --> 0:39:26.719
<v Speaker 1>the last half often and something that will continue to

0:39:26.760 --> 0:39:30.200
<v Speaker 1>be a concern in I think net neutrality is going

0:39:30.239 --> 0:39:36.239
<v Speaker 1>to suffer a huge setback in Net neutrality covers a

0:39:36.280 --> 0:39:38.680
<v Speaker 1>lot of territory, but one thing in particular I'd like

0:39:38.800 --> 0:39:42.839
<v Speaker 1>to address is the issue around Internet service providers, as

0:39:42.880 --> 0:39:47.320
<v Speaker 1>common carriers will likely see that decision reversed in twenty seventeen,

0:39:47.400 --> 0:39:49.600
<v Speaker 1>giving I s p s more freedom to operate the

0:39:49.600 --> 0:39:53.799
<v Speaker 1>way they had been before the FCC reclassified them. And

0:39:53.840 --> 0:39:56.880
<v Speaker 1>since many I s p s are also content providers,

0:39:56.920 --> 0:40:00.720
<v Speaker 1>we could see fragmentation of the Internet experience as companies

0:40:00.719 --> 0:40:05.919
<v Speaker 1>give their own content preferential treatment over competitors content. So,

0:40:06.360 --> 0:40:09.400
<v Speaker 1>in other words, if you if you own the pipes,

0:40:09.760 --> 0:40:12.040
<v Speaker 1>but you also own the stuff that's in the pipes,

0:40:12.560 --> 0:40:14.520
<v Speaker 1>or at least some of the stuff that's in the pipes.

0:40:15.239 --> 0:40:19.799
<v Speaker 1>Maybe you give the stuff you own more speed than

0:40:19.920 --> 0:40:23.560
<v Speaker 1>you do other people's stuff. You don't own that stuff,

0:40:23.600 --> 0:40:25.839
<v Speaker 1>so but you own the pipes. So you're gonna make

0:40:25.840 --> 0:40:28.640
<v Speaker 1>sure that your stuff goes through fine, and everyone else's

0:40:28.640 --> 0:40:33.200
<v Speaker 1>stuff can move as at whatever speed you feel is necessary.

0:40:33.600 --> 0:40:37.759
<v Speaker 1>That's the concern. Um here's an example. If you have

0:40:38.320 --> 0:40:42.200
<v Speaker 1>Comcast as an Internet service provider, you might notice in

0:40:42.239 --> 0:40:47.040
<v Speaker 1>this world, this hypothetical world, I should add that Comcast

0:40:47.160 --> 0:40:51.280
<v Speaker 1>content pops right up on your connected devices. So anything

0:40:51.320 --> 0:40:53.680
<v Speaker 1>you have connected through your home that you're accessing that's

0:40:53.680 --> 0:40:59.080
<v Speaker 1>a Comcast service, you get it immediately. It's perfect, no weight, great,

0:40:59.280 --> 0:41:04.879
<v Speaker 1>great experience. But stuff like Netflix, which isn't owned by Comcast,

0:41:05.719 --> 0:41:11.200
<v Speaker 1>doesn't have that smooth experience. Meanwhile, someone who's using a

0:41:11.280 --> 0:41:14.000
<v Speaker 1>T and T S service has a different experience than

0:41:14.040 --> 0:41:17.080
<v Speaker 1>you do. Comcast stuff doesn't come through on a T

0:41:17.200 --> 0:41:20.040
<v Speaker 1>and T S service. Instead, some native A T and

0:41:20.160 --> 0:41:24.640
<v Speaker 1>T content comes through easily, but other stuff it's really slow.

0:41:24.920 --> 0:41:28.480
<v Speaker 1>Discouraging people from using that other stuff and encouraging them

0:41:28.480 --> 0:41:32.439
<v Speaker 1>to use the I, S P S own content. See,

0:41:32.440 --> 0:41:34.000
<v Speaker 1>that's the kind of stuff that could happen if we

0:41:34.080 --> 0:41:36.840
<v Speaker 1>see net neutrality dismissed. We could even get to a

0:41:36.880 --> 0:41:39.680
<v Speaker 1>point where companies just say, you know what, I'm not

0:41:39.719 --> 0:41:44.440
<v Speaker 1>going to allow that content across my network period. That's

0:41:44.560 --> 0:41:48.480
<v Speaker 1>a possibility. It's not necessarily likely, but it is possible,

0:41:49.360 --> 0:41:51.120
<v Speaker 1>and there are a lot of other implications as well

0:41:51.160 --> 0:41:54.160
<v Speaker 1>beyond this. Now, it's not necessarily true that all I

0:41:54.320 --> 0:41:57.120
<v Speaker 1>s p s will immediately resort to strategies that fragment

0:41:57.160 --> 0:42:00.319
<v Speaker 1>the Internet experience. You could see companies to used to

0:42:00.320 --> 0:42:04.279
<v Speaker 1>remain fair with all content as a means of being competitive.

0:42:04.680 --> 0:42:07.000
<v Speaker 1>In other words, they're not gonna sit there and act

0:42:07.040 --> 0:42:10.319
<v Speaker 1>against somebody else because the customers would say, well, I

0:42:10.360 --> 0:42:13.560
<v Speaker 1>don't want to get my Internet service from Company A

0:42:14.320 --> 0:42:17.160
<v Speaker 1>because they're doing this jerk face move. I'll go with

0:42:17.280 --> 0:42:22.960
<v Speaker 1>company B. But that assumes that consumers have access to

0:42:23.320 --> 0:42:28.720
<v Speaker 1>multiple I s P options, which isn't exactly the case necessarily.

0:42:29.000 --> 0:42:31.840
<v Speaker 1>In the United States. For example, where I live, there's

0:42:31.960 --> 0:42:35.440
<v Speaker 1>only one I s P that delivers speeds greater than

0:42:35.480 --> 0:42:40.279
<v Speaker 1>ten megabits per second. So there's one that delivers at

0:42:40.320 --> 0:42:43.400
<v Speaker 1>a hundred megabits per second, and then all the others

0:42:43.640 --> 0:42:47.279
<v Speaker 1>are at ten megabits per second or slower. Because of that,

0:42:47.600 --> 0:42:51.439
<v Speaker 1>there's no incentive for the I s P I use

0:42:51.760 --> 0:42:54.840
<v Speaker 1>to cater to customers because it's already got an enormous

0:42:54.880 --> 0:42:58.040
<v Speaker 1>competitive advantage over all of the other I s p s.

0:42:58.440 --> 0:43:02.160
<v Speaker 1>It's already ten time is faster than the other I

0:43:02.400 --> 0:43:04.960
<v Speaker 1>s p s in my area. So if it's already

0:43:04.960 --> 0:43:07.560
<v Speaker 1>ten times faster, why do they need to bend over

0:43:07.600 --> 0:43:10.600
<v Speaker 1>backwards to make sure that they're being fair to me?

0:43:10.719 --> 0:43:14.120
<v Speaker 1>They don't. There's no incentive there. I don't have any

0:43:14.160 --> 0:43:18.000
<v Speaker 1>real option. If I leave that I s P, I

0:43:18.080 --> 0:43:20.920
<v Speaker 1>have to go with somebody who is one tenth less speed,

0:43:21.000 --> 0:43:25.200
<v Speaker 1>which is not terribly attractive to me. And without those

0:43:25.200 --> 0:43:29.759
<v Speaker 1>regulations of net neutrality, I don't have any protection that

0:43:29.960 --> 0:43:32.760
<v Speaker 1>my I s P won't go off and do something

0:43:33.480 --> 0:43:37.360
<v Speaker 1>that is puts me on a disadvantage. It's not great,

0:43:38.080 --> 0:43:41.239
<v Speaker 1>not great for me. It's fantastic for the companies, but

0:43:41.400 --> 0:43:45.239
<v Speaker 1>for the consumers not so much. Now, I don't want

0:43:45.239 --> 0:43:48.520
<v Speaker 1>to end this show on a downer note. So here's

0:43:48.560 --> 0:43:55.399
<v Speaker 1>a positive prediction for I think in we're gonna see

0:43:55.400 --> 0:43:58.960
<v Speaker 1>some real movement in the renewable energy market, both from

0:43:59.040 --> 0:44:03.719
<v Speaker 1>big companies and from consumers. Google will be purchasing enough

0:44:03.760 --> 0:44:07.200
<v Speaker 1>electricity from renewable sources to power all of its offices

0:44:07.239 --> 0:44:11.080
<v Speaker 1>and data centers in just with renewable energy. I mean,

0:44:11.080 --> 0:44:16.000
<v Speaker 1>that's amazing. Google consumes a huge amount of electricity, so

0:44:16.040 --> 0:44:21.080
<v Speaker 1>to purchase all of that from renewable sources is fantastic. Meanwhile,

0:44:21.120 --> 0:44:25.680
<v Speaker 1>Tesla and Solar City will be merged at some point

0:44:25.719 --> 0:44:30.319
<v Speaker 1>in seventeen. The merger has already started, and they will

0:44:30.400 --> 0:44:33.120
<v Speaker 1>offer people the chance to switch to solar power and

0:44:33.200 --> 0:44:36.680
<v Speaker 1>get off the grid, depending upon where you live and

0:44:36.719 --> 0:44:40.600
<v Speaker 1>how much money you have, because it is not cheap

0:44:41.160 --> 0:44:43.680
<v Speaker 1>to switch to solar power. Over the long run, you

0:44:43.760 --> 0:44:48.640
<v Speaker 1>might save money, but it's a big initial investment. But

0:44:48.719 --> 0:44:50.279
<v Speaker 1>if you're able to do that, then you would be

0:44:50.280 --> 0:44:54.160
<v Speaker 1>able to get off the grid and generate electricity through

0:44:54.160 --> 0:44:57.080
<v Speaker 1>a renewable source. I think we're gonna see a lot

0:44:57.120 --> 0:45:00.600
<v Speaker 1>more of that in tween. However, it's all so possible

0:45:00.600 --> 0:45:03.920
<v Speaker 1>that we'll see fewer tax incentives and programs that make

0:45:03.960 --> 0:45:08.080
<v Speaker 1>it easier to switch, like to create a financial incentive

0:45:08.200 --> 0:45:13.000
<v Speaker 1>to switch. We might see fewer of those um and

0:45:13.040 --> 0:45:15.400
<v Speaker 1>that might slow down adoption quite a bit. But I

0:45:15.440 --> 0:45:18.040
<v Speaker 1>still have high hopes that by the end of Seen,

0:45:18.600 --> 0:45:22.000
<v Speaker 1>we'll see a big push for environmentally friendly power sources

0:45:22.080 --> 0:45:25.080
<v Speaker 1>in lots of new places, both in big companies and

0:45:25.239 --> 0:45:29.200
<v Speaker 1>in consumer homes. And that's it for my predictions for

0:45:30.719 --> 0:45:34.640
<v Speaker 1>I want to thank I as Actar, tom Merritt, Jason Howell,

0:45:34.800 --> 0:45:38.279
<v Speaker 1>and Shannon Morrise for their contributions to this show. I

0:45:38.480 --> 0:45:41.880
<v Speaker 1>As works for c Net. He is at I As

0:45:41.920 --> 0:45:46.120
<v Speaker 1>I Y A Z on Twitter. Tom Merritt hosts the

0:45:46.200 --> 0:45:49.280
<v Speaker 1>Daily Tech News show and another show called Cord Killers.

0:45:49.520 --> 0:45:52.560
<v Speaker 1>He is at ACE Detect on Twitter. That's a C

0:45:52.920 --> 0:45:57.640
<v Speaker 1>E D T E C T and uh. Jason Howell

0:45:57.840 --> 0:45:59.960
<v Speaker 1>is a host of Tech News Today over at Twitter

0:46:00.400 --> 0:46:04.400
<v Speaker 1>This Week in Tech and is at Jason Howell on Twitter.

0:46:04.719 --> 0:46:07.960
<v Speaker 1>And Shannon Morrise is a host on Hack five That's

0:46:08.160 --> 0:46:10.839
<v Speaker 1>j K five and tons of other shows. You can

0:46:10.880 --> 0:46:14.480
<v Speaker 1>find her on Twitter at at s n U B

0:46:14.880 --> 0:46:19.200
<v Speaker 1>S snubs And thank you for listening to tech stuff

0:46:19.200 --> 0:46:21.360
<v Speaker 1>for another year. I got a lot of plans for

0:46:23.080 --> 0:46:24.840
<v Speaker 1>but I always want to hear from you guys too.

0:46:25.040 --> 0:46:27.319
<v Speaker 1>If there's a subject you'd like me to cover, or

0:46:27.400 --> 0:46:29.480
<v Speaker 1>someone I should interview on the show or have as

0:46:29.480 --> 0:46:32.840
<v Speaker 1>a guest co host. Please let me know. The email

0:46:32.840 --> 0:46:36.120
<v Speaker 1>address is tech stuff at how stuff works dot com,

0:46:36.239 --> 0:46:38.600
<v Speaker 1>or send me a message on Facebook or Twitter. I

0:46:38.719 --> 0:46:41.799
<v Speaker 1>use tech Stuff H s W for both. Hopefully the

0:46:41.880 --> 0:46:44.280
<v Speaker 1>next time you hear me, I will not have a cold,

0:46:45.120 --> 0:46:47.520
<v Speaker 1>because I know you're all wondering why a sound weird

0:46:48.040 --> 0:46:51.400
<v Speaker 1>or weirder than usual. And I will talk to you

0:46:51.440 --> 0:47:00.560
<v Speaker 1>again really soon. Happy New Year. For more on this

0:47:00.760 --> 0:47:03.239
<v Speaker 1>and thousands of other topics, is it how stuff works

0:47:03.280 --> 0:47:13.080
<v Speaker 1>dot com m