base64-bytestring VS data-lens

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


Fast base64 encoding and decoding for Haskell. (by haskell)


Haskell 98 Lenses (by roconnor)
Our great sponsors
  • SonarLint - Clean code begins in your IDE with SonarLint
  • Scout APM - Less time debugging, more time building
  • SaaSHub - Software Alternatives and Reviews
base64-bytestring data-lens
1 0
40 13
- -
2.6 0.0
about 1 month ago over 4 years 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 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.


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

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

What are some alternatives?

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

microlens - A lightweight (but compatible with ‘lens’) lenses library

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

monoid-extras - Miscellaneous constructions on monoids

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

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

union - Extensible type-safe unions for Haskell

msgpack - Haskell implementation of MessagePack /[Haskell]

fclabels - First class composable record labels for Haskell.

store - Fast binary serialization in Haskell

file-embed - Use Template Haskell to embed file contents directly.

attoparsec-iteratee - An adapter to convert attoparsec Parsers into blazing-fast Iteratees

pretty-hex - A human readable style for binary data.