Language Selection

English French German Italian Portuguese Spanish

IBM Left in the Dark

Filed under
Mac

There's no shortage of rumors as to just what really went on between Apple and IBM with regards to the souring of their relationship, and rehearsing them all here would be an exercise in futility. However, John Markoff of the New York Times has offered his take, based in-part on "close sources," and I thought it worth mentioning here.

Apple purportedly pulled a bit of a fast one on IBM, with Jobs only informing IBM of the decision late in the day Friday, right before Monday's big announcement. IBM apparently learned of the possibility of the deal the way most of us did, through the early reports of the WSJ. The question is, why? Jobs' WWDC presentation heavily implied that IBM simply couldn't deliver. The infamous image of the missing 3GHz PowerMac behind Jobs on stage certainly made it seem like Big Blue couldn't get the job done, and Jobs came off looking like he had to make a tough, but thoroughly necessary decision. IBM, not surprisingly, tells it a different way.

"Technical issues were secondary to the business issues," said an executive close to the I.B.M. side of the negotiations. Because the business was not profitable, I.B.M. "decided not to continue to go ahead with the product road map."

In other words, Apple wasn't interested in paying IBM's prices, and the prices that they would pay weren't enough for IBM to consider taking the road map further. Given Apple's lack of fear with regards to impressive price tags, this leads me to think that IBM was potentially looking to increase the prices of the PowerPC 970 in a significant way to justify spending more time on the project. Then again, no one can deny that the PowerPC 970 had a heat problem. The water-cooled PowerMac, the non-existent G5 laptop, and the 1-year overdue 3GHz part are all signs of problems at IBM. How much more scratch did IBM want to make these problems go away, and was it certain that these problems could be solved by the almighty dollar? Jobs' actions seem to suggest that, if this scenario is correct, he apparently had little faith in IBM. That, or the Blue Man Group seemed like a smarter way to preserve those profit margins.

Source.

More in Tux Machines

Linux Foundation: New Members, Certifications and Microsoft Entryism

ETSI/GNU/Linux-based MANO

  • ETSI Open Source MANO announces Release FOUR, moving faster than ever
    ETSI is pleased to announce the availability of OSM Release FOUR. Bringing a large set of new features and enhancements, this version is the most ambitious and innovative OSM Release to date and constitutes a huge leap forward in terms of functionality, user experience and maturity. This new Release brings substantial progress thanks to a number of architectural improvements, which result in a more efficient behaviour and much leaner footprint – up to 75% less RAM consumption. Additionally, its new northbound interface, aligned with ETSI NFV work, and the brand-new cloud-native setup, facilitate OSM’s installation and operation, while making OSM more open and simpler to integrate with pluggable modules and external systems, such as the existing OSS.
  • Open Source MANO Release FOUR lands
    In monitoring, ETSI says OSM Release FOUR's alarm and metric settings are easier to use, and a new policy manager adds push notifications and reactive policy configuration, which the standards body says “opens the door to closed-loop operations”. The monitoring module uses Apache Kafka as its message passing bus, and the module also implements a flexible plugin model so sysadmins can BYO monitoring environment.

today's howtos part 2

Programming: GitLab, Security, Power and Jakarta EE

  • GitLab 10.8 open sources push mirroring
    GitLab 10.8 was released this week with the open sourcing of a highly requested feature. The company announced its push mirroring capability is now open sourced. Push mirroring was originally introduced as a paid feature, but GitLab says it is one of the most frequently requested to be moved into the open-source codebase. This move will add a few new use cases for GitLab Core users, such as freelance developers being able to mirror client repos and users migrating to GitLab being able to use push mirroring to ease the migration path.
  • How Security Can Bridge the Chasm with Development
    Enhancing the relationships between security and engineering is crucial for improving software security. These six steps will bring your teams together. There's always been a troublesome rift between enterprise security teams and software developers. While the friction is understandable, it's also a shame, because the chasm between these teams makes it all the more challenging to build quality applications that are both great to use and safe.
  • Which Programming Languages Use the Least Electricity?
    Can energy usage data tell us anything about the quality of our programming languages? Last year a team of six researchers in Portugal from three different universities decided to investigate this question, ultimately releasing a paper titled “Energy Efficiency Across Programming Languages.” They ran the solutions to 10 programming problems written in 27 different languages, while carefully monitoring how much electricity each one used — as well as its speed and memory usage.
  • How Java EE found new life as Jakarta EE
    The title of this post may seem strange, but if you look a bit into Java EE's recent history, it will make sense. Originally, Sun started and ran Java Enterprise Edition, and later Oracle took over after it acquired Sun. Specifications were driven by a Sun/Oracle-governed process. At more or less regular intervals, they made a new version of the specification available, which was implemented by the server vendors. Those vendors had to license the technology compatibility kits (TCKs) and brand from Oracle. Let's fast-forward a bit. In 2013, Java EE 7 was released, and Oracle began work on EE8, but it did not progress quickly. Meanwhile, new technologies like Docker and Kubernetes came along and changed the way applications run. Instead of running a single fat server process on a big machine, the software is now split into smaller, independent services that run in a (usually) Docker container orchestrated by Kubernetes.