Archive for March, 2013

Adobe Sponsors EclipseCon


On March 25-28 the Eclipse and OSGi Alliance developer communities will meet in Boston at EclipseCon 2013 co-located with OSGi DevCon 2013. Adobe is proud to be a sponsor for this event. Carsten Ziegeler, Sr. Developer will present the Apache Sling OSGi Installer  which is used to drive installation and update deployments of the Adobe Experience Manager (AEM) 5.6. I will talk about the work of the OSGi Alliance to update the HTTP Service Specification

These Adobe presentations highlight the value Adobe is delivering to the OSGi community. Not only is the specification work possible due to Adobe’s membership in the OSGi Alliance, the actual implementation work is being done in the Apache Software Foundation where both Carsten and I are both members.  We’re happy to be involved.

If you’re attending EclipseCon or OSGi DevCon 2013, we’ll see you there.

Felix Meschberger, Principal Scientist, OSGi Alliance Board of Directors

Adobe’s ECMA TC-39 Involvement

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.

On the JavaScript front, Adobe brings expertise from areas like ActionScript and Flash, Java, Lisp, OCaml, and other languages.  We’ll use this expertise to contribute to open-source platforms and we’ll do demonstrations of ideas built on existing open-source technology. Eventually, we’d like to see some of this work make it into both open-source and proprietary implementations.

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.

We’d like to see a more uniform interface to debugging and profiling data from JavaScript engines, and from browsers and virtual machines in general. We have some exciting ideas and a compelling way of demonstrating them and foresee interest among the other TC-39 participants. We’re researching this now and will start with preliminary specification and prototypes soon.

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.

John Pampuch
Director, Languages, Compilers and Virtual Machines

Adobe Supports OpenStand

On March 9th, at the Open Future  reception at SXSW, Adobe announced support for the OpenStand  initiative. Our rationale for this was simple – OpenStand is good for the Web, good for users, and good for Adobe. It increases innovation, openness, and allows greater participation in evolving the Internet.

The Internet is built on standards. These standards come from all sorts of organizations – some formal and supported by governments, some less formal and created by industry associations, and some driven by users who believe in collective action. OpenStand takes a simple position on these organizations – if the organization is open, transparent, balanced, has due process in creation, and has broad consensus – then the organization and its specifications are legitimate.

The approach advocated by OpenStand seems to be intuitively obvious; good technical standards which are accepted and implemented by the industry should be judged not on their origin, but rather on their utility to the industry. A poor standard with a “proper background and backing” is still a poor standard.

The Internet is ubiquitous – from mobile phones to tablets to desktops – all form factors, all types of information, design, and literally “everything”.  It is a golden age for creative display and use of information – all driven by innovation, which then is “standardized” so users can access it and interoperate with complementary services.

Adobe has contributed significantly and will continue to contribute to efforts to document and test these innovative activities in conjunction with W3C with the Web Platform Docs (WPD) project and Test the Web Forward.   We have also (along with Microsoft and Google), supported the HTML5 editor as this standard moves to completion and we are also active in WebKit specs, as well as in formal metadata standards. All of these venues are important – and all build the ability of the market to innovate, grow, and change. And that’s what OpenStand is all about, which is why Adobe has chosen to support it.

Carl Cargill
Principal Scientist