Linux for Suits - Picking New Fights
Sometime this year there will be more than three billion mobile phones in the world. To put that in perspective (relying on last month's LJ Index), compare that to 1.4 billion credit cards, 1.3 billion land lines, 1.1 billion Net connections, 800 million cars, 200 million computer games, 100 million PVRs and 85 million iPods.
Cell phones are networked computing devices. A growing percentage of them run on Linux. Yet the OpenMoko (openmoko.com) and Trolltech's Qtopia Greenphone (www.trolltech.com/products/qtopia/greenphone), both wide-open working prototypes, are rarities. They face an enormous uphill battle against silo'd alliances between cell service carriers and equipment makers, such as Nokia and Motorola.
Yet the world needs open phones. In fact, I'd hazard a prophesy that open phones are inevitable, because there will be far more money to be made because of open phones than will ever be made with closed ones (and closed services offered only by carriers). We're starting to see vertical cracks in the closed wall of mobile telephony in settings such as universities, where rogue companies like Rave Wireless (disclosure: I consult them) provide students with custom (based on open) phones that run on familiar networks (such as Cingular and T-Mobile), but that do far more than the closed phones sold at stores by those same networks. Users are even free to do their own programming, create and add their own features and services. With each crack of this kind in a vertical market, the chance improves that open phones will become the norm rather than the exception.
The protagonists here are Linux techies, but working a much larger world of possibilities. The problem, as ever, is less a matter of closed systems than of the mentality behind it.
Once markets start to open up, it will be easy to fill whole magazine issues with stories of clever hacks and deployment successes.
Desktop Linux has been approaching without ever arriving since the mid-1990s. Most Linux Journal readers are there already, of course. But they're wizards. The muggles are still on Windows and Mac boxes. What we've needed for the duration is one or more of the major hardware OEMs to wake up and smell the volume. Last year, Lenovo began selling Linux-loaded ThinkPads in a committed way, but not aggressively. Lenovo didn't push it. This year, Dell set out bait in the form of IdeaStorm, a site that had all the look of a “conversational” marketing ploy, but instead served as a hole in the Windows-only dike that has been holding the Linux desktop river outside of Dell's headquarters for the duration. That hole quickly widened to a river of its own, flooding through Dell's product development system. (See the IdeaStorm story in this issue's UpFront.)
I'd love to be a fly on the wall when Michael Dell tells Steve Ballmer that Dell will be selling Linux-branded laptops and desktops in a much more public way, because the company has no choice: the market demands it.
HP, Sony and the rest won't be far behind. As the volume grows, so will the portfolio of applications and the sum of expertise about Linux desktops and laptops.
This is a category that will explode very quickly. I'm willing to bet right now that in June 2008, Linux Journal will have an unavoidably personal focus to every issue—for the simple reason that there will be too much going on with desktops and laptops.
Or maybe not. We don't know yet. Lenovo, HP and Dell may continue quietly to fill orders for desktop Linux without ever marketing it aggressively. This won't go on forever, but the asymptote may still stay flat for another year, two or three.
Meanwhile, desktop and laptop Linux are still worth fighting for, just like we've been doing for the last decade or more.
I have a confession to make. Or a Make to confess. I love Make magazine. I wish we'd done something like that first. Kudos to Dale Daugherty and the O'Reilly folks for pulling that one off and doing a great job with it—also for not running too much Linux-type stuff in there.
When I started with Linux Journal in the late 1990s, we were basically a how-to magazine. To a large degree, we still are. Most of our readers are hands-on types in any case. Problem solvers. Most of our writers (myself excluded) are too.
So I'm wondering...now that Linux is (or can be) in nearly everything, what can we make or fix that's one or more layers up? What can we do with MythTV that's beyond a set-top box? Pluto is a cool (and Linux-based) whole-home automation, security, entertainment and telecom system. But, it's still a system. A deep and under-appreciated (and under-deployed) virtue of openness is modularity. You want to be able to mix and match different stuff from different makers, including (especially) yourself. We should be making Legos with Linux, not just embedding it in finished closed products that work only with themselves.
Here the fight is for the right and ability to build what you want, any way you want to build it. Although Make is oriented toward doing fun hacks on already-made stuff (turning a mouse into a robot or adding temperature control to a coffeemaker), we'd angle more toward making the modules, and the things-with-modules that allow anybody to build anything. Our protagonists would be the same DIY-ers we've had all along, but the problem would be Building Anything. Fun problem.
Years ago, I talked about how the software industry was turning into a construction industry—when architects, designers, builders and their specialties would all be independent of any one company's platform or development environment. Now we're almost there, but not quite. The fight here is to make Linux and its endless variety of “stacks” into the base materials with which people can put together using their own virtual Home Depots.
Doc Searls is Senior Editor of Linux Journal
|Designing Electronics with Linux||May 22, 2013|
|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|
- New Products
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Designing Electronics with Linux
- 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
- Nice article, thanks for the
8 hours 19 min ago
- I once had a better way I
14 hours 5 min ago
- Not only you I too assumed
14 hours 22 min ago
- another very interesting
16 hours 15 min ago
- Reply to comment | Linux Journal
18 hours 9 min ago
- Reply to comment | Linux Journal
1 day 1 hour ago
- Reply to comment | Linux Journal
1 day 1 hour ago
- Favorite (and easily brute-forced) pw's
1 day 3 hours ago
- Have you tried Boxen? It's a
1 day 9 hours ago
- seo services in india
1 day 13 hours 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?