brendan at mozilla.org
Fri Sep 7 16:55:02 PDT 2007
ES embeddings exist where URIs make no sense, so it's not a good
candidate for the core standard. But we expect the burgeoning Ajax
ecosystem to keep on burgeoning (http://www.answers.com/main/ntquery?
gwp=13&s=burgeon), and make good use of shared library hosting
arrangements such as those provided by code.google.com and the like.
This should yield innovation and consolidation, as it has already for
some JS libraries, and as it did over the years for C (like JS, C
lacks built-in I/O primitives -- teletypes then or URIs now would not
fit in the core language).
You could make the same argument I'm making here about JSON and a few
other standard library proposals. I will not special-plead on their
behalf. Indeed we've had open issues about the detailed design of the
"right" JSON API on this list, which linger and nag (at me, at any
ECMA would be foolish to try to standardize too much I/O mechanism
and the like prematurely, but you and others on es4-discuss should
definitely collaborate (and on this list, for now -- we could use the
feedback both ways).
On Sep 7, 2007, at 2:29 PM, Garrett Smith wrote:
> I've decided to propose a URI class to deal with the handling of URIs
> that is so prevalent in Ajax apps and also in Flash and to a lesser
> extent, Adobe Reader.
> I propose this idea here because noticed that there are other places
> besides the web that can use it (Flash, Reader). A URI class could be
> implemented in ES to cover all these needs.
> I have a proposal page at http://www.dhtmlkitchen.com/rec/URI.html
> I won't copy paste the entire thing here. It prints on 3 pages if you
> set margin to 0 and scale to 70%.
> Is this the appropriate way to make a proposal?
> Programming is a collaborative art.
> Es4-discuss mailing list
> Es4-discuss at mozilla.org
More information about the Es4-discuss