On Sun, 10 Nov 2013 08:20:33 -0000, Adam Barth <[email protected]> wrote:
This is similar to AppCache vs Alex's ServiceWorkers. AppCache
addresses a small set of use cases, probably not enough. ServiceWorkers
provides the
tools to address a lot of use cases, but isn't directly itself a
solution;
you use it to build solutions. Another example would be the WebForms2
repetition model, vs Rafael's <template>. The repetition model idea
solved some specific use cases, but trying to make it solve all use
cases would
be a hugely complicated endeavour and would be really ugly. <template>
provides a tool with which you can build specific solutions, but isn't
itself a direct solution.
I basically agree with Ian. Let's address the simple use cases first
(i.e., device-pixel-ratio switching) and worry about the more complex
use cases in the future.
If we go that path I'm afraid we'll end up with a horrible mess of several
incomplete client-side and server-side solutions clobbered together with
preloader-killing scripts.
The closest thing to what Ian is suggesting is <x-picture> implemented
with <img postpone>, but due to standardization failure it won't be able
to benefit from image preloader or offer users/UAs ability to control
image selection.
Basically authors will hate us. We've been going in circles for a couple
of years now and all we have to offer is an incomplete solution? And
browser vendors can't even agree which one of the half-baked solutions is
it going to be :(
--
regards, Kornel
