CRN: IBM jumps aboard blog bandwagon: (Kudos to Blogsphere/OpenNTF for mention/link):

Analyst Dana Gardner, who had been critical of IBM's blogging status till now, is encouraged. "This is a big step for IBM as well as for blogging and RSS delivery of collaborative content in general," said Gardner, principal analyst with Interarbor Solutions, Gilford, N.H.

"While blogging may be viewed by the public as a hobbyist's plaything, it is serious fro business productivity and IBM-like Apple, Yahoo, Google and Microsoft is on the bandwagon," he noted.
CNET: IBM tacks blogs to Workplace:
IBM plans to add blogging capabilities to the next version of its Workplace collaboration and development software, the company said on Wednesday.

The company offered the details of its blog-related plans as part of a preview into the upgrades that will arrive sometime in August, when the company is expected to release its Workplace 2.5 and Workplace Designer 2.5 offerings. IBM said the addition of the blogs to the collaboration and software development tools is a concession to the growing popularity of the Web pages among its corporate clients.

Blogs, the shortened term for Web logs, are most frequently used by corporate workers to share information regarding projects they're working on, according to the company.
Redmonk's James Governor, On Lotus and the Advantages of Componentization (a good read, and fully disclosed, too):
IBM has been working towards componentized rather than monolithic approaches to its software portfolio for quite a while now. Microsoft keeps telling the world Lotus is dead, but in truth its just decomposing...

This decomposition is a good thing because it allows IBM to add new functionality to Lotus tooling far more quickly than it could in the past. Which major vendor will be the first to embed blogging capabilities into its enterprise collaboration toolset, IBM or Microsoft? It seems the answer may well be Big Blue. This is decoupled innnovation; small things loosely joined, that's the "getting things done" kind of innovation. ...

IBM may have made some poor decisions along the way (anyone for K-station, Koranteng?), but it didn't trash community skills investments (even though many Lotus partners were sure it would). The technology changes, but IBM keeps its developers and customers onside.

I am sure folks at Microsoft will be spluttering by now if they are reading this, but you should probably worry about the programming model changes you're currently pushing your own developers through before you throw stones at IBM.

Talking of throwing stones, I have no real interest in regurgitating the ongoing spattle between Ed Brill and the Exchange team but its great fun to watch.

Post a Comment