- From: Florian Bösch <pyalot@gmail.com>
- Date: Wed, 26 Nov 2014 19:22:29 +0100
- To: Ted Mielczarek <ted@mozilla.com>
- Cc: WebApps WG <public-webapps@w3.org>
- Message-ID: <CAOK8ODjpK1di9ePXvJ0SiJm=z6i_hVKPjDnJTT57CEpc5OZObw@mail.gmail.com>
+1 https://www.w3.org/Bugs/Public/show_bug.cgi?id=27444 On the polling vs. live object. - I'd be nice if there was a way to poll but not allocate a new object everytime. This has been relegated to "oh we'll get better GCs in JS eventually, let's not structure our API around not having a good GC". I can't say how realistic this is, but I keep hearing it year after year, so... - Polling has an advantage for realtime applications that wish to do "late polling". That is, first render a bunch of stuff, that could take say, 14ms, and then poll the input for stuff you can do at the last second. This reduces input -> output latency. On Wed, Nov 26, 2014 at 3:40 PM, Ted Mielczarek <ted@mozilla.com> wrote: > Hello, > > The Gamepad spec has been languishing for some time, and I take > responsibility for that. However, on the bright side we have two > implementations shipping (Firefox, Chrome), and another shipping in > previews (IE) that, while not completely compatible, are usable in a > compatible manner, which is a great thing. > > We've had some spec bugs filed as a result of implementors reading the > spec, so those clearly need to be taken care of to finish the spec off. > Some of them are small corner cases[1,2,3], while one is a fairly large > oversight[4] that I've known about and haven't had time to spec > (liveness of Gamepad objects). The latter had significant discussion on > the mailing list[5] and I know what I need to do, it's just going to > require a fair bit of editing to spec it properly. > > Additionally, I met with some interested parties a few weeks ago at the > Mozilla office and we identified a fairly small spec addition[6] that > would help content libraries deal with the biggest interop issue that > they currently deal with in practice. I would like to spec this as well > before calling the spec done. > > My goal is to sit down and do some spec editing in the next month or > two, finish up the remaining issues, and move the spec forward to match > the reality of implementations. > > -Ted > > 1. https://www.w3.org/Bugs/Public/show_bug.cgi?id=17309 > 2. https://www.w3.org/Bugs/Public/show_bug.cgi?id=25203 > 3. https://www.w3.org/Bugs/Public/show_bug.cgi?id=26203 > 4. https://www.w3.org/Bugs/Public/show_bug.cgi?id=21434 > 5. http://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0238.html > 6. https://www.w3.org/Bugs/Public/show_bug.cgi?id=27444 > > >
Received on Wednesday, 26 November 2014 18:22:56 UTC