|about 1 month ago||8 months ago|
|BSD 3-clause "New" or "Revised" License||BSD 3-clause "New" or "Revised" License|
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.
[Offer] Tutoring for Computer Science / Programming / Software Engineering topics
2 projects | reddit.com/r/tutor | 3 Sep 2022
I'm a software engineer with 3 years of professional experience. I worked for 2 years at Microsoft on Azure Compute and now work at Google, working on improving Google search. I am the sole maintainer of the popular open-source library microlens with 80k downloads. I've also contributed to the Koka programming language developed at Microsoft Research.
microlens is looking for a new maintainer
2 projects | reddit.com/r/haskell | 8 May 2022
microlens is a tiny van Laarhoven lenses library, mostly just copying definitions from lens and trying to avoid dependencies as much as possible. It has gained some popularity (742 package downloads in the last 30 days, vs the 1724 of the original lens).
Yatima: A programming language for the decentralized web
16 projects | news.ycombinator.com | 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: 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.
What are some alternatives?
data-lens - Haskell 98 Lenses
asn1-encoding - ASN1 Raw/BER/DER/CER reader/writer in haskell
msgpack - Haskell implementation of MessagePack / msgpack.org[Haskell]
cassava-conduit - Conduit interface for cassava [Haskell]
bimap - Bidirectional mapping between two key types
fclabels - First class composable record labels for Haskell.
filesystem-trees - Traverse and manipulate directories as lazy rose trees
buffer-builder - Haskell library for efficiently building up buffers
proto-lens - API for protocol buffers using modern Haskell language and library patterns.