Adobe is supporting, using, and contributing to Web standards, and ECMAScript is no exception. We’re actively building applications and tools built on and for Web technology, and are becoming keenly aware of the strengths and weaknesses of Web technologies for development. That being said, Adobe is returning to the ECMA committee TC-39. During the week of March 11, Adobe’s Bernd Mathiske and Avik Chaudhuri attended the technical committee meeting. (Our entire ECMAScript team includes language design, type theory, compiler, concurrency and VM experts).
Ultimately, Adobe’s goal is to improve the Web experience for everyone. Making developers more productive is a key means to achieve this goal. One way we’re hoping to help is by improving the consistency of ECMAScript across its various implementations. While we’re aware that in practice, implementation differences come more from browser integration, we also plan to work with browser vendors to improve that consistency too. This will help us to develop better tools and make it easier for us to create our own Web applications.
My personal favorite feature that hopefully will become part of ECMAScript 6 is modules. The approach under consideration is highly flexible, versatile, and quite easy to use. It will have a huge effect on making ECMAScript scale to much more complex systems.
Performance matters a lot to Adobe, and this might be an area of ECMAScript where we can also help. This is mostly an implementation issue, so we’ll help on open-source implementations too. That also means ideas like asm.js and River Trail are compelling for us, and we’re willing to help with standardization on those fronts too.
I hope this introduction to our ECMA TC-39 participation is helpful and encouraging to TC-39 and the community at large.
Director, Languages, Compilers and Virtual Machines