[whatwg] Application deployment
russell.leggett at gmail.com
Thu Jul 31 10:32:33 PDT 2008
I don't necessarily think it's dirty, but any choices that game the system
for purely performance reasons seem hackish to me. Concatenating js files
for performance reasons is certainly less offensive than css sprites, but it
still begs the question: is this always the right choice. For example, let's
say I'm using jQuery plus a few plugins. The resources are really separate
entities from third parties. Should I have to concatenate them?
That said, there is clearly not much interest for this proposal here.
I graciously concede :)
On Wed, Jul 30, 2008 at 2:43 PM, Kristof Zelechovski
<giecrilj at stegny.2a.pl>wrote:
> in one source file and I am not sure what is wrong with it, except that a
> library should consist of books, but that concept was already broken long
> *From:* whatwg-bounces at lists.whatwg.org [mailto:
> whatwg-bounces at lists.whatwg.org] *On Behalf Of *Russell Leggett
> *Sent:* Wednesday, July 30, 2008 4:25 PM
> *To:* Peter Kasting
> *Cc:* whatwg at whatwg.org
> *Subject:* Re: [whatwg] Application deployment
> It seems to me that many of the additions to the HTML spec are there
> because they provide a standard way to do something we are already doing
> with a hack or more complicated means. CSS sprites are clearly a hack.
> Concatenating js files are clearly a hack. Serving from
> multiple sub-domains to beat the connection limit is also a workaround. My
> proposal is intended to approach the deployment issue directly, because I
> think it is a limitation in the html spec itself and therefore, I think the
> html spec should provide its own solution. My proposal may not be the best
> way, but assuming the issue will be dealt with eventually by some other
> party through some other means does not seem right either.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg