- From: Tobie Langel <tobie@fb.com>
- Date: Thu, 20 Sep 2012 17:43:18 +0000
- To: Greg Billock <gbillock@google.com>, Jungkee Song <jungkee.song@samsung.com>
- CC: Norifumi Kikkawa <Norifumi.Kikkawa@jp.sony.com>, Paul Kinlan <paulkinlan@google.com>, WebIntents <public-web-intents@w3.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>, "Frederick.Hirsch@nokia.com" <Frederick.Hirsch@nokia.com>
On 9/20/12 7:27 PM, "Greg Billock" <gbillock@google.com> wrote: >The discomfort I'm estimating as the most acute >is client developers wanting to get started. I'd like them to have as >few problems as possible using the API, and so I'd like to make their >path as clear as possible. That's actually easily mitigated by providing example code developers can copy. It also an issue during a relatively short period of time and is relevant to that particular API only. It's also very possible that the developers will be familiar with the pattern having seen it elsewhere. However, inconsistencies in the platform hurt the productivity of beginner, intermediate and seasoned developers alike. Not only does it hurt developers when they are using that particular API, but it also hurts them **every time they will use any other API where consistency with that particular API would have been expected.** In other words, coming up a custom solution here diminishes the quality of the platform as a whole. --tobie
Received on Thursday, 20 September 2012 17:43:54 UTC