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

redis-oxide

Multi-threaded implementation of redis written in rust

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

What to know before exploring

What it is

Multi-threaded implementation of redis written in rust

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, 3:56:07 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 year3 dated mentions

Observed mentions: 2020-02-06 23:58:35 UTC to 2024-08-26 13:44:02 UTC.

0122020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 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 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
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

3 sources
In practice I am not sure how true that is. There is a phenomenal ecosystem around org-mode that will require an amazing amount of work to recreate in other editors. I haven't seem other editors get close to the convenience and integration org-mode has in emacs. For example, org-babel lets me dynamically generate entire sections of a README on github[0]: #+BEGIN_SRC python :results output raw :format org :exports results ... elided python to generate org mode ... #+END_SRC Not to mention org-capture, org-agenda, or the various org-export-* functions. The deep hackiness of emacs lets this stuff just work naturally. And the quality of org-export is just amazing, especially when compared to say pandoc. I have done all of my university assignments in org-mode, augmenting with latex where required, and it just works. Same concept
Read the rest
with my website, I have a tiny function to turn org-mode buffers into live html rendering experience with basic elisp: (defun make-blogging-mode () (interactive) (toggle-word-wrap) (toggle-truncate-lines) (flycheck-mode) (flycheck-vale-toggle-enabled) (add-hook 'after-save-hook 'org-mode-export-hook) ) And a file hook (at the top of the org mode file so it runs automatically for me) # -*- find-file-hook: make-blogging-mode -*- This isn't just a simple, context-free grammar that any other editor can emulate. It's an entire ecosystem that needs to be translated, and many have tried and failed. Edit: Forgot to mention tables and the spreadsheet feature. Another hurdle a text editor will need to implement to recreate the experience [0] https://github.com/dpbriggs/redis-oxide/blob/master/README.o...
In Things Markdown got wrong
I'm finishing up my rust project convenient-skiplist [0] so I can finally achieve sorted set time-complexity parity between redis-oxide [1] and actual redis [2]. It's been quite challenging to get indexing working in a coherent and performant way. My sorted set implementation is "pure" in the sense you can only travel right and down, so you have to dance carefully to make the arithmetic work. And the fact it's in rust adds the additional headaches of borrow checker / etc. Very fun though. [0] https://github.com/dpbriggs/convenient-skiplist [1] https://github.com/dpbriggs/redis-oxide [2] https://redis.io/commands/zpopmax
In Ask HN: What are you currently working on?

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.