![]() |
2 年之前 | |
---|---|---|
.. | ||
README.md | 2 年之前 | |
bytebuffer-dataview.js | 2 年之前 | |
bytebuffer-dataview.min.js | 2 年之前 | |
bytebuffer-dataview.min.js.gz | 2 年之前 | |
bytebuffer-dataview.min.map | 2 年之前 | |
bytebuffer-node.js | 2 年之前 | |
bytebuffer.js | 2 年之前 | |
bytebuffer.min.js | 2 年之前 | |
bytebuffer.min.js.gz | 2 年之前 | |
bytebuffer.min.map | 2 年之前 |
ByteBuffer.js uses either ArrayBuffers in the browser or Buffers under node.js.
Using Typed Arrays here is pretty much ideal, but it requires a somewhat recent browser.
bytebuffer.js uses an ArrayBuffer as its backing buffer, accessed through an Uint8Array.
bytebuffer.min.js has been compiled with Closure Compiler using advanced optimizations.
bytebuffer.min.js.gz
has also been gzipped using -9
.
bytebuffer.min.map is the source map generated by Closure Compiler.
Using DataViews is generally slower but works well with common polyfills for older browsers (avoids array access operators on Typed Arrays).
bytebuffer-dataview.js uses an ArrayBuffer as its backing buffer, accessed through a DataView.
bytebuffer-dataview.min.js has been compiled with Closure Compiler using advanced optimizations.
bytebuffer-dataview.min.js.gz
has also been gzipped using -9
.
bytebuffer-dataview.min.map is the source map generated by Closure Compiler.