I did some rabbit holing around bitwise nots in JavaScript:https://remysharp.com/2017/09/08/dive-into-bitwise-not-and-numbers …
-
Show this thread
-
Replying to @rem @Lady_Ada_King
Confused by this section… Those are 8 bits, or 1 byte — not 8 bytes.pic.twitter.com/C9qxoYAOII
2 replies 0 retweets 0 likes -
1 reply 0 retweets 0 likes -
I’m probably misreading something…
1 reply 0 retweets 0 likes -
Perhaps it is a spelling mistake? new UInt8Array(1) will be a 1 byte array. (8 bits)
3 replies 0 retweets 0 likes -
Replying to @Lady_Ada_King @mathias and
More precisely we get a new 8 bit ArrayBuffer and it can be accessed via the new UInt8Array.
1 reply 0 retweets 0 likes -
Replying to @Lady_Ada_King @mathias and
I wrote about typed array buffers herehttps://medium.com/samsung-internet-dev/being-fast-and-light-using-binary-data-to-optimise-libraries-on-the-client-and-the-server-5709f06ef105 …
1 reply 0 retweets 0 likes
What’s confusing is that “bit” is swapped with “byte” in that entire section (IIUC) yet the distinction is what it’s explicitly calling out
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.