bimap VS base64-bytestring

Compare bimap vs base64-bytestring and see what are their differences.


Bidirectional mapping between two key types (by joelwilliamson)


Fast base64 encoding and decoding for Haskell. (by haskell)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
bimap base64-bytestring
0 1
22 45
- -
0.0 4.7
almost 2 years ago 7 months ago
Haskell Haskell
BSD 3-clause "New" or "Revised" License BSD 3-clause "New" or "Revised" License
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.


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

We haven't tracked posts mentioning bimap yet.
Tracking mentions began in Dec 2020.


Posts with mentions or reviews of base64-bytestring. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-06-07.
  • Yatima: A programming language for the decentralized web
    16 projects | | 7 Jun 2021
    Sure, if you consider Haskell's runtime (I know that technically GHC /= Haskell, but in practice it's the only Haskell that matters, except maybe something like Asterius) all the primitives are backed by C libraries:

    Likewise with conventions around pointers, arrays, etc. to the point where if you want to do anything really low-level or performance sensitive in Haskell, you're essentially punching a hole into C. As a random example, within the fast base64bytestring library, you find lots of use of `malloc`, `ForeignPtr` etc.: And of course because this is C there aren't really many safety guarantees here.

    The plan with Yatima with its primitives, and eventually when we write an FFI is to integrate with Rust in the same way that Haskell uses C. My hope is that with Yatima's affine types we might even be able to FFI to and from safe Rust (since the borrow checker uses affine types), but this is a little bit of a research project to see how much that works. Even to unsafe Rust though, we have better safety guarantees than C, since unsafe Rust's UB is still more restricted than C's is.

What are some alternatives?

When comparing bimap and base64-bytestring you can also consider the following projects:

msgpack - Haskell implementation of MessagePack /[Haskell]

asn1-encoding - ASN1 Raw/BER/DER/CER reader/writer in haskell

data-lens - Haskell 98 Lenses

procrastinating-variable - Haskell values that cannot be evaluated immediately.

cassava-conduit - Conduit interface for cassava [Haskell]

schedule-planner - Calculate an ideal schedule layout from a set of timeslots

unamb-custom - Functional concurrency with unambiguous choice, using a custom scheduler.

buffer-builder - Haskell library for efficiently building up buffers

data-lens-fd - Lenses with Functional Dependencies

proto-lens - API for protocol buffers using modern Haskell language and library patterns.

filesystem-trees - Traverse and manipulate directories as lazy rose trees