sabotaging JDO's market momentum
Posted in response to JDO 2.0 Public Review Ballot by Robin Roos on TheServerSide.com:The absence of technical objections to JDO 2.0 and the recurring theme of confusion with JSR 220 persistence indicates that the purpose of the votes against JDO 2.0 are to prevent JDO 2.0 implementations (which many JDO vendors are already making preview releases available) from gaining market momentum before JSR 220 persistence implementations appear for the first time.
Their fear is not "market confusion". It is market certainty that proven JDO 2.0 implementations will reach the market and achieve broad success (market share) long before JSR 220 persistence reaches the market, thereby relegating JSR 220 persistence to irrelevance. They know that successful adoption of a technology will make it virtually impossible to displace with an alternative that arrives late, even if it exhibits some modest degree of superiority. The technology with dominant market share will also not remain stagnant, and its vendors would quickly incorporate improvements according to demand.
There is a large community of developers with both money and expertise to invest in adopting a prolific persistence technology. It is a ubiquitous problem for many applications. There is fear that JDO 2.0 will be adequate to the needs of many, rendering the promise of JSR 220 persistence irrelevant, if JDO 2.0 is widely adopted quickly. The only confusion that would ensue is the consequent irrelevance of JSR 220 persistence to the market.
Therefore, I would suggest that if the Java Community Process is acting against the interests of the community that it proports to serve by sabotaging a technology that the community demands, the JDO vendors should release their products according to the latest available draft without the endorsement of the JCP Executive Committee. The market can vote with their hearts, minds, and dollars; the politically motivated votes in favor of JSR 220 persistence would merely become a hollow victory for the opponents of JDO 2.0.
posted by Ben Eng @ 23:27
0 comments
