HP's first move is discontinuing operations for its (Linux-based) WebOS devices, including phones and tablets. The next is unloading its Personal Systems Group (PSG). In a press release titled HP to Evaluate Strategic Alternatives for Personal Systems Group, the company explains,
HP today announced that its board of directors has authorized the evaluation of strategic alternatives for its Personal Systems Group (PSG), including the exploration of the separation of its PC business into a separate company through a spin-off or other transaction.
PSG has a proud history of innovation and technological leadership as well as a strong operating track record and industry-leading profitability. PSG is the leading manufacturer of personal computers in the world and had annual revenues of approximately $41 billion in fiscal year 2010. PSG enjoys leading global market positions in consumer and commercial PCs.
HP is implementing a plan to fundamentally transform the company. An important component of the plan is focusing its investments, resources and management attention to drive higher value solutions to enterprise, small and midsize business and public sector customers.
So they want to be big and dull. Fine. Go do that.
From the Linux angle, there is much more potential excitement in what they're giving up.
According to the Computerworld piece, HP shipped 14,888,086 PCs in Q2/2011, for a 17.5% share of a worldwide total of 85,219,865 units. (Source: Gartner, July 2011.) But PCs are commodities now. Microsoft's Windows OS, for which new PCs have been designed for a generation, has gone blah. Used to be Microsoft led the clone-makers around by the nose. Now Microsoft is walking Nokia around the barnyard while the clone-makers are losing interest in the whole show.
It would be way cool if Somebody Big stepped up for Linux, and took over the PC bus that's coasting along in the slow lane while Apple rockets by in an aluminum-anodized blur. Who might that be? There's only one possibility: Google.
Hey, they just went vertical in the phone hardware business with Motorola, which everybody's calling Googlerola now. Why not with PCs? Will we call that move gHooPle?
Does anybody want Microsoft to buy HP's PC business instead? That's a possibility this piece in the Seattle PI suggests. Microsoft would do to the Windows-based PC business what Google did to the Android-based smartphone business.
The buzzphrase du jour here is "vertical integration." Apple's success has given a new caché to it. Never mind that Apple is a industrial mutant and an example only of itself.
In fact vertical integration has been around since Industry won the Industrial Revolution. Getting past it is one of the great achievements of both the PC and the Internet (and of Linux with both). The horizontality of both has created a vast foundation for innovation and wealth-building out the wazoo.
Google saw that, aligned with it, and went horizontal big-time with Android. But horizontal (the commodity play) has drawbacks. This afternoon I met with a smartphone developer that makes an identical app for iPhone and Android. He said actual usage of the app on iPhone is 10x that of the same app on Android. (Note that we're talking usage here, not installs. His first point: iPhones still make apps easier to use. His second one: Google buying Motorola is ideal for him, because Googlerola is sure to raise the bar on usability, and create a single development target across all the different Android smartphones.
Another way of looking at the gHooPle prospect: Google can lead PC growth and evolution the way Microsoft did the generation before, and the way Google is doing with smartphones and hand-helds, right now. gHooPle might even leap ahead of Apple, because Apple still has a two-OS problem (iOS and OS X). Can Android be a one-OS for all personal devices? Why not?
At this point we're moving into the realm of pure speculation. (Which is fun. We like that.) But what's not in doubt is that the PC business is dull and languishing, and the biggest player in the business is folding its cards and walking away from the game.
Something is about to go down here. What is it? And what should it be?
Tell us quick, before it happens.
Doc Searls is Senior Editor of Linux Journal
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
|Introduction to MapReduce with Hadoop on Linux||Jun 05, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Introduction to MapReduce with Hadoop on Linux
- RSS Feeds
- New Products
- Weechat, Irssi's Little Brother
- Validate an E-Mail Address with PHP, the Right Way
- Tech Tip: Really Simple HTTP Server with Python
- Reply to comment | Linux Journal
39 min 14 sec ago
- Welcome to 1998
1 hour 27 min ago
- notifier shortcomings
1 hour 51 min ago
3 hours 28 min ago
- Android User
3 hours 29 min ago
- Reply to comment | Linux Journal
5 hours 23 min ago
8 hours 12 min ago
- This is a good post. This
13 hours 25 min ago
- Great, This is really amazing
13 hours 27 min ago
- These posts are really good
13 hours 29 min ago
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?