WEBVTT - Open vs. Closed: A TechStuff Debate

0:00:00.280 --> 0:00:02.840
<v Speaker 1>Brought to you by the reinvented two thousand twelve Camra.

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:14.480
<v Speaker 1>tex Stuff from hou stufferks dot com. This episode of

0:00:14.520 --> 0:00:16.639
<v Speaker 1>tech Stuff is brought to you by Hover dot com.

0:00:17.079 --> 0:00:20.400
<v Speaker 1>Hover is all about making domain registration and service simple.

0:00:20.840 --> 0:00:23.599
<v Speaker 1>Rather than selling a ton of services, they focus on

0:00:23.680 --> 0:00:27.319
<v Speaker 1>making it easy to register and manage domains and emails. However,

0:00:27.440 --> 0:00:31.320
<v Speaker 1>has two new domain services, Premium Domains and Clunker trade Ins.

0:00:31.880 --> 0:00:34.560
<v Speaker 1>If you have any Clunker domains registered with Hover now,

0:00:34.560 --> 0:00:36.959
<v Speaker 1>you can trade them in. If you have domains you've

0:00:36.960 --> 0:00:39.519
<v Speaker 1>registered or renewed it Hovered and you'd like to upgrade

0:00:39.520 --> 0:00:42.720
<v Speaker 1>your domain, however, will take your old domains back. However,

0:00:42.760 --> 0:00:45.159
<v Speaker 1>will credit you everything you've spent on your old clunker

0:00:45.200 --> 0:00:48.560
<v Speaker 1>with Hover, the original registration fee and any renewal fees.

0:00:49.120 --> 0:00:52.240
<v Speaker 1>Visit Hover today at Hover dot com slash tex stuff.

0:00:52.800 --> 0:00:55.480
<v Speaker 1>If you need a standard domain, use offer code tex

0:00:55.520 --> 0:00:58.080
<v Speaker 1>stuff and get ten percent off. If you want to

0:00:58.080 --> 0:01:00.240
<v Speaker 1>trade in a clunker, just call the custom of our

0:01:00.280 --> 0:01:03.400
<v Speaker 1>service number on their website or email. That's Hover dot

0:01:03.480 --> 0:01:10.959
<v Speaker 1>com slash tech stuff. Hello, They're welcome to tech Stuff.

0:01:10.959 --> 0:01:12.839
<v Speaker 1>My name is Chris Poulette and I am an editor

0:01:12.880 --> 0:01:16.400
<v Speaker 1>at How Stuff Works, sitting across from me, debatedbly Is,

0:01:17.080 --> 0:01:19.959
<v Speaker 1>as always a senior writer Jonathan st I had the

0:01:20.000 --> 0:01:23.120
<v Speaker 1>story bit by bit from various people, and as generally

0:01:23.120 --> 0:01:25.839
<v Speaker 1>happens in such cases, each time it was a different story.

0:01:27.480 --> 0:01:30.679
<v Speaker 1>So today we're going to have a goofy little debate

0:01:30.920 --> 0:01:35.000
<v Speaker 1>about open systems versus closed systems. We just decided that

0:01:35.040 --> 0:01:37.200
<v Speaker 1>we're going to experiment with this. We've never done one

0:01:37.200 --> 0:01:39.399
<v Speaker 1>of these before, and in fact, we decided on it

0:01:39.480 --> 0:01:42.440
<v Speaker 1>about thirty seconds before we started recording, and so to

0:01:42.520 --> 0:01:47.119
<v Speaker 1>determine who would represent which side, we did the most

0:01:47.160 --> 0:01:49.480
<v Speaker 1>scientific thing we could think of. We flipped a coin.

0:01:49.840 --> 0:01:52.520
<v Speaker 1>It's the quarter United States quarter for those of you

0:01:52.680 --> 0:01:55.760
<v Speaker 1>who think that matters. Uh. And it turns out that

0:01:56.040 --> 0:01:58.200
<v Speaker 1>mint did it come from? Um you know what? I

0:01:58.200 --> 0:01:59.760
<v Speaker 1>put it back in my pocket, So I don't know.

0:02:00.360 --> 0:02:03.720
<v Speaker 1>But but Mr Chris rigged. Mr Chris Philette will be

0:02:03.720 --> 0:02:07.600
<v Speaker 1>representing the open system side and I shall be representing

0:02:07.600 --> 0:02:09.600
<v Speaker 1>the closed system side. So I think that proves it

0:02:09.680 --> 0:02:13.480
<v Speaker 1>wasn't rigged. Look at the kind of phone I'm using.

0:02:13.600 --> 0:02:16.720
<v Speaker 1>So anyway, Uh, I think I think in order to

0:02:16.720 --> 0:02:18.560
<v Speaker 1>really understand what we're talking about. First, we have to

0:02:19.040 --> 0:02:22.400
<v Speaker 1>establish what we mean by an open versus a closed system.

0:02:22.440 --> 0:02:24.680
<v Speaker 1>So let me tell you what a closed system is.

0:02:25.200 --> 0:02:28.480
<v Speaker 1>Closed system is quality people. That's what a closed system is.

0:02:29.639 --> 0:02:34.040
<v Speaker 1>Closed system is where you create a an infrastructure, uh

0:02:34.120 --> 0:02:37.760
<v Speaker 1>an ecosystem, if you will, where you control as many

0:02:37.800 --> 0:02:41.640
<v Speaker 1>of the factors as you possibly can, and you don't

0:02:41.680 --> 0:02:46.359
<v Speaker 1>allow outside influences to change your system. So an example

0:02:46.800 --> 0:02:50.360
<v Speaker 1>of a company that takes the closed system approach is Apple.

0:02:51.400 --> 0:02:54.400
<v Speaker 1>That's not to say that Apple only does the closed

0:02:54.400 --> 0:02:56.160
<v Speaker 1>off approach. If it did, then you would never be

0:02:56.200 --> 0:02:58.400
<v Speaker 1>able to run any other kind of software or app

0:02:58.520 --> 0:03:01.720
<v Speaker 1>on Apple products. You would only be able to run

0:03:01.760 --> 0:03:05.200
<v Speaker 1>Apple created stuff. But it's an example of a system

0:03:05.240 --> 0:03:08.080
<v Speaker 1>because it's more closed than it is open. And there

0:03:08.120 --> 0:03:10.119
<v Speaker 1>are various reasons for doing this, but we'll get into

0:03:10.160 --> 0:03:12.880
<v Speaker 1>that in the debate. But that that's kind of what

0:03:13.800 --> 0:03:16.040
<v Speaker 1>how I define a closed system. It's one where you're

0:03:16.080 --> 0:03:18.639
<v Speaker 1>trying to control as much as possible, and it's all

0:03:18.720 --> 0:03:20.840
<v Speaker 1>coming from or as much of it as possible is

0:03:20.840 --> 0:03:24.200
<v Speaker 1>coming from a single source, and the outside stuff is

0:03:24.520 --> 0:03:28.120
<v Speaker 1>shut away. Yes, And and I think as we talk

0:03:28.200 --> 0:03:31.640
<v Speaker 1>about this, our listeners will realize that there are few

0:03:31.680 --> 0:03:36.880
<v Speaker 1>absolutes in this discussion. Very true. Okay, so open source

0:03:37.480 --> 0:03:42.080
<v Speaker 1>information wants to be free, and the ore are computing

0:03:42.120 --> 0:03:46.560
<v Speaker 1>devices should too. It's the only way to be, uh,

0:03:46.560 --> 0:03:49.920
<v Speaker 1>you know, free to be you and me? Um okay

0:03:49.960 --> 0:03:55.000
<v Speaker 1>yea hippy. No, an open system is is something that

0:03:55.400 --> 0:03:59.080
<v Speaker 1>is not made for corporate gain. It is out there

0:03:59.200 --> 0:04:01.720
<v Speaker 1>for the public to use. Anybody who wants to make

0:04:01.720 --> 0:04:05.480
<v Speaker 1>a contribution to it. Can people can use it, uh

0:04:05.520 --> 0:04:09.200
<v Speaker 1>if they want to. And there it's it's there as

0:04:09.360 --> 0:04:12.440
<v Speaker 1>offered as a public service. Um. And is therefore the

0:04:12.480 --> 0:04:16.560
<v Speaker 1>people of the people, by the people, and you closed

0:04:16.760 --> 0:04:20.560
<v Speaker 1>system punks should leave us alone because this is the

0:04:20.600 --> 0:04:22.359
<v Speaker 1>way it really should be and trying to make a

0:04:22.400 --> 0:04:24.720
<v Speaker 1>buck off that is wrong. Yeah. So if you think

0:04:24.760 --> 0:04:26.960
<v Speaker 1>of it, uh, an open system is sort of democratic

0:04:27.000 --> 0:04:30.440
<v Speaker 1>and that anyone can really contribute to it and and

0:04:30.600 --> 0:04:32.920
<v Speaker 1>change it. And also we should point out before we

0:04:32.960 --> 0:04:35.799
<v Speaker 1>really get into this debate, uh, that it is possible

0:04:35.880 --> 0:04:40.200
<v Speaker 1>to have a a product probably that's for sale, either

0:04:40.279 --> 0:04:42.599
<v Speaker 1>that's an open system or a closed system. Open and

0:04:42.640 --> 0:04:44.560
<v Speaker 1>closed does not mean that one is free and one

0:04:44.680 --> 0:04:48.200
<v Speaker 1>is is you charge for Yeah, I was I I did. Yeah,

0:04:48.240 --> 0:04:50.080
<v Speaker 1>that's a good point. I should have pointed out that

0:04:50.160 --> 0:04:53.960
<v Speaker 1>sort of the quote unquote ideal version when when a

0:04:53.960 --> 0:04:56.200
<v Speaker 1>lot of people talk about open source, right, if you're

0:04:56.240 --> 0:04:59.359
<v Speaker 1>going the ultimate open source, like the utopian version of

0:04:59.400 --> 0:05:03.880
<v Speaker 1>open source, when you're talking about that's cool, that's cool, Yeah,

0:05:03.880 --> 0:05:05.600
<v Speaker 1>because there there really is a spectrum here. But we're

0:05:05.600 --> 0:05:09.159
<v Speaker 1>gonna try and be like hardcore. So mal, let me

0:05:09.200 --> 0:05:12.800
<v Speaker 1>explain why I think that closed systems are superior to

0:05:12.920 --> 0:05:17.080
<v Speaker 1>open systems. So with a closed system and with with

0:05:18.360 --> 0:05:21.560
<v Speaker 1>with with everything coming from a single source. So in

0:05:21.600 --> 0:05:23.480
<v Speaker 1>this case, let's say it's a company. A company is

0:05:23.520 --> 0:05:26.640
<v Speaker 1>creating a product that is closed off, no other outside

0:05:26.640 --> 0:05:30.000
<v Speaker 1>influence can can come into this product. It means that

0:05:30.040 --> 0:05:33.440
<v Speaker 1>there's an expectation of quality control that you don't have

0:05:33.480 --> 0:05:36.440
<v Speaker 1>with open systems. You actually can test everything, make sure

0:05:36.440 --> 0:05:39.520
<v Speaker 1>everything works properly on the hardware. So if we're talking

0:05:39.520 --> 0:05:42.280
<v Speaker 1>about a computer, we know that the software will work

0:05:42.360 --> 0:05:45.000
<v Speaker 1>on the computer because the software and hardware have been

0:05:45.040 --> 0:05:49.479
<v Speaker 1>developed together from the ground up. It means that you

0:05:49.520 --> 0:05:53.720
<v Speaker 1>don't have to worry about some weird incompatibility issue when

0:05:53.760 --> 0:05:58.280
<v Speaker 1>you try and install a program onto this device, because

0:05:58.320 --> 0:06:00.719
<v Speaker 1>again everything is coming from the same source and was

0:06:00.839 --> 0:06:04.080
<v Speaker 1>made to work together. Now this can go beyond just

0:06:04.160 --> 0:06:06.640
<v Speaker 1>a computer. Let's say that you have a computer and

0:06:06.720 --> 0:06:08.960
<v Speaker 1>a smartphone and a tablet and they're all part of

0:06:08.960 --> 0:06:12.160
<v Speaker 1>the same closed system. It means that you can expect

0:06:12.320 --> 0:06:17.400
<v Speaker 1>a fairly uniform experience across these three platforms, and maybe

0:06:17.400 --> 0:06:19.520
<v Speaker 1>even be able to port your experience from one to

0:06:19.560 --> 0:06:21.440
<v Speaker 1>the other. And what I mean by that is, let's

0:06:21.440 --> 0:06:24.520
<v Speaker 1>say I'm watching a movie on my smartphone and then

0:06:24.680 --> 0:06:26.240
<v Speaker 1>I decide, you know what, I really want to look

0:06:26.279 --> 0:06:28.000
<v Speaker 1>at this on a bigger screen, and I tap it

0:06:28.040 --> 0:06:30.520
<v Speaker 1>over to my tablet, and the tablet starts playing the

0:06:30.560 --> 0:06:33.119
<v Speaker 1>movie exactly where I left off, and it all works

0:06:33.120 --> 0:06:37.279
<v Speaker 1>seamlessly because it's all running on the same platform that's

0:06:37.600 --> 0:06:40.799
<v Speaker 1>meant to work together. That is one of the big

0:06:40.839 --> 0:06:43.359
<v Speaker 1>benefits of a closed system is that you have a

0:06:43.480 --> 0:06:47.480
<v Speaker 1>uniformity in the experience and an expectation of things are

0:06:47.520 --> 0:06:50.640
<v Speaker 1>just gonna work because it was all built together and

0:06:50.720 --> 0:06:56.919
<v Speaker 1>meant to work together. Why are you taking away my choice?

0:06:58.400 --> 0:07:01.640
<v Speaker 1>If I want to have a different video card than

0:07:01.680 --> 0:07:04.880
<v Speaker 1>the one you stuck in my computer, I want to

0:07:04.920 --> 0:07:06.960
<v Speaker 1>be able to remove it and stick a different one

0:07:07.000 --> 0:07:10.240
<v Speaker 1>in there, you know what. And it's and it's frustrating

0:07:10.280 --> 0:07:13.520
<v Speaker 1>because any time I want to change a component on

0:07:13.560 --> 0:07:16.960
<v Speaker 1>my computer or I want something a little different, UH,

0:07:17.000 --> 0:07:19.760
<v Speaker 1>you know, I have to deal with all the complications

0:07:19.800 --> 0:07:23.760
<v Speaker 1>that you're closed off. UH system is is taking away

0:07:24.160 --> 0:07:29.000
<v Speaker 1>And the problem is that, UH, you're also restricting competition

0:07:29.360 --> 0:07:32.480
<v Speaker 1>because in your closed system, there's only one way to

0:07:32.520 --> 0:07:34.240
<v Speaker 1>go for a tablet, and there's one way to go

0:07:34.280 --> 0:07:35.840
<v Speaker 1>for an MP three player, and there's one way to

0:07:35.840 --> 0:07:37.400
<v Speaker 1>go for a smartphone. There's one way to go for

0:07:37.440 --> 0:07:41.000
<v Speaker 1>a computer. And I want I want choice. I want

0:07:41.040 --> 0:07:44.960
<v Speaker 1>to be able to customize my my computing experience. I

0:07:45.000 --> 0:07:48.400
<v Speaker 1>want to be able to buy something cheaper because competition

0:07:48.920 --> 0:07:51.760
<v Speaker 1>is driving down the cost of these products. So I

0:07:51.800 --> 0:07:54.200
<v Speaker 1>could go to your store and buy the one computer

0:07:54.280 --> 0:07:56.160
<v Speaker 1>you've got, or I could go to this store over

0:07:56.200 --> 0:07:58.600
<v Speaker 1>here and buy fifty different computers, and all of them

0:07:58.640 --> 0:08:02.120
<v Speaker 1>are cheaper than yours, and some of them even outperform yours. Well,

0:08:02.200 --> 0:08:03.800
<v Speaker 1>So what do you say to that? Here's what I

0:08:03.800 --> 0:08:05.680
<v Speaker 1>say to that. Sure, it might be cheaper, and even

0:08:05.720 --> 0:08:08.360
<v Speaker 1>if you have a device, a particular individual device that

0:08:08.400 --> 0:08:11.680
<v Speaker 1>performs better than one of my particular individual devices. If

0:08:11.720 --> 0:08:15.560
<v Speaker 1>you are trying to have an experience that spans multiple devices,

0:08:15.560 --> 0:08:19.000
<v Speaker 1>then you're going to start encountering things where the compatibility

0:08:19.040 --> 0:08:23.320
<v Speaker 1>issues come into play, and you may have things like

0:08:23.520 --> 0:08:27.680
<v Speaker 1>software crashes because it's not designed to work together seamlessly

0:08:28.000 --> 0:08:30.920
<v Speaker 1>like a closed system is. So you might spend less

0:08:30.960 --> 0:08:35.120
<v Speaker 1>money initially when you first purchase your vast array of

0:08:35.559 --> 0:08:38.920
<v Speaker 1>choice here and you've got let you know, your ultimate

0:08:38.920 --> 0:08:40.400
<v Speaker 1>price tag is lower than you would if you have

0:08:40.440 --> 0:08:45.120
<v Speaker 1>bought everything from my superior closed system store. But the

0:08:45.200 --> 0:08:48.360
<v Speaker 1>amount of frustration you're going to have as that experience

0:08:48.520 --> 0:08:52.920
<v Speaker 1>is unsatisfactory because the various pieces are not playing together

0:08:53.000 --> 0:08:58.000
<v Speaker 1>properly is far going to outweigh the miniscule additional investment

0:08:58.040 --> 0:08:59.440
<v Speaker 1>you would have to make if you had purchased it

0:08:59.480 --> 0:09:02.240
<v Speaker 1>all from me in the first place. And yeah, you're

0:09:02.320 --> 0:09:05.640
<v Speaker 1>one individual device might behave better or perform better than

0:09:05.679 --> 0:09:09.240
<v Speaker 1>why one individual device, but collectively, the experience is much

0:09:09.240 --> 0:09:11.880
<v Speaker 1>more satisfying on my end than it is on yours,

0:09:11.880 --> 0:09:15.920
<v Speaker 1>because it's yours is piecemeal, and also my system is

0:09:15.960 --> 0:09:19.800
<v Speaker 1>designed to just work. Your system is designed to make

0:09:19.840 --> 0:09:22.440
<v Speaker 1>me have to have a computer science degree if I

0:09:22.480 --> 0:09:24.360
<v Speaker 1>want to figure out how to do the same thing

0:09:24.400 --> 0:09:31.319
<v Speaker 1>on one device as I'm doing on another device. Ha superior,

0:09:31.400 --> 0:09:33.680
<v Speaker 1>You say, yes, I don't think that word means what

0:09:33.760 --> 0:09:36.160
<v Speaker 1>you think. Well, here, let me put it to you

0:09:36.240 --> 0:09:38.960
<v Speaker 1>another way. Let's let's let's take a look at the

0:09:38.960 --> 0:09:42.200
<v Speaker 1>way a closed system versus an open system attacks the

0:09:42.280 --> 0:09:47.760
<v Speaker 1>problem of malware, because they have very different approaches. Right, So,

0:09:47.920 --> 0:09:52.320
<v Speaker 1>if we're talking about the perfect closed system, ideally there's

0:09:52.320 --> 0:09:55.800
<v Speaker 1>no malware because nothing from outside is being introduced into

0:09:55.840 --> 0:09:59.920
<v Speaker 1>the system unless there's some you know, disgruntled employee that

0:10:00.000 --> 0:10:03.240
<v Speaker 1>I bullied out of out of their sanity. We don't

0:10:03.280 --> 0:10:05.720
<v Speaker 1>have to worry about malware entering into the closed system

0:10:05.720 --> 0:10:09.560
<v Speaker 1>because everything is made by this one entity and it's

0:10:09.559 --> 0:10:11.200
<v Speaker 1>all made to work together, so you don't have to

0:10:11.200 --> 0:10:15.600
<v Speaker 1>worry about some sort of virus perpetuating itself through your system.

0:10:15.920 --> 0:10:22.199
<v Speaker 1>Now that's different from the way open systems attack malware. Well,

0:10:23.000 --> 0:10:26.400
<v Speaker 1>see the open systems, you could have other people, multiple

0:10:26.440 --> 0:10:29.640
<v Speaker 1>people working on solutions to things like vulnerabilities in the

0:10:29.679 --> 0:10:34.600
<v Speaker 1>operating system, and people who are working on uh anti

0:10:34.679 --> 0:10:38.760
<v Speaker 1>malware software for your system. So the thing is, that's

0:10:38.800 --> 0:10:41.920
<v Speaker 1>a small price to pay for the ability to hack

0:10:42.000 --> 0:10:44.840
<v Speaker 1>into the system and change whatever you want to change

0:10:44.880 --> 0:10:48.360
<v Speaker 1>about the system. If you want to, uh, get into

0:10:48.400 --> 0:10:51.200
<v Speaker 1>the operating system and see what makes it tick and

0:10:51.360 --> 0:10:56.560
<v Speaker 1>learn more about what what programs and what functions are

0:10:56.600 --> 0:10:59.080
<v Speaker 1>going on in the background. For example, you could be

0:10:59.120 --> 0:11:01.960
<v Speaker 1>monitoring everything I do, but if you're in your closed system,

0:11:01.960 --> 0:11:04.640
<v Speaker 1>I can't get into the background to see that. Then

0:11:04.840 --> 0:11:07.080
<v Speaker 1>you know you could be doing this all without my knowledge.

0:11:07.559 --> 0:11:10.280
<v Speaker 1>Um So with an open system, I I'm free to

0:11:10.360 --> 0:11:13.680
<v Speaker 1>install any software I want to or remove any software

0:11:13.720 --> 0:11:16.560
<v Speaker 1>I want to from my device. And I could even

0:11:16.559 --> 0:11:20.120
<v Speaker 1>write my own because you know it's open, and uh,

0:11:20.400 --> 0:11:23.199
<v Speaker 1>it gives me the opportunity to to hack in and

0:11:23.240 --> 0:11:25.240
<v Speaker 1>play with it and make it my own instead of

0:11:25.280 --> 0:11:27.280
<v Speaker 1>make it what your vision is. Because what if your

0:11:27.400 --> 0:11:31.640
<v Speaker 1>closed vision, you're closed off, walled off, little garden isn't

0:11:31.679 --> 0:11:35.040
<v Speaker 1>what I think of as being the best experience for me,

0:11:35.080 --> 0:11:38.199
<v Speaker 1>because hey, everybody's an individual, right Well. First of all,

0:11:38.240 --> 0:11:41.360
<v Speaker 1>we know what you want, even when you don't see

0:11:41.400 --> 0:11:43.440
<v Speaker 1>That's the thing is, we know what you want. You

0:11:43.480 --> 0:11:45.760
<v Speaker 1>don't know what you want, but we know what you want.

0:11:46.200 --> 0:11:48.199
<v Speaker 1>You think you know what you want, but until you've

0:11:48.240 --> 0:11:52.160
<v Speaker 1>actually bought into our our closed system, you really haven't

0:11:52.640 --> 0:11:56.560
<v Speaker 1>haven't experienced it, And we're going to go back into

0:11:56.600 --> 0:11:59.760
<v Speaker 1>the quality issue. Let's talk about the quality of and

0:11:59.760 --> 0:12:02.520
<v Speaker 1>we're talking about computing systems here. Let's talk about the

0:12:02.600 --> 0:12:07.160
<v Speaker 1>quality of the programs that you're running on your system. Again,

0:12:07.320 --> 0:12:10.439
<v Speaker 1>with the closed system approach, those programs have been built

0:12:10.480 --> 0:12:12.680
<v Speaker 1>for a very specific set of hardware, which does not

0:12:12.840 --> 0:12:15.400
<v Speaker 1>change from what you know that if I buy my

0:12:15.480 --> 0:12:18.400
<v Speaker 1>computer from this closed system and someone else buys their

0:12:18.440 --> 0:12:21.280
<v Speaker 1>computer from the same closed system, those two computers are

0:12:21.280 --> 0:12:25.200
<v Speaker 1>going to be identical in every meaningful way, So we

0:12:25.280 --> 0:12:27.920
<v Speaker 1>know that the software is going to work equally well

0:12:28.120 --> 0:12:30.560
<v Speaker 1>on my system as it is on their system. Whereas

0:12:30.559 --> 0:12:32.440
<v Speaker 1>if we both just go into a computer store and

0:12:32.480 --> 0:12:36.719
<v Speaker 1>we each just buy a computer from various you know, manufacturers,

0:12:36.840 --> 0:12:39.640
<v Speaker 1>there's no guarantee that the same kind of software is

0:12:39.679 --> 0:12:41.679
<v Speaker 1>going to work just as well in my machine as

0:12:41.720 --> 0:12:43.800
<v Speaker 1>it is on their machine, even if the two machines

0:12:43.840 --> 0:12:46.840
<v Speaker 1>are running the same operating system, because we have difficulties

0:12:46.920 --> 0:12:51.800
<v Speaker 1>introduced by things like device drivers and hardware differences. With

0:12:51.880 --> 0:12:54.360
<v Speaker 1>the closed system, you've eliminated that you don't have to

0:12:54.360 --> 0:12:57.200
<v Speaker 1>worry about that so much. So that means that the

0:12:57.320 --> 0:13:01.000
<v Speaker 1>quality of the experience of the software. Put aside the

0:13:01.080 --> 0:13:04.360
<v Speaker 1>quality of the software itself, but the experience of using

0:13:04.360 --> 0:13:08.280
<v Speaker 1>it is going to be less frustrating. Uh the you know,

0:13:08.520 --> 0:13:11.040
<v Speaker 1>you might say that there's a downside with the whole

0:13:11.120 --> 0:13:13.640
<v Speaker 1>choice factor, but at the same time, you don't have

0:13:13.720 --> 0:13:17.320
<v Speaker 1>to worry about it crashing all the time or just

0:13:17.400 --> 0:13:20.840
<v Speaker 1>not behaving the proper way. I think. Sure, sometimes things happen,

0:13:20.880 --> 0:13:23.800
<v Speaker 1>but on a much less frequent basis than on these

0:13:23.840 --> 0:13:27.480
<v Speaker 1>these little open systems out there that that just well,

0:13:27.960 --> 0:13:30.640
<v Speaker 1>I don't know, they they they just they just are

0:13:30.640 --> 0:13:35.520
<v Speaker 1>like every anything goes well with the potential of with

0:13:35.520 --> 0:13:38.960
<v Speaker 1>with open source software, you have to potential a limitless

0:13:39.000 --> 0:13:42.719
<v Speaker 1>potential of applications that could be run for it. The

0:13:43.120 --> 0:13:47.440
<v Speaker 1>more open you become, the greater the possibilities. Um. You know.

0:13:47.600 --> 0:13:51.199
<v Speaker 1>So you can have your closed system and have things

0:13:51.280 --> 0:13:55.439
<v Speaker 1>that run specifically on that hardware. But you know, programmers

0:13:55.480 --> 0:13:59.120
<v Speaker 1>like their choices too, and they're gonna go where where

0:13:59.160 --> 0:14:01.240
<v Speaker 1>the wealth of soft where it is, and that's when

0:14:01.240 --> 0:14:05.079
<v Speaker 1>you attract more users, and vice versa and versa visa.

0:14:05.200 --> 0:14:09.959
<v Speaker 1>And I disagree with that because users, most users don't

0:14:10.000 --> 0:14:12.640
<v Speaker 1>want to be curators. And if you are a user

0:14:12.640 --> 0:14:14.800
<v Speaker 1>of an open system, you have to be a curator

0:14:14.880 --> 0:14:17.280
<v Speaker 1>because there's so much that you're talking about, so much

0:14:17.360 --> 0:14:21.440
<v Speaker 1>variety and so much choice, that it's overwhelming to the

0:14:21.480 --> 0:14:24.080
<v Speaker 1>average user. You sit down and you see like there's

0:14:23.920 --> 0:14:26.520
<v Speaker 1>it's like walking into a library and you have no

0:14:26.600 --> 0:14:28.240
<v Speaker 1>idea what book you want to read. You just know

0:14:28.320 --> 0:14:30.120
<v Speaker 1>you want to read a book, and you walk into

0:14:30.240 --> 0:14:33.960
<v Speaker 1>an enormous library and you have no idea where to go.

0:14:34.280 --> 0:14:37.960
<v Speaker 1>It's too confusing. Whereas in a closed system, it's been

0:14:38.000 --> 0:14:41.200
<v Speaker 1>curated for you. Your choices are limited, but at the

0:14:41.200 --> 0:14:43.840
<v Speaker 1>same time, you don't have to worry about going through

0:14:44.440 --> 0:14:48.640
<v Speaker 1>eight thousand different word processing programs in order to find

0:14:48.640 --> 0:14:51.400
<v Speaker 1>one that suits your needs. There's really only one choice,

0:14:51.680 --> 0:14:55.640
<v Speaker 1>and if it suits your needs, that's awesome. Jonathan, you ignorance.

0:14:56.040 --> 0:15:01.520
<v Speaker 1>Ha ha oh Saturday night Life. I bet you they

0:15:01.560 --> 0:15:05.840
<v Speaker 1>cut that. Um anyhow, uh well, see, there's one thing

0:15:05.960 --> 0:15:08.640
<v Speaker 1>that that you're leaving out here, the market, because what

0:15:08.760 --> 0:15:12.360
<v Speaker 1>happens here is the market helps people whittle down their choices.

0:15:12.680 --> 0:15:15.960
<v Speaker 1>When you have something the the word processor of choice,

0:15:16.360 --> 0:15:20.720
<v Speaker 1>the one that that more people are using than people understand,

0:15:20.800 --> 0:15:24.400
<v Speaker 1>it's the best seller phenomenon it's like you look at

0:15:24.400 --> 0:15:26.280
<v Speaker 1>the best seller lists and you and you say, you

0:15:26.280 --> 0:15:29.200
<v Speaker 1>know what, these books are very popular. I bet you

0:15:29.280 --> 0:15:31.680
<v Speaker 1>anything that if I if I read it, I'm you know,

0:15:31.760 --> 0:15:33.920
<v Speaker 1>I will at least look at these first because I

0:15:33.960 --> 0:15:36.360
<v Speaker 1>know lots of people like them, and that helps people

0:15:36.640 --> 0:15:39.600
<v Speaker 1>make choices as far as software is concerned, and you know,

0:15:39.920 --> 0:15:43.440
<v Speaker 1>there's always a new programmer coming online to develop new

0:15:43.480 --> 0:15:47.400
<v Speaker 1>software and you can always help be the kingmaker for

0:15:47.400 --> 0:15:50.160
<v Speaker 1>the next generation of software too. But not in the

0:15:50.160 --> 0:15:53.080
<v Speaker 1>closed system where you know your choices are somewhat limited.

0:15:54.160 --> 0:15:55.840
<v Speaker 1>I don't know. I'm trying to think of a best

0:15:55.880 --> 0:16:00.280
<v Speaker 1>selling open source software example, and it's really hard. Well,

0:16:00.320 --> 0:16:02.680
<v Speaker 1>you know, in a lot of cases, open source software

0:16:02.800 --> 0:16:07.480
<v Speaker 1>can be free or donationware, and a donationware world, people

0:16:07.600 --> 0:16:10.200
<v Speaker 1>pay what they what it's worth to them. And sure

0:16:10.280 --> 0:16:14.000
<v Speaker 1>some people are going to pay a quarter, and there

0:16:14.000 --> 0:16:16.880
<v Speaker 1>are also people who pay a hundred dollars for the

0:16:16.920 --> 0:16:19.080
<v Speaker 1>same piece of software because it means more to them

0:16:19.120 --> 0:16:22.120
<v Speaker 1>and it's important to them to donate to the community.

0:16:22.160 --> 0:16:25.800
<v Speaker 1>I mean, you know, not found that out? How did

0:16:25.920 --> 0:16:30.280
<v Speaker 1>how did Minecraft? Just you know, it's it's a thing. Yeah,

0:16:30.320 --> 0:16:32.240
<v Speaker 1>but I still think that the closed system is the

0:16:32.280 --> 0:16:35.720
<v Speaker 1>way to go. It's a sustainable business model. It means

0:16:35.760 --> 0:16:40.000
<v Speaker 1>that you once you develop your your your line of devotees,

0:16:40.400 --> 0:16:43.600
<v Speaker 1>you're good to go. I mean because you you've created

0:16:43.640 --> 0:16:47.520
<v Speaker 1>that expectation of that quality of experience that you deliver

0:16:47.680 --> 0:16:51.760
<v Speaker 1>upon consistently, and by doing that, you know that you know,

0:16:51.800 --> 0:16:54.880
<v Speaker 1>as long as you maintain that level of quality, that

0:16:54.960 --> 0:16:58.800
<v Speaker 1>you will have a customer base moving forward. Whereas with

0:16:58.880 --> 0:17:02.000
<v Speaker 1>this open source roach, I don't see how you're gonna be,

0:17:02.120 --> 0:17:05.160
<v Speaker 1>you know, really making a sustainable business out of that.

0:17:05.480 --> 0:17:09.080
<v Speaker 1>And while the ideals are wonderful and fantastic and and

0:17:09.080 --> 0:17:13.280
<v Speaker 1>and and and happy and all that mess um, I

0:17:13.320 --> 0:17:16.840
<v Speaker 1>just don't see it, you know, perpetuating itself after a

0:17:16.840 --> 0:17:20.680
<v Speaker 1>certain amount. You know, eventually a guy's got to eat well.

0:17:20.720 --> 0:17:23.760
<v Speaker 1>And and that's why I think, uh, that's why I

0:17:23.760 --> 0:17:27.800
<v Speaker 1>think openness is sort of a bell curve. Yeah, because

0:17:28.080 --> 0:17:30.520
<v Speaker 1>the one end you have the clothe the the completely

0:17:30.560 --> 0:17:34.040
<v Speaker 1>closed off system with fewer fewer users, which you know,

0:17:34.359 --> 0:17:37.360
<v Speaker 1>we should point out again there's not really that many.

0:17:37.680 --> 0:17:40.119
<v Speaker 1>I can't think of any company that would be that

0:17:40.280 --> 0:17:43.399
<v Speaker 1>I could point to that say absolutely is this like

0:17:43.480 --> 0:17:45.879
<v Speaker 1>even the systems that we think of as closed like

0:17:45.960 --> 0:17:50.320
<v Speaker 1>Apple and Nintendo aren't really that closed. Otherwise no third

0:17:50.320 --> 0:17:52.520
<v Speaker 1>party developer would ever be able to create anything for

0:17:52.560 --> 0:17:56.280
<v Speaker 1>their platforms. Right. And then at the other side, UM,

0:17:56.400 --> 0:18:00.240
<v Speaker 1>I'm trying to think of somebody who is really completely

0:18:00.359 --> 0:18:04.520
<v Speaker 1>open as far as open source. But that's as close

0:18:04.560 --> 0:18:06.720
<v Speaker 1>as you can get. Yeah. And the thing is, as

0:18:06.880 --> 0:18:12.200
<v Speaker 1>Jonathan pointed out earlier, UM, Lennox is free and it's

0:18:12.240 --> 0:18:14.800
<v Speaker 1>you know, the sources open, which is in the guts

0:18:14.840 --> 0:18:17.360
<v Speaker 1>of the operating system are open for people to use.

0:18:17.560 --> 0:18:19.800
<v Speaker 1>And there are distributions of Linux that are completely free

0:18:19.840 --> 0:18:22.600
<v Speaker 1>for people to use, and there are others that. Uh.

0:18:22.640 --> 0:18:25.560
<v Speaker 1>There is a purchase price because it is tailored two

0:18:25.640 --> 0:18:29.399
<v Speaker 1>specific needs and usually has some support level of support

0:18:29.400 --> 0:18:31.399
<v Speaker 1>built into that. So if you buy the software, then

0:18:31.440 --> 0:18:33.520
<v Speaker 1>you can expect to have someone to call if you've

0:18:33.560 --> 0:18:36.040
<v Speaker 1>got a problem. Yeah. Sometimes it's not the software itself

0:18:36.080 --> 0:18:38.840
<v Speaker 1>that's that's got the price tag. It's the support. Yeah.

0:18:39.080 --> 0:18:42.199
<v Speaker 1>So for example, Buntu is that way you can you

0:18:42.200 --> 0:18:44.680
<v Speaker 1>can get a free version of a Buntu and install

0:18:44.720 --> 0:18:46.400
<v Speaker 1>it on your computer. By the way, the debate part

0:18:46.440 --> 0:18:48.679
<v Speaker 1>of this podcast is over In case you hadn't realized

0:18:48.720 --> 0:18:51.640
<v Speaker 1>that We're now getting into the more informational side. Um. Yeah,

0:18:51.720 --> 0:18:54.159
<v Speaker 1>the the and I think that went really well. The

0:18:54.960 --> 0:18:58.080
<v Speaker 1>but Abuntu, you you can get that for free and

0:18:58.119 --> 0:19:00.960
<v Speaker 1>install that on a machine for free. But if you

0:19:01.040 --> 0:19:04.480
<v Speaker 1>want to have professional level support, then you can pay

0:19:04.560 --> 0:19:06.640
<v Speaker 1>a certain amount of money and then you will have

0:19:06.720 --> 0:19:12.040
<v Speaker 1>access to UM support staff, which could be anything from

0:19:12.040 --> 0:19:14.679
<v Speaker 1>my computer isn't behaving properly, what is the what is

0:19:14.680 --> 0:19:16.520
<v Speaker 1>the source of this problem? How do I fix it too?

0:19:17.240 --> 0:19:22.120
<v Speaker 1>I'm running an actual closed network of machines in this

0:19:22.160 --> 0:19:24.080
<v Speaker 1>one business, and I need to know how to set

0:19:24.080 --> 0:19:26.639
<v Speaker 1>this up so that everything is secure that kind of

0:19:26.960 --> 0:19:30.359
<v Speaker 1>it's it's all levels of support. Uh. And and you know,

0:19:30.520 --> 0:19:33.600
<v Speaker 1>there are definitely arguments both for and against the closed

0:19:33.600 --> 0:19:36.640
<v Speaker 1>and open systems, as we were demonstrating earlier. And it's

0:19:36.680 --> 0:19:40.280
<v Speaker 1>not that one system is inherently better or worse than

0:19:40.320 --> 0:19:44.200
<v Speaker 1>the other. They're just different philosophies on how to provide

0:19:44.760 --> 0:19:48.719
<v Speaker 1>UM goods and services. Yeah. Really there the arguments we

0:19:48.720 --> 0:19:51.360
<v Speaker 1>were making. I think, um, you know, there were good

0:19:51.440 --> 0:19:53.960
<v Speaker 1>arguments on both sides. I think the it works better.

0:19:54.600 --> 0:19:58.000
<v Speaker 1>There are arguments I've heard sort of like the ones

0:19:58.359 --> 0:20:00.919
<v Speaker 1>the debate we just had that we're are more heated

0:20:01.119 --> 0:20:03.879
<v Speaker 1>than that. You thin get the when you're actually thinking

0:20:03.880 --> 0:20:06.439
<v Speaker 1>about both sides and not taking a side, it it

0:20:06.480 --> 0:20:08.800
<v Speaker 1>kind of works better because really there are some benefits

0:20:09.040 --> 0:20:12.800
<v Speaker 1>with with clothes, you do have things that just work, um,

0:20:12.800 --> 0:20:14.720
<v Speaker 1>But with open you do have a lot more choice

0:20:14.720 --> 0:20:16.479
<v Speaker 1>and the ability to tinker more with it. And it's

0:20:16.480 --> 0:20:18.800
<v Speaker 1>sort of really, I think depends on what you're looking for.

0:20:19.200 --> 0:20:21.960
<v Speaker 1>So this is why so many people use Windows because

0:20:21.960 --> 0:20:25.320
<v Speaker 1>it's sort of an open closed system. Windows is Windows

0:20:25.320 --> 0:20:28.600
<v Speaker 1>the sort of the middle ground. Uh, it's it's it

0:20:28.720 --> 0:20:31.240
<v Speaker 1>leans closed. Yeah, it lands closed, but it has a

0:20:31.280 --> 0:20:33.840
<v Speaker 1>lot of flexibility for people to build applications that run

0:20:33.840 --> 0:20:37.199
<v Speaker 1>on Windows. So in that that sense, it's open in

0:20:37.280 --> 0:20:40.879
<v Speaker 1>the in the way that you know, again, third party

0:20:40.920 --> 0:20:44.159
<v Speaker 1>developers create the vast majority of software that runs on

0:20:44.200 --> 0:20:48.000
<v Speaker 1>Windows based PCs. You know, very a small percentage of

0:20:48.000 --> 0:20:51.119
<v Speaker 1>the software that runs on Windows based PCs comes from Microsoft.

0:20:51.800 --> 0:20:55.240
<v Speaker 1>There there's there are very important applications that are on

0:20:55.240 --> 0:20:58.359
<v Speaker 1>a typical Windows based PC that are from Microsoft. But

0:20:58.480 --> 0:21:00.320
<v Speaker 1>you know, if you're like, if you're going to some

0:21:00.600 --> 0:21:04.040
<v Speaker 1>video gamers house and you're looking at his rig and

0:21:04.560 --> 0:21:07.240
<v Speaker 1>or her rig, I should say because you know, I've

0:21:07.240 --> 0:21:11.320
<v Speaker 1>met some lead female video gamers who could wipe the

0:21:11.320 --> 0:21:14.399
<v Speaker 1>floor with me in any game I've shows, which is

0:21:14.520 --> 0:21:18.040
<v Speaker 1>very they're staring at you now as a matter of fact. Yeah,

0:21:18.160 --> 0:21:19.760
<v Speaker 1>well I'll probably end up seeing some of them at

0:21:19.800 --> 0:21:23.639
<v Speaker 1>c E s uh, and they'll again I won't challenge

0:21:23.680 --> 0:21:26.120
<v Speaker 1>them that I already know how I would turn out anyway.

0:21:26.359 --> 0:21:27.879
<v Speaker 1>So you but you go on, you look at the

0:21:27.880 --> 0:21:31.119
<v Speaker 1>software on that person's computer, and you're gonna see that

0:21:31.160 --> 0:21:33.560
<v Speaker 1>there's a ton of stuff on there that never came

0:21:33.560 --> 0:21:36.240
<v Speaker 1>out of Microsoft. Uh. And same, the same sort of

0:21:36.240 --> 0:21:39.120
<v Speaker 1>thing applies to Apple. It's not there. It's not as

0:21:39.200 --> 0:21:42.520
<v Speaker 1>much software as far as just you know, sheer numbers

0:21:42.760 --> 0:21:45.000
<v Speaker 1>as you would find for a Windows based PC. But

0:21:45.320 --> 0:21:46.879
<v Speaker 1>you know, even Apple, which we think of as a

0:21:46.920 --> 0:21:50.440
<v Speaker 1>really like a walled garden or a closed system, depends

0:21:50.440 --> 0:21:52.520
<v Speaker 1>heavily on third party developers. If it didn't, the app

0:21:52.600 --> 0:21:56.000
<v Speaker 1>store for the iPhone and iPad and and iPod touch

0:21:56.359 --> 0:21:58.840
<v Speaker 1>would be empty. You know, there would be very few

0:21:58.880 --> 0:22:02.960
<v Speaker 1>apps that you could run because Apple only provides a few. Um.

0:22:03.040 --> 0:22:06.320
<v Speaker 1>But you know, they they they lean very heavily on

0:22:06.400 --> 0:22:08.760
<v Speaker 1>third parbaty developers. Not at the same time, third parbaty,

0:22:08.800 --> 0:22:13.680
<v Speaker 1>developers have to go through a very rigorous UH routine

0:22:13.720 --> 0:22:16.360
<v Speaker 1>in order to submit an app and have it featured

0:22:16.359 --> 0:22:18.199
<v Speaker 1>in the App Store, And of course if it's not

0:22:18.240 --> 0:22:20.919
<v Speaker 1>in the App Store, technically you can't load it on

0:22:20.960 --> 0:22:23.600
<v Speaker 1>an Apple device unless you've gone through the process of

0:22:23.680 --> 0:22:28.119
<v Speaker 1>jail breaking it. But using it unaltered an unaltered Apple device,

0:22:28.520 --> 0:22:31.440
<v Speaker 1>you can only load things that are through the the

0:22:31.480 --> 0:22:34.879
<v Speaker 1>Apple's official App Store, So in that sense it's closed

0:22:34.880 --> 0:22:36.719
<v Speaker 1>off because if it's not approved, then it doesn't go

0:22:36.760 --> 0:22:38.840
<v Speaker 1>on the same thing with Nintendo. You know, they would

0:22:38.840 --> 0:22:41.719
<v Speaker 1>certify the games that would go on their systems, and

0:22:41.760 --> 0:22:44.800
<v Speaker 1>if it didn't get Nintendo certification, it didn't it didn't

0:22:44.840 --> 0:22:50.679
<v Speaker 1>get made, didn't become available on the Nintendo. So uh,

0:22:50.840 --> 0:22:53.080
<v Speaker 1>that's a closed way of looking at And again that

0:22:53.119 --> 0:22:56.800
<v Speaker 1>goes to that sort of quality control argument where the

0:22:58.280 --> 0:23:02.600
<v Speaker 1>closed the company perpetuating this closed system could argue that

0:23:02.960 --> 0:23:07.280
<v Speaker 1>this means that we only have applications of a certain

0:23:07.320 --> 0:23:09.760
<v Speaker 1>quality that we know are going to run properly on

0:23:09.800 --> 0:23:12.960
<v Speaker 1>our hardware. They're not going to cause any problems with

0:23:13.000 --> 0:23:15.560
<v Speaker 1>anything else running on our hardware, and they're going to

0:23:15.600 --> 0:23:18.919
<v Speaker 1>deliver an experience that we you know, it reaches a

0:23:18.960 --> 0:23:21.600
<v Speaker 1>certain level that we have come to expect with our

0:23:21.640 --> 0:23:25.000
<v Speaker 1>our products. Um, whereas if you go with an open system,

0:23:25.000 --> 0:23:28.000
<v Speaker 1>it's more like we want anyone to be able to

0:23:28.840 --> 0:23:32.000
<v Speaker 1>potentially run anything on this system that's been designed for it,

0:23:32.400 --> 0:23:34.520
<v Speaker 1>and we don't want to limit that at all. We

0:23:34.560 --> 0:23:39.119
<v Speaker 1>don't want to put our biases against certain kinds of applications,

0:23:39.119 --> 0:23:42.440
<v Speaker 1>are certain ways of creating stuff in play. We want

0:23:42.480 --> 0:23:47.159
<v Speaker 1>it to be an open playground for everybody. Yeah. Yeah, well, uh,

0:23:47.240 --> 0:23:49.239
<v Speaker 1>you know, for for Windows, you can argue, you can

0:23:49.280 --> 0:23:52.320
<v Speaker 1>make the hardware argument, well, I can go and build

0:23:52.680 --> 0:23:54.840
<v Speaker 1>my own system from the components that I can get

0:23:54.840 --> 0:23:57.360
<v Speaker 1>in my my corner electronics store, and I can make

0:23:57.400 --> 0:23:59.080
<v Speaker 1>my own system and install Windows on it, and it's

0:23:59.080 --> 0:24:02.760
<v Speaker 1>gonna work. Of course, chances are that the there are

0:24:02.840 --> 0:24:05.199
<v Speaker 1>drivers for the video card and there are drivers for

0:24:05.240 --> 0:24:07.360
<v Speaker 1>all the devices that you're going to do it because

0:24:07.400 --> 0:24:09.919
<v Speaker 1>you're running Windows on it, And you would also have

0:24:09.960 --> 0:24:13.440
<v Speaker 1>to take considerations like, uh, which kind of motherboard are

0:24:13.440 --> 0:24:16.840
<v Speaker 1>you using? Because only certain motherboards will support certain processors

0:24:16.840 --> 0:24:20.399
<v Speaker 1>but not other processors. So yeah, you've got limitations on

0:24:20.400 --> 0:24:23.000
<v Speaker 1>on you know, It's not like even building a PC

0:24:23.480 --> 0:24:27.280
<v Speaker 1>from scratch is not totally open because some components are

0:24:27.280 --> 0:24:31.680
<v Speaker 1>going to limit which other components you can actually put

0:24:31.720 --> 0:24:34.720
<v Speaker 1>into your machine. In other words, not everything is compatible

0:24:34.760 --> 0:24:38.240
<v Speaker 1>with everything else, which is uh for for people who

0:24:38.240 --> 0:24:43.200
<v Speaker 1>are interested in dabbling with Lenox. That can be frustrating because, um,

0:24:43.240 --> 0:24:46.840
<v Speaker 1>the drivers come around some some component manufacturers will write

0:24:46.880 --> 0:24:50.919
<v Speaker 1>a driver for Lenox for their card or or device,

0:24:51.160 --> 0:24:53.200
<v Speaker 1>but not all of them will, and so it relies

0:24:53.240 --> 0:24:55.679
<v Speaker 1>on the community to put one in there. And for

0:24:55.720 --> 0:24:57.480
<v Speaker 1>people who go, you know what, I really want to

0:24:57.520 --> 0:25:01.159
<v Speaker 1>try one to or you know Lenox meant or you know,

0:25:01.640 --> 0:25:04.320
<v Speaker 1>any of the others, and I want to try this out.

0:25:04.320 --> 0:25:05.919
<v Speaker 1>So they put it the disk in there, they reboot

0:25:05.920 --> 0:25:07.600
<v Speaker 1>their machines, and they'll find out that parts of their

0:25:07.640 --> 0:25:13.200
<v Speaker 1>system don't don't quite work. Yeah, and the more the

0:25:13.240 --> 0:25:15.440
<v Speaker 1>more frustrating for people who are just playing around. Yeah,

0:25:15.520 --> 0:25:18.919
<v Speaker 1>the more obscure the elements are inside your machine, the

0:25:19.160 --> 0:25:21.600
<v Speaker 1>less likely you're gonna find support just off the top

0:25:21.640 --> 0:25:23.639
<v Speaker 1>of the bat. I mean, if it's something that's a

0:25:23.720 --> 0:25:26.359
<v Speaker 1>really popular component, then you can it's a pretty safe

0:25:26.359 --> 0:25:28.600
<v Speaker 1>bet that someone out there has created a driver for

0:25:28.640 --> 0:25:31.639
<v Speaker 1>it for an open source operating system, just because you

0:25:31.680 --> 0:25:33.280
<v Speaker 1>know law of averages. You've got a lot of people

0:25:33.280 --> 0:25:35.960
<v Speaker 1>who are using the same kind of hardware, then there's

0:25:35.960 --> 0:25:38.159
<v Speaker 1>a good chance someone has designed something so that that

0:25:38.240 --> 0:25:41.840
<v Speaker 1>hardware will work properly with an open source operating system.

0:25:42.080 --> 0:25:45.040
<v Speaker 1>But if you've got, you know, some cheap sound card

0:25:45.160 --> 0:25:48.159
<v Speaker 1>that you found that it's made by someone that hardly

0:25:48.160 --> 0:25:50.960
<v Speaker 1>anyone knows about, it may not have the support there

0:25:51.680 --> 0:25:54.040
<v Speaker 1>in an open source operating system. But then you know,

0:25:54.080 --> 0:25:56.040
<v Speaker 1>the same thing is true with if you if you

0:25:56.480 --> 0:26:00.359
<v Speaker 1>upgrade a Windows based PC and you go to the

0:26:00.400 --> 0:26:03.520
<v Speaker 1>newest form of Windows, often you will find that one

0:26:03.520 --> 0:26:07.720
<v Speaker 1>of the big problems is that you'll lose um support

0:26:07.760 --> 0:26:11.920
<v Speaker 1>for certain kinds of peripherals. The drivers will not update

0:26:12.040 --> 0:26:14.679
<v Speaker 1>or they aren't compatible with the new operating system, and

0:26:14.760 --> 0:26:18.760
<v Speaker 1>sometimes they gets patched, or sometimes the device manufacturers will

0:26:18.760 --> 0:26:21.880
<v Speaker 1>release a new driver that works specifically with a new

0:26:21.920 --> 0:26:24.440
<v Speaker 1>operating system. But you can get stuck that way too,

0:26:24.480 --> 0:26:27.120
<v Speaker 1>so it's not like it's only with open source. In fact,

0:26:27.760 --> 0:26:29.520
<v Speaker 1>that was one of the big problems that people were

0:26:29.560 --> 0:26:32.840
<v Speaker 1>reporting with mac Os ten Lion, was that you know,

0:26:33.000 --> 0:26:35.679
<v Speaker 1>if you upgraded that which is a closed system, you

0:26:35.720 --> 0:26:39.600
<v Speaker 1>know what you're talking about a known quantity with Apple hardware.

0:26:40.680 --> 0:26:43.679
<v Speaker 1>But if you upgraded, there were certain peripherals that they

0:26:44.160 --> 0:26:47.359
<v Speaker 1>didn't have driver support anymore, and you know, or certain

0:26:47.400 --> 0:26:49.639
<v Speaker 1>software that had no no longer had support, and it

0:26:49.680 --> 0:26:51.760
<v Speaker 1>was software that was designed to run on the Mac

0:26:51.760 --> 0:26:54.960
<v Speaker 1>operating system and yet could not run this newest version

0:26:55.000 --> 0:26:58.080
<v Speaker 1>of the OS. UH. So it's not like it's a

0:26:58.119 --> 0:27:01.080
<v Speaker 1>problem that's unique to open source. It can also happen

0:27:01.200 --> 0:27:04.320
<v Speaker 1>in a closed system. UM. You know, the people who

0:27:04.359 --> 0:27:07.000
<v Speaker 1>create closed systems would probably argue what happens less frequently,

0:27:07.240 --> 0:27:09.160
<v Speaker 1>or that you might not have to wait as long.

0:27:09.359 --> 0:27:13.359
<v Speaker 1>But that's you know, kind of splitting hairs. Yeah, that's um.

0:27:13.400 --> 0:27:16.359
<v Speaker 1>That's another thing too for for operating systems that are

0:27:17.280 --> 0:27:21.280
<v Speaker 1>designed by the community. UM, there's you know, it may

0:27:21.280 --> 0:27:23.840
<v Speaker 1>be difficult to find a particular driver or piece of

0:27:23.880 --> 0:27:27.200
<v Speaker 1>software simply because somebody may not necessarily be working on it.

0:27:27.720 --> 0:27:30.440
<v Speaker 1>Depending on if there are vulnerabilities in the operating system

0:27:30.440 --> 0:27:32.840
<v Speaker 1>the UH generally something like that is going to draw

0:27:32.840 --> 0:27:35.360
<v Speaker 1>the attention of the community and will be fixed more quickly.

0:27:35.680 --> 0:27:37.680
<v Speaker 1>Apple gets criticized from time to time when they find

0:27:37.760 --> 0:27:40.720
<v Speaker 1>vulnerabilities in the operating system that could open the machine

0:27:40.800 --> 0:27:45.679
<v Speaker 1>up to UH uh possible attack. UM you know, for

0:27:45.920 --> 0:27:48.399
<v Speaker 1>not acting on it as quickly as Microsoft does with

0:27:48.440 --> 0:27:51.720
<v Speaker 1>its patches. UM. You know. So there's there's a trade

0:27:51.720 --> 0:27:55.800
<v Speaker 1>off there, UM, but there is I think there is

0:27:55.840 --> 0:27:58.440
<v Speaker 1>some benefit in a way of being that more hybrid

0:27:58.480 --> 0:28:03.000
<v Speaker 1>system because um, you know, that attracts the most users.

0:28:03.000 --> 0:28:06.560
<v Speaker 1>I want some flexibility, but I want most mostly I

0:28:06.600 --> 0:28:09.200
<v Speaker 1>want it to work. UM. So you get that sort

0:28:09.240 --> 0:28:12.479
<v Speaker 1>of combo uh system. And that's really sort of what

0:28:12.520 --> 0:28:14.800
<v Speaker 1>Android is really when you get down to it. Because

0:28:15.160 --> 0:28:20.840
<v Speaker 1>Android works on a multitude of different phones, whereas iOS.

0:28:21.119 --> 0:28:26.280
<v Speaker 1>Apple's iOS system works on Apple branded phones and those

0:28:26.359 --> 0:28:29.880
<v Speaker 1>only UM and some of the others due to the

0:28:29.880 --> 0:28:32.080
<v Speaker 1>the web os worked on the on the Palm phones,

0:28:32.600 --> 0:28:35.080
<v Speaker 1>UM you know, those are those are closed systems. UM.

0:28:35.240 --> 0:28:37.720
<v Speaker 1>Windows works on a on a variety of different phones.

0:28:37.760 --> 0:28:40.600
<v Speaker 1>But the problem is for developers, and they find this

0:28:40.800 --> 0:28:44.960
<v Speaker 1>with a variety of systems too, that um uh closed

0:28:44.960 --> 0:28:47.600
<v Speaker 1>system is an easier target for them to hit. UM.

0:28:47.720 --> 0:28:51.920
<v Speaker 1>One of the complaints I've heard from Android developers is that, uh,

0:28:52.120 --> 0:28:55.080
<v Speaker 1>they have difficulty writing software that will work with all

0:28:55.120 --> 0:28:58.240
<v Speaker 1>the different versions of the operating system they're out there,

0:28:58.240 --> 0:29:00.520
<v Speaker 1>and all all these different phones with all the different

0:29:00.840 --> 0:29:04.480
<v Speaker 1>hardware components, the thing being a part of the problem

0:29:04.520 --> 0:29:06.800
<v Speaker 1>being the carriers, because they're not the ones not pushing

0:29:06.800 --> 0:29:09.480
<v Speaker 1>out the operating system updates for the different phones. Some

0:29:09.560 --> 0:29:11.800
<v Speaker 1>of the older updates are just lingering on. I'm not

0:29:12.000 --> 0:29:15.640
<v Speaker 1>looking at you people who won't update my phone months

0:29:15.720 --> 0:29:20.440
<v Speaker 1>after Jonathan's gotten his anyway, um anyhow, Yes, I'm beating

0:29:20.480 --> 0:29:22.400
<v Speaker 1>the desk of my can because I'm angry with them.

0:29:22.520 --> 0:29:23.960
<v Speaker 1>But yeah, I mean that's a it's a problem for

0:29:24.000 --> 0:29:26.440
<v Speaker 1>developers a closed system. Hey, you know you have a

0:29:27.360 --> 0:29:31.320
<v Speaker 1>specific range of components. You know what kind of processor

0:29:31.400 --> 0:29:32.920
<v Speaker 1>in general is going to be in there. You have

0:29:32.920 --> 0:29:35.920
<v Speaker 1>a pretty good idea what the operating system entails. You know,

0:29:36.000 --> 0:29:37.920
<v Speaker 1>it's it's an easy target to hit. But the problem

0:29:38.080 --> 0:29:40.840
<v Speaker 1>with in the Mac cases, fewer people are using it,

0:29:41.160 --> 0:29:44.320
<v Speaker 1>so it's less it's a less desirable target hit because

0:29:44.320 --> 0:29:46.880
<v Speaker 1>there are fewer dollars to be made by writing software

0:29:46.920 --> 0:29:49.160
<v Speaker 1>for it. Trade off. Getting back to the idea of

0:29:49.200 --> 0:29:53.680
<v Speaker 1>the clothes versus open and operate system updates, uh so,

0:29:53.760 --> 0:29:56.200
<v Speaker 1>let's let's go ahead and we'll talk about Apple versus Google,

0:29:56.240 --> 0:29:58.880
<v Speaker 1>because that's that's pretty easy. And even then again, Apple

0:29:58.960 --> 0:30:01.360
<v Speaker 1>is not totally a close stem and Google. Google is

0:30:01.360 --> 0:30:05.080
<v Speaker 1>certainly not totally an open system. But it's a different approach, right,

0:30:05.160 --> 0:30:07.920
<v Speaker 1>Like you were saying, Uh, the iOS is only going

0:30:07.960 --> 0:30:10.640
<v Speaker 1>to appear on iPhones, You're not going to find that

0:30:10.680 --> 0:30:14.040
<v Speaker 1>another hardware. Um, it's because the iPhone was designed to

0:30:14.080 --> 0:30:15.840
<v Speaker 1>do it. That That's the way Apple once it done,

0:30:15.880 --> 0:30:19.840
<v Speaker 1>it's and that's how it's intended. So yeah, sticking with

0:30:19.880 --> 0:30:23.680
<v Speaker 1>phones because that makes it it makes illustration, makes illustration.

0:30:24.280 --> 0:30:28.480
<v Speaker 1>Uh So then on the Android side, Android can theoretically

0:30:28.520 --> 0:30:31.520
<v Speaker 1>be added to Like a manufacturer can choose to partner

0:30:31.560 --> 0:30:33.920
<v Speaker 1>with Google and create an Android phone. It's free, it's

0:30:33.960 --> 0:30:36.240
<v Speaker 1>pretty system is free. They can they can just build.

0:30:36.280 --> 0:30:37.760
<v Speaker 1>All you have to do is build hardware that is

0:30:37.760 --> 0:30:41.200
<v Speaker 1>capable of supporting Android, and then they are allowed to

0:30:41.400 --> 0:30:44.400
<v Speaker 1>have Android as the operating system for that smartphone. So

0:30:44.480 --> 0:30:47.760
<v Speaker 1>two different approaches. Um. Now with Apple, when there's an

0:30:47.760 --> 0:30:50.920
<v Speaker 1>OS update for iOS, Apple can push that out to

0:30:51.000 --> 0:30:54.400
<v Speaker 1>all the different devices that can still support that iOS.

0:30:54.440 --> 0:30:56.000
<v Speaker 1>But there's still going to be some that get left

0:30:56.040 --> 0:31:00.720
<v Speaker 1>behind eventually, just because the physical limitations of hardware will

0:31:00.720 --> 0:31:02.600
<v Speaker 1>be reached, you won't be able to go beyond this.

0:31:02.800 --> 0:31:05.680
<v Speaker 1>So if you have a first generation iPhone, it's only

0:31:05.680 --> 0:31:07.520
<v Speaker 1>going to run iOS up to a certain point, and

0:31:07.560 --> 0:31:09.600
<v Speaker 1>after that you're never gonna get an update again, because

0:31:09.800 --> 0:31:12.160
<v Speaker 1>you've reached the capacity of what that hardware is capable

0:31:12.200 --> 0:31:18.440
<v Speaker 1>of achieving without having a completely unsatisfying experience using that iPhone. Well,

0:31:18.480 --> 0:31:21.840
<v Speaker 1>they could just never make a newer one, except then

0:31:21.960 --> 0:31:24.400
<v Speaker 1>everyone would have what they were going to buy and

0:31:24.440 --> 0:31:27.120
<v Speaker 1>there wouldn't be any reason for them upgrade. So anyway,

0:31:27.240 --> 0:31:32.160
<v Speaker 1>Uh but yeah, But but if you have a fairly

0:31:32.200 --> 0:31:36.280
<v Speaker 1>recent like usually it's within for the last three generations,

0:31:36.560 --> 0:31:38.680
<v Speaker 1>the latest one, the one right before that, and maybe

0:31:38.720 --> 0:31:41.560
<v Speaker 1>the one before that, you typically are able to get

0:31:41.600 --> 0:31:45.840
<v Speaker 1>the latest um software upgrade. You might eventually get left behind,

0:31:45.920 --> 0:31:48.760
<v Speaker 1>like the three GS is probably getting pretty close to

0:31:48.800 --> 0:31:52.520
<v Speaker 1>its upper limits right now. But uh, you know, meanwhile,

0:31:52.520 --> 0:31:54.640
<v Speaker 1>when you go over to the Android side, you have

0:31:54.720 --> 0:31:57.920
<v Speaker 1>all these different carriers and they're all having they all

0:31:57.960 --> 0:32:01.920
<v Speaker 1>have handsets with different capabilities, and uh, you know, some

0:32:02.040 --> 0:32:04.400
<v Speaker 1>of those handsets might be able to run the latest

0:32:04.480 --> 0:32:06.840
<v Speaker 1>version of Android and some of them might not, you know,

0:32:07.080 --> 0:32:09.120
<v Speaker 1>or if they were to run the latest version of Android,

0:32:09.320 --> 0:32:11.719
<v Speaker 1>the handset might get really hot and the battery might

0:32:11.800 --> 0:32:15.640
<v Speaker 1>drain really quickly, so you would have a very unhappy

0:32:15.680 --> 0:32:17.920
<v Speaker 1>experience u seeing it, even if you had the lace version.

0:32:17.920 --> 0:32:19.360
<v Speaker 1>You're like, well, I've got the lace version, but my

0:32:19.360 --> 0:32:22.760
<v Speaker 1>phone lasts for two hours, then it's dead, and at

0:32:22.800 --> 0:32:24.200
<v Speaker 1>the whole time it feels like it's gonna set my

0:32:24.240 --> 0:32:27.120
<v Speaker 1>pants on fire. Um, make all the excuses you want,

0:32:27.120 --> 0:32:28.720
<v Speaker 1>they still haven't pushed it out to my phone. Okay,

0:32:28.760 --> 0:32:31.920
<v Speaker 1>Well for some people, like Chris setting your pants on fire,

0:32:31.960 --> 0:32:35.960
<v Speaker 1>apparently it's a feature, not a bug. Um, but what

0:32:36.120 --> 0:32:39.960
<v Speaker 1>kills there? You go, Okay, well we've all learned something

0:32:40.040 --> 0:32:44.360
<v Speaker 1>new about christa. Um. So yeah, the the that is

0:32:44.400 --> 0:32:46.880
<v Speaker 1>that is one of the downsides. Now again, like Chris

0:32:46.880 --> 0:32:48.800
<v Speaker 1>was saying, you've got a lot more choice with the

0:32:48.840 --> 0:32:52.200
<v Speaker 1>open system. So if you want a phone that has

0:32:52.240 --> 0:32:56.160
<v Speaker 1>a certain processor in it or has a certain kind

0:32:56.200 --> 0:32:57.960
<v Speaker 1>of camera in it, you've got a lot more choice

0:32:57.960 --> 0:32:59.960
<v Speaker 1>than you would if you are on the other side.

0:33:00.080 --> 0:33:02.360
<v Speaker 1>Closestem You've got you know, with the closestem you essentially

0:33:02.360 --> 0:33:05.200
<v Speaker 1>have the latest version of it, and usually the one

0:33:05.280 --> 0:33:10.040
<v Speaker 1>directly before it, and maybe the one before that. And

0:33:10.240 --> 0:33:12.560
<v Speaker 1>uh yeah, I mean you have all the people that

0:33:12.600 --> 0:33:15.640
<v Speaker 1>have adopted and and Android numbers that we've that have

0:33:15.680 --> 0:33:18.320
<v Speaker 1>been coming out as of about the time that we're

0:33:18.320 --> 0:33:23.440
<v Speaker 1>recording this in very very late. Um, Android numbers are

0:33:23.600 --> 0:33:29.440
<v Speaker 1>taking off. I mean they're far outstripping apples iPhone new

0:33:29.480 --> 0:33:32.440
<v Speaker 1>customers even as fast as the iPhone sales. And I

0:33:32.440 --> 0:33:35.320
<v Speaker 1>think there are two big reasons. But I'm sorry, go ahead,

0:33:35.520 --> 0:33:38.800
<v Speaker 1>Well I was gonna say, is that, well, go ahead, Well,

0:33:38.840 --> 0:33:41.080
<v Speaker 1>the two big reasons I see is one, there's way

0:33:41.080 --> 0:33:43.800
<v Speaker 1>more choice. Yeah, right, so you've got like all these

0:33:43.800 --> 0:33:47.600
<v Speaker 1>different options. And two there are a lot more lower

0:33:47.760 --> 0:33:51.000
<v Speaker 1>cost options out there, Like with the iPhone you've got

0:33:51.120 --> 0:33:53.320
<v Speaker 1>you know, you've got the latest version, which is going

0:33:53.360 --> 0:33:55.720
<v Speaker 1>to be pretty expensive, and then the older version, which

0:33:55.760 --> 0:33:58.600
<v Speaker 1>is slightly less expensive. But you're not gonna find any

0:33:58.760 --> 0:34:01.240
<v Speaker 1>like bargain bin types off you're not gonna come across.

0:34:01.800 --> 0:34:03.800
<v Speaker 1>I don't know if anyone who's ever offered like a

0:34:03.840 --> 0:34:07.320
<v Speaker 1>free iPhone with a two year contract, but there have

0:34:07.480 --> 0:34:12.080
<v Speaker 1>been Android phones, the older ones. Yeah, um, actually low

0:34:12.120 --> 0:34:14.680
<v Speaker 1>cost I guess maybe not free. Um. Well, that the

0:34:14.680 --> 0:34:18.160
<v Speaker 1>thing is that now that that Android is becoming the

0:34:18.200 --> 0:34:22.920
<v Speaker 1>big target for developers in its class. Um, you know,

0:34:23.040 --> 0:34:24.879
<v Speaker 1>there are all kinds of apps that are out there

0:34:24.880 --> 0:34:28.160
<v Speaker 1>and available for it. Um. They're also all kinds of

0:34:28.200 --> 0:34:30.520
<v Speaker 1>app stores that you can use to You don't have

0:34:30.560 --> 0:34:33.160
<v Speaker 1>to go through just the Google Marketplace if you don't

0:34:33.200 --> 0:34:34.960
<v Speaker 1>want to, although you do have to change a setting

0:34:34.960 --> 0:34:36.719
<v Speaker 1>on your phone in order to be able to access them.

0:34:36.840 --> 0:34:40.760
<v Speaker 1>That that's correct. Um. The thing is, though, the bigger

0:34:40.800 --> 0:34:44.040
<v Speaker 1>the target, the more people the developers of all kinds,

0:34:44.280 --> 0:34:48.759
<v Speaker 1>including malware developers, It attracts that um not you know,

0:34:48.800 --> 0:34:50.480
<v Speaker 1>this has nothing to do with the quality of the

0:34:50.520 --> 0:34:54.360
<v Speaker 1>operating system or the security measures inherent in the operating system.

0:34:54.440 --> 0:34:57.680
<v Speaker 1>It's just a bigger target and therefore it's a um,

0:34:57.719 --> 0:35:00.680
<v Speaker 1>a juicier place to strike for the person and even

0:35:00.719 --> 0:35:03.200
<v Speaker 1>the legit people too. I mean, hey, I can I

0:35:03.200 --> 0:35:04.839
<v Speaker 1>can sell my app in this app store and reach

0:35:04.880 --> 0:35:07.319
<v Speaker 1>five thousand people. I can sell my app in this

0:35:07.440 --> 0:35:12.239
<v Speaker 1>app store and reach five million people itself far more

0:35:12.360 --> 0:35:15.600
<v Speaker 1>over here. The thing is, though, and also UH and

0:35:15.920 --> 0:35:18.080
<v Speaker 1>I would argue that this is the case for any

0:35:18.360 --> 0:35:22.799
<v Speaker 1>tech that has reached that kind of UH adoption rate,

0:35:23.080 --> 0:35:25.680
<v Speaker 1>that it also inspires a lot of junk. I mean,

0:35:25.719 --> 0:35:30.920
<v Speaker 1>we saw it with Attari when opened up the platform

0:35:31.000 --> 0:35:32.799
<v Speaker 1>and allowed other people to write software for it. They

0:35:32.840 --> 0:35:34.760
<v Speaker 1>were all kind of that's what caused the video game crept,

0:35:34.760 --> 0:35:36.719
<v Speaker 1>which is where I was getting into the whole curation

0:35:36.800 --> 0:35:40.040
<v Speaker 1>argument in the debate. If you are using an open system,

0:35:40.080 --> 0:35:42.640
<v Speaker 1>then you're gonna have a lot more choice with when

0:35:42.640 --> 0:35:44.799
<v Speaker 1>it comes to not just you know, options, but but

0:35:44.880 --> 0:35:47.960
<v Speaker 1>apps that you can run. But that also means that

0:35:48.000 --> 0:35:50.400
<v Speaker 1>with the good comes a lot of bad, not that

0:35:50.440 --> 0:35:53.040
<v Speaker 1>the closed systems necessarily you know, it's not that Apple

0:35:53.200 --> 0:35:55.719
<v Speaker 1>is free of bad apps. There are plenty of bad

0:35:55.760 --> 0:35:58.680
<v Speaker 1>apps in the Apple App Store, So I don't mean

0:35:58.719 --> 0:36:01.520
<v Speaker 1>to say that, but no, no, it because that there's

0:36:01.640 --> 0:36:05.120
<v Speaker 1>not necessarily like there's no qualifier to create an app

0:36:05.280 --> 0:36:07.839
<v Speaker 1>for Google, and you can submit to the Google Marketplace,

0:36:07.960 --> 0:36:09.600
<v Speaker 1>or you can even host it somewhere else if you

0:36:09.640 --> 0:36:12.160
<v Speaker 1>want to and not even go through the the process

0:36:12.160 --> 0:36:14.680
<v Speaker 1>of submitting it to Google market and people can still

0:36:14.719 --> 0:36:17.680
<v Speaker 1>find it and download it to their shorts or tablets,

0:36:18.040 --> 0:36:22.360
<v Speaker 1>you know, mobile devices. Um, but yeah, that curation becomes

0:36:22.360 --> 0:36:25.400
<v Speaker 1>a problem because then if you've got that much choice

0:36:25.560 --> 0:36:28.239
<v Speaker 1>and there's no like, there's no one out there who's

0:36:28.280 --> 0:36:30.120
<v Speaker 1>kind of curating this for you, it all falls on

0:36:30.160 --> 0:36:33.600
<v Speaker 1>your shoulders. And uh, that can just get exhausting. I mean,

0:36:33.640 --> 0:36:38.160
<v Speaker 1>I mean looking through just the list of applications, uh,

0:36:38.400 --> 0:36:41.520
<v Speaker 1>just you know, going page by page. You sit there

0:36:41.560 --> 0:36:43.000
<v Speaker 1>and think, well, I could look at the ones that

0:36:43.040 --> 0:36:45.200
<v Speaker 1>are the most popular and use that as kind of

0:36:45.200 --> 0:36:48.040
<v Speaker 1>a guide of curation. But it may very well be

0:36:48.120 --> 0:36:50.919
<v Speaker 1>that the app that really meets my needs is eight

0:36:50.960 --> 0:36:54.000
<v Speaker 1>pages down. And you know that gets kind of frustrating

0:36:54.000 --> 0:36:58.640
<v Speaker 1>after a while. Um. Yeah, And it's it's It's funny

0:36:58.640 --> 0:37:00.799
<v Speaker 1>too because one of the things that to some people

0:37:00.960 --> 0:37:04.440
<v Speaker 1>have said against Lenox. I mean, I've I've used a

0:37:04.440 --> 0:37:06.600
<v Speaker 1>couple of different flavors of Linux. I really like the

0:37:06.600 --> 0:37:10.640
<v Speaker 1>operating system. I Um, I don't like that there are

0:37:10.719 --> 0:37:14.160
<v Speaker 1>fewer people writing software for it, but I still I

0:37:14.239 --> 0:37:16.200
<v Speaker 1>love the idea, and I like the operating system an

0:37:16.200 --> 0:37:18.880
<v Speaker 1>awful lot um and the more I play with it,

0:37:18.920 --> 0:37:21.680
<v Speaker 1>the more I've enjoyed using it. But the thing is,

0:37:21.840 --> 0:37:24.360
<v Speaker 1>some people have said that the fact that it's free

0:37:24.760 --> 0:37:28.440
<v Speaker 1>is a problem because it sort of encourages people to

0:37:28.440 --> 0:37:30.880
<v Speaker 1>think that it's not actually worth anything. Right, it should

0:37:30.920 --> 0:37:33.759
<v Speaker 1>have money. It gives it gives a It gives some

0:37:33.840 --> 0:37:36.520
<v Speaker 1>people the feeling that, well, if it's free, it must

0:37:36.520 --> 0:37:40.080
<v Speaker 1>not be very good. Because yeah, because you know, if

0:37:40.120 --> 0:37:41.839
<v Speaker 1>it were good, I'd have to pay money for it,

0:37:42.160 --> 0:37:44.239
<v Speaker 1>which is untrue. Which is funny because if you had

0:37:44.239 --> 0:37:45.560
<v Speaker 1>to pay money for it, people will be trying to

0:37:45.560 --> 0:37:47.359
<v Speaker 1>find a way around having to pay money for it.

0:37:48.680 --> 0:37:51.200
<v Speaker 1>Now you're you're making my brain hurt. Here's the crazy Okay,

0:37:51.440 --> 0:37:56.520
<v Speaker 1>stereotypical computer user, stereotypical Internet savvy computer user. All right,

0:37:56.960 --> 0:37:59.400
<v Speaker 1>if something doesn't cost money, then it's not worth having.

0:37:59.440 --> 0:38:01.640
<v Speaker 1>If it's If something costs money, it's worth having, but

0:38:01.840 --> 0:38:05.480
<v Speaker 1>you shouldn't pay for it. Yeah, like you are a

0:38:05.520 --> 0:38:08.640
<v Speaker 1>messed up person. Typical computer user. You need to re

0:38:08.760 --> 0:38:11.880
<v Speaker 1>examine your priorities. Yeah, yeah, well I think And by

0:38:11.920 --> 0:38:15.640
<v Speaker 1>the way, I was once like you, well, I think yeah,

0:38:16.000 --> 0:38:18.319
<v Speaker 1>ideally to me anyway, And I think it does come

0:38:18.320 --> 0:38:22.160
<v Speaker 1>down to personal choice. I think ideally, Um, I do

0:38:22.239 --> 0:38:25.000
<v Speaker 1>prefer a hybrid. I do want I don't want to

0:38:25.000 --> 0:38:26.600
<v Speaker 1>have to. I like the idea of being able to

0:38:26.640 --> 0:38:29.480
<v Speaker 1>hack into things and being able to make choices and

0:38:29.800 --> 0:38:31.960
<v Speaker 1>fool around with stuff, but I want it at the end,

0:38:32.000 --> 0:38:33.920
<v Speaker 1>I wanted to be able to work. I don't want

0:38:33.960 --> 0:38:37.480
<v Speaker 1>to spend all my time hacking with it. I was like, Okay,

0:38:37.480 --> 0:38:39.359
<v Speaker 1>I'm done now. I want to close the hood and

0:38:39.440 --> 0:38:41.560
<v Speaker 1>play on it, and I can't. Kind it broke. And

0:38:41.640 --> 0:38:45.480
<v Speaker 1>we both own devices that run Android, and we both

0:38:45.520 --> 0:38:49.080
<v Speaker 1>own devices that run Apple operating systems, so we both

0:38:49.120 --> 0:38:51.600
<v Speaker 1>own Windows computers. Yeah, so I mean, it's it's not

0:38:51.680 --> 0:38:54.440
<v Speaker 1>like it's not like we're saying this as fanboys of

0:38:54.480 --> 0:38:56.360
<v Speaker 1>one system versus another, even though we played that in

0:38:56.400 --> 0:38:59.640
<v Speaker 1>the debate. Um, I mean I I own an Android phone.

0:38:59.680 --> 0:39:02.239
<v Speaker 1>My wife has an iPhone, and we are both very

0:39:02.239 --> 0:39:05.280
<v Speaker 1>happy with our devices for very different reasons. It meets

0:39:05.280 --> 0:39:08.200
<v Speaker 1>exactly what she wants in a smartphone, but for me

0:39:08.360 --> 0:39:11.080
<v Speaker 1>it would probably be it's a beautiful device and it

0:39:11.120 --> 0:39:13.440
<v Speaker 1>has a great interface, but it probably would be more

0:39:13.480 --> 0:39:17.400
<v Speaker 1>frustrating to me than my Android phone, which meets my needs.

0:39:17.719 --> 0:39:20.479
<v Speaker 1>Whereas the Android phone, I know for a fact, would

0:39:20.800 --> 0:39:23.040
<v Speaker 1>annoy and irritate my wife because she used to have

0:39:23.160 --> 0:39:26.640
<v Speaker 1>one and she doesn't anymore and she never will again

0:39:27.480 --> 0:39:30.239
<v Speaker 1>because she's very happy with her iPhone. So again, it's

0:39:30.320 --> 0:39:35.320
<v Speaker 1>too just two different people and two different uh preferences

0:39:35.360 --> 0:39:37.640
<v Speaker 1>for the operating system. It's it's not that one is

0:39:37.680 --> 0:39:40.040
<v Speaker 1>inherently better or worse than the other. It's just that

0:39:40.120 --> 0:39:42.279
<v Speaker 1>it suits mine you know, one suits my needs and

0:39:42.280 --> 0:39:45.000
<v Speaker 1>one suits sers. Yeah. Yeah, it's it's it all comes

0:39:45.040 --> 0:39:47.920
<v Speaker 1>down to the stuff that matters to the individual. Um.

0:39:48.000 --> 0:39:51.120
<v Speaker 1>And in the end, I think it's it's uh, most

0:39:51.120 --> 0:39:54.160
<v Speaker 1>people sort of go for the mix of things. Well,

0:39:54.200 --> 0:39:56.200
<v Speaker 1>I want this part to just work, but the rest

0:39:56.200 --> 0:39:57.759
<v Speaker 1>of it I want to be able to fool around with.

0:39:57.800 --> 0:40:00.600
<v Speaker 1>And I think that's another one of the appeals of Windows.

0:40:00.440 --> 0:40:04.800
<v Speaker 1>It's it's sort of that middle ground. Um. You know, like,

0:40:04.800 --> 0:40:06.880
<v Speaker 1>like I said, we all own the various devices, and

0:40:07.160 --> 0:40:10.040
<v Speaker 1>we all see the value and and the limitations of

0:40:10.080 --> 0:40:12.719
<v Speaker 1>each system. Um. I think I think it really you know,

0:40:13.080 --> 0:40:16.759
<v Speaker 1>if if, however you're going about it, if you're dedicated

0:40:16.800 --> 0:40:19.200
<v Speaker 1>to making the best possible product or service that you

0:40:19.400 --> 0:40:21.880
<v Speaker 1>that you possibly can, whether it's as a member of

0:40:21.920 --> 0:40:25.319
<v Speaker 1>the community of the open source world, or if it's

0:40:25.480 --> 0:40:28.799
<v Speaker 1>you know, a closed system, I think that is what's

0:40:28.840 --> 0:40:32.239
<v Speaker 1>most important to me. The whole open versus closed is

0:40:32.400 --> 0:40:35.560
<v Speaker 1>just a general philosophy that guides your your development process.

0:40:35.640 --> 0:40:38.839
<v Speaker 1>It's not something that you know, I should definitely be

0:40:39.320 --> 0:40:44.319
<v Speaker 1>you know, uh endorsed or or or scorned. Well, it

0:40:44.360 --> 0:40:47.240
<v Speaker 1>frustrates me listening to people talk about it and seeing

0:40:47.239 --> 0:40:50.759
<v Speaker 1>comments online from people who are so devoted to one

0:40:50.800 --> 0:40:53.960
<v Speaker 1>side or the other that they will scream and call

0:40:54.080 --> 0:40:57.160
<v Speaker 1>names and use profanity to definite side and going. But

0:40:57.360 --> 0:40:59.560
<v Speaker 1>I mean, I see, I see arguments for both sides,

0:40:59.680 --> 0:41:01.840
<v Speaker 1>and yeah, I think there are valid points for both ye.

0:41:01.920 --> 0:41:03.840
<v Speaker 1>And it's it is a dangerous thing because once you

0:41:03.840 --> 0:41:05.879
<v Speaker 1>get once you become a fan of a certain way

0:41:05.880 --> 0:41:08.959
<v Speaker 1>of doing things, then it almost feels like if someone

0:41:09.080 --> 0:41:12.000
<v Speaker 1>else praises a different way of doing it, that it's

0:41:12.040 --> 0:41:15.520
<v Speaker 1>somehow an Yeah, it's an attack against what you like,

0:41:15.920 --> 0:41:19.480
<v Speaker 1>which isn't necessarily the case. It's yeah, no, it's definitely

0:41:19.480 --> 0:41:20.920
<v Speaker 1>not fair. But it does happen all the time. I

0:41:20.920 --> 0:41:22.920
<v Speaker 1>see it all the time where someone will praise one

0:41:22.960 --> 0:41:25.600
<v Speaker 1>system and someone else takes that as hey, you're saying

0:41:25.640 --> 0:41:28.200
<v Speaker 1>that the system I like sucks, And no, that's not

0:41:28.280 --> 0:41:31.120
<v Speaker 1>what I said. I just said that this system was

0:41:31.200 --> 0:41:34.359
<v Speaker 1>also good. I didn't even mention your system. Please don't

0:41:34.440 --> 0:41:38.279
<v Speaker 1>yell at me trolls. So if you want to know

0:41:38.320 --> 0:41:40.520
<v Speaker 1>more about that, listen to our podcast on how trolls

0:41:40.520 --> 0:41:47.799
<v Speaker 1>work East Jonathan Strickland in the operating system you like stinks? Right? Yeah, Okay, Well,

0:41:47.840 --> 0:41:51.759
<v Speaker 1>that that's a good summary. This was fun. I don't

0:41:51.760 --> 0:41:54.120
<v Speaker 1>know that will necessarily do any more debates, but this

0:41:54.239 --> 0:41:56.799
<v Speaker 1>was we just decided, like I said off the top

0:41:56.800 --> 0:41:59.480
<v Speaker 1>of the bat, yeah, maybe we'll do another one where

0:41:59.520 --> 0:42:02.239
<v Speaker 1>we'll do a very specific debate and how to pick

0:42:02.320 --> 0:42:06.879
<v Speaker 1>two different things that that clearly have a divider between them.

0:42:06.920 --> 0:42:08.719
<v Speaker 1>In fact, we get a third person in here. We

0:42:08.760 --> 0:42:13.759
<v Speaker 1>could do the Xbox versus PlayStation versus Nintendo throwdown, which

0:42:13.800 --> 0:42:18.760
<v Speaker 1>would be a blast. We have one person just crying

0:42:18.800 --> 0:42:21.920
<v Speaker 1>in the corner and say alright, so guys, if you

0:42:22.000 --> 0:42:25.400
<v Speaker 1>have any suggestions for future debates or other podcast let's know,

0:42:25.719 --> 0:42:27.800
<v Speaker 1>let's go on Facebook or Twitter. Are handled. There is

0:42:27.920 --> 0:42:30.239
<v Speaker 1>tech stuff hs W and Chris and I will talk

0:42:30.239 --> 0:42:35.240
<v Speaker 1>to you again really soon. This episode of tech Stuff

0:42:35.280 --> 0:42:37.759
<v Speaker 1>is brought to you by Hover dot com. However his

0:42:37.840 --> 0:42:41.400
<v Speaker 1>domain name registration and management. That's simple. Upgrade to a

0:42:41.480 --> 0:42:44.560
<v Speaker 1>premium domain and trade in your old clunkers. Visit hub

0:42:44.760 --> 0:42:51.840
<v Speaker 1>dot com. Slash tech Stuffs brought to you by the

0:42:51.840 --> 0:42:55.239
<v Speaker 1>reinvented two thousand twelve camera. It's ready, are you