WEBVTT - 2011 Prediction Results

0:00:00.280 --> 0:00:02.960
<v Speaker 1>Brought to you by the reinvented two thousand twelve Camray.

0:00:03.160 --> 0:00:08.840
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:09.000 --> 0:00:17.560
<v Speaker 1>tech Stuff from how stuff works dot com. Hello everyone,

0:00:17.600 --> 0:00:20.480
<v Speaker 1>welcome to tech stuff. My name is Chris Poulette, and

0:00:20.480 --> 0:00:22.840
<v Speaker 1>I am an editor at how stuff works dot com.

0:00:22.840 --> 0:00:24.920
<v Speaker 1>Sitting across from me, someone who is not an editor,

0:00:24.960 --> 0:00:28.440
<v Speaker 1>but he is a senior writer, is Jonathan Strickland. When

0:00:28.440 --> 0:00:31.160
<v Speaker 1>the earth was still flat, and clouds made of fire,

0:00:31.200 --> 0:00:35.440
<v Speaker 1>and mountains stretched up to the sky sometimes higher. I

0:00:35.440 --> 0:00:37.479
<v Speaker 1>think I've actually used that quote before. You might have,

0:00:37.680 --> 0:00:41.080
<v Speaker 1>but anyway, Hey, we're talking about stuff we already said before. Anyway,

0:00:41.240 --> 0:00:45.159
<v Speaker 1>that's true. Today we are recording our follow up on

0:00:45.200 --> 0:00:49.320
<v Speaker 1>our predictions for twenty eleven. And before we get into

0:00:49.520 --> 0:00:52.400
<v Speaker 1>what we predicted for the year eleven and how we

0:00:52.520 --> 0:00:55.880
<v Speaker 1>did how our predictions did, we should mention that we're

0:00:55.920 --> 0:01:00.400
<v Speaker 1>recording this in early early early December in order for

0:01:00.480 --> 0:01:02.520
<v Speaker 1>us to have enough episodes to get through the end

0:01:02.520 --> 0:01:05.440
<v Speaker 1>of the year. So, uh, some of these predictions that

0:01:05.480 --> 0:01:09.039
<v Speaker 1>have not come true may still come true. Your mileage

0:01:09.040 --> 0:01:12.760
<v Speaker 1>may vary. I'm covering our bases. Okay, that's good. Did

0:01:12.760 --> 0:01:16.080
<v Speaker 1>you fix the broken scoreboard? Problem that we had. Yes, yes,

0:01:16.120 --> 0:01:19.840
<v Speaker 1>we no longer the whole checks and uh and exes

0:01:19.920 --> 0:01:22.959
<v Speaker 1>have been fixed. I've moved on to a totally different

0:01:23.000 --> 0:01:26.640
<v Speaker 1>score keeping systems. Yeah, so we're comfortable with that. Yeah,

0:01:26.640 --> 0:01:28.280
<v Speaker 1>we don't have to worry. I know that there was

0:01:28.360 --> 0:01:33.160
<v Speaker 1>some there was some controversy or controversy, uh from a

0:01:33.240 --> 0:01:37.600
<v Speaker 1>previous scorecard where apparently all of my predictions got checks

0:01:37.600 --> 0:01:40.600
<v Speaker 1>and all of Chris's predictions got xs no matter what

0:01:40.720 --> 0:01:42.880
<v Speaker 1>the content. I am happy to say that will not

0:01:42.959 --> 0:01:45.720
<v Speaker 1>be the case this year. Alright then, alright, so, uh

0:01:45.880 --> 0:01:48.480
<v Speaker 1>so let's you want to start with them one of

0:01:48.520 --> 0:01:50.360
<v Speaker 1>yours here, I've got, I've got I've got them all

0:01:50.440 --> 0:01:52.480
<v Speaker 1>laid out into mine and yours. Is that how you

0:01:52.520 --> 0:01:55.280
<v Speaker 1>have it as well? Yes, that is so how I

0:01:55.280 --> 0:01:57.880
<v Speaker 1>have it set up. And I have to have to

0:01:57.880 --> 0:02:01.240
<v Speaker 1>own up to picking some I felt were pretty easy

0:02:01.400 --> 0:02:04.600
<v Speaker 1>because that whole checks and excess thing through me, and

0:02:04.640 --> 0:02:08.080
<v Speaker 1>I figured I wanted at least one or two that

0:02:08.160 --> 0:02:11.080
<v Speaker 1>I figured I could actually, like you just nail it. Yeah. So,

0:02:11.600 --> 0:02:15.400
<v Speaker 1>speaking of which, I said that the iPad two would

0:02:15.400 --> 0:02:18.480
<v Speaker 1>get a would get a camera, forward facing camera and

0:02:18.520 --> 0:02:21.920
<v Speaker 1>a faster processor. And I got the faster processor thing, right,

0:02:21.960 --> 0:02:24.720
<v Speaker 1>and I got well, I sort of got the camera thing.

0:02:25.200 --> 0:02:28.080
<v Speaker 1>It's got a couple of cameras right right. You you

0:02:28.120 --> 0:02:30.320
<v Speaker 1>originally said it was just gonna be the one camera

0:02:30.360 --> 0:02:33.120
<v Speaker 1>and it'd be forward facing. So that was based on

0:02:33.160 --> 0:02:35.040
<v Speaker 1>the fact that you know, I have an iPad one

0:02:35.520 --> 0:02:37.720
<v Speaker 1>and it's got this little if you have if you

0:02:37.760 --> 0:02:39.959
<v Speaker 1>see an iPad one, you could see on the opposite

0:02:40.080 --> 0:02:42.639
<v Speaker 1>end of the front of it from one of the

0:02:43.120 --> 0:02:45.840
<v Speaker 1>home button is there's sort of a little Yeah, if

0:02:45.840 --> 0:02:47.080
<v Speaker 1>you hold it the right light, you could see the

0:02:47.080 --> 0:02:49.200
<v Speaker 1>sort of a little cut out where the camera might

0:02:49.280 --> 0:02:52.519
<v Speaker 1>have been had they chosen to throw it in there. Right. Well,

0:02:52.600 --> 0:02:55.200
<v Speaker 1>maybe they didn't have the miniaturization just right where they

0:02:55.200 --> 0:02:57.320
<v Speaker 1>could fit all the components in, or maybe it's just

0:02:57.560 --> 0:03:00.840
<v Speaker 1>you know, problems or whatever. Yeah, but anyway, yeah, so,

0:03:01.080 --> 0:03:03.440
<v Speaker 1>but but you've got that more right than wrong. So

0:03:03.639 --> 0:03:08.320
<v Speaker 1>you get uh, let me check my score sheet here, Okay,

0:03:08.680 --> 0:03:13.239
<v Speaker 1>page seventy three. You get one one and a half

0:03:13.320 --> 0:03:21.000
<v Speaker 1>tablets for that that prediction tablets. That's that's what says here. Okay, yeah, okay,

0:03:21.080 --> 0:03:24.040
<v Speaker 1>So I said that the iPhone would move to Verizon,

0:03:24.120 --> 0:03:27.400
<v Speaker 1>but not until twelve and you said it was going

0:03:27.440 --> 0:03:29.480
<v Speaker 1>to come out in twenty eleven, and you got that right,

0:03:29.520 --> 0:03:31.840
<v Speaker 1>And what it did in fact moved to right. In fact,

0:03:31.840 --> 0:03:35.400
<v Speaker 1>it moved to Sprint as well. In UM, I said

0:03:35.400 --> 0:03:37.560
<v Speaker 1>that they were going to announce that the iPhone was

0:03:37.560 --> 0:03:39.280
<v Speaker 1>moving to Verizon, but I did not think it was

0:03:39.320 --> 0:03:41.280
<v Speaker 1>going to move to twelve And at the time, I

0:03:41.320 --> 0:03:45.120
<v Speaker 1>believe that that was because of the rumored agreement between

0:03:45.160 --> 0:03:47.400
<v Speaker 1>Apple and a T and tight that it was going

0:03:47.480 --> 0:03:49.360
<v Speaker 1>to be a five year agreement, which means that it

0:03:49.360 --> 0:03:54.000
<v Speaker 1>wouldn't have expired until But whatever the cases, it actually

0:03:54.040 --> 0:03:57.120
<v Speaker 1>did move to Verizon. So whereas I got the announced

0:03:57.160 --> 0:03:59.760
<v Speaker 1>part right, I got the date totally wrong. You got it.

0:04:00.720 --> 0:04:05.120
<v Speaker 1>Let me check here, Um I have to cross reference. Oh,

0:04:05.240 --> 0:04:10.360
<v Speaker 1>according to this, I get a smart foe, but not

0:04:10.400 --> 0:04:13.640
<v Speaker 1>be any because um I didn't get it, all right,

0:04:14.320 --> 0:04:16.280
<v Speaker 1>So I it's so we got one half tablets to

0:04:16.360 --> 0:04:19.880
<v Speaker 1>a smart foe, all right, Okay, then let's move back

0:04:19.880 --> 0:04:24.000
<v Speaker 1>to one of yours. All right. I predicted that the

0:04:24.040 --> 0:04:30.480
<v Speaker 1>Google Chrome OS would get an underwhelming response, and yeah,

0:04:30.480 --> 0:04:34.239
<v Speaker 1>that's I mean it was. People were excited when Google

0:04:34.320 --> 0:04:38.360
<v Speaker 1>Chrome officially debuted back in the summer, and a lot

0:04:38.360 --> 0:04:40.320
<v Speaker 1>of people did try and sign up to get a

0:04:40.400 --> 0:04:44.840
<v Speaker 1>Chrome book, but ultimately I think, I mean, I haven't

0:04:44.880 --> 0:04:49.640
<v Speaker 1>heard anything about chromebooks since the Io event. Really. Yeah,

0:04:49.680 --> 0:04:51.520
<v Speaker 1>it's just not one of those things that's been in

0:04:51.520 --> 0:04:53.440
<v Speaker 1>the news. I mean, we know they're out there and

0:04:53.520 --> 0:04:56.320
<v Speaker 1>people are developing for them, but it's just not it's

0:04:56.360 --> 0:04:59.159
<v Speaker 1>not taking any like, it's not hitting the news cycle

0:04:59.200 --> 0:05:02.760
<v Speaker 1>at all. Wish I had predicted Wave would would would go,

0:05:03.240 --> 0:05:06.200
<v Speaker 1>would recede, would go out to low time, but but

0:05:06.240 --> 0:05:08.440
<v Speaker 1>I didn't. Well, you get sort of similar because they

0:05:08.520 --> 0:05:10.320
<v Speaker 1>got a lot of hype right out of the gate

0:05:10.360 --> 0:05:14.239
<v Speaker 1>and then they just sort of you know, yeah, yeah,

0:05:14.279 --> 0:05:17.200
<v Speaker 1>well according to this, because of that prediction, in the

0:05:17.200 --> 0:05:19.040
<v Speaker 1>fact that you got it right, you get three shiny

0:05:19.120 --> 0:05:24.640
<v Speaker 1>hubcaps caps. Yeah, so three shiny hubcaps for that prediction.

0:05:25.520 --> 0:05:27.640
<v Speaker 1>Moving back to one of mine, I said that a

0:05:27.720 --> 0:05:29.719
<v Speaker 1>cloud competing would move to the next level with more

0:05:29.760 --> 0:05:32.800
<v Speaker 1>web based services. We saw a lot of web based

0:05:32.800 --> 0:05:36.920
<v Speaker 1>services premier this year. So let's let's just a lot

0:05:36.960 --> 0:05:40.800
<v Speaker 1>of them are our media related, like I Cloud, Google Music,

0:05:41.000 --> 0:05:44.839
<v Speaker 1>Amazon Cloud Player. We also had some players that already

0:05:44.839 --> 0:05:48.200
<v Speaker 1>existed in the out there on the web kind of

0:05:48.240 --> 0:05:50.480
<v Speaker 1>make their way finally over to the United States, Spotify

0:05:50.640 --> 0:05:53.680
<v Speaker 1>being a big example. Um, and of course there's they're

0:05:53.720 --> 0:05:56.920
<v Speaker 1>the other ones that were here already, mog and r

0:05:56.960 --> 0:05:59.920
<v Speaker 1>d O yep. So I think I think it's a

0:06:00.120 --> 0:06:02.920
<v Speaker 1>to say that that's that's true. And now we probably

0:06:02.960 --> 0:06:07.159
<v Speaker 1>didn't see as many moves in the enterprise space as

0:06:07.200 --> 0:06:10.120
<v Speaker 1>could have been. Right, We didn't see that many companies

0:06:10.160 --> 0:06:13.680
<v Speaker 1>moved to all cloud based services, although I know there

0:06:13.680 --> 0:06:16.520
<v Speaker 1>are a few out there that have adopted the Google

0:06:17.200 --> 0:06:21.120
<v Speaker 1>ecosystem as their corporate ecosystem, so that they use Google

0:06:21.200 --> 0:06:25.599
<v Speaker 1>Docs and Gmail and everything as their corporate email. So

0:06:25.720 --> 0:06:28.320
<v Speaker 1>there have been some. It's just not been huge, but

0:06:28.480 --> 0:06:31.119
<v Speaker 1>we've seen it a lot in the consumer space. So

0:06:31.440 --> 0:06:34.240
<v Speaker 1>for that prediction, I get rain drops keep falling on

0:06:34.320 --> 0:06:36.479
<v Speaker 1>my head, which is gonna make the rest of this

0:06:37.000 --> 0:06:40.960
<v Speaker 1>episode a little damp. You know, I'm I'm not sure

0:06:41.000 --> 0:06:43.400
<v Speaker 1>I understand exactly how you came up with a scoring system.

0:06:43.600 --> 0:06:45.520
<v Speaker 1>The problem is really going to be totaling it at

0:06:45.560 --> 0:06:48.400
<v Speaker 1>the end. But let's just keep going, shall we. All Right,

0:06:48.440 --> 0:06:51.599
<v Speaker 1>all right, well, I uh I believe that. Uh well,

0:06:51.920 --> 0:06:56.120
<v Speaker 1>let's actually go uh in in you know, uh continuum. Here,

0:06:56.360 --> 0:06:58.480
<v Speaker 1>I'm going to skip ahead on your list that you

0:06:58.560 --> 0:07:02.160
<v Speaker 1>put together, and and point out that I did say

0:07:02.200 --> 0:07:06.160
<v Speaker 1>that Spotify would show up here, yes, and uh, and

0:07:06.200 --> 0:07:08.560
<v Speaker 1>I didn't think so. I didn't think so I said

0:07:08.600 --> 0:07:11.080
<v Speaker 1>it would not. Well I at the time when you

0:07:11.080 --> 0:07:12.800
<v Speaker 1>made the prediction, and I think it was an off

0:07:12.840 --> 0:07:15.120
<v Speaker 1>the cuff prediction, if I recall correctly. Yeah, that was.

0:07:15.240 --> 0:07:16.880
<v Speaker 1>That was That felt like going out on a lamb.

0:07:16.920 --> 0:07:19.160
<v Speaker 1>I remember, Yeah, And I I just said, you know,

0:07:19.200 --> 0:07:21.520
<v Speaker 1>I said, well, let's make this interesting. I'll say it

0:07:21.560 --> 0:07:23.400
<v Speaker 1>won't and that way, no matter what, one of us

0:07:23.400 --> 0:07:26.120
<v Speaker 1>will be right. And in that respect, I was right.

0:07:27.040 --> 0:07:30.760
<v Speaker 1>But you you got that, you got that correct. Spotify did,

0:07:30.920 --> 0:07:33.400
<v Speaker 1>in fact debut in the United States. I was a

0:07:33.440 --> 0:07:36.120
<v Speaker 1>little I was a little skeptical because there had been

0:07:36.200 --> 0:07:38.480
<v Speaker 1>at the time when we made the podcast of the Predictions,

0:07:38.800 --> 0:07:41.800
<v Speaker 1>there had been a lot of news about how Spotify

0:07:41.920 --> 0:07:45.760
<v Speaker 1>had been having some problems making agreements with or reaching

0:07:45.800 --> 0:07:48.720
<v Speaker 1>agreements with major labels. Yeah, and that was the thing

0:07:48.720 --> 0:07:51.000
<v Speaker 1>that was holding it back. They had wanted to debut

0:07:51.160 --> 0:07:53.840
<v Speaker 1>a lot earlier than they had the opportunity to say,

0:07:54.000 --> 0:07:57.360
<v Speaker 1>and I just saw that that resistance holding out even

0:07:57.440 --> 0:08:00.440
<v Speaker 1>more than uh, than it actually did. So yeah, you

0:08:00.560 --> 0:08:02.800
<v Speaker 1>got that right. And let's say, according to this you

0:08:02.840 --> 0:08:06.520
<v Speaker 1>get the black spot from Treasure Island. So it seems

0:08:06.560 --> 0:08:11.200
<v Speaker 1>kind of bad, you know. I'm sorry, it's just it's

0:08:11.240 --> 0:08:14.240
<v Speaker 1>some of these awards are a little less prestigious and

0:08:14.240 --> 0:08:18.560
<v Speaker 1>and glamorous than others. But that's the Spotify Award, right there,

0:08:18.800 --> 0:08:22.600
<v Speaker 1>Spotify Award. Okay, alright, So I said that there was

0:08:22.640 --> 0:08:27.840
<v Speaker 1>gonna be a dramatic increase in cyber warfare in twenty eleven,

0:08:27.880 --> 0:08:29.680
<v Speaker 1>and I think it's safe to say that there was

0:08:31.000 --> 0:08:34.839
<v Speaker 1>a greater focus on cyber warfare um, and we saw

0:08:35.520 --> 0:08:40.160
<v Speaker 1>several stories pop up about cyber warfare. Uh. And there

0:08:40.200 --> 0:08:44.080
<v Speaker 1>was the recent news that came out where, uh, we

0:08:44.120 --> 0:08:49.240
<v Speaker 1>had accusations that state sponsored hacking had been taking place

0:08:49.280 --> 0:08:54.000
<v Speaker 1>over in Europe. Yeah. Uh, Plus there was the news

0:08:54.040 --> 0:08:58.600
<v Speaker 1>about trying to hack into various systems in uh Iran.

0:08:59.120 --> 0:09:04.040
<v Speaker 1>There was a allegations that Chinese systems were trying to

0:09:04.080 --> 0:09:07.240
<v Speaker 1>hack into various security systems around the world. And then

0:09:07.240 --> 0:09:11.320
<v Speaker 1>there was stuckx net, which was um a piece of

0:09:11.360 --> 0:09:15.440
<v Speaker 1>malware that people said was specifically aimed at taking out

0:09:16.040 --> 0:09:20.319
<v Speaker 1>Iran's nuclear infrastructure because of what it would do is

0:09:20.360 --> 0:09:25.000
<v Speaker 1>it would change the the RPMs at which a various

0:09:25.000 --> 0:09:28.199
<v Speaker 1>equipment would rotate, and it would cause like a centrifuge,

0:09:28.200 --> 0:09:32.800
<v Speaker 1>and it would cause potentially it would cause a massive meltdown.

0:09:32.960 --> 0:09:34.920
<v Speaker 1>Well maybe not a meltdown, but it would cause a

0:09:34.960 --> 0:09:39.400
<v Speaker 1>massive accident failure. But in in the case of stux Net,

0:09:39.520 --> 0:09:42.040
<v Speaker 1>it looks like all of those were detected early enough

0:09:42.080 --> 0:09:47.559
<v Speaker 1>to to um head off a major malfunction. One of

0:09:47.600 --> 0:09:50.440
<v Speaker 1>the things we've talked about when we talk about cyber attacks,

0:09:50.440 --> 0:09:53.239
<v Speaker 1>though of any kind, really is that it's difficult sometimes

0:09:53.240 --> 0:09:56.120
<v Speaker 1>to pinpoint, especially from people who know what they're doing,

0:09:56.280 --> 0:09:59.520
<v Speaker 1>difficult to pinpoint exactly who's behind an attack. So it

0:09:59.520 --> 0:10:03.160
<v Speaker 1>could be uh, state sponsored, it could not be, and

0:10:03.360 --> 0:10:06.880
<v Speaker 1>we might never know without you know, having something to

0:10:06.920 --> 0:10:09.480
<v Speaker 1>back it up, having a proof behind it. And so

0:10:09.520 --> 0:10:11.800
<v Speaker 1>it's kind of difficult to say whether some of these

0:10:11.800 --> 0:10:14.400
<v Speaker 1>were state sponsored or not because of the way they

0:10:14.440 --> 0:10:17.640
<v Speaker 1>appear to have happened. There are plenty of stories about

0:10:17.679 --> 0:10:23.240
<v Speaker 1>it's anonymous and lull SEC attacking various targets. So I

0:10:23.600 --> 0:10:26.160
<v Speaker 1>think I got this, uh fairly, I think this. I

0:10:26.200 --> 0:10:28.760
<v Speaker 1>think it's fair to give me this one. So apparently,

0:10:28.800 --> 0:10:31.600
<v Speaker 1>according to this, I get in return for that correct

0:10:32.360 --> 0:10:35.680
<v Speaker 1>prediction about an increase in cyber war, I get high

0:10:35.800 --> 0:10:42.280
<v Speaker 1>anxiety on DVD. Okay, all right, So, uh let's see

0:10:43.080 --> 0:10:46.280
<v Speaker 1>the year the tablet. Um that was one of yours

0:10:47.240 --> 0:10:50.800
<v Speaker 1>and uh I said that, um, the Android OS would

0:10:50.920 --> 0:10:55.240
<v Speaker 1>launch a new era of tablets. Um. I feel like

0:10:56.040 --> 0:10:58.600
<v Speaker 1>in one respect, the I mean, the tablet market really

0:10:58.600 --> 0:11:03.200
<v Speaker 1>did take off. Um, but still the Android. I thought

0:11:03.200 --> 0:11:05.839
<v Speaker 1>the release of Android would do for tablets what it

0:11:05.880 --> 0:11:11.880
<v Speaker 1>did for smart smartphones, where it outnumbers the sales of

0:11:11.960 --> 0:11:16.439
<v Speaker 1>iOS based devices that's Apple's operating system for its own devices,

0:11:16.520 --> 0:11:20.920
<v Speaker 1>and not so much out selling iOS. The iPad is

0:11:20.960 --> 0:11:23.520
<v Speaker 1>still a dominant player in the market. Although there there

0:11:23.559 --> 0:11:26.280
<v Speaker 1>are some quite good Android based tablets, there are also

0:11:26.360 --> 0:11:30.680
<v Speaker 1>some quite terrible. Yeah, and and we also saw the

0:11:30.720 --> 0:11:35.040
<v Speaker 1>debut of things like the Amazon Kindle Fire, which is

0:11:35.040 --> 0:11:37.720
<v Speaker 1>is burning up the charts right now as we record

0:11:37.760 --> 0:11:41.800
<v Speaker 1>this Fire, I see what you did. Also, Barnes and

0:11:41.800 --> 0:11:44.559
<v Speaker 1>Noble came out with its own Nook tablet that did

0:11:44.640 --> 0:11:47.880
<v Speaker 1>quite well. A lot of enthusiasts really enjoy that. Again,

0:11:47.880 --> 0:11:49.760
<v Speaker 1>it's early December, so it's kind of hard to tell.

0:11:49.800 --> 0:11:54.800
<v Speaker 1>Those are fairly new. The BlackBerry playbook didn't do as well,

0:11:55.120 --> 0:11:57.880
<v Speaker 1>but um but it's also out there. And then there's

0:11:57.880 --> 0:12:01.480
<v Speaker 1>the second place compcause second place to the iPad, which

0:12:01.480 --> 0:12:04.040
<v Speaker 1>had its own We even devoted our own episode to

0:12:04.120 --> 0:12:11.160
<v Speaker 1>this uh HPS lovely uh webOS based device, which you know,

0:12:11.160 --> 0:12:14.520
<v Speaker 1>the webo s of course said bye bye to everybody,

0:12:14.600 --> 0:12:18.120
<v Speaker 1>although you never know. I mean that whole situation is

0:12:18.160 --> 0:12:20.160
<v Speaker 1>so I'm going to talk about that in our we

0:12:20.160 --> 0:12:24.520
<v Speaker 1>haven't recorded our predictions, I'm going to talk about that one.

0:12:24.559 --> 0:12:27.040
<v Speaker 1>But yeah, as a matter of fact, as a Palm

0:12:27.080 --> 0:12:29.880
<v Speaker 1>decided to discontinue it, they put it on massive discount

0:12:29.880 --> 0:12:32.880
<v Speaker 1>and now holds the second place behind the eye because

0:12:32.920 --> 0:12:35.040
<v Speaker 1>if you don't remember, the touch pad went on sale

0:12:35.040 --> 0:12:38.040
<v Speaker 1>for like wasn't it, Yeah, and people just gobbled them

0:12:38.080 --> 0:12:40.800
<v Speaker 1>up because everyone's like, a hundred dollar tablet, that's exactly

0:12:40.800 --> 0:12:42.720
<v Speaker 1>what I want. I don't care what uperating system it

0:12:42.720 --> 0:12:45.440
<v Speaker 1>has or what it can or can't do. Uh yeah,

0:12:45.520 --> 0:12:48.880
<v Speaker 1>that's probably gonna be some buyer's remorse in the future

0:12:49.000 --> 0:12:50.840
<v Speaker 1>from some of those folks. But it sort of depends

0:12:50.840 --> 0:12:53.560
<v Speaker 1>on what HP does with the whether or not whether

0:12:53.640 --> 0:12:56.560
<v Speaker 1>or not it truly is continued to be supported in

0:12:56.679 --> 0:13:01.880
<v Speaker 1>some fashion or not, it could all be a huge ploy. Yeah. Anyhow,

0:13:02.080 --> 0:13:04.400
<v Speaker 1>so yeah, I think I don't know. I get some

0:13:04.440 --> 0:13:06.520
<v Speaker 1>credit there. I didn't. I didn't get the android part

0:13:06.720 --> 0:13:10.559
<v Speaker 1>quite right. Right, According to to my notes here, this

0:13:10.640 --> 0:13:16.480
<v Speaker 1>means that you get a red herring. So um, it's

0:13:16.600 --> 0:13:17.880
<v Speaker 1>I think. I guess I'll have to see how this

0:13:17.960 --> 0:13:20.240
<v Speaker 1>all totally. It's in a tank in the back, so

0:13:20.400 --> 0:13:23.360
<v Speaker 1>I'll bring it out after the show, unless, of course,

0:13:23.400 --> 0:13:26.760
<v Speaker 1>it disappeared, in which case will have herring loss. That's true, Yeah,

0:13:26.880 --> 0:13:29.520
<v Speaker 1>it would be a dramatic loss and herring. Speaking of tablets,

0:13:29.559 --> 0:13:32.199
<v Speaker 1>your next prediction was sort of tablet related. Yeah, I

0:13:32.200 --> 0:13:35.200
<v Speaker 1>said that laptop sales would depth but they wouldn't totally

0:13:35.240 --> 0:13:39.520
<v Speaker 1>crash due to uh, tablets, And that's pretty much true.

0:13:39.600 --> 0:13:42.880
<v Speaker 1>I mean there was laptop sales took a pretty big hit,

0:13:43.400 --> 0:13:47.600
<v Speaker 1>but desktop sales have taken a hit due to laptops. Yeah,

0:13:47.720 --> 0:13:50.800
<v Speaker 1>laptops still haven't been completely replaced yet, and I don't

0:13:50.800 --> 0:13:52.880
<v Speaker 1>think they ever will be totally replaced, just like I

0:13:52.880 --> 0:13:56.520
<v Speaker 1>don't think desktops will ever be totally replaced. I think

0:13:56.559 --> 0:13:59.960
<v Speaker 1>I think maybe our our focus will be will show

0:14:00.280 --> 0:14:03.400
<v Speaker 1>to mobile devices effect it already has but it will

0:14:03.440 --> 0:14:06.440
<v Speaker 1>continue to move in that direction, and that laptops and

0:14:06.559 --> 0:14:11.880
<v Speaker 1>desktops will be used more for very specific but limited functions. Um,

0:14:11.960 --> 0:14:13.840
<v Speaker 1>I think that will continue, but I don't. I don't

0:14:13.880 --> 0:14:18.800
<v Speaker 1>see them disappearing entirely. So yeah, I get, Um, you

0:14:18.840 --> 0:14:20.720
<v Speaker 1>know what I got for this one? What's that? I

0:14:20.760 --> 0:14:25.560
<v Speaker 1>got the tildy key from my old computer. That's what

0:14:25.640 --> 0:14:29.480
<v Speaker 1>I got for that one. Then yeah, um, how long

0:14:29.480 --> 0:14:32.720
<v Speaker 1>has that been missing? Anyway? About two and a half years,

0:14:32.760 --> 0:14:37.080
<v Speaker 1>I think, Yeah, got a hole in it. Yeah, but

0:14:37.120 --> 0:14:40.560
<v Speaker 1>you know how that happened? We uh, you know, we

0:14:40.600 --> 0:14:45.080
<v Speaker 1>talked about on our podcast Google Plus this year, which

0:14:45.120 --> 0:14:48.280
<v Speaker 1>of course none of us predicted, and uh in Facebook,

0:14:48.440 --> 0:14:50.520
<v Speaker 1>but you know what get we what we didn't talk

0:14:50.560 --> 0:14:53.920
<v Speaker 1>about so much? What's my Space? I wonder why that happened? Well,

0:14:53.960 --> 0:14:58.960
<v Speaker 1>you know, I made a prediction that Fox was gonna unload. Yeah,

0:14:58.960 --> 0:15:00.920
<v Speaker 1>technically I should say, and this is my fault because

0:15:00.960 --> 0:15:02.480
<v Speaker 1>I wrote down the notes this way, but technically we

0:15:02.520 --> 0:15:07.760
<v Speaker 1>should say news Corps, the parent company. Yeah, so I'm

0:15:07.800 --> 0:15:09.840
<v Speaker 1>just reading it. So but yeah, news Corp. No, No,

0:15:09.880 --> 0:15:11.640
<v Speaker 1>I was the one who wrote it. So it's you know,

0:15:11.800 --> 0:15:14.520
<v Speaker 1>and I don't blame you at all that news Corps sold.

0:15:15.280 --> 0:15:18.120
<v Speaker 1>You said that news Core would sell my Space for

0:15:18.960 --> 0:15:22.040
<v Speaker 1>a dollar fifty and some coupon books. You were so

0:15:22.120 --> 0:15:26.000
<v Speaker 1>close thirty five million dollars. Yeah, and they spent what

0:15:26.080 --> 0:15:29.200
<v Speaker 1>five eight million when they bought it something like that.

0:15:29.320 --> 0:15:33.040
<v Speaker 1>It's that's crazy, you know. Every time I right after

0:15:33.080 --> 0:15:36.160
<v Speaker 1>that happened, every time I passed by those billboards advertising

0:15:36.160 --> 0:15:38.560
<v Speaker 1>how many millions you could win if you if you

0:15:38.560 --> 0:15:41.080
<v Speaker 1>won the lottery, I thought, that's funny. I could have

0:15:41.120 --> 0:15:44.320
<v Speaker 1>bought my my Space if I won the lottery after

0:15:44.360 --> 0:15:47.200
<v Speaker 1>taxes even Yeah, I mean that that I would have

0:15:47.280 --> 0:15:49.160
<v Speaker 1>done that. You nailed it, though, I mean, and that

0:15:49.240 --> 0:15:52.000
<v Speaker 1>was one of those those predictions that it sounds like

0:15:52.040 --> 0:15:55.200
<v Speaker 1>it's really kind of like, if you weren't if you're

0:15:55.240 --> 0:15:57.360
<v Speaker 1>not really thinking about too hard, if you're not putting

0:15:57.400 --> 0:16:01.200
<v Speaker 1>yourself back in the mind frame we were in twenty

0:16:01.840 --> 0:16:04.160
<v Speaker 1>you might think, well, that's an easy prediction to make,

0:16:04.200 --> 0:16:06.640
<v Speaker 1>except for the fact that news Corp had held onto

0:16:06.680 --> 0:16:09.160
<v Speaker 1>my Space. I mean, my Space was hadn't been relevant

0:16:09.200 --> 0:16:11.840
<v Speaker 1>for a couple of years. I was actually thinking there

0:16:11.880 --> 0:16:14.720
<v Speaker 1>was more of a possibility in terms of that. I

0:16:14.720 --> 0:16:17.040
<v Speaker 1>was thinking that was possible that Newscore might just bury

0:16:17.160 --> 0:16:22.960
<v Speaker 1>my space right and right next to man. Yeah, pretty much. Yeah,

0:16:22.960 --> 0:16:25.920
<v Speaker 1>I eat it. But no, they and you said they'd

0:16:25.920 --> 0:16:28.680
<v Speaker 1>sell it. They did, so you get, oh, oh, it

0:16:28.720 --> 0:16:31.520
<v Speaker 1>looks like it's our most valuable prize. Yet you get

0:16:31.640 --> 0:16:36.080
<v Speaker 1>Rupert Murdock's big toenail. You know, if you believe in

0:16:36.120 --> 0:16:39.040
<v Speaker 1>like sympathetic magic, you can work some mean mojo. Now,

0:16:39.880 --> 0:16:43.720
<v Speaker 1>so hey, you just hold on to that. So alright, So,

0:16:43.840 --> 0:16:46.440
<v Speaker 1>speaking of sales, Yeah, I said that eBay would sell

0:16:46.480 --> 0:16:51.040
<v Speaker 1>off Skype. Now the eagle eared listeners out there, we're

0:16:51.080 --> 0:16:53.160
<v Speaker 1>all eager to point out that, um hey, you know what,

0:16:53.280 --> 0:16:57.120
<v Speaker 1>he may technically sold Skype in two thousand nine, So

0:16:57.280 --> 0:16:59.840
<v Speaker 1>making that a two thousand prediction for two thousand eleven,

0:16:59.880 --> 0:17:03.200
<v Speaker 1>my it seem a little ridiculous, except that eBay had

0:17:03.240 --> 0:17:08.119
<v Speaker 1>retained thirty five of Skype. They were they weren't the

0:17:08.160 --> 0:17:10.920
<v Speaker 1>majority owner in Skype anymore, but they still owned thirty

0:17:11.880 --> 0:17:13.840
<v Speaker 1>And that's kind of what I was going for when

0:17:13.880 --> 0:17:16.040
<v Speaker 1>I made the prediction, although I didn't make that clear

0:17:16.080 --> 0:17:19.840
<v Speaker 1>in the prediction, so it just sounded ridiculous. But in fact,

0:17:19.920 --> 0:17:23.680
<v Speaker 1>in two thousand eleven, Microsoft bought Skype. Now I think

0:17:23.800 --> 0:17:26.000
<v Speaker 1>I wish I had predicted that Microsoft was going to

0:17:26.080 --> 0:17:27.680
<v Speaker 1>be the company to do this, because then it would

0:17:27.680 --> 0:17:33.040
<v Speaker 1>be a really phenomenal prediction, right, but it but I didn't.

0:17:33.160 --> 0:17:35.760
<v Speaker 1>I didn't foresee it being Microsoft. I just figured someone

0:17:35.760 --> 0:17:38.280
<v Speaker 1>would buy it. And Microsoft bought it for eight point

0:17:38.320 --> 0:17:43.840
<v Speaker 1>five billion dollars. That's a pretty big number. And because

0:17:43.880 --> 0:17:45.359
<v Speaker 1>I got this one pretty much, right, I get a

0:17:45.440 --> 0:17:49.400
<v Speaker 1>chordless phone. Wow, that's that's pretty nice. Yeah, but there's

0:17:49.400 --> 0:17:53.280
<v Speaker 1>no base station. It's just the chordless phone. All right,

0:17:53.480 --> 0:17:57.919
<v Speaker 1>So you know you have more than than I do

0:17:57.960 --> 0:17:59.440
<v Speaker 1>because I was chicken last year, So why don't we

0:17:59.480 --> 0:18:02.680
<v Speaker 1>do another one of Okay? So I also said that

0:18:02.760 --> 0:18:06.320
<v Speaker 1>inleven we would have a true test of the four

0:18:06.400 --> 0:18:09.080
<v Speaker 1>G technologies that would roll out and things like y

0:18:09.200 --> 0:18:12.200
<v Speaker 1>max and lt E. And I know before you guys

0:18:12.280 --> 0:18:14.920
<v Speaker 1>right in, I know that y max is not truly

0:18:15.000 --> 0:18:18.639
<v Speaker 1>four G. Uh. In fact, the definition of four G

0:18:18.840 --> 0:18:21.520
<v Speaker 1>now is almost meaningless. We need to do an episode

0:18:21.520 --> 0:18:24.920
<v Speaker 1>specifically about what is two G, three G, four G

0:18:25.560 --> 0:18:28.160
<v Speaker 1>and and why are they designated that way? And why

0:18:28.200 --> 0:18:31.160
<v Speaker 1>is it so complicated? Yeah, I mean the big thing

0:18:31.240 --> 0:18:34.680
<v Speaker 1>is a speed issue, because I mean even T mobile marketing,

0:18:34.720 --> 0:18:38.160
<v Speaker 1>it's upgraded three G h s P A plus technology.

0:18:38.200 --> 0:18:41.399
<v Speaker 1>They can depending on the market and the technology, like

0:18:41.440 --> 0:18:44.439
<v Speaker 1>in the specific hardware you're using, H s P A

0:18:44.480 --> 0:18:48.440
<v Speaker 1>plus can outpace LTE, so probably won't by the time

0:18:48.600 --> 0:18:52.240
<v Speaker 1>lt matures. Right, So that the T mobile's argument was

0:18:52.359 --> 0:18:54.560
<v Speaker 1>that it was a four G speed, so you might

0:18:54.560 --> 0:18:56.120
<v Speaker 1>as well call it four a G because if it's

0:18:56.440 --> 0:19:00.760
<v Speaker 1>if if, if we're using the g's as shorthand, then

0:19:00.840 --> 0:19:04.000
<v Speaker 1>we're just saying that this this device is works faster

0:19:04.160 --> 0:19:07.159
<v Speaker 1>than that device, in which case, you know, there's an

0:19:07.680 --> 0:19:10.600
<v Speaker 1>G three G network and the l T E is

0:19:10.640 --> 0:19:12.680
<v Speaker 1>sort of a one G four G networks. It really,

0:19:12.760 --> 0:19:14.800
<v Speaker 1>it just got more confusing. I don't think that we

0:19:14.920 --> 0:19:19.320
<v Speaker 1>really saw a battle there. So but LTE one, you're

0:19:19.400 --> 0:19:21.000
<v Speaker 1>right about that. I did say the l T E

0:19:21.119 --> 0:19:23.399
<v Speaker 1>would win, and that is true. Lt is is by

0:19:23.480 --> 0:19:27.600
<v Speaker 1>far the dominant UH four G technology that's out there

0:19:27.680 --> 0:19:30.320
<v Speaker 1>right now. In fact, I think that within another year

0:19:30.400 --> 0:19:32.680
<v Speaker 1>this is going into a prediction almost but within another

0:19:32.760 --> 0:19:36.119
<v Speaker 1>year it'll probably even more evident, although we may be seeing,

0:19:37.119 --> 0:19:40.239
<v Speaker 1>you know, rumors of the next emerging technology come out.

0:19:40.280 --> 0:19:43.480
<v Speaker 1>By the time we finally settle on this emerging technology,

0:19:43.800 --> 0:19:46.719
<v Speaker 1>of course, that's the way the way tech works. So um,

0:19:46.960 --> 0:19:52.000
<v Speaker 1>I get the letter G. Okay, yeah, at least until

0:19:52.040 --> 0:19:56.399
<v Speaker 1>it comes along because he eats everything except for Z

0:19:56.920 --> 0:19:59.119
<v Speaker 1>and uh you know, I actually I had predicted that

0:19:59.320 --> 0:20:01.240
<v Speaker 1>a T and T would roll out it's for G

0:20:01.400 --> 0:20:03.200
<v Speaker 1>network by the end of the year, and it it

0:20:03.440 --> 0:20:06.280
<v Speaker 1>actually has, which is an LTE network. I think we

0:20:06.359 --> 0:20:10.399
<v Speaker 1>piggyback those in the predictions episode. So do I get

0:20:10.440 --> 0:20:12.320
<v Speaker 1>a G two for for that one? Actually you said

0:20:12.359 --> 0:20:14.760
<v Speaker 1>it was a T and T and uh, strangely enough,

0:20:14.800 --> 0:20:16.520
<v Speaker 1>I think this might have been a typo. But you

0:20:16.640 --> 0:20:22.159
<v Speaker 1>get an ad at you know. They they're terrible as

0:20:22.200 --> 0:20:24.760
<v Speaker 1>far as gas mileage goes. Yeah, and let me tell

0:20:24.800 --> 0:20:27.639
<v Speaker 1>you when I was bringing that sucker into the office

0:20:27.720 --> 0:20:33.000
<v Speaker 1>this morning, Uh, traffic on four hundred was a nightmare. Yeah.

0:20:33.040 --> 0:20:34.560
<v Speaker 1>But the nice thing is you can you know you're

0:20:34.560 --> 0:20:36.800
<v Speaker 1>already there, and that that you don't really have to

0:20:36.880 --> 0:20:38.600
<v Speaker 1>go very far to get up to the floor that

0:20:38.680 --> 0:20:40.760
<v Speaker 1>we're on. No, that's true. I just kind of popped

0:20:40.800 --> 0:20:44.160
<v Speaker 1>open the cockpit and and then just made a quick

0:20:44.240 --> 0:20:46.640
<v Speaker 1>jump over to our our patio and that was fine.

0:20:46.880 --> 0:20:49.159
<v Speaker 1>There you go, all right, So let's see, let me

0:20:49.160 --> 0:20:51.160
<v Speaker 1>do another one. Of mine. I said that, Um oh,

0:20:51.560 --> 0:20:54.639
<v Speaker 1>here's one that was very excited about. Yes, I predicted

0:20:54.720 --> 0:20:58.439
<v Speaker 1>that a new version of the Nintendo WE would debut

0:20:58.520 --> 0:21:02.480
<v Speaker 1>at E three and you was right right. I can't

0:21:02.520 --> 0:21:05.960
<v Speaker 1>believe it. Uh yeah, that WE You was you? Was?

0:21:06.320 --> 0:21:10.680
<v Speaker 1>You was exactly right? Yes We you Ui Ui? Um

0:21:10.920 --> 0:21:14.360
<v Speaker 1>it sounds like a European ambulance. Yeah. I had said

0:21:14.400 --> 0:21:16.639
<v Speaker 1>that it would probably be the HD version of the WE,

0:21:16.880 --> 0:21:18.440
<v Speaker 1>but it's a little bit more than that. Because this

0:21:18.600 --> 0:21:20.920
<v Speaker 1>is the WE. You also has a new kind of

0:21:21.000 --> 0:21:24.080
<v Speaker 1>controller that has its own touch screen interface embedded in

0:21:24.200 --> 0:21:27.639
<v Speaker 1>the controller itself. So it's kind of like combining the ELT,

0:21:27.880 --> 0:21:33.720
<v Speaker 1>the the Nintendo DS sort of technology with the WE

0:21:34.160 --> 0:21:37.960
<v Speaker 1>console system and putting it all together so that you have, uh,

0:21:38.240 --> 0:21:40.040
<v Speaker 1>you know, a game going on on the screen and

0:21:40.080 --> 0:21:42.439
<v Speaker 1>then occasionally might have many games pop up on your controller,

0:21:42.480 --> 0:21:45.080
<v Speaker 1>which we've seen in previous console systems, and we've talked

0:21:45.080 --> 0:21:47.040
<v Speaker 1>about that before in the past, but this will be

0:21:47.160 --> 0:21:51.480
<v Speaker 1>the most kind of mature version of that technology that

0:21:51.560 --> 0:21:54.639
<v Speaker 1>we've seen so far. So yeah, I got that right.

0:21:54.720 --> 0:21:57.879
<v Speaker 1>I was really amazed, And unfortunately it looks like I

0:21:58.000 --> 0:22:04.400
<v Speaker 1>won some WE. So let's just move on, all right, Hey,

0:22:04.640 --> 0:22:06.760
<v Speaker 1>actually that that was a c S. That was actually

0:22:07.240 --> 0:22:09.919
<v Speaker 1>that was at E three, right, Yeah, but you didn't

0:22:10.000 --> 0:22:11.800
<v Speaker 1>go to C E S. And I think you're going

0:22:11.840 --> 0:22:13.959
<v Speaker 1>again next year. Oh yes, I've already got it all

0:22:14.000 --> 0:22:17.960
<v Speaker 1>planned out. So why don't you tell us about your

0:22:18.040 --> 0:22:20.800
<v Speaker 1>C E S predictions? Okay, So because that we found

0:22:20.840 --> 0:22:24.600
<v Speaker 1>that out pretty quickly. It's in January. So I predicted yeah,

0:22:24.640 --> 0:22:27.359
<v Speaker 1>because when we recorded this last year, it was right

0:22:27.400 --> 0:22:29.639
<v Speaker 1>around the same time as early December, and I was

0:22:29.680 --> 0:22:33.159
<v Speaker 1>predicting what would happen in early January, and so surprise,

0:22:33.200 --> 0:22:35.639
<v Speaker 1>surprise was right for most of it. I said that

0:22:35.680 --> 0:22:37.280
<v Speaker 1>there would be a lot of three D tech around,

0:22:37.320 --> 0:22:39.680
<v Speaker 1>and there were was quite a bit, and there has

0:22:39.760 --> 0:22:42.160
<v Speaker 1>been for a few years. Actually, three D tech probably

0:22:42.200 --> 0:22:45.600
<v Speaker 1>didn't get quite the same amount of attention that it

0:22:45.720 --> 0:22:48.640
<v Speaker 1>did the year before, but it was still pretty much everywhere,

0:22:48.760 --> 0:22:53.080
<v Speaker 1>and you even had companies, especially like Sony, and I

0:22:53.160 --> 0:22:55.920
<v Speaker 1>think even Panasonic might have also had one. I know

0:22:56.000 --> 0:22:58.920
<v Speaker 1>a couple of different companies had the glasses free three

0:22:59.040 --> 0:23:02.080
<v Speaker 1>D televisions on this playing, which we've talked about before

0:23:02.240 --> 0:23:04.680
<v Speaker 1>and about how you know, there are problems with glasses

0:23:04.720 --> 0:23:08.040
<v Speaker 1>free three D tech, mostly stemming from the fact that

0:23:08.160 --> 0:23:10.560
<v Speaker 1>if you are not in a the right position in

0:23:10.640 --> 0:23:13.040
<v Speaker 1>front of the television, you're going to get a very blurry,

0:23:13.520 --> 0:23:17.320
<v Speaker 1>disorienting experience. It's not very pleasant, but you know, there's

0:23:17.359 --> 0:23:20.600
<v Speaker 1>still advances being made with that technology. So I also

0:23:20.640 --> 0:23:24.119
<v Speaker 1>said there'll probably be more wireless data streaming between devices,

0:23:24.640 --> 0:23:26.200
<v Speaker 1>and they're kind of was, but it wasn't in the

0:23:26.240 --> 0:23:28.000
<v Speaker 1>way that I had predicted. I thought it was going

0:23:28.080 --> 0:23:32.159
<v Speaker 1>to be more like high data transfers, so things like

0:23:32.240 --> 0:23:35.399
<v Speaker 1>a Blu Ray player and a television set having a

0:23:35.520 --> 0:23:39.000
<v Speaker 1>wireless like a wide gig connection between the two where

0:23:39.040 --> 0:23:42.000
<v Speaker 1>you could watch content directly on your TV from your

0:23:42.000 --> 0:23:44.239
<v Speaker 1>Blu Ray without having to have a cable to connect them.

0:23:44.760 --> 0:23:48.800
<v Speaker 1>But really, what the wireless data streaming stuff, the way

0:23:48.840 --> 0:23:51.320
<v Speaker 1>it played out at CS this is more about ecosystems.

0:23:51.840 --> 0:23:55.480
<v Speaker 1>It was more about having a device or a collection

0:23:55.520 --> 0:23:58.320
<v Speaker 1>of devices and being able to port and experience from

0:23:58.359 --> 0:24:00.680
<v Speaker 1>one device to the next in a very seamless way.

0:24:01.119 --> 0:24:05.760
<v Speaker 1>So in the ultimate example, you might be watching a

0:24:06.800 --> 0:24:09.480
<v Speaker 1>video on your on your smartphone as you're walking in

0:24:09.560 --> 0:24:13.159
<v Speaker 1>the door, and then you transfer that video seamlessly to

0:24:13.240 --> 0:24:14.920
<v Speaker 1>your television so you can watch the rest of it

0:24:15.040 --> 0:24:16.760
<v Speaker 1>on TV and it picks up right where you left

0:24:16.800 --> 0:24:19.280
<v Speaker 1>off on the smartphone. That kind of idea, and we

0:24:19.400 --> 0:24:21.879
<v Speaker 1>haven't really reached that point yet, but there were a

0:24:21.920 --> 0:24:24.359
<v Speaker 1>lot of the like kind of the foundation for that

0:24:24.480 --> 0:24:27.600
<v Speaker 1>technology was on display quite a bit at CES. Yeah,

0:24:27.720 --> 0:24:31.360
<v Speaker 1>the cloud, the cloud seems to have acquired that more

0:24:31.400 --> 0:24:33.720
<v Speaker 1>than your your home. So you know, if you're using

0:24:33.760 --> 0:24:36.920
<v Speaker 1>a service, a streaming movie service that you subscribe to

0:24:37.000 --> 0:24:38.800
<v Speaker 1>over the internet, you can pose it in one thing

0:24:38.880 --> 0:24:41.000
<v Speaker 1>and you have your account in the other room and

0:24:41.160 --> 0:24:43.240
<v Speaker 1>seen it advertise more in that capacity than I have

0:24:43.359 --> 0:24:45.320
<v Speaker 1>in the You buy this thing and stick in your

0:24:45.359 --> 0:24:48.080
<v Speaker 1>house and it makes this happen. Yeah, essentially in order

0:24:48.200 --> 0:24:50.800
<v Speaker 1>for the second the version that I saw at CS,

0:24:50.920 --> 0:24:53.159
<v Speaker 1>for order for that version to really play out, you

0:24:53.160 --> 0:24:56.400
<v Speaker 1>would pretty much have to buy all of your electronics

0:24:56.680 --> 0:25:00.600
<v Speaker 1>from a single source, like a single manufacturer for that

0:25:00.680 --> 0:25:03.440
<v Speaker 1>to work, because they all have their own proprietary ways

0:25:03.520 --> 0:25:08.240
<v Speaker 1>of developing this this uh system. Yeah, I wonder why

0:25:08.320 --> 0:25:10.959
<v Speaker 1>that is. Whereas the version you're talking about is much

0:25:11.000 --> 0:25:14.680
<v Speaker 1>more consumer friendly, and that it is if it's cloud based,

0:25:14.920 --> 0:25:16.960
<v Speaker 1>as long as whatever it is you're buying has the

0:25:17.000 --> 0:25:21.480
<v Speaker 1>capacity to tap into that that cloud system then you're fine.

0:25:21.800 --> 0:25:24.879
<v Speaker 1>So you could have devices from multiple manufacturers and have

0:25:25.040 --> 0:25:29.040
<v Speaker 1>them seamlessly interact, because what they're doing is they're pulling

0:25:29.119 --> 0:25:32.359
<v Speaker 1>stuff from the cloud, and that's where the coordination is

0:25:32.440 --> 0:25:35.800
<v Speaker 1>coming from, not through the devices themselves. But that's not

0:25:36.000 --> 0:25:38.720
<v Speaker 1>the way it was presented at c E s UM.

0:25:39.560 --> 0:25:41.960
<v Speaker 1>I also said that there'd be a lot more green tech,

0:25:42.040 --> 0:25:45.800
<v Speaker 1>and there was UM and uh so yeah for this one,

0:25:45.880 --> 0:25:52.359
<v Speaker 1>I get UM too. Hurt feet apparently. Yeah, I think

0:25:52.400 --> 0:25:55.360
<v Speaker 1>you cashed in on that one a long time ago. Yeah,

0:25:55.440 --> 0:25:58.440
<v Speaker 1>I'll be doing it again soon. Yea. Yeah, speaking of

0:25:59.240 --> 0:26:01.840
<v Speaker 1>green tech, Yeah, you kind of seem to think that

0:26:02.320 --> 0:26:05.680
<v Speaker 1>green green would sort of go away. I I what

0:26:05.800 --> 0:26:12.320
<v Speaker 1>I thought was that the big flashy green tech UM developments,

0:26:12.359 --> 0:26:16.399
<v Speaker 1>things like like these these crazy power plants or whatever. Uh,

0:26:16.760 --> 0:26:21.560
<v Speaker 1>big flashy technologies would sort of fade away in comparison

0:26:21.640 --> 0:26:27.840
<v Speaker 1>to more modest but but achievable green technologies. So in

0:26:27.920 --> 0:26:30.639
<v Speaker 1>other words, you know, you wouldn't see something that was

0:26:30.720 --> 0:26:35.639
<v Speaker 1>going to supposedly eliminate our dependence upon fossil fuels. UM

0:26:35.960 --> 0:26:39.159
<v Speaker 1>like these these big long reach projects that cost a

0:26:39.200 --> 0:26:40.879
<v Speaker 1>lot of money and take will take a lot of

0:26:40.920 --> 0:26:42.880
<v Speaker 1>time to develop. What we would see a lot more

0:26:43.320 --> 0:26:47.040
<v Speaker 1>investment in things like this power chord will automatically shut

0:26:47.080 --> 0:26:50.080
<v Speaker 1>off and not allow your devices to draw vampire power.

0:26:50.160 --> 0:26:53.399
<v Speaker 1>That kind of stuff. It's not not terribly exciting or sexy,

0:26:53.520 --> 0:26:55.840
<v Speaker 1>but it does make a difference, and that, in fact,

0:26:56.080 --> 0:27:00.600
<v Speaker 1>is pretty much how played out. Um. In fact, I

0:27:00.640 --> 0:27:03.439
<v Speaker 1>would argue that in some ways, green technology is kind

0:27:03.440 --> 0:27:05.600
<v Speaker 1>of the buzz has kind of died a little bit.

0:27:05.800 --> 0:27:08.160
<v Speaker 1>You don't. You don't hear about it as much as

0:27:08.200 --> 0:27:12.919
<v Speaker 1>you did, unless, of course, it relates to Celindra. There

0:27:12.960 --> 0:27:17.719
<v Speaker 1>are some exceptions. That's more about the controversy of funding

0:27:17.800 --> 0:27:21.440
<v Speaker 1>a company that that was not doing so hot with

0:27:21.600 --> 0:27:23.560
<v Speaker 1>government money. Or you might hear about it about a

0:27:23.640 --> 0:27:26.200
<v Speaker 1>car that gets in a collision in three days later

0:27:26.359 --> 0:27:29.600
<v Speaker 1>bursts into flames because the battery, the electric battery inside

0:27:29.640 --> 0:27:31.680
<v Speaker 1>of it was damaged, but it takes a while for

0:27:31.880 --> 0:27:36.840
<v Speaker 1>the damage to actually result in a catastrophic failure. There's

0:27:36.880 --> 0:27:41.600
<v Speaker 1>that news too. Yep. So uh for this, I get

0:27:42.320 --> 0:27:45.720
<v Speaker 1>a piece of green felt that was from the same

0:27:46.440 --> 0:27:50.200
<v Speaker 1>bolt of cloth where they made kermit. Hey, it's not easy,

0:27:50.320 --> 0:27:54.200
<v Speaker 1>that's it. That's a pretty cool prize. Yeah, yeah, I

0:27:54.680 --> 0:27:58.800
<v Speaker 1>bungled this next one of mine, but Jonathan got it right.

0:27:59.080 --> 0:28:01.359
<v Speaker 1>Um I said that to what we had been talking about,

0:28:01.359 --> 0:28:08.239
<v Speaker 1>that giant speaking of power, energy sucking stuff. Apple had

0:28:08.280 --> 0:28:10.760
<v Speaker 1>been building this giant data center in North Carolina, and

0:28:11.280 --> 0:28:13.639
<v Speaker 1>we had been speculating, or many of the media had

0:28:13.720 --> 0:28:15.560
<v Speaker 1>been about what they were actually going to do with

0:28:15.680 --> 0:28:20.040
<v Speaker 1>that thing. Um well, it's actually still kind of unclear.

0:28:20.200 --> 0:28:22.880
<v Speaker 1>But um I thought that Apple was going to launch

0:28:22.880 --> 0:28:29.720
<v Speaker 1>its own streaming media music service. And no, no, I didn't. No,

0:28:29.920 --> 0:28:32.399
<v Speaker 1>I Cloud as many things, but it's not really a

0:28:32.480 --> 0:28:35.240
<v Speaker 1>streaming music service. Yeah, and I think that's what what's

0:28:35.240 --> 0:28:38.400
<v Speaker 1>in that center is iCloud. It's supporting i Cloud, but

0:28:38.560 --> 0:28:41.680
<v Speaker 1>it's not yeah eye Cloud. Now, well, it sort of

0:28:41.760 --> 0:28:43.320
<v Speaker 1>depends on how you look at it, but I don't

0:28:43.320 --> 0:28:45.680
<v Speaker 1>think of it as a streaming music service like uh,

0:28:45.800 --> 0:28:48.320
<v Speaker 1>you know last Fm or Pandora and the radio side.

0:28:48.560 --> 0:28:51.000
<v Speaker 1>I think of it like a Lotify. It's more like

0:28:51.160 --> 0:28:55.080
<v Speaker 1>a more like a locker sty style. However, they do

0:28:55.280 --> 0:28:59.000
<v Speaker 1>have for the paying subscribers the music match service, which

0:28:59.480 --> 0:29:01.560
<v Speaker 1>identify eyes the stuff that you got on your your

0:29:01.600 --> 0:29:04.440
<v Speaker 1>computer and you don't have to upload your music. You

0:29:04.800 --> 0:29:07.280
<v Speaker 1>you can say okay, well you got it there don't

0:29:07.320 --> 0:29:11.000
<v Speaker 1>worry about it. As long as iTunes has that song

0:29:11.320 --> 0:29:13.560
<v Speaker 1>in its database, you have a copy of it, you

0:29:13.640 --> 0:29:18.640
<v Speaker 1>can listen to it reasonably nice bit rate too. Yeah yeah, Actually,

0:29:18.840 --> 0:29:20.719
<v Speaker 1>in some cases it will be a better bit rate

0:29:20.800 --> 0:29:23.240
<v Speaker 1>than the song you might have on your system, depending

0:29:23.280 --> 0:29:25.480
<v Speaker 1>on Let's say, if you had a c D and

0:29:25.560 --> 0:29:27.840
<v Speaker 1>you ripped music from that CD and you were, you know,

0:29:27.960 --> 0:29:30.760
<v Speaker 1>trying to conserve space, so you ripped it at a

0:29:30.880 --> 0:29:34.200
<v Speaker 1>low bit rate. The bit rate if if iTunes can

0:29:34.280 --> 0:29:37.560
<v Speaker 1>match the song, and you are an iTunes match customer,

0:29:38.040 --> 0:29:40.440
<v Speaker 1>then you will the one that will appear in your

0:29:40.480 --> 0:29:43.360
<v Speaker 1>iTunes account, your iCloud account will actually be at a

0:29:43.440 --> 0:29:45.520
<v Speaker 1>higher bit rate, possibly than the one the one that

0:29:45.640 --> 0:29:48.520
<v Speaker 1>was on your machine. Yeah, so that's kind of nice. Yeah,

0:29:48.600 --> 0:29:50.400
<v Speaker 1>but you got this one right. It's not technically a

0:29:50.480 --> 0:29:55.480
<v Speaker 1>streaming music service, so according to this you even get

0:29:55.600 --> 0:30:00.160
<v Speaker 1>prizes when things aren't right. So, uh, this one is

0:30:00.600 --> 0:30:05.640
<v Speaker 1>a uh it's a little fried apple pie from McDonald's

0:30:05.640 --> 0:30:08.280
<v Speaker 1>in a bag that was left in this studio at

0:30:08.400 --> 0:30:11.880
<v Speaker 1>our twenty ten Predictions episode, which is not good because

0:30:11.920 --> 0:30:16.920
<v Speaker 1>they've been baked for twenty years now, so you're kind

0:30:16.960 --> 0:30:21.200
<v Speaker 1>of gonna need to um, probably dispose of that in

0:30:21.520 --> 0:30:25.600
<v Speaker 1>the most secure vessel that we have in this office,

0:30:25.640 --> 0:30:30.920
<v Speaker 1>which I believe is Josh Clark. Well, speaking of apples anything, Yeah,

0:30:31.600 --> 0:30:33.880
<v Speaker 1>you know, it's kind of late, since we've been talking

0:30:33.920 --> 0:30:35.920
<v Speaker 1>for about thirty minutes now, but it's kind of late.

0:30:36.080 --> 0:30:37.760
<v Speaker 1>But I'm starting to get a little skeptical of this

0:30:37.920 --> 0:30:42.120
<v Speaker 1>scoring system. Um, but yeah, speaking of apples, the next

0:30:42.160 --> 0:30:45.600
<v Speaker 1>prediction came true sort of. Oh, the accepted it didn't

0:30:45.720 --> 0:30:48.240
<v Speaker 1>where I said light peak would debut, we did, but

0:30:48.320 --> 0:30:50.880
<v Speaker 1>it it wasn't light peak, well it was. It was

0:30:51.320 --> 0:30:53.520
<v Speaker 1>light Peak. It was just called Thunderbolt, and it didn't

0:30:53.560 --> 0:30:57.280
<v Speaker 1>use light it used copper. How else and every other way,

0:30:57.320 --> 0:31:00.440
<v Speaker 1>that prediction was completely right. Um, yeah, I said that

0:31:00.520 --> 0:31:03.120
<v Speaker 1>light peak would debut inven and and all right. To

0:31:03.200 --> 0:31:07.080
<v Speaker 1>be fair, the very first generation of light Peak, even

0:31:07.120 --> 0:31:09.560
<v Speaker 1>back when it was just called light Peak, was still

0:31:09.640 --> 0:31:12.040
<v Speaker 1>going to be copper based. It was not going to

0:31:12.120 --> 0:31:14.440
<v Speaker 1>be until it moved a little bit beyond that where

0:31:14.480 --> 0:31:16.320
<v Speaker 1>it was going to go to the actual fiber optic

0:31:16.440 --> 0:31:18.160
<v Speaker 1>lines where it was going to use light. And this,

0:31:18.400 --> 0:31:21.560
<v Speaker 1>in case you don't know, it's the technology that allows

0:31:21.920 --> 0:31:25.640
<v Speaker 1>very fast data transfer speed between devices and it can

0:31:25.720 --> 0:31:28.120
<v Speaker 1>be any sort of device that that you know can

0:31:28.160 --> 0:31:30.120
<v Speaker 1>have the sort of port on. It's very similar to

0:31:30.400 --> 0:31:33.880
<v Speaker 1>USB technology, or at least that's the purpose of it

0:31:34.040 --> 0:31:36.760
<v Speaker 1>is very much the same as USB technology, except that, uh,

0:31:37.200 --> 0:31:39.360
<v Speaker 1>light peak, when it's just going to be fiber optics,

0:31:39.400 --> 0:31:41.320
<v Speaker 1>if there's no copper wire and there will not be

0:31:41.520 --> 0:31:44.600
<v Speaker 1>able to power a device as well as transferred data.

0:31:45.240 --> 0:31:48.200
<v Speaker 1>USB s can. USB s can provide power. Right. So

0:31:48.400 --> 0:31:50.800
<v Speaker 1>in fact, my my phone right now is plugged in

0:31:50.960 --> 0:31:53.320
<v Speaker 1>via USB cord to my computer, which means that the

0:31:53.880 --> 0:31:56.880
<v Speaker 1>batteries not being drained because it's it's pulling power from

0:31:56.960 --> 0:32:00.160
<v Speaker 1>the computer itself. Light Peak would not work that way

0:32:00.200 --> 0:32:02.719
<v Speaker 1>because if it were just the fiber optics, now, if

0:32:02.720 --> 0:32:04.880
<v Speaker 1>they paired it with copper wire, then yes, you could

0:32:05.200 --> 0:32:09.280
<v Speaker 1>carry electricity across the copper wire while the the fiber

0:32:09.320 --> 0:32:12.720
<v Speaker 1>optics carried the data. Well, the very first generation of

0:32:12.840 --> 0:32:15.240
<v Speaker 1>light peak was just copper wire. They weren't including the

0:32:15.320 --> 0:32:18.800
<v Speaker 1>fiber optics, and that did appear in products. In twenty eleven,

0:32:18.920 --> 0:32:23.200
<v Speaker 1>it appeared exclusively in Apple products and it was renamed Thunderbolt.

0:32:23.960 --> 0:32:26.200
<v Speaker 1>But it was the same technology. It's the same thing.

0:32:26.680 --> 0:32:30.160
<v Speaker 1>So because I got this right, more right than not right,

0:32:30.240 --> 0:32:32.600
<v Speaker 1>even though there were a lot of kind of cheating

0:32:32.760 --> 0:32:35.360
<v Speaker 1>around the fact of what light Peak was and how

0:32:35.440 --> 0:32:37.880
<v Speaker 1>it debuted. I think what you meant and what they

0:32:37.960 --> 0:32:39.880
<v Speaker 1>meant were two different things. I think you should get

0:32:39.880 --> 0:32:43.120
<v Speaker 1>credit for. Yeah, so I get my award. Is I

0:32:43.200 --> 0:32:46.200
<v Speaker 1>get a light but it's over at the Frankenstein Place,

0:32:46.440 --> 0:32:49.240
<v Speaker 1>so you have to pick it up after the show. Yeah,

0:32:49.800 --> 0:32:53.200
<v Speaker 1>you did say that we would be using discs less

0:32:53.840 --> 0:32:57.200
<v Speaker 1>I did. I said that we that digital distribution would

0:32:57.240 --> 0:33:00.640
<v Speaker 1>become a much bigger thing in an eleven that it

0:33:00.720 --> 0:33:03.040
<v Speaker 1>had in previous years. And we've seen that. We've seen

0:33:03.120 --> 0:33:05.880
<v Speaker 1>mac os ten Lion goes ten Lion, We've seen uh

0:33:06.760 --> 0:33:09.440
<v Speaker 1>beta builds of Windows eight. We've seen and I think

0:33:09.480 --> 0:33:13.200
<v Speaker 1>when Microsoft is going to go to primarily digital distribution,

0:33:13.280 --> 0:33:16.040
<v Speaker 1>when when Windows eight comes out? Yeah, and you can

0:33:16.200 --> 0:33:19.680
<v Speaker 1>you can buy games on the various game consoles through

0:33:19.760 --> 0:33:23.160
<v Speaker 1>their online stores and download directly to the console, as

0:33:23.200 --> 0:33:26.400
<v Speaker 1>opposed to going out and buying a disc, Steam, Steam

0:33:26.680 --> 0:33:30.800
<v Speaker 1>and other huge games for the PC. So yeah, I

0:33:31.040 --> 0:33:33.920
<v Speaker 1>um I for this. I get a whole bunch of

0:33:34.600 --> 0:33:38.800
<v Speaker 1>zeros and ones. That's what I got for those YEA

0:33:39.160 --> 0:33:42.760
<v Speaker 1>and a little bit in the back. Um. Yeah, this

0:33:42.920 --> 0:33:45.560
<v Speaker 1>next one is a little hard to quantify that I

0:33:45.800 --> 0:33:48.000
<v Speaker 1>that I'm predicted. Uh. I said that we're going to

0:33:48.080 --> 0:33:53.400
<v Speaker 1>be more investments into, uh the alternatives to rare earth metals,

0:33:53.440 --> 0:33:57.160
<v Speaker 1>which are hard. They're they're plentiful, but they're hard to

0:33:57.240 --> 0:34:02.320
<v Speaker 1>find in large amounts in one place. Um and you know,

0:34:02.440 --> 0:34:05.520
<v Speaker 1>therefore they are somewhat expensive. China sort of has the

0:34:05.560 --> 0:34:07.800
<v Speaker 1>market cornered right at the moment, and they're starting to

0:34:07.920 --> 0:34:11.120
<v Speaker 1>use more for their own devices. So I figured that

0:34:11.239 --> 0:34:14.000
<v Speaker 1>more people would would be looking for alternatives to those.

0:34:15.280 --> 0:34:18.359
<v Speaker 1>I haven't really read a whole lot about that. Um,

0:34:18.960 --> 0:34:22.399
<v Speaker 1>so I'm thinking that I I think I'm pretty sure

0:34:22.520 --> 0:34:25.120
<v Speaker 1>that I'm thinking that I think that I think that

0:34:25.520 --> 0:34:29.799
<v Speaker 1>maybe I was wrong. See, Yeah, this one's uh uh yeah,

0:34:29.960 --> 0:34:31.520
<v Speaker 1>this was hard to hear. A lot of this was

0:34:31.560 --> 0:34:33.960
<v Speaker 1>a hard one to research, right because I mean it's yeah,

0:34:34.160 --> 0:34:36.720
<v Speaker 1>it's unless you're hard to find info on you unless

0:34:36.719 --> 0:34:40.000
<v Speaker 1>you're reading very detailed reports. Um. Yeah, we didn't hear

0:34:40.080 --> 0:34:43.200
<v Speaker 1>much about this, and as far as the rare earth

0:34:43.239 --> 0:34:47.400
<v Speaker 1>metal crisis is still going on, so uh So, unfortunately

0:34:47.480 --> 0:34:49.799
<v Speaker 1>because of this, I have to you were talking about

0:34:49.800 --> 0:34:54.440
<v Speaker 1>alternatives too. Rare metals. Uh so I've got and um

0:34:55.239 --> 0:34:59.120
<v Speaker 1>the best of Limp Biscuit album for you Alternative metal.

0:34:59.200 --> 0:35:03.480
<v Speaker 1>There you shouldn't have, I know, really well you shouldn't have.

0:35:03.600 --> 0:35:07.239
<v Speaker 1>You can put that next year, apple Pie. Uh so

0:35:07.920 --> 0:35:10.680
<v Speaker 1>you know we've got a new PlayStation portable coming out.

0:35:11.000 --> 0:35:14.040
<v Speaker 1>Yeah I said that. I said I that in eleven

0:35:14.080 --> 0:35:17.360
<v Speaker 1>we'd see the PlayStation phone launch and the experien Play launched.

0:35:18.320 --> 0:35:22.160
<v Speaker 1>That was the PlayStation phone. It was it was, It wasn't.

0:35:22.640 --> 0:35:26.640
<v Speaker 1>It wasn't branded that. It wasn't branded as a PlayStation

0:35:26.840 --> 0:35:28.640
<v Speaker 1>Well it kind of was. Well, I mean it had

0:35:28.680 --> 0:35:30.960
<v Speaker 1>a slide out section, which is what I said it

0:35:31.000 --> 0:35:33.719
<v Speaker 1>would have, with a little game pad on it, which

0:35:33.800 --> 0:35:36.440
<v Speaker 1>is what That's exactly what I said. Uh, and it's

0:35:36.600 --> 0:35:38.320
<v Speaker 1>it was called the Experience Play. It even went on

0:35:38.360 --> 0:35:42.040
<v Speaker 1>sale for a hundred bucks. So, um, I got that one.

0:35:42.239 --> 0:35:44.800
<v Speaker 1>I got that one totally right, I got a hedgehog.

0:35:45.800 --> 0:35:49.200
<v Speaker 1>I'm squinting what that's right. There wasn't PlayStation phone. It's

0:35:49.200 --> 0:35:54.239
<v Speaker 1>the Experience Play. Look it up. Okay, it's uh, let's see,

0:35:54.560 --> 0:35:56.800
<v Speaker 1>but it wasn't called it anyway. Do you want me

0:35:56.840 --> 0:35:58.360
<v Speaker 1>to do one more? Since that way it'll kind of

0:35:58.400 --> 0:36:01.160
<v Speaker 1>even this out. Uh, well, I think I think your

0:36:01.239 --> 0:36:04.200
<v Speaker 1>last one should be the last one we talk about here. No, no,

0:36:04.320 --> 0:36:06.160
<v Speaker 1>I think your last one should be the last one

0:36:06.239 --> 0:36:10.359
<v Speaker 1>we talk about. That's true, so I'll do another one. Uh.

0:36:10.560 --> 0:36:13.280
<v Speaker 1>So I had also said that color ink e readers

0:36:13.320 --> 0:36:17.239
<v Speaker 1>would launch in uh and that didn't happen. Instead of

0:36:17.280 --> 0:36:21.000
<v Speaker 1>color e Inc. We saw the e reader companies go

0:36:21.160 --> 0:36:25.480
<v Speaker 1>towards a more tablet design. Wha, They're using lc D displays,

0:36:25.560 --> 0:36:29.080
<v Speaker 1>not e ink displays for that, So that was wrong.

0:36:29.280 --> 0:36:32.160
<v Speaker 1>I did not get that right. I mean, uh, the

0:36:32.640 --> 0:36:34.880
<v Speaker 1>I don't know if there was like a hold up

0:36:34.920 --> 0:36:37.120
<v Speaker 1>on the technology or if it was just they figured

0:36:37.200 --> 0:36:40.200
<v Speaker 1>that the tablet, the tablet experience would be a superior

0:36:40.239 --> 0:36:43.520
<v Speaker 1>experience to ink, or if the people who wanted color

0:36:43.640 --> 0:36:46.160
<v Speaker 1>really didn't care so much about things like battery life

0:36:46.239 --> 0:36:48.279
<v Speaker 1>that kind of thing. Yeah, I think that's that's a

0:36:48.320 --> 0:36:52.040
<v Speaker 1>big part of it. Color et Inc. Does exist. Actually,

0:36:52.080 --> 0:36:54.800
<v Speaker 1>it's been out well, I mean it it's existed for

0:36:55.000 --> 0:36:57.040
<v Speaker 1>some time now, not in a long long time, but

0:36:57.480 --> 0:36:59.480
<v Speaker 1>you know, it was in existence when we had that

0:36:59.560 --> 0:37:02.920
<v Speaker 1>conversation Asian. The problem is it doesn't show nearly as

0:37:02.960 --> 0:37:06.399
<v Speaker 1>many colors, and they're not nearly as bright as um

0:37:06.760 --> 0:37:08.880
<v Speaker 1>you know, an l an L E D display or

0:37:08.880 --> 0:37:12.520
<v Speaker 1>an l C D display. So the thing is you're

0:37:12.560 --> 0:37:14.719
<v Speaker 1>you're getting more vibrant colors, but at the cost of

0:37:14.800 --> 0:37:18.759
<v Speaker 1>battery life on these tablet type displays. And I think

0:37:18.800 --> 0:37:21.960
<v Speaker 1>people sort of expect, especially for the things that they're

0:37:21.960 --> 0:37:24.600
<v Speaker 1>saying for the new generation of tablets where they're going

0:37:24.640 --> 0:37:28.520
<v Speaker 1>to have even more high definition displays. I think that

0:37:28.680 --> 0:37:32.200
<v Speaker 1>may uh you know, relegate color eat inc. To a

0:37:32.320 --> 0:37:34.480
<v Speaker 1>very small set of devices in the future. So but

0:37:34.520 --> 0:37:36.560
<v Speaker 1>I thought they were coming out to Yeah, yeah, So

0:37:36.719 --> 0:37:38.759
<v Speaker 1>that one was a miss. Let me do one more

0:37:38.840 --> 0:37:42.000
<v Speaker 1>on mine in that way, when we alternate, it should

0:37:42.520 --> 0:37:44.440
<v Speaker 1>turn out so that your last ones are the last one.

0:37:44.560 --> 0:37:46.520
<v Speaker 1>Well yeah, yeah, and then this one you were right on. Yeah.

0:37:46.560 --> 0:37:48.480
<v Speaker 1>I said that there we would start seeing near fields

0:37:48.520 --> 0:37:52.560
<v Speaker 1>communication systems show up in smartphones and ding. Yeah, it

0:37:52.640 --> 0:37:56.080
<v Speaker 1>started popping up, not not at the level that I

0:37:56.200 --> 0:37:58.960
<v Speaker 1>was hoping for, but it's it has started to emerge.

0:37:59.080 --> 0:38:03.120
<v Speaker 1>And that's the technology that allows you to make payment

0:38:03.239 --> 0:38:08.160
<v Speaker 1>transfers just by swiping your phone near uh a station

0:38:08.320 --> 0:38:12.879
<v Speaker 1>like a payment station. And Google Wallet debut. Google Wallet

0:38:12.960 --> 0:38:16.920
<v Speaker 1>debut and added a lot of that functionality into uh,

0:38:17.280 --> 0:38:20.080
<v Speaker 1>managing that kind of system. So on your end, so

0:38:20.239 --> 0:38:21.680
<v Speaker 1>you would you what you would do is you would

0:38:21.680 --> 0:38:24.840
<v Speaker 1>have to have a particular kind of credit card for

0:38:25.000 --> 0:38:29.800
<v Speaker 1>Google Wallet to tie into this system, and then Google

0:38:29.840 --> 0:38:32.440
<v Speaker 1>Wallet would manage your account and would also let you

0:38:32.560 --> 0:38:37.120
<v Speaker 1>subscribe to things like coupon deals and and rewards deals

0:38:38.040 --> 0:38:40.840
<v Speaker 1>and would apply those every time you went to purchase stuff.

0:38:40.880 --> 0:38:43.319
<v Speaker 1>So that way, if you had a coupon for something,

0:38:43.360 --> 0:38:46.359
<v Speaker 1>it would automatically get applied when you bought that thing.

0:38:46.440 --> 0:38:48.520
<v Speaker 1>You wouldn't have to remember it. It would be in

0:38:48.600 --> 0:38:51.960
<v Speaker 1>there in your phone already, which was great. Uh. And

0:38:52.080 --> 0:38:56.759
<v Speaker 1>for that I get an electromagnetic field around me at

0:38:56.760 --> 0:39:00.120
<v Speaker 1>all times, so, um, my computer is no longer are

0:39:00.320 --> 0:39:03.120
<v Speaker 1>really displaying things properly? But other than that, it's pretty awesome.

0:39:03.239 --> 0:39:06.480
<v Speaker 1>Where your fair to day cage? Um? So uh, I

0:39:06.600 --> 0:39:11.279
<v Speaker 1>predicted that hd TV prices would stagnate. You said there

0:39:11.280 --> 0:39:14.560
<v Speaker 1>wouldn't be any more dramatic drops in price that they

0:39:14.600 --> 0:39:17.320
<v Speaker 1>had pretty much. You know, they might creep lower, but

0:39:17.400 --> 0:39:21.160
<v Speaker 1>they wouldn't be You wouldn't see a huge like it's crazy.

0:39:21.160 --> 0:39:26.359
<v Speaker 1>You can get this hd TV screen for two hundred bucks. Um,

0:39:27.040 --> 0:39:29.000
<v Speaker 1>I don't know I think, based on my own personal

0:39:29.080 --> 0:39:33.719
<v Speaker 1>research since I bought an HDTV that uh that that's

0:39:33.760 --> 0:39:37.520
<v Speaker 1>pretty accurate. Um, you know, I I think that, Uh,

0:39:37.880 --> 0:39:41.040
<v Speaker 1>I think there is probably a greater diversity. You see

0:39:41.080 --> 0:39:44.279
<v Speaker 1>a lot more manufacturers with you know, sort of a

0:39:44.440 --> 0:39:48.200
<v Speaker 1>cheap model and a nicer model. Um, but the nicer

0:39:48.280 --> 0:39:50.359
<v Speaker 1>ones have stayed about the same price that I saw

0:39:50.480 --> 0:39:55.800
<v Speaker 1>them in. Yeah. And because you got that right, I

0:39:56.000 --> 0:40:00.600
<v Speaker 1>decided that would necessitate a reward that was high definition

0:40:00.640 --> 0:40:03.919
<v Speaker 1>but low in price. So I got you this HD

0:40:04.080 --> 0:40:07.520
<v Speaker 1>DVD player. Oh, thanks, You're welcome. That was one of

0:40:07.560 --> 0:40:11.840
<v Speaker 1>our very first podcasts. Uh. Next, um, we had I

0:40:11.960 --> 0:40:15.920
<v Speaker 1>had the prediction that Duke Knewcombe Forever would launch INN

0:40:16.200 --> 0:40:18.440
<v Speaker 1>and Chris, you agreed, and I agreed with you, and

0:40:18.600 --> 0:40:22.560
<v Speaker 1>we were right, and so many people are so sorry

0:40:22.640 --> 0:40:24.520
<v Speaker 1>that we were right. Yeah. Yeah. It was one of

0:40:24.560 --> 0:40:26.840
<v Speaker 1>those games where again, like for those who don't know,

0:40:26.960 --> 0:40:30.640
<v Speaker 1>it was what thirteen years in the making, um, and

0:40:30.680 --> 0:40:34.120
<v Speaker 1>it had been delayed numerous times, mostly due to things

0:40:34.200 --> 0:40:38.239
<v Speaker 1>like the the lead project manager in charge of the

0:40:38.360 --> 0:40:40.880
<v Speaker 1>game would look at the game and decide that the

0:40:41.520 --> 0:40:44.000
<v Speaker 1>the physics engine or the graphics engine was too out

0:40:44.000 --> 0:40:46.080
<v Speaker 1>of date and that they needed to redesign the game

0:40:46.440 --> 0:40:49.560
<v Speaker 1>for a new engine, and then every yeah, and they

0:40:49.600 --> 0:40:52.160
<v Speaker 1>would scrap everything and start over, and then by the

0:40:52.239 --> 0:40:55.440
<v Speaker 1>time that would be ready to debut, they'd see another

0:40:55.600 --> 0:41:00.560
<v Speaker 1>new system that was even better, which would necessitate ripping

0:41:00.600 --> 0:41:02.840
<v Speaker 1>it all apart and starting over again. And part of

0:41:02.920 --> 0:41:06.200
<v Speaker 1>this is because when Duke Newcome three D first came out,

0:41:06.680 --> 0:41:09.000
<v Speaker 1>it was it came out right at the right time.

0:41:09.160 --> 0:41:12.320
<v Speaker 1>You know, it was taking advantage of technology and and

0:41:12.520 --> 0:41:16.160
<v Speaker 1>using it at its best for that time, right like,

0:41:16.239 --> 0:41:18.279
<v Speaker 1>it was the perfect timing for that game to come

0:41:18.320 --> 0:41:21.839
<v Speaker 1>out on the on the systems that it did, because um,

0:41:22.040 --> 0:41:25.520
<v Speaker 1>it looked very sophisticated compared to other games. It was

0:41:25.600 --> 0:41:28.040
<v Speaker 1>state of the art, and they wanted to try and

0:41:28.120 --> 0:41:30.080
<v Speaker 1>recapture that. But the problem with that is that a

0:41:30.160 --> 0:41:32.480
<v Speaker 1>lot of that ends up just being luck. It's not

0:41:32.680 --> 0:41:35.200
<v Speaker 1>just you know, and you can't really plan for it

0:41:35.280 --> 0:41:37.920
<v Speaker 1>because designing a game and building a game and releasing

0:41:37.960 --> 0:41:42.080
<v Speaker 1>it takes time, and sometimes within that time frame, technology

0:41:42.120 --> 0:41:45.200
<v Speaker 1>has moved along while you've been developing, and especially since

0:41:45.239 --> 0:41:50.440
<v Speaker 1>technology is developing faster and faster, it's just future proofing

0:41:50.480 --> 0:41:52.920
<v Speaker 1>a project like that is really tough to do. It's

0:41:52.920 --> 0:41:55.160
<v Speaker 1>sort of like writing a vampire book for the market

0:41:55.239 --> 0:41:58.320
<v Speaker 1>now now that everyone is tired of the vampire genre

0:41:58.480 --> 0:42:01.000
<v Speaker 1>sort of. You know, you'd have to know what's going

0:42:01.080 --> 0:42:03.400
<v Speaker 1>to be big next, and happened to hit it right

0:42:03.440 --> 0:42:07.400
<v Speaker 1>at the right time, Zombies. So uh it did launch.

0:42:07.640 --> 0:42:13.120
<v Speaker 1>The reviews were almost universally negative or at the very

0:42:13.320 --> 0:42:16.040
<v Speaker 1>at the very best most the some of the best

0:42:16.160 --> 0:42:18.279
<v Speaker 1>reviews I read, like the most positive reviews just called

0:42:18.320 --> 0:42:21.279
<v Speaker 1>it mediocre. So I didn't see anyone say that it

0:42:21.400 --> 0:42:25.520
<v Speaker 1>was a good game. Hasn't really burned up the charts either. Yeah,

0:42:25.760 --> 0:42:29.400
<v Speaker 1>and I didn't purchase it because I mean, I had

0:42:29.480 --> 0:42:31.400
<v Speaker 1>heard enough things where I thought that maybe I just

0:42:31.600 --> 0:42:33.960
<v Speaker 1>I would prefer to remember Duke from back in the

0:42:34.040 --> 0:42:38.080
<v Speaker 1>days when I, uh I played the game the first game,

0:42:38.120 --> 0:42:40.200
<v Speaker 1>the Duke NUKEMB three D, not the first Duke Nukem

0:42:40.320 --> 0:42:42.359
<v Speaker 1>game because those were side scrollers, but the first first

0:42:42.400 --> 0:42:45.440
<v Speaker 1>person shooter Duke Nukem game. But yeah, so I got

0:42:45.480 --> 0:42:48.680
<v Speaker 1>that one right. So because of that, I get an

0:42:48.840 --> 0:42:52.920
<v Speaker 1>enormous set of weights which I can't move unless I

0:42:53.000 --> 0:42:55.560
<v Speaker 1>have them in the ad at and unfortunately that's yours,

0:42:55.640 --> 0:43:00.320
<v Speaker 1>not mine. I was going to suggest that actually, and finally,

0:43:00.440 --> 0:43:03.759
<v Speaker 1>one of my predictions that I'm so happy about because

0:43:03.760 --> 0:43:07.160
<v Speaker 1>I got it wrong last time, Jonathan would get a

0:43:07.280 --> 0:43:10.359
<v Speaker 1>new computer, new work computer by the end of the year.

0:43:10.960 --> 0:43:14.480
<v Speaker 1>So this is actually I sort of got it right. Yeah,

0:43:14.520 --> 0:43:16.239
<v Speaker 1>he sort of got it right because it's new to me,

0:43:17.719 --> 0:43:19.799
<v Speaker 1>but it wasn't new out of the box. Not new

0:43:19.800 --> 0:43:24.240
<v Speaker 1>out of the box. It is a gently used gentle

0:43:24.840 --> 0:43:28.000
<v Speaker 1>it was you didn't gently gently use the last one,

0:43:28.040 --> 0:43:31.120
<v Speaker 1>which is why it had Problemly, Hey, that was just

0:43:31.800 --> 0:43:34.360
<v Speaker 1>just because the keys wouldn't work. That wasn't because I

0:43:34.440 --> 0:43:37.120
<v Speaker 1>was pounding on it or anything. That again would be

0:43:37.239 --> 0:43:42.680
<v Speaker 1>Josh Clark. Yeah, it's our resident loud type of right. Yeah, no, he'sack.

0:43:42.960 --> 0:43:46.120
<v Speaker 1>So the yeah, you got it kind of right, because

0:43:46.320 --> 0:43:48.520
<v Speaker 1>I did get a new computer. It wasn't you. It

0:43:48.640 --> 0:43:50.960
<v Speaker 1>wasn't brand new, but it was new to me. So

0:43:51.320 --> 0:43:54.560
<v Speaker 1>because you got that one right, you get my old computer.

0:43:55.280 --> 0:43:57.560
<v Speaker 1>Oh goody, I have a door that needs propping open it.

0:43:58.120 --> 0:43:59.719
<v Speaker 1>You know, if you want, I'll even lend you the

0:43:59.800 --> 0:44:02.239
<v Speaker 1>till leaky since you're lending me the ad at Hey, okay,

0:44:02.320 --> 0:44:05.600
<v Speaker 1>that's a wait. So so what is the score? You've

0:44:05.640 --> 0:44:09.120
<v Speaker 1>got this complex scoring system, right, so I have I

0:44:09.239 --> 0:44:12.799
<v Speaker 1>have totaled our our predictions. It's a little weird because

0:44:12.800 --> 0:44:15.800
<v Speaker 1>I made I made more predictions than you did, so

0:44:16.040 --> 0:44:20.280
<v Speaker 1>that kind of throws things off. But according to my calculations,

0:44:20.880 --> 0:44:23.920
<v Speaker 1>at the end of the day, your predictions scored a

0:44:24.120 --> 0:44:31.200
<v Speaker 1>Sega dreamcast, My predictions scored. It looks like it's, um well,

0:44:31.200 --> 0:44:33.160
<v Speaker 1>it looks like it's a World Pool Bath. I'm not

0:44:33.360 --> 0:44:41.520
<v Speaker 1>sure how these compare directly. Uh, but um, I'm sure

0:44:41.520 --> 0:44:42.840
<v Speaker 1>I'll figure it out by the time we do this

0:44:42.960 --> 0:44:45.719
<v Speaker 1>next year. All right, Okay, so yeah, I think that

0:44:45.880 --> 0:44:48.919
<v Speaker 1>went really well. Um, I hope that. Uh, I feel

0:44:48.960 --> 0:44:53.920
<v Speaker 1>like I won. Yeah, I guess maybe. I mean, we

0:44:54.000 --> 0:44:56.239
<v Speaker 1>don't actually get the Sega Dreamcast of the World Pool

0:44:56.320 --> 0:45:00.239
<v Speaker 1>Pool Bath. That's just our score, right, I see, you know,

0:45:00.400 --> 0:45:04.360
<v Speaker 1>it's like, you know, I honestly don't know where to

0:45:04.440 --> 0:45:06.560
<v Speaker 1>go from there. In fact, now it seems like this

0:45:06.760 --> 0:45:08.440
<v Speaker 1>whole set of rules that I came up with it

0:45:08.560 --> 0:45:10.640
<v Speaker 1>was just a colossal waste of time. And I just

0:45:10.680 --> 0:45:13.319
<v Speaker 1>found out I got a ticket for an improperly parked

0:45:13.360 --> 0:45:16.279
<v Speaker 1>at at Yeah. Sorry, not much it costs to pay

0:45:16.320 --> 0:45:19.680
<v Speaker 1>off a ticket. I couldn't fit it into the parking deck. No,

0:45:19.960 --> 0:45:22.800
<v Speaker 1>and now the parking deck is collapsed. Well, that's also

0:45:23.160 --> 0:45:28.000
<v Speaker 1>not good. So let's just wrap this up that I think, actually,

0:45:28.640 --> 0:45:31.160
<v Speaker 1>all being said, a lot of our predictions did come true.

0:45:31.200 --> 0:45:33.480
<v Speaker 1>We didn't have as many huge misses this year as

0:45:33.520 --> 0:45:36.960
<v Speaker 1>we have then years passed, which just means we're gonna harder. Yeah,

0:45:36.960 --> 0:45:42.279
<v Speaker 1>we're gonna try harder for twelve predictions. But also there

0:45:42.320 --> 0:45:44.319
<v Speaker 1>were a lot of big news stories that we did

0:45:44.440 --> 0:45:47.239
<v Speaker 1>not predict at all and uh, and we're going to

0:45:47.360 --> 0:45:51.759
<v Speaker 1>do an entire episode about the year in review, like

0:45:52.000 --> 0:45:56.200
<v Speaker 1>what happened in eleven and uh and that will cover

0:45:56.560 --> 0:45:58.319
<v Speaker 1>some of the stories we've talked about here, but also

0:45:58.440 --> 0:46:00.480
<v Speaker 1>a lot of stories that that we just did not

0:46:00.880 --> 0:46:04.400
<v Speaker 1>foresee at all. And I hope you guys will enjoy that.

0:46:04.719 --> 0:46:09.360
<v Speaker 1>This is going to be the last few episodes for eleven.

0:46:09.480 --> 0:46:12.680
<v Speaker 1>So thank you guys for listening to us for yet

0:46:12.760 --> 0:46:15.160
<v Speaker 1>another year, and we're looking forward to talking to you

0:46:15.280 --> 0:46:17.520
<v Speaker 1>more in the future. And if you guys have any

0:46:17.600 --> 0:46:20.839
<v Speaker 1>suggestions for podcast topics that you think we should cover,

0:46:21.280 --> 0:46:24.040
<v Speaker 1>you can email us our email addresses tech Stuff at

0:46:24.160 --> 0:46:26.440
<v Speaker 1>how stuff works dot com, or you can let us

0:46:26.480 --> 0:46:28.520
<v Speaker 1>know on Facebook or Twitter or handled there is tech

0:46:28.600 --> 0:46:30.799
<v Speaker 1>stuff H. S W and Chris and I will talk

0:46:30.800 --> 0:46:35.719
<v Speaker 1>to you again, I predict really soon. Be sure to

0:46:35.800 --> 0:46:38.560
<v Speaker 1>check out our new video podcast, Stuff from the Future.

0:46:38.920 --> 0:46:41.719
<v Speaker 1>Join how Stuffwork staff as we explore the most promising

0:46:41.800 --> 0:46:46.440
<v Speaker 1>and perplexing possibilities of tomorrow. The How Stuff Works iPhone

0:46:46.440 --> 0:46:54.120
<v Speaker 1>app has arrived down at it Today on iTunes, brought

0:46:54.160 --> 0:46:57.320
<v Speaker 1>to you by the reinvented two thousand twelve camera. It's ready,

0:46:57.560 --> 0:46:57.840
<v Speaker 1>are you