Related to some engine rewrite and SSE, AVX, AVX2 cpu optimisation I did last year on cryptoxide :
Verifiable Random Function (VRF) are one of the key cryptographic primitive for Ouroboros Praos, that allows to participate in the block creation lottery. Let's dig in the detail of the tech
While Stack is really good at magically summoning all the compilers you need, adding your own compiled compiler is not quite documented. For testing specific version that doesn't have a release, or testing your own compiler modification, it's useful to add your own compiler in a build tool that by default works in a multi compiler settings.
Dealing with complex C-structure-like data in haskell often force the developer to have to deal with C files, and create a system that is usually a tradeoff between efficiency, modularity and safety.
Foreign class doesn't quite cut it, external program needs C files,
binary parsers (binary, cereal) are not efficient or modular.
Let's see if we can do better using the advanced haskell type system.
A new hope. Foundation is a new library that tries to define a new modern Haskell framework. It is also trying to be more than a library: A common place for the community to improve things and define new things
Rust is a pretty interesting language, in the area of C++ but more modern / better. The stated goal of rust are: "a systems programming language focused on three goals: safety, speed, and concurrency". Combining Rust with Haskell could create some interesting use cases, and could replace use of C in some projects while providing a more high level and safer approach where Haskell cannot be used.
For the last 5 years, I've worked intermittently on cryptographic related packages for Haskell. Lately, I've consolidated it all in one single package. Announcing cryptonite
All too often, things are downloaded without safety from hosts and mirrors. Here's a practical guide to know where you stand and improve the situation.
Each time, I've used the time API in Haskell, I'm left with the distinct feeling that the API is not what I want it to be. After one time too many searching the API to do some basic thing, I've decided to look at the design space and just try implementing what I want to use.
Following discussions with fellow haskellers, regarding the need to be careful with adding packages that could depends on GPL or proprietary licenses, it turns out it's not easy to get your dependencies's licenses listed.
On unix system, we get access to syscalls that maps files or devices into memory. The main syscall is mmap, but there's also some others syscalls in the same family to handle mapped memories like mlock, munlock, mprotect, madvise, msync.
One year ago, I've started some big changes on the tls package. I've finally manage to wrap it up in something that people can use straight out of hackage.
One of my side projects that has been running for couple of years now, was to get Cryptography up to scratch in haskell. Back when I started TLS, there were many various cryptography related projects and libraries. Many were not easy to use, none were consistent, many had performance problems.
After reading one too many time ghc core's output, i've been itching to have a more interactive output.