HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
BurntSushi
byteorder
Rust2020–2024
BurntSushi / byteorder

byteorder

Rust library for reading/writing numbers in big-endian and little-endian.

3Distinct people
4Mentions
0Explicit recommenders
1.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Rust library for reading/writing numbers in big-endian and little-endian.

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 6:59:22 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 year4 dated mentions

Observed mentions: 2020-10-30 08:05:27 UTC to 2024-07-22 06:06:51 UTC.

012020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

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
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

1 sources
Hmmm, maybe there is some confusion here. At least for ripgrep in particular, it has always been dual licensed under the MIT and the UNLICENSE[1]. This was itself a continuation of a decision I made a bit earlier with regards to another project[2]. Namely, I had been using only the UNLICENSE. But dual licensing with the MIT allowed folks with a more conservative risk profile to use the project. But the point of linking to VS Code's decision was to say that I have direct experience with situations in which a copyleft license might have inhibited use of my software. That is, it's an example that runs counter to my goal of as many people using my code as possible. This doesn't mean copyleft is never used in popular projects or that copyleft somehow perfectly inhibits popularity. I mean, obviously that's not true. But the existence of popular
Read the rest
copyleft projects doesn't mean that copyleft isn't itself a barrier to use in other circumstances. [1] - https://github.com/BurntSushi/ripgrep/blob/master/COPYING [2] - https://github.com/BurntSushi/byteorder/issues/26
In Software licensing and my opposition to copyleft

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.