W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

Re: ISSUE-73: Are we going to support non-ECMAScript languages?

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 7 Apr 2006 01:46:36 +0000 (UTC)
To: Cameron McCormack <cam@mcc.id.au>
Cc: Web APIs WG <public-webapi@w3.org>
Message-ID: <Pine.LNX.4.62.0604070143080.21459@dhalsim.dreamhost.com>

On Fri, 7 Apr 2006, Cameron McCormack wrote:
> 
> Web APIs Issue Tracker:
> > > [re creating an XHR object in non-ES languages]
> ...
> > > (a) Leave it up to the language
> > > (b) Create a method on some object (like Window or Document) that returns an
> > >     the object.
> > > (c) Do it through DOMImplementation
> 
> Ian Hickson:
> > If you do either (b) or (c), please make it specific to that language 
> > binding and no _not_ permit a JS implementation to expose that API.
> 
> Why?

Because every single code path adds a new set of bugs, with its own set 
of Web pages that depend on it, with its own set of confused authors, 
with time spent implementing it, fixing it, testing it, etc.

We already have at least three ways of obtaining an XMLHttpRequest object, 
we don't need a fourth.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 7 April 2006 01:46:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT