Language Selection

English French German Italian Portuguese Spanish

Apple's Deal With Intel Won't Rattle IBM

Filed under
Hardware

While Apple Computer Inc.'s new embrace of Intel Corp. microprocessors leaves IBM in the cold, the news really isn't bad for Big Blue, which may have found the Apple account more trouble than it was worth.

For one thing, IBM Corp. derived relatively little revenue from making its "Power" brand of chips for Apple's Macintosh computers, which own about 2 percent of the global market.

IBM's future chip plans are focused elsewhere - notably the next generation of video game consoles made by Microsoft Corp., Sony Corp, and Nintendo, Co. IBM's chips also power several kinds of IBM server computers, which account for a huge chunk of the company's hardware revenue.

Both kinds of machines require such high levels of performance that it becomes an expensive and challenging proposition to adapt their chips for personal computers, especially mobile devices that present stricter energy and cooling requirements.

So while winning Apple's business gives Intel some bragging rights, ceasing to make chips for Macs will let IBM focus on markets it believes can be much bigger.

"It's never a happy time when you lose a customer, no matter how large they are, but Apple's impact on the PC market is marginal at best these days," said Charles King, principal analyst at Pund-IT Research. "It will have more of a PR impact than a financial impact."

Added SG Cowen Co. analyst Steve Weber: "This move will likely have indiscernible impact."

IBM shares were down 67 cents, 0.9 percent, at $75.12 in afternoon trading on the New York Stock Exchange.

IBM declined to comment on Apple's announcement Monday other than to release a statement reiterating its chip strategy. "IBM is aggressively moving the Power architecture beyond the PC," the statement said.

While most computer companies long ago abandoned chip manufacturing to industry-standard suppliers such as Intel and Advanced Micro Devices Inc., IBM has stayed with it as part of a broader strategy to distinguish the company as an innovative, high-end tech provider. That desire to focus on top-tier markets motivated the recent spinoff of IBM's PC business to China's Lenovo Group Ltd.

With IBM's internal chip needs falling short of the company's manufacturing capacity - and demand from outside companies such as Apple only tepid - IBM's microelectronics division lost $252 million in 2003, the last year in which IBM released detailed figures. The segment grew at a paltry 0.6 percent in 2004, while IBM's overall sales jumped 8.3 percent to $96 billion.

But IBM's long-term microprocessing bet lies in a new breed of chips, code-named Cell, being developed with Sony and Toshiba Corp. Promising blazing speeds and the ability to carry out 10 sets of computing instructions at once, Cell is due to come out next year.

Hopes for Cell are so high that Sony, which plans to use Cell chips in the next generation of PlayStation game consoles, has invested $325 million in improvements to IBM's semiconductor plant in East Fishkill, N.Y.

IBM's production of chips for Apple accounted for only about 2 percent of Fishkill's capacity.

Associated Press

More in Tux Machines

Trisquel 9.0 Development Plans and Trisquel 8.0 Release

  • Trisquel 9.0 development plans
    Just as we release Trisquel 8.0, the development of the next version begins! Following the naming suggestions thread I've picked Etiona, which sounds good and has the fewest search results. We currently do our development in a rented dedicated server in France, and although it is functional it has many performance and setup issues. It has 32 gigs of RAM, which may sound like plenty but stays below the sweet spot where you can create big enough ramdisks to compile large packages without having to ever write to disk during the build process, greatly improving performance. It also has only 8 cores and rather slow disks. The good news is that the FSF has generously decided to host a much larger dedicated build server for us, which will allow us to scale up operations. The new machine will have fast replicated disks, lots of RAM and two 12 core CPUs. Along with renewing the hardware, we need to revamp the software build infrastructure. Currently the development server runs a GitLab instance, Jenkins and pbuilder-based build jails. This combination was a big improvement from the custom made scripts of early releases, but it has some downsides that have been removed by sbuild. Sbuild is lighter and faster and has better crash recovery and reporting.
  • Trisquel 8.0 LTS Flidas
    Trisquel 8.0, codename "Flidas" is finally here! This release will be supported with security updates until April 2021. The first thing to acknowledge is that this arrival has been severely delayed, to the point where the next upstream release (Ubuntu 18.04 LTS) will soon be published. The good news is that the development of Trisquel 9.0 will start right away, and it should come out closer to the usual release schedule of "6 months after upstream release". But this is not to say that we shouldn't be excited about Trisquel 8.0, quite the contrary! It comes with many improvements over Trisquel 7.0, and its core components (kernel, graphics drivers, web browser and e-mail client) are fully up to date and will receive continuous upgrades during Flidas' lifetime. Trisquel 8.0 has benefited from extensive testing, as many people have been using the development versions as their main operating system for some time. On top of that, the Free Software Foundation has been using it to run the Libreplanet conference since last year, and it has been powering all of its new server infrastructure as well!

today's howtos

FOSS Events in Europe: Rust, foss-north, KubeCon + CloudnativeCon Europe 2018

  • Rust loves GNOME Hackfest: Day 1
    This is a report of the first day of the Rust loves GNOME Hackfest that we are having in Madrid at the moment. During the first day we had a round of introductions and starting outlining the state of the art.
  • Madrid GNOME+Rust Hackfest, part 1
    I'm in Madrid since Monday, at the third GNOME+Rust hackfest! The OpenShine folks are kindly letting us use their offices, on the seventh floor of a building by the Cuatro Caminos roundabout. I am very, very thankful that this time everyone seems to be working on developing gnome-class. It's a difficult project for me, and more brainpower is definitely welcome — all the indirection, type conversion, GObject obscurity, and procedural macro shenanigans definitely take a toll on oneself.
  • Five days left
    I use to joke that the last week before foss-north is the worst – everything is done, all that is left is the stress.
  • KubeCon + CloudnativeCon Europe 2018
    The Cloud Native Computing Foundation’s flagship conference will be taking place in Copenhagen from May 2-4. It will cover Kubernetes, Prometheus OpenTracing, Fluentd, Linkerd, gRPC, CoreDNS, and other key technologies in cloud native computing.

Programming: Taxonomy of Tech Debt, Python and More

  • A Taxonomy of Tech Debt
    Hi there. I’m Bill “LtRandolph” Clark, and I’m the engineering manager for the Champions team on LoL. I’ve worked on several different teams on League over the past years, but one focus has been consistent: I’m obsessed with tech debt. I want to find it, I want to understand it, and where possible, I want to fix it. When engineers talk about any existing piece of technology - for example League of Legends patch 8.4 - we often talk about tech debt. I define tech debt as code or data that future developers will pay a cost for. Countless blog posts, articles, and definitions have been written about this scourge of software development. This post will focus on types of tech debt I’ve seen during my time working at Riot, and a model for discussing it that we’re starting to use internally. If you only take away one lesson from this article, I hope you remember the “contagion” metric discussed below.
  • 6 Python datetime libraries
    Once upon a time, one of us (Lacey) had spent more than an hour staring at the table in the Python docs that describes date and time formatting strings. I was having a hard time understanding one specific piece of the puzzle as I was trying to write the code to translate a datetime string from an API into a Python datetime object, so I asked for help.
  • Getting started with Anaconda Python for data science
  • How to install the Moodle learning management system
  • Anatomy of a JavaScript Error
  • Is DevOps compatible with part-time community teams?