node's internal buffer methods for writing and reading utf8 is faster than textencoder/textdecoder
January 4, 2025 at 1:18 AM
node's internal buffer methods for writing and reading utf8 is faster than textencoder/textdecoder
even faster rich text facet segmentation, because why not (t/y @voidlinux.mom)
github.com/mary-ext/atcut…
github.com/mary-ext/atcut…
November 15, 2024 at 5:24 AM
even faster rich text facet segmentation, because why not (t/y @voidlinux.mom)
github.com/mary-ext/atcut…
github.com/mary-ext/atcut…
Usa o TextEncoder com length.
September 7, 2024 at 9:48 PM
Usa o TextEncoder com length.
ECMAScript excitement 😉
Congrats to @jasnell.me on advancing Typed Array Concatenation to Stage 1 at TC39 today 🎉
It aims to improve the performance of this concat operation compared to userland libraries.
Congrats to @jasnell.me on advancing Typed Array Concatenation to Stage 1 at TC39 today 🎉
It aims to improve the performance of this concat operation compared to userland libraries.
![const enc = new TextEncoder();
const u8_1 = enc.encode('hello');
const u8_2 = enc.encode('world');
const u8_3 = Uint8Array.concat([u8_1, u8_2]);](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:w227epg3attqnssfdkx6ex6a/bafkreih3olwqia2py3t6uuc3qed3cldxqhzqvbk424j43twfsecmvzsrua)
November 18, 2025 at 7:52 AM
ECMAScript excitement 😉
Congrats to @jasnell.me on advancing Typed Array Concatenation to Stage 1 at TC39 today 🎉
It aims to improve the performance of this concat operation compared to userland libraries.
Congrats to @jasnell.me on advancing Typed Array Concatenation to Stage 1 at TC39 today 🎉
It aims to improve the performance of this concat operation compared to userland libraries.
In the JS world, we knew we had access to the TextEncoder/TextDecoder APIs, which enabled us to get utf8 buffers which we could slice on byte ranges.
Given that utf8 code units are bytes, we figured that the best move was to run with that. All languages can do byte indexing.
Given that utf8 code units are bytes, we figured that the best move was to run with that. All languages can do byte indexing.
May 8, 2024 at 10:03 PM
In the JS world, we knew we had access to the TextEncoder/TextDecoder APIs, which enabled us to get utf8 buffers which we could slice on byte ranges.
Given that utf8 code units are bytes, we figured that the best move was to run with that. All languages can do byte indexing.
Given that utf8 code units are bytes, we figured that the best move was to run with that. All languages can do byte indexing.
ECMAScript excitement 😉
Congrats to @jasnell.me on advancing Typed Array Find Within to Stage 1 at TC39 today 🎉
It aims to provide a native indexOf operations for Typed Arrays.
docs.google.com/presentation...
Congrats to @jasnell.me on advancing Typed Array Find Within to Stage 1 at TC39 today 🎉
It aims to provide a native indexOf operations for Typed Arrays.
docs.google.com/presentation...
November 18, 2025 at 8:05 AM
ECMAScript excitement 😉
Congrats to @jasnell.me on advancing Typed Array Find Within to Stage 1 at TC39 today 🎉
It aims to provide a native indexOf operations for Typed Arrays.
docs.google.com/presentation...
Congrats to @jasnell.me on advancing Typed Array Find Within to Stage 1 at TC39 today 🎉
It aims to provide a native indexOf operations for Typed Arrays.
docs.google.com/presentation...
Counting post length, it's graphemes, your UI client should use something like Intl.Segmenter to split the string and count visual clusters
But ATProto facet offsets are *bytes*, so encode the string to UTF-8 using (TextEncoder().encode(text)) then calc the start+end offsets from the Uint8Array.
But ATProto facet offsets are *bytes*, so encode the string to UTF-8 using (TextEncoder().encode(text)) then calc the start+end offsets from the Uint8Array.
May 5, 2026 at 11:35 PM
Counting post length, it's graphemes, your UI client should use something like Intl.Segmenter to split the string and count visual clusters
But ATProto facet offsets are *bytes*, so encode the string to UTF-8 using (TextEncoder().encode(text)) then calc the start+end offsets from the Uint8Array.
But ATProto facet offsets are *bytes*, so encode the string to UTF-8 using (TextEncoder().encode(text)) then calc the start+end offsets from the Uint8Array.
📝 The skrub TextEncoder brings the power of HuggingFace language models to embed text features in tabular machine learning, for all those use cases that involve text-based columns.
May 28, 2025 at 8:43 AM
📝 The skrub TextEncoder brings the power of HuggingFace language models to embed text features in tabular machine learning, for all those use cases that involve text-based columns.
It's wild to me that JS has strings and Uint8Arrays (byte arrays) but no built-in API that converts between the 2 data types. TextEncoder is a web API, not a builtin
December 18, 2024 at 2:11 PM
It's wild to me that JS has strings and Uint8Arrays (byte arrays) but no built-in API that converts between the 2 data types. TextEncoder is a web API, not a builtin
You might also wonder what the hell this is, and you might need to sit down for this. It's a binary encoding of IP ranges to countries, to the tune of 338KB on the wire (1.3MB unzipped).
All in the critical path, naturally.
All in the critical path, naturally.
May 24, 2025 at 5:30 AM
You might also wonder what the hell this is, and you might need to sit down for this. It's a binary encoding of IP ranges to countries, to the tune of 338KB on the wire (1.3MB unzipped).
All in the critical path, naturally.
All in the critical path, naturally.
У старого проекту на роботі є приховані таланти - ламається не відразу, а через декілька комітів) Видно що з душею зроблене.. Помилка - TextEncoder is not defined у тестах
September 9, 2025 at 6:38 AM
У старого проекту на роботі є приховані таланти - ламається не відразу, а через декілька комітів) Видно що з душею зроблене.. Помилка - TextEncoder is not defined у тестах
Very cool technique by @nastystereo.com for POST based CSRF without a content-type header using a Blob object, Interestingly it also seems to work using a Uint8Array
December 2, 2024 at 8:25 PM
Very cool technique by @nastystereo.com for POST based CSRF without a content-type header using a Blob object, Interestingly it also seems to work using a Uint8Array
if you use typed arrays and advanced features via TextEncoder/Decoder be aware it's a real mess in terms of expectations and the kind of buffers these can handle ... also: zero symmetry in there 🥲
summarized in this gist:
gist.github.com/WebReflectio...
summarized in this gist:
gist.github.com/WebReflectio...
TextEncoder & TextDecoder shenanigans
TextEncoder & TextDecoder shenanigans. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
March 3, 2025 at 1:18 PM
if you use typed arrays and advanced features via TextEncoder/Decoder be aware it's a real mess in terms of expectations and the kind of buffers these can handle ... also: zero symmetry in there 🥲
summarized in this gist:
gist.github.com/WebReflectio...
summarized in this gist:
gist.github.com/WebReflectio...
implemented a subset of textencoder/decoder in my pet js runtime ^-^
also ported deno's webidl implementation
also ported deno's webidl implementation
January 11, 2025 at 7:28 AM
implemented a subset of textencoder/decoder in my pet js runtime ^-^
also ported deno's webidl implementation
also ported deno's webidl implementation
I can't figure out how to move Text above TextEncoder etc, but close enough
May 6, 2025 at 9:55 AM
I can't figure out how to move Text above TextEncoder etc, but close enough
fully implemented TextEncoder/TextDecoder in the new version of github.com/easrng/safe-... :D
GitHub - easrng/safe-whatwg
Contribute to easrng/safe-whatwg development by creating an account on GitHub.
github.com
May 17, 2025 at 12:20 AM
fully implemented TextEncoder/TextDecoder in the new version of github.com/easrng/safe-... :D
New big yavascript update :3
github.com/suchipi/yava...
Highlights:
- ES2020 -> ES2023
- Improved top-level await support
- Added TextEncoder/TextDecoder
- Added import attribute support
- exec/Worker improvements on Windows
- Bytecode (de)serializer improvements.
- FreeBSD support added
github.com/suchipi/yava...
Highlights:
- ES2020 -> ES2023
- Improved top-level await support
- Added TextEncoder/TextDecoder
- Added import attribute support
- exec/Worker improvements on Windows
- Bytecode (de)serializer improvements.
- FreeBSD support added
Release v0.16.0 · suchipi/yavascript
This is a big update which has been a long time coming!
New Stuff
The underlying engine has been updated to support most of the ES2023 specification (it was previously ES2020). Notably, several ne...
github.com
June 7, 2026 at 4:56 AM
New big yavascript update :3
github.com/suchipi/yava...
Highlights:
- ES2020 -> ES2023
- Improved top-level await support
- Added TextEncoder/TextDecoder
- Added import attribute support
- exec/Worker improvements on Windows
- Bytecode (de)serializer improvements.
- FreeBSD support added
github.com/suchipi/yava...
Highlights:
- ES2020 -> ES2023
- Improved top-level await support
- Added TextEncoder/TextDecoder
- Added import attribute support
- exec/Worker improvements on Windows
- Bytecode (de)serializer improvements.
- FreeBSD support added
Here's what it supports so far:
- console, fs, process, path, Buffer, URL, EventEmitter, TextEncoder/TextDecoder
- Both callback and Promise APIs work setTimeout, setInterval, async/await
- Proper exception handling with stack traces
- console, fs, process, path, Buffer, URL, EventEmitter, TextEncoder/TextDecoder
- Both callback and Promise APIs work setTimeout, setInterval, async/await
- Proper exception handling with stack traces
January 2, 2026 at 3:08 PM
Here's what it supports so far:
- console, fs, process, path, Buffer, URL, EventEmitter, TextEncoder/TextDecoder
- Both callback and Promise APIs work setTimeout, setInterval, async/await
- Proper exception handling with stack traces
- console, fs, process, path, Buffer, URL, EventEmitter, TextEncoder/TextDecoder
- Both callback and Promise APIs work setTimeout, setInterval, async/await
- Proper exception handling with stack traces
🦖 TextEncoder: encoding property 🦖
https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder/encoding
The TextEncoder.encoding read-only property returns a string containing the name of the encoding algorithm used by the specific encoder.
#webdev
https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder/encoding
The TextEncoder.encoding read-only property returns a string containing the name of the encoding algorithm used by the specific encoder.
#webdev
TextEncoder: encoding property
The TextEncoder.encoding read-only property returns a string containing the name of the encoding algorithm used by the specific encoder.
developer.mozilla.org
April 18, 2026 at 8:56 AM
🦖 TextEncoder: encoding property 🦖
https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder/encoding
The TextEncoder.encoding read-only property returns a string containing the name of the encoding algorithm used by the specific encoder.
#webdev
https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder/encoding
The TextEncoder.encoding read-only property returns a string containing the name of the encoding algorithm used by the specific encoder.
#webdev
🦖 Random MDN: TextEncoder: encoding property 🦖
https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder/encoding
The TextEncoder.encoding read-only property returns a string containing the name of the encoding algorithm used by the specific encoder.
#webdev
https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder/encoding
The TextEncoder.encoding read-only property returns a string containing the name of the encoding algorithm used by the specific encoder.
#webdev
TextEncoder: encoding property
The TextEncoder.encoding read-only property returns a string containing the name of the encoding algorithm used by the specific encoder.
developer.mozilla.org
March 5, 2026 at 2:29 AM
🦖 Random MDN: TextEncoder: encoding property 🦖
https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder/encoding
The TextEncoder.encoding read-only property returns a string containing the name of the encoding algorithm used by the specific encoder.
#webdev
https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder/encoding
The TextEncoder.encoding read-only property returns a string containing the name of the encoding algorithm used by the specific encoder.
#webdev
bruh TextEncoder used to support utf16 but at some point they decided it wasn't used enough and removed it 🥴
its so dumb that TextDecoder supports non-utf8 encodings and TextEncoder doesn't
its so dumb that TextDecoder supports non-utf8 encodings and TextEncoder doesn't
November 28, 2024 at 10:40 AM
bruh TextEncoder used to support utf16 but at some point they decided it wasn't used enough and removed it 🥴
its so dumb that TextDecoder supports non-utf8 encodings and TextEncoder doesn't
its so dumb that TextDecoder supports non-utf8 encodings and TextEncoder doesn't
How I Learned to Stop Worrying and Love the TextEncoder() interface.
May 25, 2024 at 12:28 AM
How I Learned to Stop Worrying and Love the TextEncoder() interface.
And if you want to work with text then you need to use the asymmetric TextEncoder/TextDecoder 🫠
June 18, 2025 at 6:11 AM
And if you want to work with text then you need to use the asymmetric TextEncoder/TextDecoder 🫠