We could name a couple of big ones (GMail was already mentioned before), they already have designs ready to go into test as soon as they get SharedScript in a dev build. If there was no desire from actual app developer teams for SharedScript, we would not have the reason to continue with it long time ago.
That also pretty much means if we won't do SharedScript, we'll need to explore other opportunities toward efficient sharing of code and data which does not make people to write a multithreaded UI as SharedWorker solution would do. We have practically zero positive response to SharedWorkers being used this way. Granted, this is "just one company" but the limited unscientific poll kind of shows the direction... On Mon, Nov 30, 2009 at 1:58 PM, Jeremy Orlow <jor...@chromium.org> wrote: > On Mon, Nov 30, 2009 at 1:54 PM, Geoffrey Garen <gga...@apple.com> wrote: > >> > There are a lot of people inside Google that have a lot of experience >> with web standards, browsers, and web apps that seem to think this is useful >> and worth the effort to experiment with it. >> >> Who exactly inside Google is waiting to build a new service, feature, or >> experiment using SharedScript? >> > > I don't think we can or should have to say specifically, but several major > apps with millions of users. > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
