administrative-scripting-with-julia
nbb
administrative-scripting-with-julia | nbb | |
---|---|---|
7 | 48 | |
160 | 808 | |
- | 0.5% | |
5.2 | 7.8 | |
7 months ago | 17 days ago | |
Jupyter Notebook | 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.
administrative-scripting-with-julia
- GitHub - ninjaaron/administrative-scripting-with-julia: Guide for writing shell scripts in Julia
-
Administrative Scripting with Julia
I appreciate the "Why You Shouldn't Use Julia for Administrative Scripts" section[0] which asked exactly the questions I would have asked.
The choice of (non-Bash) language to write command line utilities is in a bit of odd spot right now. Python is basically almost everywhere installed but the dependency on runtime + venv oddities bring their own set of problems. Java has the same runtime need issues though things might improve with initiatives regarding native binary compilation (though including the runtime may not produce exactly lightweight executables). Perl used to be a hot favorite in this space but I don't think lot of people are writing new stuff in Perl even though it is still present by default almost everywhere. Go is almost perfect here except I don't want to deal with 3x the boilerplate. Personally I think Rust isn't a bad choice (libraries like clap hugely reduce the boilerplate) but the learning curve makes it a harder sell (even though for basic utilities, I don't think there would be too much wrestling with the borrow checker). Another choice that comes to mind is Nim; I think it is very well positioned except a lot of people don't know even about it so its a hard sell + even among those who know, everyone is looking at everyone else to take the initiative to adopt it in a corporate environment at a non-trivial scale.
[0]: https://github.com/ninjaaron/administrative-scripting-with-j...
-
Lisp or Julia
My question is actually not what everyone uses, but what is best suited for the task. Those two things are, of course, almost always different, because the average person is anything but smart. Here you see that Julia is indeed better suited for handling data than Bash: https://github.com/ninjaaron/administrative-scripting-with-julia And here you see that Lisp will be the best scripting language for certain persons: https://quotepark.com/quotes/1879617-larry-wall-is-lisp-a-candidate-for-a-scripting-language-whil/ Obviously, if you don't have in-depth experience with both languages, you don't have to answer my question.
nbb
-
Embeddable Common Lisp 23.9.9
The SCI/babashka clojure interpreter might be a good fit, if you're ok with a lisp.
It's mature and fully sandboxed.
https://github.com/babashka/nbb
-
create-helix-app: project templates with Helix and more
To try it out, run npx create-helix-app in your terminal. It is powered by Nbb, Ink, and Helix itself!
-
Releasing Longdown: Convert longform markdown files to outline format used by Logseq
Thanks for building! May also want to share in #extension-news in discord to reach more users. Fwiw, you might be able to write the whole script without the need for compilation with https://github.com/babashka/nbb. You may also be interested in https://github.com/logseq/nbb-logseq as a fair amount of logseq core is scriptable
-
Administrative Scripting with Julia
I wish there was something elaborated for scripts that run on Node. I've been using nbb[1] for scripting, and although it all runs through Node.js, it is fast and quick to prototype scripts. The best part is in CI I can simply `npx nbb path/to/script.cljs`. Things get clunky if I want to use anything about of the Node stdlib though, since then you need the dreaded node_modules folder around.
[1] https://github.com/babashka/nbb
-
I'm considering moving from Clojure to Common Lisp
For clojure I just found for babashka it seems someone natively compiled jsoup with graalvm and exposed (minimal functionality from it) as a babashka pod, or a possibility would be use nbb like babashka for node. But if racket has the libraries you need and you don't need js/jvm ecosystem than I'm sure it'll be great also
-
Is anyone using Shadow on the backend ?
There are some folks using nbb on the backend as well: https://github.com/babashka/nbb, e.g. in AWS Lambdas or via the sitefox framework: https://github.com/chr15m/sitefox. Don't expect stellar performance from nbb since it's interpreted CLJS rather than compiled (as you have with shadow-cljs) but for small scoped projects and fast prototyping it might be ok.
-
What's the best lisp to js compiler
https://github.com/babashka/nbb (babashka for nodejs)
-
nbb: I'm confused how to include dependencies from Clojars
I tried reproducing this example from the nbb documentation.
- nbb, scripting for Clojure on Node.js, turns 1.0!
-
i am so ANGRY with Clojure community
If you don't want to deal with the tooling but want to practice the language, have a look at https://github.com/babashka/nbb