Wednesday, March 21st, 2007

Microsoft joins the OpenAjax Alliance

Category: Announcements, Atlas

When the OpenAjax Alliance was created Microsoft was invited, but didn’t take up the offer. They were noticeably absent from the early meetings.

Well, now Bertrand Le Roy of the Atlas team will be at the meetings as the OpenAjax Alliance Welcomes Microsoft and Other New Members and Announces Interoperability Awards:

“Microsoft is joining the OpenAJAX Alliance to collaborate with other industry leaders to help evolve AJAX-style development by ensuring a high degree of interoperability,” said Keith Smith, group product manager of the Core Web Platform & Tools to UX Web/Client Platform & Tools team at Microsoft Corp. “By joining OpenAJAX, Microsoft is continuing its commitment to empower Web developers with technology that works cross-browser and cross-platform.”

The newest OpenAjax Alliance members include: 24SevenOffice, ActiveGrid, ActiveState, Appeon, Aptana, Arimaan Global Consulting, Custom Credit Systems (Thinwire), ESRI, Getahead (DWR), Global Computer Enterprises, GoETC, Helmi Technologies, HR-XML, iPolipo, Isomorphic Software, JSSL, Lightstreamer, Microsoft, MobileAware, NetScript Technologies, OpenSpot, OpenSymphony (OpenQA), OpSource, OS3.IT, Redmonk, Tealeaf Technology, Teleca Mobile, Transmend, Visible Measures, Visual WebGui and Volantis Systems.

The Alliance is also announcing that the following members have all been awarded OpenAjax Interoperability certificates: Apache XAP, Dojo Foundation, ICEsoft, ILOG, Isomorphic, IT Mill, Lightstreamer, Open Link, Open Spot, Nexaweb, Software AG and TIBCO. The interoperability certificates represent progress by both OpenAjax Alliance and its members towards defining and achieving industry support for OpenAjax Conformance.

Posted by Dion Almaer at 12:27 am

3 rating from 30 votes


Comments feed TrackBack URI

Is it just me that finds it interesting that most of the guys that are leading the field of Ajax development are not represented by these big companies? In the list you can spot a few leaders, but most of them are followers.

I think it’s admirable of them to try and insure interoperability (buzzword du-jour), but let’s face it… most of the innovative work and the work towards interoperability is done by guys working in smaller organisations, where marketing and product managers is not dictating development, but where development of new features is done because it’s required by the users or because it helps the developers.

Comment by Morgan Roderick — March 21, 2007

My experience is that commercial development is very much “done because it’s required by the users or because it helps the developers” – in fact the marketing and product managers often dictate that r&d must do X because some users need it. The difference is that the users are called “customers” ;-)

I’m also sure that more and more of the ajax developers you are referring to are going to join the OpenAjax Alliance, once it gets easier for individual developers and communities to do so – there has been some discussions about this.

Personally, I’m think the interoperability efforts are great – it will allow developers to use the tools they are familiar with. For instance, using the IT Mill Toolkit mentioned, the java programmers would be using pure java to develop the application while you could use your favorite ajax (js) framework to develop the presentation (l&f, themes, components, …)
Another scenario is integrating full-fledged web applications into web sites, where the applications and sites are made with different frameworks (best suited for the task).

//Just some thoughts

Comment by Marc — March 21, 2007

Well, now that MS is involved, I expect the specs to reach no less than 400 pages :-) Anyone noticed that Atlas comes with a lib to add MS-propriatary methods to W3C compliant browsers and thous promoting them instead of doing it the other way around or offering an abstraction interface like any other self-respecting library?

I’m also sure that more and more of the ajax developers you are referring to are going to join the OpenAjax Alliance, once it gets easier for individual developers and communities to do so

You mean after fait accompli by the corp buddies?

Comment by Martin — March 21, 2007

“Growing healthy? let’s infest it!”

M$ is like a disease…

Comment by disease — March 21, 2007

Taking a look at Microsoft’s history of interoperability, I’d say my opinion of the OpenAjax Alliance has just dropped drastically. How many corporations do they have in there? How many day-to-day developers could even begin to explain OpenAjax conformance?

Screw that, I no longer care about this bureaucratic joke.

Comment by The Hater — March 21, 2007

Isn’t it obvious or I am missing the point? The first step Microsoft should be doing is to get their IEs compliant with standards. The second step is to maintain this kind of compliant-mentality moving forward.

Comment by Kevin Hoang Le — March 21, 2007

i agree with Kevin. MS has been very innovative with the web. I believe some of the things they’ve done should be made standard. However they should try to comply to standards first instead of breaking it and forcing their proprietary methods on us to make it work. Whenver I hear or see the words “Open”, “Standard” and “Microsoft” together, I think “oh crap”.

Comment by cdude — March 21, 2007

Martin: apparently, you haven’t been looking at the Microsoft Ajax Library lately. We moved away from this compatibility layer approach more than a year ago, among other reasons to promote the standard way of doing things. You might want to check out the 1.0 version that we shipped at the beginning of the year. Hopefully you might change your mind.

Comment by Bertrand Le Roy — March 22, 2007

Leave a comment

You must be logged in to post a comment.