luciano/babashka
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

companies [skip ci]

Browse source
This commit is contained in:
Michiel Borkent 2021-10-04 21:24:45 +02:00
parent 0b2f70247f
commit 7fc03e4bb4
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -58,21 +58,21 @@ $ ls | bb -i '(filter #(-> % io/file .isDirectory) *input*)'
bb took 4ms. bb took 4ms.
``` ```
### Babashka users ## Babashka users
See [companies](doc/companies.md) for a list of companies using babashka. See [companies](doc/companies.md) for a list of companies using babashka.
Are you using babashka in your company or personal projects? Let us know Are you using babashka in your company or personal projects? Let us know
[here](https://github.com/babashka/babashka/issues/254). [here](https://github.com/babashka/babashka/issues/254).
### Setting expectations ## Setting expectations
Babashka uses [sci](https://github.com/borkdude/sci) for interpreting Babashka uses [SCI](https://github.com/borkdude/sci) for interpreting
Clojure. Sci implements a substantial subset of Clojure. Interpreting code is in Clojure. SCI implements a substantial subset of Clojure. Interpreting code is in
general not as performant as executing compiled code. If your script takes more general not as performant as executing compiled code. If your script takes more
than a few seconds to run or has lots of loops, Clojure on the JVM may be a than a few seconds to run or has lots of loops, Clojure on the JVM may be a
better fit as the performance on JVM is going to outweigh its better fit as the performance on JVM is going to outweigh its startup time
startup time penalty. Read more about the differences with Clojure penalty. Read more about the differences with Clojure
[here](#differences-with-clojure). [here](#differences-with-clojure).
## Status ## Status