Betting on Darwin
Doc: Why release the browser source now?
Marc: Today we're at an inflection point, a trigger point, when there's an alignment with the energy of growth. Linux is hot. The technologists have adopted it, and it's growing fast all through the open source community. This gives us confidence that we couldn't screw it up if we tried. And now we can't de-commit. This thing has been set in motion. Even if we do nothing, there's no stopping what's going to happen. It's going to be fun.
Doc: A few years back, somebody at Netscape called—maybe it was you—and said, without meaning insult, that the OS is “just a device driver.” Is Linux well suited to that role?
Marc: Yes. Linux is evolving naturally to do what an OS does best, while Windows is constantly adding non-OS functionalities as part of a vertical strategy to take over layer after layer above the OS. This looks a lot like what IBM did first and Apple did all over again on the IBM model. It has made Microsoft much more vulnerable to a grass-roots technology movement like Linux, and is one of the reasons Linux is the only non-Microsoft OS that's gaining market share. It's amazing that these companies make the same mistakes over and over again, but they do.
Doc: There is an irony here. One of the reasons why PCs rather than Macintoshes were established in companies, was that, although everybody agreed Macintoshes were better, the technologists would rather work with DOS because they could easily write DOS programs that addressed a specific problem. In the same way today, the technologists would rather work with Linux. What you said at SVLUG about customers using Macintoshes and PCs at work and Linux boxes at home isn't just a joke. There's something going on here.
Marc: Absolutely. Technologists are driving progress, and it's easier to drive with Linux than with anything else.
Doc: Tell me more about your role in the Linux movement.
Tom: What we want to do is give Linux critical mass so it hits a crossover point. There's a huge development community that's growing bigger every day. And it's an efficient one relying on massive peer review that you can't replicate inside the corporate world, although the two overlap a great deal. So we're betting on Darwin here—natural selection. All we're doing with Mozilla.org is helping create conditions that give evolution a hand.
Marc: It's the exact same thing I saw with the Net. Before it hit critical mass, the Internet had a million plus users. People were using it every day, and all of them were technologists. But the Net was also unapproachable and not understandable to people outside that community. They'd scratch their heads and wouldn't get the point. The crossover point came with e-mail and the Web—though I think e-mail was the bigger driver. Suddenly it became relevant to everybody. But first it had to reach a critical mass in the technologist community. Linux is there today, and it's ready to cross over. But it requires specific catalyzing events, just like the Internet did.
Doc: And releasing the Mozilla source may be just the event.
Doc: You say you are looking for Linux to obtain a scalability to support a lot of database transactions and large-scale information processing that Solaris, AIX and those other UNIX variants perform. It seems to me the kind of guys who hang around Linux are not the kind of guys who want to do that kind of programming. Is that true?
Tom: You mean put SMP (symmetric multi-processing) into the kernel?
Tom: All you need is a couple or a few people who can steer and many other people who say “Oh, that's an issue? I'll deal with it.” And competent programmers will be all over it.
Marc: Especially since this has already been done multiple times.
Tom: That's my point. This is not uncharted water. Companies have done it. They know where the problems are.
Doc: But it's uncharted water outside of companies, and Linux is sort of this extra-corporate thing. Does the Open Source community sit around caring about this sort of issue?
Tom: If you asked this question six or seven years ago, then you'd have a hard time finding a large and broad enough variety of people who have spent time making, for example, SMP kernels work. In 1998, that's no longer true. You can scoot up and down the street and find people who have done it. A lot of those guys go to the Linux Users Group meetings and are interested in getting SMP in the machine they've got at home. It's just not that remote of a science anymore. So I think your characterization is no longer valid. Marc, do you know Linus's position on this? He thinks it's time to do it, right?
Doc: So then it's done. It's going to happen.
Tom: That's right.
Doc: Would you dedicate any internal resources to making it happen?
Marc: Not currently. If there was something specific we could do to help, maybe. But I'm not suggesting Netscape should take more of a leadership role in determining the future of Linux. That seems to be working just fine. Of course, in any case where we can help, we'd be interested in figuring out how.
Doc: I'm trying to figure out how this larger community works. Some of these guys are working at this on their day jobs and some aren't.
Marc: Typically they have very relevant day jobs. At least one person in every technology company on the planet is in this community; so again, this is the same thing that happened with the Internet, and why it broke into the mainstream. It infiltrated itself into all these companies through resident technologists who were interested in it.
Doc Searls is Senior Editor of Linux Journal
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- The Secret Password Is...
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- New Products
3 hours 59 min ago
- Keeping track of IP address
5 hours 50 min ago
- Roll your own dynamic dns
11 hours 4 min ago
- Please correct the URL for Salt Stack's web site
14 hours 15 min ago
- Android is Linux -- why no better inter-operation
16 hours 30 min ago
- Connecting Android device to desktop Linux via USB
16 hours 59 min ago
- Find new cell phone and tablet pc
17 hours 57 min ago
19 hours 26 min ago
- Automatically updating Guest Additions
20 hours 34 min ago
- I like your topic on android
21 hours 21 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?