We could do a custom JIT using Intel's crypto acceleration.
Could be even more epic than writing regexp JITs, I'm telling you it'll make
other engines look like fisher-price toys!
-Filip
On Apr 1, 2013, at 1:26 PM, Gavin Barraclough wrote:
> On Apr 1, 2013, at 12:36 PM, Glenn Adams wrote:
>
On Apr 1, 2013, at 1:26 PM, Gavin Barraclough wrote:
> On Apr 1, 2013, at 12:36 PM, Glenn Adams wrote:
>
>> correction... NTSC = Never The Same Color (twice)
>
> How do we intend to implement this? – any pseudo random behaviour needs to be
> cryptographically secure to avoid risking an inform
On Apr 1, 2013, at 12:36 PM, Glenn Adams wrote:
> correction... NTSC = Never The Same Color (twice)
How do we intend to implement this? – any pseudo random behaviour needs to be
cryptographically secure to avoid risking an information leak here.
G.
_
On Mon, Apr 1, 2013 at 10:39 AM, Michael Saboff wrote:
> I had heard that there is some disagreement among browser vendors as to
> video formats being supported with the Web VHS API. Safari will only
> support the Not Too Saturated Colors (NTSC) format to improve clarity,
> while Chrome has agre
Hi Ryosuke,
Thank you for the feedback.
On Mon, Apr 1, 2013 at 2:06 PM, Ryosuke Niwa wrote:
> Why are rewind(), forward(), pause() and eject() all blocking APIs? I don't
> think we should be blocking the main thread while those operations are
> taking place. In particular, rewind() can take any
> Implementations that use ECMAScript to implement the APIs defined in this
> specification must implement them in a manner consistent with the ECMAScript
> Bindings defined in the Web IDL specification [WEBIDL], as this specification
> uses that specification and terminology.
Why are we still
On Mon, Apr 1, 2013 at 7:06 PM, Ryosuke Niwa wrote:
>
> I'm also confused by the fact VHSOutput interface has a
> method, streamToYouTube, that specifically supports one website. Are we
> expecting to add methods like streamToDailyMotion, streamToUStream, etc...?
> I'd prefer coming up with a g
Why are rewind(), forward(), pause() and eject() all blocking APIs? I don't
think we should be blocking the main thread while those operations are
taking place. In particular, rewind() can take anywhere from a few seconds
to a few minutes. We should let authors show some kind of UI for
rewinding,
Finally.
-- Darin
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev
9 matches
Mail list logo
