January 24, 2004
@ 09:45 PM
Comments [2]
BEA missing the cluetrain

Don says that BEA's Deputy CTO has missed the cluetrain. I absolutely agree with Don's opinion on this article and what's even worse than the things said is what the article implies. If that is BEA's official position, this is nothing less than an outing that they are passengers in the backseat of a car that is driven by IBM and Microsoft (switching drivers every once in a while) and that they're neither behind the spirit of the whole undertaking nor do they fully understand the specifications they have put their names on. Integration or standardization on the API level has failed miserably in countless attempts and any middleware company (including BEA) that is out there to compete on features must go beyond the least common denominator approach to win over customers. Does BEA have Indigo envy?

Categories: Technology | Indigo

« I've got my blogging mojo back | Home | Longhorn In Budapest: The relevance of I... »
Monday, January 26, 2004 8:52:56 PM UTC
The article was a misunderstanding on the journalist's part. The point I made in the interview was that BEA, Microsoft and others are very committed to Web Services and the standards around them, and that the work we’ve done together on inter-operability (through WS-I and other forums) has been outstanding. I followed that up by pointing out that interoperability doesn’t mean that you don’t get locked-in to a platform: real lock-in happens at the API level, hence our customers’ preference for a standards-based API such as J2EE, rather than a proprietary one, such as .NET’s.
Benjamin Renaud
Tuesday, July 04, 2006 9:03:38 PM UTC
The article was a misunderstanding on the journalist's part. The point I made in the interview was that BEA, Microsoft and others are very committed to Web Services and the standards around them, and that the work we’ve done together on inter-operability (through WS-I and other forums) has been outstanding. I followed that up by pointing out that interoperability doesn’t mean that you don’t get locked-in to a platform: real lock-in happens at the API level, hence our customers’ preference for a standards-based API such as J2EE, rather than a proprietary one, such as .NET’s.
backgammon for money
Comments are closed.