process
filepath
Our great sponsors
| process | filepath | |
|---|---|---|
| 3 | 1 | |
| 200 | 66 | |
| 4.5% | - | |
| 6.5 | 7.5 | |
| about 2 months ago | 9 days ago | |
| Clojure | Haskell | |
| Eclipse Public License 1.0 | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
process
-
Poor documentation?
Check out babashka/fs and babashka/process as well. These are still based on Java interop underneath but they have some more features than the clojure.java.io and clojure.java.sh libraries. I tend to reach for these first when I need to do something filesystem or process related.
-
How do I install module?
A bit off-topic but if you're looking for an up-to-date maintained library to shell out in Clojure, take a look at process
-
ClojureRS – Clojure interpreter implemented in Rust
Nothing prevents you from using babashka and still use it as a glue for Unix programs. The difference is you get a nicer language (my opinion), a REPL if you want, and also you do get access to a lot more libraries from Java and Clojure and the pod concept of you want too as well.
So to be clear, you can easily use ImageMagick, curl, jq, pup, etc. See: https://clojure.github.io/clojure/clojure.java.shell-api.htm... and https://github.com/babashka/process
Other benefits are that you only need to learn Clojure and suddenly you can use it for everything, backend apps, frontend apps, scripts, etc. You don't need to learn bash, js and Java/go, make, etc.
> Then I did a very brief search for clojure libraries, things like parsing html. Most of the github projects were not seeing much activity (like last commit in 2020)
This surprises everyone, but those libraries still work, have no bugs, are missing no features, and can be used without issues in production.
Clojure is one of the most stable language, so things never break and almost never need updating.
People have a kind of Stockholm syndrome I think coming to other languages that if something didn't need a bug fix in a year it must be abandoned and broken.
And the reason you often don't need to update those libraries to keep up with the environment, like OS versions, is because they all leverage existing runtimes under the hood like JVM and that's the one that updates. So they're all secure and kept up to date, working with new OS and new architecture for free as JVM updates. This applies to Babashka as well, because it is implemented using a JVM.
filepath
-
Haskell - Important Libraries
filepath
What are some alternatives?
farolero - Thread-safe Common Lisp style conditions and restarts for Clojure(Script) and Babashka.
twitch - A high level file watcher DSL
ClojureRS - Clojure, implemented atop Rust (unofficial)
optparse-generic - Auto-generate a command-line parser for your datatype
bench - Command-line benchmark tool
selinux - Haskell bindings for the SELinux API
conch - A flexible library for shelling out in Clojure
turtle - Shell programming, Haskell style
taffybar - A gtk based status bar for tiling window managers such as XMonad
fs - File system utility library for Clojure
unix - POSIX functionality