The latest in the ongoing series of political battles surrounding apparently obscure technical arguments concerns JavaScript, whose mobile profile is managed by the Open Mobile Alliance, and which is critical to creating web services and multimedia applications for small devices. The two companies are leading a clash over the next version of JavaScript, which in its standards- based implementation is officially called ECMAScript. Microsoft is arguing that a completely new language is needed to cope with the new demands of the internet, and unsurprisingly as volunteered a project based on its own Jscript as an alternative to a simple version 4.0 of ECMAScript. Meanwhile, open source software house Mozilla, whose CTO Brendan Eich was the creator of JavaScript, is calling for greater continuity with existing web efforts.
Eich and Microsoft’s Internet Explorer platform architect, Chris Wilson, have been trading arguments in their respective blogs. Wilson argued that ECMAScript 4.0 would be such a major structural change from the current technology that ‘a completely new language should be developed. We could continue supporting existing users as well as freeing the new language from constraints (including the constraint of supporting scripts written in the old language),” he wrote. He complained that the ECMA committee was ignoring Microsoft’s concerns, hinting that the software giant might plough its own furrow. “I also think it’s a shame that the response to any dissent has equated to shouting the dissenters down,’ Wilson added in a later post.
Eich retorted that ECMA had been very open, but Microsoft had not had much input, and accused the larger company of letting its own Jscript stagnate once it gained dominance in browsers. He believes Microsoft is trying to keep the web, mobile and fixed, under its control via Jscript and IE.
Yahoo is Microsoft’s major supporter in the row, arguing that there should be improvements to ECMAScript 3 plus modern scripting functionality provided by a totally different language. Adobe has been the most vocal backer of the Mozilla view, calling for an overhaul of ECMAScript, but preserving backwards compatibility with old code.
Most developers agree that ECMAScript 3 is anachronistic compared to modern dynamic scripting languages, and the new version should add new syntax elements, many of them influenced by Java and Python. However, ECMAScript 4 is largely backwards compatible with conventional JavaScript. This, argues Microsoft, makes it impossible to add modern features without making ECMAScript far more complex, breaking existing code, and creating new interoperability problems.
Meanwhile, this month saw the W3C and OpenAjax Alliance holding a workshop to try to put some definitions behind the mobile web, which is evolving rapidly but with increasing levels of confusion and political debates such as the one over scripting. The groups set out five key issues and will work on proposals for how these should be addressed or resolved.
‘ What is the ‘One Web’ and what are the key features of the devices, such as embedded cameras, reduced memory and content entry techniques.
‘ Access to device capabilities. Mobile Ajax requires the availability of scripting APIs (using ECMAScript/JavaScript) to services like GPS, messaging, and camera manipulation. Currently, the languages of the web and the internal languages of mobile handsets are incompatible with stakeholders like Microsoft, Vodafone and Opera having their own APIs.
‘ Mobile widgets will represent a second major workflow (in addition to the browser) for Mobile Ajax technologies and for access to applications.
‘ Issues of server-side adaptation.
‘ Does Mobile Ajax need specific new standards or will minor incremental changes to existing standards suffice?
The workshop largely concluded that a common Ajax platform will become available across both desktop and mobile devices – ”it will be web on mobile, not a separate mobile web’.