hspec VS nixpacks

While of course Haskell has more normal testing infrastructure available (eg. https://hspec.github.io/), my favorite bit of Haskell testing is QuickCheck, which IIUC started life in Haskell and has been reimplemented in other languages with various degrees of effectiveness and various degrees of connection to the original project.

John Hughes (not the filmmaker) gives a great talk about it: https://youtu.be/zi0rHwfiX1Q

hspec is a great library for testing, you can also use it to group different kind of tests, like property-based tests with QuickCheck.

Example with Nixpacks:

We have an upcoming nixpacks builder that should work on ARM/ARM64, but there are issues in the nixpacks codebase I'm still trying to sort out before that lands.

I think this is something the writer of the article would be delighted to find: https://github.com/railwayapp/nixpacks

Yes, it builds the Dockerfile if it exists otherwise it uses nixpacks to create an image from source files for any language/framework. This image is then run using docker run .

I think this is true for Nix in the deployment/ops space, where debugging a broken build can be very frustrating. Language improvements are going to be less useful for app developers, the Flake learning curve is not going to get better with a type system.

Perhaps something like heroku buildpaks (https://github.com/railwayapp/nixpacks ?) would help devs get on the Nix train.

Hey! Any plans on integrating nixpacks? I'm one of the core maintainers & would love to help you out. No worries if not.

Uses NixPacks to build the images;