Are there any known-good polyfills for the current draft Typed Objects /
Binary Data spec?
Presently, JSIL has a set of primitives that roughly correspond with a big
chunk of the draft specification. I'm interested in seeing whether they can
work atop ES6 typed objects, which means either
On Sun, Nov 17, 2013 at 10:23 AM, K. Gadd k...@luminance.org wrote:
Are there any known-good polyfills for the current draft Typed Objects /
Binary Data spec?
I want this, too, and will start working on it soon-ish if nobody else does
or already did.
Presently, JSIL has a set of primitives
Since the strawman is close to the final spec, questions/nitpicks:
I noticed the current spec explicitly provides no control over element
alignment/padding. Are there specific reasons behind that? It dramatically
reduces the value of typed objects for doing file I/O (aside from the
endianness
On Nov 17, 2013, at 6:14 , David Herman dher...@mozilla.com wrote:
Does this imply module src= ?
Works either way, inline or external. (Requiring src= is one of the reasons
why script async was a non-starter.)
Is the value of `src` a module ID or a path? How about when packages are used
Typed Objects polyfill lives here: https://github.com/dherman/structs.js
Dave and I work on it, current status is pretty close to strawman minus
handles and cursors (which are a bit controversial at this point and as far
as I understand are not is Firefox implementation).
The polyfill includes a
On Nov 17, 2013, at 11:59 AM, Axel Rauschmayer a...@rauschma.de wrote:
On Nov 17, 2013, at 6:14 , David Herman dher...@mozilla.com wrote:
Does this imply module src= ?
Works either way, inline or external. (Requiring src= is one of the
reasons why script async was a non-starter.)
Is
Oh, of course: I completely forgot about that. Thanks for the link!
On Sun, Nov 17, 2013 at 10:42 PM, Dmitry Lomov dslo...@google.com wrote:
Typed Objects polyfill lives here: https://github.com/dherman/structs.js
Dave and I work on it, current status is pretty close to strawman minus
Nice script indeed, and it would be very nice to somehow be able to flag
that module for production/performance reason where slower engines in
slower hardware are not penalized much if the native implementation is not
in place.
Something that acts almost transparently, if that makes sense at all.
Is the value of `src` a module ID or a path? How about when packages are
used (for bundling)? Is there a way to combine module IDs and packages?
For the most part the answer to these kinds of questions is that we support
all of the above, but I'd like to wait just a little bit longer
9 matches
Mail list logo
