develooper Front page | perl.perl5.porters | Postings from August 2001

Re: The case for SDKs

From:
Matt Sergeant
Date:
August 3, 2001 03:42
Subject:
Re: The case for SDKs
Message ID:
Pine.LNX.4.30.0108031140070.18744-100000@ted.sergeant.org
On Fri, 3 Aug 2001, Tim Bunce wrote:

> I think there were two big mistakes in the SDK process.

I think there were three :-)

> One was the understanding that we should select and include only _one_
> module for any given area of functionality. Thereby forcing us into
> futile debates about which of several similar modules to include.
>
> I see no problem with 'lowering the bar' of entry into an SDK.
> The requirements should be simply that the module:
> 	is reasonably useful
> 	is reasonably well documented
> 	the interface is reasonably stable
> If that means we end up with an SDK with five different date modules,
> so what?
>
> The other mistake was that we were trying to define 'the' (one) SDK.
> I'd rather see multiple SDKs (web centric, database centric, xml, net, etc).
> Sure they'll be overlaps, but that's a bonus not a problem.

The third mistake I think was made (as I voiced at the p5p meeting) was
that it was too much of a burden on a couple of people to do all of the
SDK(s). They should be farmed out to experts in their particular field,
and those experts should be capable of farming out any work they need
done before putting stuff in the SDK to other people.

So, should we kickstart this process?

-- 
<Matt/>

    /||    ** Founder and CTO  **  **   http://axkit.com/     **
   //||    **  AxKit.com Ltd   **  ** XML Application Serving **
  // ||    ** http://axkit.org **  ** XSLT, XPathScript, XSP  **
 // \\| // ** mod_perl news and resources: http://take23.org  **
     \\//
     //\\
    //  \\




nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About