Good idea, streamline and optimise for the end user, be abundant with information for the developer. That way it would increase reliability for the end user too, as the live production code is less likely to change/have errors introduced, whereas if the developer code goes a little wrong, it's not as big a problem.
On Jan 9, 2008 2:26 PM, Jason Cartwright <[EMAIL PROTECTED]> wrote: > I disagree. Using gigs and gigs of bandwidth needlessly and making an app > run slower for millions of people, just so a few developers can hack around > with it? > > Much better to release an API and sample source code separately. > Example... > > Built for users: http://maps.google.com > Built for developers: http://code.google.com/apis/maps/ > > J > > > On Jan 9, 2008 12:13 PM, Dave Crossland <[EMAIL PROTECTED]> wrote: > > > On 09/01/2008, Jason Cartwright <[EMAIL PROTECTED]> wrote: > > > > > > Production client-side code really shouldn't have documentation in. > > > > If the BBC is serious about supporting innovation around the iPlayer, > > it ought to leave it in here. > > > > -- > > Regards, > > Dave > > (Personal opinion only) > > - > > Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, > > please visit > > http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. > > Unofficial list archive: > > http://www.mail-archive.com/[email protected]/ > > > > >
