HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
tc39
proposal-arraybuffer-base64
HTML2023–2023
tc39 / proposal-arraybuffer-base64 · Archived

proposal-arraybuffer-base64

TC39 proposal for Uint8Array<->base64/hex

2Distinct people
3Mentions
0Explicit recommenders
280GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

TC39 proposal for Uint8Array<->base64/hex

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2023-10-23 18:35:44 UTC to 2023-10-24 18:19:54 UTC.

012023-10-23 18:00:00 UTC to 2023-10-23 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 23, 18:002023-10-23 19:00:00 UTC to 2023-10-23 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-23 20:00:00 UTC to 2023-10-23 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-23 21:00:00 UTC to 2023-10-23 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-23 22:00:00 UTC to 2023-10-23 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-23 23:00:00 UTC to 2023-10-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 00:00:00 UTC to 2023-10-24 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 01:00:00 UTC to 2023-10-24 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 02:00:00 UTC to 2023-10-24 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 03:00:00 UTC to 2023-10-24 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 04:00:00 UTC to 2023-10-24 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 05:00:00 UTC to 2023-10-24 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 06:00:00 UTC to 2023-10-24 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 24, 06:002023-10-24 07:00:00 UTC to 2023-10-24 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 08:00:00 UTC to 2023-10-24 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 09:00:00 UTC to 2023-10-24 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 10:00:00 UTC to 2023-10-24 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 11:00:00 UTC to 2023-10-24 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 12:00:00 UTC to 2023-10-24 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 13:00:00 UTC to 2023-10-24 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 14:00:00 UTC to 2023-10-24 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-10-24 15:00:00 UTC to 2023-10-24 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 16:00:00 UTC to 2023-10-24 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 17:00:00 UTC to 2023-10-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-24 18:00:00 UTC to 2023-10-24 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 24, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 23, 18:002023-10-23 18:00:00 UTC2023-10-23 19:00:00 UTC101
Oct 23, 19:002023-10-23 19:00:00 UTC2023-10-23 20:00:00 UTC000
Oct 23, 20:002023-10-23 20:00:00 UTC2023-10-23 21:00:00 UTC000
Oct 23, 21:002023-10-23 21:00:00 UTC2023-10-23 22:00:00 UTC000
Oct 23, 22:002023-10-23 22:00:00 UTC2023-10-23 23:00:00 UTC000
Oct 23, 23:002023-10-23 23:00:00 UTC2023-10-24 00:00:00 UTC000
Oct 24, 00:002023-10-24 00:00:00 UTC2023-10-24 01:00:00 UTC000
Oct 24, 01:002023-10-24 01:00:00 UTC2023-10-24 02:00:00 UTC000
Oct 24, 02:002023-10-24 02:00:00 UTC2023-10-24 03:00:00 UTC000
Oct 24, 03:002023-10-24 03:00:00 UTC2023-10-24 04:00:00 UTC000
Oct 24, 04:002023-10-24 04:00:00 UTC2023-10-24 05:00:00 UTC000
Oct 24, 05:002023-10-24 05:00:00 UTC2023-10-24 06:00:00 UTC000
Oct 24, 06:002023-10-24 06:00:00 UTC2023-10-24 07:00:00 UTC000
Oct 24, 07:002023-10-24 07:00:00 UTC2023-10-24 08:00:00 UTC000
Oct 24, 08:002023-10-24 08:00:00 UTC2023-10-24 09:00:00 UTC000
Oct 24, 09:002023-10-24 09:00:00 UTC2023-10-24 10:00:00 UTC000
Oct 24, 10:002023-10-24 10:00:00 UTC2023-10-24 11:00:00 UTC000
Oct 24, 11:002023-10-24 11:00:00 UTC2023-10-24 12:00:00 UTC000
Oct 24, 12:002023-10-24 12:00:00 UTC2023-10-24 13:00:00 UTC000
Oct 24, 13:002023-10-24 13:00:00 UTC2023-10-24 14:00:00 UTC000
Oct 24, 14:002023-10-24 14:00:00 UTC2023-10-24 15:00:00 UTC101
Oct 24, 15:002023-10-24 15:00:00 UTC2023-10-24 16:00:00 UTC000
Oct 24, 16:002023-10-24 16:00:00 UTC2023-10-24 17:00:00 UTC000
Oct 24, 17:002023-10-24 17:00:00 UTC2023-10-24 18:00:00 UTC000
Oct 24, 18:002023-10-24 18:00:00 UTC2023-10-24 19:00:00 UTC101

What Hacker News says

1 sources
The proposal for native base64 support for Uint8Arrays is mine. I'm glad to see people are interested in using it. (So am I!) For a status update, for the last year or two the main blocker has been a conflict between a desire to have streaming support and a desire to keep the API small and simple. That's now resolved [1] by dropping streaming support, assuming I can demonstrate a reasonably efficient streaming implementation on top of the one-shot implementation, which won't be hard unless "reasonably efficient" means "with zero copies", in which case we'll need to keep arguing about it. I've also been working on documenting [2] the differences between various base64 implementations in other languages and in JS libraries to ensure we have a decent picture of the landscape when designing this. With luck, I hope to advance the proposal to s
Read the rest
tage 3 ("ready for implementations") within the next two meetings of TC39 - so either next month or January. Realistically it will probably take a little longer than that, and of course implementations take a while. But it's moving along. [1] https://github.com/tc39/proposal-arraybuffer-base64/issues/1... [2] https://gist.github.com/bakkot/16cae276209da91b652c2cb3f612a...
In Goodbye, Node.js Buffer

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.