- base64-bytestring VS msgpack
- base64-bytestring VS asn1-encoding
- base64-bytestring VS data-lens
- base64-bytestring VS cassava-conduit
- base64-bytestring VS bimap
- base64-bytestring VS buffer-builder
- base64-bytestring VS fclabels
- base64-bytestring VS filesystem-trees
- base64-bytestring VS proto-lens
- base64-bytestring VS histogram-fill
Base64-bytestring Alternatives
Similar projects and alternatives to base64-bytestring
-
-
-
Onboard AI
Learn any GitHub repo in 59 seconds. Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev.
-
-
-
-
yatima-lang-alpha
A programming language for the decentralized web
-
-
InfluxDB
Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.
-
buffer-builder
Haskell library for efficiently building up buffers
-
-
filesystem-trees
Traverse and manipulate directories as lazy rose trees
-
matrix.to
A simple stateless privacy-protecting URL redirecting service for Matrix
-
proto-lens
API for protocol buffers using modern Haskell language and library patterns.
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
base64-bytestring reviews and mentions
-
Yatima: A programming language for the decentralized web
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: https://hackage.haskell.org/package/ghc-prim-0.4.0.0/docs/GH...
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.: https://github.com/haskell/base64-bytestring/blob/master/Dat... 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.
Stats
haskell/base64-bytestring is an open source project licensed under BSD 3-clause "New" or "Revised" License which is an OSI approved license.
The primary programming language of base64-bytestring is Haskell.