> Isn't this essentially the "code-on-demand" aspect of REST?

> -Mike

> On Oct 4, 2012, at 9:47 PM, Kin Lane <kinl...@gmail.com> wrote:

> I don't think you are whack.  It's more of the conundrum that is the last
> Web APIs movement.   What is an API?  REST?  SOAP?  What makes the movement
> successful?  Everyone has their opinions.

> I classify JavaScript API under, "Embeddable".

> If you build a button, badget, widget or sophisticated JS app.  It's client
> side and thus can be embedded anywhere.  It's build for syndication and
> embeddability.

> Google Maps was built for hackability.  I remember Lars talking about this
> in the early days, in one of his keynotes.  The JS isn't the API.  The API
> drives the JS.

> Companies like Band Page, do the JS embed driven by API, but don't release
> the API.  It's there.  They acknowledge that savvy devs will hack it, and
> they won't prevent it.  Much like google maps team admitted to.

> I think naming matters.  I think your right.  JS API is not right, but I
> don't think my approach is either.

> I find advocating for an API is first.  Whether you make that public or not
> is up to you.  Then a healthy embeddable strategy is important, either way.

> I think JS is inherently client side or SDK...but then again NodeJS has
> bucked that trend.

> But great conversation and thoughts.  I think you have opened up something,
> few discuss.

> And needs more discussion.

> Kin Lane
> kinl...@gmail.com
> apievangelist.com / apivoice.com

> ** Attending API Strategy & Practice conference? **

> On Thu, Oct 4, 2012 at 4:36 PM, landlessness <br...@apigee.com> wrote:

>> Craftsfolk,

>> This is a silly question, but it's on my mind.

>> Just built an app using HTML5 & JavaScript using the 'JavaScript APIs'
>> from Google Maps and LinkedIn.

>> Along the way whenever I visited their dev sites
>> (https://developers.google.com/maps/documentation/javascript/reference &
>> https://developer.linkedin.com/documents/javascript-api-reference-0) I kept
>> thinking, this isn't a JavaScript API.

>> It's a JavaScript library calling an API.

>> Am I whack? Anyone else think the JavaScript API naming is weird? Isn't it
>> a JavaScript library (or sdk)? Does the naming matter? :~)

>> -b

>> --
>> You received this message because you are subscribed to the Google Groups
>> "API Craft" group.
>> To unsubscribe from this group, send email to
>> api-craft+unsubscribe@googlegroups.com.
>> Visit this group at http://groups.google.com/group/api-craft?hl=en.

> --
> You received this message because you are subscribed to the Google Groups
> "API Craft" group.
> To unsubscribe from this group, send email to
> api-craft+unsubscribe@googlegroups.com.
> Visit this group at http://groups.google.com/group/api-craft?hl=en.

> --
> You received this message because you are subscribed to the Google Groups
> "API Craft" group.
> To unsubscribe from this group, send email to
> api-craft+unsubscribe@googlegroups.com.
> Visit this group at http://groups.google.com/group/api-craft?hl=en.