Blog

Here you can find many details about the design and implementation of NeoPG, and the challenges along the way.

C++ as a migration path for legacy C code

NeoPG is written in C++, while GnuPG is written in C. This article explains why.

34c3 Retrospective

I gave a lightning talk about NeoPG at the 34c3 and talked to some people in the community.

No daemons in NeoPG

NeoPG will not have long-running daemons. This article explains why.

Why a single binary is the right thing for NeoPG

NeoPG only provides a single binary for everything, while GnuPG is split up into many binaries. This article explains why.

No generated code in NeoPG

Generated code should be avoided. This article explains why.

Why a single repository is good for NeoPG

NeoPG combines all code in a single repository, while GnuPG uses many repositories. This article explains why.

Why CMake is better than Autoconf for NeoPG

NeoPG uses CMake instead of Autoconf. This article explains why.