<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Binary on Commentary of Takao</title><link>https://takao.blog/en/tags/binary/</link><description>Recent content in Binary on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/binary/index.xml" rel="self" type="application/rss+xml"/><item><title>JavaScript Typed Arrays: Binary Data Processing in the Browser</title><link>https://takao.blog/en/web/js-typed-arrays/</link><pubDate>Tue, 10 Sep 2024 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/js-typed-arrays/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post JavaScript Typed Arrays: Binary Data Processing in the Browser" /&gt;&lt;p&gt;JavaScript&amp;rsquo;s native &lt;code&gt;Number&lt;/code&gt; type — an IEEE 754 double-precision float — is inefficient for binary data. Early solutions involved manual byte packing in plain arrays, which was slow and error-prone. ECMAScript 2015 formalized Typed Arrays, bringing C-like memory management to JavaScript. This three-layer architecture — &lt;code&gt;ArrayBuffer&lt;/code&gt;, TypedArray views, and &lt;code&gt;DataView&lt;/code&gt; — enables high-performance binary data processing in the browser and Node.js.&lt;/p&gt;
&lt;h2 id="arraybuffer-foundation"&gt;ArrayBuffer Foundation
&lt;/h2&gt;&lt;p&gt;&lt;code&gt;ArrayBuffer&lt;/code&gt; represents a fixed-length raw binary buffer. It cannot be read or written directly — you must use a view:&lt;/p&gt;</description></item></channel></rss>