You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Working with ArrayBuffers under node.js is subobtimal for a few reasons:
Pretty much everything in the node universe uses Buffers, so copying between ArrayBuffers and Buffers is required regularily.
Copying between Buffers and ArrayBuffers can be ridiculously slow (see).
Thus, building two different but API-compatible versions of ByteBuffer.js (one for node using Buffers and one for the browser using ArrayBuffers) is what we want from a performance perspective, while keeping in mind to make it a robust and developer-friendly library that can be used in the same way on servers and browsers, regardless of the backing buffer's type.
ByteBuffer 3 will do exactly that besides making the API more intuitive.
The text was updated successfully, but these errors were encountered:
Working with ArrayBuffers under node.js is subobtimal for a few reasons:
Thus, building two different but API-compatible versions of ByteBuffer.js (one for node using Buffers and one for the browser using ArrayBuffers) is what we want from a performance perspective, while keeping in mind to make it a robust and developer-friendly library that can be used in the same way on servers and browsers, regardless of the backing buffer's type.
ByteBuffer 3 will do exactly that besides making the API more intuitive.
The text was updated successfully, but these errors were encountered: