pod-registry
babashka-sql-pods
| pod-registry | babashka-sql-pods | |
|---|---|---|
| 2 | 2 | |
| 87 | 77 | |
| - | - | |
| 8.1 | 4.8 | |
| 13 days ago | 8 months ago | |
| Clojure | Clojure | |
| - | Eclipse Public License 1.0 |
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.
pod-registry
-
Babashka: GraalVM Helped Create a Scripting Environment for Clojure
babashka supports html parsing through pods:
https://github.com/babashka/pod-registry
Pods can be written in any language and they can expose functions to babashka by implementing a protocol.
One pod exposing HTML parsing is:
https://github.com/retrogradeorbit/bootleg
Here is an example of how to use that:
https://github.com/babashka/pod-registry/blob/master/example...
-
Lokke: Clojure for Guile
This is not how babashka (or the underlying sci interpreter) works: babashka doesn't transpile to another language, but directly executes the code (via an intermediate analyzed representation). Babashka (and sci) are implemented on the JVM in Clojure itself and can leverage libraries directly from that ecosystem, without re-implementing everything for a different host than the JVM. A bb (or sci) program consists of pre-compiled Clojure code (via GraalVM native-image) and interpreted glue code. It aims to be as compatible as possible with JVM Clojure. Babashka integrates with tools.deps.alpha and can execute several existing Clojure libraries "as is" (https://github.com/borkdude/babashka/blob/master/doc/projects.md). It aims to be as compatible as possible with JVM Clojure. With the introduction of pods (https://github.com/babashka/pod-registry) it is able to leverage libraries from other ecosystems as well.
babashka-sql-pods
- Babashka: GraalVM Helped Create a Scripting Environment for Clojure
-
GraalVM at Facebook
I've used native-image both directly and indirectly. Directly to implement a Clojure-language authentication server which needed a small memory footprint. Indirectly through @borkdude's https://github.com/babashka/babashka which provides a native-image binary that can run much of the Clojure language.
We open-sourced some babashka code at https://github.com/staticweb-io/staticweb-open-wp/tree/maste... One major caveat: when I wrote that code, babashka didn't have any MySQL support, so I shelled out to the MySQL CLI. Later, I figured out how to compile the MySQL JDBC drivers with native-image and it's now available at https://github.com/babashka/babashka-sql-pods along with HSQLDB, SQL Server, Oracle, and Postgres drivers.
What are some alternatives?
lokke - Lokke: Clojure for Guile
nbb - Scripting in Clojure on Node.js using SCI
clojure-scheme - Clojure to Scheme to C to the bare metal.
quickdoc - Quick and minimal API doc generation for Clojure
pod-babashka-aws - Deprecated, use https://github.com/grzm/awyeah-api
babashka-tools - A collection of Babashka tools
babashka - A Clojure babushka for the grey areas of Bash (native fast-starting Clojure scripting environment) [Moved to: https://github.com/babashka/babashka]
.dotfiles - My dotfiles
staticweb-open-wp - A fully open-source, customizable template for Static WordPress stacks on AWS.
backup-scripts - The various scripts I use to back up my home computers using ssh and rsync
hickory - HTML as data
reaver - A Clojure library for extracting data from HTML.