W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2013

Re: Request for JSON-LD API review (was: Coordination)

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 16 Apr 2013 16:55:20 -0700
Message-ID: <CAAWBYDAuad5RdC5TUNwmiMkQe3roBYFKqODJGWmWMo1doQgJ6Q@mail.gmail.com>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Cc: "public-script-coord@w3.org" <public-script-coord@w3.org>, public-rdf-comments@w3.org
On Tue, Apr 16, 2013 at 8:30 AM, Markus Lanthaler
<markus.lanthaler@gmx.net> wrote:
> After a short discussion with Robin we decided to use method overloading to
> have the "callback" parameter always last while still having an optional
> "options" parameter. We are aware of the fact this isn't allowed at the
> moment and already raised an issue for WebIDL [2].
>
> Boris Zbarsky already raised his concerns about this style as not being
> "platform consistent" [3].
>
> We also considered Futures but decided that introducing a normative
> dependency to the DOM spec is not acceptable at this stage.

Pardon my french, but:

Fuck. Dependencies.

Worrying about dependencies falls into the "technical purity" bucket,
and your ladder of constituencies is:

Technical Purity < Implementors < Authors < Users

(Actually, it probably falls more into the "Bureaucracy" bucket, which
sits even lower than technical purity.)

If there is a correct way to do things, but it would introduce a new
dependency, your job is to do the correct thing and then figure out
how to route around the bureaucracy.  Anything else is abandoning your
responsibility toward all the other constituencies.

In this case, your API is a textbook example of Futures.  You have an
async call which returns a single value, or an error.  You can't get
much more perfect than that.

~TJ
Received on Tuesday, 16 April 2013 23:56:07 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:49 UTC