From b6342d2d8997fa46d71eba343f6f5ac5f8d4b607 Mon Sep 17 00:00:00 2001 From: Michiel Borkent Date: Thu, 30 Apr 2020 13:18:10 +0200 Subject: [PATCH] Dev note --- doc/dev.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/dev.md b/doc/dev.md index 4ed3d61f..1ad19f9b 100644 --- a/doc/dev.md +++ b/doc/dev.md @@ -31,11 +31,12 @@ When adding libraries to babashka, consider these evaluation criteria: - The functionality can't be met by shelling out to another CLI or can't be written as a small layer over an existing CLI (like `babashka.curl`) instead. -If none of the criteria are met, but adding a feature is still useful to a -particular company or niche audience, it can still be added when hidden behind a -feature flag. This is the case for `next.jdbc` and the `PostgresQL` and `HSQLDB` -database drivers. Companies interested in these features can compile an instance -of babashka themselves, instead of using the standard distributed version. +If not all of the criteria are met, but adding a feature is still useful to a +particular company or niche audience, adding it behind a feature flag is still a +possibility. This is currently the case for `next.jdbc` and the `PostgresQL` and +`HSQLDB` database drivers. Companies interested in these features can compile an +instance of babashka themselves, instead of using the standard distributed +version. ### Adding classes