This article is more than 1 year old
Standards that suit
Adobe MAX Adobe Systems' chief technology officer has placed his faith standards bodies to help overcome Balkanization in an important web technology, despite losing a recent round of vendor combat.
Kevin Lynch said at MAX that Adobe would continue participation in bodies like ECMA, even though they aren't moving as fast as his company would clearly like.
He noted technologies like ECMAScript are moving too fast to be nailed down as completed specifications.
"All have excellent technical teams and it's nice to have peer pressure between the implementations to be the best," Lynch said. "For the web, it would be better if we got these folks together and develop a common implementation. We have another fragmented solution."
And therein lies the rub.
Not only can standards bodies be too slow for companies like Adobe, they don't always go the way they want them too.
ECMA in August decided to abandon plans for a radical rewrite of ECMAScript that would have created version 4 for an evolution to version 3.1 instead, following lobbying by Microsoft. The real problem for Adobe was it had based ActionScript - which underpins its Flash Player - on ECMAScript 4. Tamarin, incidentally, was based on source code from the ActionScript virtual machine.
"It can be difficult to get rapid innovation in standards bodies," Lynch said. "We are going to continue participating. We are going to do so in a way that factors in the other voices."
Lynch said you could standardize "mature" technologies such as Adobe's PDF, which is an ISO standard. But: "ECMAScript is still moving pretty quickly, so it's harder to nail down." ®