From 3d5fe23f674c8564461cc19815a71f8b0393f8df Mon Sep 17 00:00:00 2001 From: Dennis Gosnell Date: Fri, 7 Jan 2022 11:21:42 +0900 Subject: [PATCH] wip --- 2022-01-03-purenix.md | 2 +- 2022-01-05-who-would-like-purenix.md | 12 ++++++--- 2022-01-10-why-purenix.md | 40 ++++++++++++++++++++++++++++ 3 files changed, 49 insertions(+), 5 deletions(-) create mode 100644 2022-01-10-why-purenix.md diff --git a/2022-01-03-purenix.md b/2022-01-03-purenix.md index 3edeb40..aebd5b3 100644 --- a/2022-01-03-purenix.md +++ b/2022-01-03-purenix.md @@ -26,7 +26,7 @@ If you just want to play around with PureNix, all you need is the first post. What sort of programmers would find PureNix easy to get started with? -1. Why PureNix? (coming soon) +1. [Why PureNix?](./2022-01-10-why-purenix) Why we decided to start working on PureNix. diff --git a/2022-01-05-who-would-like-purenix.md b/2022-01-05-who-would-like-purenix.md index e12e155..eff8cb2 100644 --- a/2022-01-05-who-would-like-purenix.md +++ b/2022-01-05-who-would-like-purenix.md @@ -6,8 +6,10 @@ draft: false ------------------------------------------------------ *This post is the second post in a -[series about PureNix](./2022-01-03-purenix). The previous post was about -[getting started with PureNix](./2022-01-04-getting-started-with-purenix).* +[series about PureNix](./2022-01-03-purenix). The previous post is about +[getting started with PureNix](./2022-01-04-getting-started-with-purenix). +The next post is about +[why we started writing PureNix](./2022-01-10-why-purenix).* PureNix will be easy to get started with for developers that have a good understanding of both Haskell-like languages and Nix. Developers without this @@ -130,8 +132,10 @@ Nix. You may have a harder time if you're new to either Haskell-like languages, or Nix. *This post is the second post in a -[series about PureNix](./2022-01-03-purenix). The previous post was about -[getting started with PureNix](./2022-01-04-getting-started-with-purenix).* +[series about PureNix](./2022-01-03-purenix). The previous post is about +[getting started with PureNix](./2022-01-04-getting-started-with-purenix). +The next post is about +[why we started writing PureNix](./2022-01-10-why-purenix).* ## Using PureNix Professionally diff --git a/2022-01-10-why-purenix.md b/2022-01-10-why-purenix.md new file mode 100644 index 0000000..edd299f --- /dev/null +++ b/2022-01-10-why-purenix.md @@ -0,0 +1,40 @@ +------------------------------------------------------ +title: Why PureNix? +summary: What lead to us starting to write PureNix? +tags: haskell, nixos, purescript +draft: false +------------------------------------------------------ + +*This post is the third post in a [series about PureNix](./2022-01-03-purenix). +The previous post is about +[who would find PureNix easy to use](./2022-01-05-who-would-like-purenix).* + +[PureNix]() started out half as a joke. This post explains why we started +working on PureNix, and how it moved from a joke to something we are excited +about. + +## The Idea + +I was a mentor for [Summer of Nix 2021](https://summer.nixos.org/). One of the +nice things about Summer of Nix is that the organizers arranged for various +people in the Nix community to give presentations about Nix-related topics. +One of the presentations was from [@adisbladis](https://github.com/adisbladis) +about [poetry2nix](https://github.com/nix-community/poetry2nix). + +`poetry2nix` is a Nix library for building Python packages that use +[Poetry](https://python-poetry.org/) to build. + +## Conclusion + +*This post is the second post in a +[series about PureNix](./2022-01-03-purenix). The previous post is about +[getting started with PureNix](./2022-01-04-getting-started-with-purenix). +The next post is about +[why we started writing PureNix](./2022-01-10-why-purenix).* + +## Using PureNix Professionally + +If your company is considering PureNix in order to tame a complicated Nix +codebase, [Jonas](https://jonascarpay.com/) and I currently have time available +for consulting or freelance. Feel free to [get in touch](/about). We are also +available for any other Nix/Haskell/PureScript-related work.