critbit VS data-reify

Compare critbit vs data-reify and see what are their differences.

data-reify

Reification of data structures using observable sharing (by ku-fpg)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
critbit data-reify
3 -
330 28
- -
0.0 3.4
over 2 years ago 9 months ago
C Haskell
- GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

critbit

Posts with mentions or reviews of critbit. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-21.
  • Ask HN: What are some 'cool' but obscure data structures you know about?
    54 projects | news.ycombinator.com | 21 Jul 2022
    > Good use-case: routing. Say you have a list of 1 million IPs that are [deny listed].

    Apparently, bloom filters make for lousy IP membership checks, read: https://blog.cloudflare.com/when-bloom-filters-dont-bloom/

    CritBit Trie [0] and possibly Allotment Routing Table (ART) are better suited for IPs.

    [0] https://github.com/agl/critbit

    [1] https://web.archive.org/web/20210720162224/https://www.harig...

  • Rethink-app: DNS over HTTPS, firewall, and connection tracker for Android
    8 projects | news.ycombinator.com | 29 May 2022
    developer here

    I'd imagine the app should work over IPv6-only networks thanks to 464xlat. I may be wrong, because I've never tested it on a IPv6-only network.

    The reason for IPv6 is two fold:

    1. Firewall today simply stores classless IP address rules as strings in a sqlite table fronted by a lfu cache backed by a typical hash-map. With IPv6, I'd imagine, this won't scale. So, we need a more economical in-memory data-structure (like a crit-bit trie [0] or art tree).

    2. Apparently LwIP has problems with HappyEyeballs (I personally never saw it, but got a couple of reports from users about it that it was an unrecoverable error once the connectivity was lost, and the firewall had to be restarted). We're in the process of replacing LwIP with gvisor/netstack now [2], just to get IPv6 support back on track.

    [0] https://github.com/agl/critbit

    [1] http://www.hariguchi.org/art/art.pdf

    [2] https://github.com/celzero/firestack/issues/3

  • Critbit Trees in C(WEB)
    1 project | news.ycombinator.com | 30 Jan 2022

data-reify

Posts with mentions or reviews of data-reify. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning data-reify yet.
Tracking mentions began in Dec 2020.

What are some alternatives?

When comparing critbit and data-reify you can also consider the following projects:

flatbuffers - An implementation of the flatbuffers protocol in Haskell.

encode-string - String encoding and decoding in Haskell

tables - Deprecated because of

text - Haskell library for space- and time-efficient operations over Unicode text.

rethink-app - DNS over HTTPS / DNS over Tor / DNSCrypt client, WireGuard proxifier, firewall, and connection tracker for Android.

hnix - A Haskell re-implementation of the Nix expression language

semantic-source - Parsing, analyzing, and comparing source code across many languages

jump - Jump start your Haskell development

nextstep-plist - Parser and printer for NextStep style plist files

unordered-containers - Efficient hashing-based container types

data-treify - Reify a recursive data structure into an explicit graph.

refined - Refinement types with static checking