Re: Declarative vs. procedural

It would be helpful if we can identify some concrete use cases which you
want to enable purely with markup and leave the rest to the JS API. If we
remove the click-to-permit use case, the only other one I've heard so far is
the automatic binding use case which is something a built-in Voice IME can
address without any change to the web page.

Cheers
Satish


On Thu, Oct 20, 2011 at 10:55 PM, Robert Brown
<Robert.Brown@microsoft.com>wrote:

> I'm not sure this is the right study to draw that conclusion from. The
> language that's missing from the list is "HTML". It would be more conclusive
> to find out what proportion of HTML web apps include java script.
>
> -----Original Message-----
> From: public-xg-htmlspeech-request@w3.org [mailto:
> public-xg-htmlspeech-request@w3.org] On Behalf Of Charles Hemphill
> Sent: Thursday, October 20, 2011 12:05 PM
> To: public-xg-htmlspeech@w3.org
> Subject: Declarative vs. procedural
>
> Hi Everyone,
>
> I mentioned some numbers from an article that I noticed last week:
> http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html.  The top
> 2 programming languages are known by about 17% of the programmers (each).
> JavaScript is known by about 2% of programmers.  This might be surprising
> given the billions of Web pages out there.
>
> Having a JavaScript API is fine, but keep in mind that there are many HTML
> developers who know little to no JavaScript.  It's good to have a
> declarative markup option for those who specialize in markup.  The
> JavaScript API should then fit with and extend the declarative markup
> option.   That's easier to do now than to retrofit later.
>
> Best regards,
> Charles
>
>
>
>
>
>