|author||Christopher Brannon <firstname.lastname@example.org>||2021-03-31 14:31:10 -0700|
|committer||Christopher Brannon <email@example.com>||2021-03-31 14:31:10 -0700|
Add sales bullshit to README.
1 files changed, 8 insertions, 0 deletions
@@ -6,6 +6,14 @@ to work just now.
NAWP stores content in an sqlite database. It is dynamic, not a static
site generator. It is supposed to run as a CGI script.
+## Why Would Anyone Actually Want to Use it?
+Here's a short list of reasons.
+* Minimum dependencies. No PHP, no external RDBMS. Just the binary and a CGI-capable web server. If you pass `-static -L -static` on the `csc` command line when building it, you can even have a fully-static binary with no external dependencies at all.
+* Because you don't need the features of a more capable platform; you just want a publishing tool with as little friction as possible.
+* Because you know and love Scheme. You can reason about it and fix it when it breaks. Rest assured, it will break.
Here is a list of the external Scheme libraries ("eggs" in Chicken Scheme parlance) that NAWP needs: