From 0adfcd636b7ea200c89edd47688e5d55893dce00 Mon Sep 17 00:00:00 2001 From: Michiel Borkent Date: Sun, 6 Dec 2020 23:06:06 +0100 Subject: [PATCH] Doc [skip ci] --- doc/surveys/2020-11.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/surveys/2020-11.md b/doc/surveys/2020-11.md index e9ee6c57..37dd3af7 100644 --- a/doc/surveys/2020-11.md +++ b/doc/surveys/2020-11.md @@ -211,13 +211,14 @@ The majority of people use babashka as a replacement for `bash`, `python` or writing small and short-running scripts that are cross-platform. In this scenario babashka is used for CLI utilities, ETL (data processing) scripts, automation / CI / devops and scripts ran from editors like emacs and vim. Some -people use it in places where they want to avoid or can't have JVM installation -or in memory constrained environments. Some people answered: whenever I can. +people use it in places where they want to avoid or can't have a JVM +installation or in memory constrained environments. Some people answered: +whenever I can. *My comment:* Babashka's original goal was to be a Clojure replacement for shell scripting and -it seems to have pulled that off according to the above summary. +based on the answers, it seems to have pulled that off. ### Q8 What operating system do you run babashka on?