Jeff Gould
October 3, 2008

Standards, open standards and double standards

In my last post I took Big Blue to task for its announcement that it intends to wage war against Microsoft in the world’s standards bodies. The motivation for this bellicose declaration was IBM’s stinging defeat last Spring in its battle to prevent the International Organization for Standardization (ISO) from ratifying Microsoft’s de facto office document standard (OOXML).

IBM charges that Microsoft won at the ISO only because it packed the national standards organizations that make up the ISO membership with its pals.

But the thing that galls me about IBM’s position – and the reason I wrote my post – is not its goody-two-shoes stance about lobbying. No, it’s the flagrant hypocrisy behind this whole open standards campaign. In a nutshell, Big Blue conspicuously fails to practice what it preaches.

Click to read more...

More articles by Jeff Gould, CEO & Director of Research, Peerstone Research

Search

Want to host a Solution Center on Interop News?
For more information, Click Here.

« Open-source efforts derailed by 'loud minority' | Main | Microsoft's Ramji extends olive branch to Eclipse users »
Thursday
20Mar

The Mainframe lives, Part 1

By Ned Madden (TechNewsWorld)
Mainframes occupy a market position between supercomputers and "minicomputers"-- the medium-scale, centralized multi-user systems now more commonly termed "midrange computers" and "servers" for PC networks. However, with the general increase in computing power, the differences between the various systems are becoming less marked.
IBM has found one way to sidestep the mainframe vs. distributed computing dilemma by simply calling its mainframes something else.
Today, IBM refers to its larger processors as large servers and emphasizes that they can be used to serve distributed users and smaller servers in a computing network.

http://www.technewsworld.com/story/62178.html


PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>