Leaving the Land of the Giants
Today in the mail came our copies of Vanity Fair and the New Yorker, both Condé Nast publications. Both looked different and confusing. Instead of the usual cover art, there were collections of squares and rectangles that called to mind the tablet app Flipboard, which organizes "social" content in the form of picture-tiles one can flip through like one would a magazine. I have Flipboard, but its lack of an outline-like organizing structure, such as a directory or a table of contents, annoys me. I thought, This can't be real. This has to be an ad for something. Then I saw the small print: "A sample of the new New Yorker experience on the Windows 8 desktop." Oy vay. Microsoft and Condé Nast hit into a triple-play on that one, because it made me hate the OS while dreading at the same time having an "experience" like what it showed.
So far, I've met only one Windows user who likes Windows 8, and that's just for some deeply buried technical stuff. Everybody else either doesn't like it or hates it outright. The UI, reportedly nice on phones and tablets, is strange on anything with a keyboard and mouse or trackpad. The learning curve is more like a wall, and—well, nobody asked for all this new stuff. As for the new Surface tablet, it looks like the second coming (and going) of the Tablet PC (http://en.wikipedia.org/wiki/Microsoft_Tablet_PC). One version of the OS doesn't even run Microsoft's Office apps. Some game developers called the new OS and its Apple-like "store" for silo-ing apps a "catastrophe" (http://www.neowin.net/news/valve-co-founder-windows-8-is-a-catastrophe) and a "disaster" (http://www.neowin.net/news/blizzards-rob-pardo-windows-8-is-not-awesome-for-the-company).
On the mobile front, Microsoft teamed up with Nokia to bet the former mobile-phone giant's farm on Windows-based phones, which promptly tanked in the marketplace. Now farmland for both companies is shrinking like a puddle on a hot day.
In fact, Microsoft has some legacy advantages. It always has been far more open and supportive toward developers than Apple. Unlike Facebook and Google, its users are actually paying customers. And it has always been, at its heart, a personal computing company. That too should give it a kind of advantage over Facebook, Google, Twitter and everybody betting on "social" (read: advertising), "the cloud" and "big data"—all of which are corporate/enterprise plays.
Over the years, I've known and worked with a lot of good people inside Microsoft, all of whom have labored to open the company's technology, make it play better with others in the marketplace, and put some truly innovative technologies to work. The company's decision to default Do Not Track in the "on" position with the latest rev of Internet Explorer was astute, correct and perhaps even brave. It's the kind of thing that a clued-in company would do. I've also seen some excellent Microsoft research on user feelings and preferences in respect to lost on-line privacy. That should energize Microsoft around some fresh opportunities, but the company seems to lack adrenal glands. Opportunities are lost every day the company fails to win hearts and minds by standing behind users—its customers—in the fight against abuses of privacy.
Instead, Microsoft continues to fight Google straight-up with an Online Services Division that has lost $billions over recent years.
Amazon is strongest among The Economist's four giant squid, or thrones. It succeeds, Jeff Bezos says, "by starting with the customer and moving backwards". By 2009, Amazon already controlled more than a third of all e-commerce (http://www.pcmag.com/article2/0,2817,2345381,00.asp). Since then, I've heard numbers as high as 50%. Whatever the number, you can see the result by looking inside any UPS or Fedex delivery truck and eyeballing all the boxes labeled Amazon or Zappos (Amazon's shoe store).
While Apple, Google and Facebook all clearly have good engineers and solid technical infrastructure, Amazon tops them all by connecting its innards directly both to individuals and to techies among business customers. It is a rare example of a geek-driven company that also understands and loves to do business with everybody it can.
Amazon's only shortcoming is one it shares with the rest of retailing, as well as with its big-squid competitors: it runs a big data silo where customer data goes in, but not back out to individuals. For example, I would like to have a cooperative data-sharing relationship with Amazon, in which I tell it everything I own (or feel like telling it I own), so it doesn't bother trying to sell me what I already have but didn't buy from Amazon. I would like my personal API to be one it could program against, just as I (or my fourth party) can program using its APIs. This requires a respect on Amazon's part for the fact that my life is bigger than the corner that deals with it—and that I can do more with my own data than it can. Also that that this will be a Good Thing for both of us.
But there isn't any sign that this will happen, mostly because we don't yet have our own APIs, and managing our own data isn't something many of us do yet, least of all so we can deal in one consistent way with many suppliers. Mostly, we just fill up hard drives and hope whatever we have "in the cloud" is sort of safe and not going to bite us some way in the future.
Which brings us to the rest of the world.
The revolution we're in is a personal one, not a corporate one. It is a revolution in which personal empowerment has turned out to be good for enterprises because it was good for individuals. This fact has been manifest ever since PCs appeared on Earth around the turn of the 1980s.
To MIS directors in 1983, "personal computing" was oxymoronic. Computing was a corporate thing called data processing. It was big and expensive and specialized and centralized. But those same MIS directors had to start dealing with personal computing because individuals in their organizations and out in the marketplace were getting more done with their own word processing, spreadsheets and accounting software than companies could get done with their old big-iron data processing systems.
Likewise, IT directors in 1997 had to start dealing with personal communications (e-mail, instant messaging, personal publishing), because people in their organizations and out in the marketplace had tools of their own that stripped the gears of what the companies could do with their big old legacy systems.
IT directors in 2009 had to start dealing with iThings and Androids because that's what employees and users brought to work, and customers brought to stores, along with zillions of apps that far exceeded in what could be done with company-issued BlackBerries.
Today's "big data" bluster—all that stuff about how marketing can now know more about the customer than she knows about herself—is mainframe talk. Individuals know more about themselves than systems of any kind can guess at, no matter how much data those systems gather. Given the means to control our own lives, with their own personal platforms (not just ones on their devices, but on their own pile of data), we will be able to do far more with that data than can any other entity. We also can do it cooperatively with other entities, provided neither of us is busy trying to lock in or control the other.
In the next several years, personal data and personal operating systems for managing relationships using that data will be as revolutionary as PCs were in 1983, the Internet was in 1996 and mobile was in 2009. We can keep watching giants battle all they want. But the action that matters most won't be theirs. It will be ours.
Fist graphic via Shutterstock.com.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide