Fork me on GitHub
#announcements
<
2021-10-08
>
mkvlr09:10:25

🚀 Just released a very first preview version of Clerk, a local-first notebook built on top of regular Clojure namespaces: • io.github.nextjournal/clerk {:mvn/version "0.1.164"}. • Quickest way to play with it is cloning https://github.com/nextjournal/clerk-demo. • More info can be found in the https://nextjournal.com/mk/clerk-preview • My favorite notebook is https://storage.googleapis.com/nextjournal-cas-eu/data/8VwPbq6xWQadigCghK7KH5Q3WhUdCNU1d3LCgBnDNUJPyNH1Qw1JfDGFcBmCodHTY8rQDZDTS6UobY3dTLw4suxpGK#/notebooks%2Frule_30.clj 🕹️ Would really appreciate if folks took it for a spin and give feedback in #nextjournal on what can still needs to be improved before its open source release. 🙏:skin-tone-2:

🎉 31
metal 9
👁️ 2
rickmoynihan12:10:30

looks great and I managed to get it working; but the onboarding from the clerk-demo repo could be a little more straightforward. It could for example include an alias or user.clj that set it up to work. Also it looks like some of the notebook files don’t work out of the box; e.g. one of the examples includes jdbc, but it’s not in the deps.edn etc. Similarly some bits of the getting started snippet aren’t in the demo project; e.g. there’s no src directory. So you could perhaps integrate the getting started guide into the clerk demo repo??

rickmoynihan12:10:43

I’m also curious how it relates to http://nextjournal.com

1
rickmoynihan13:10:19

ah cool — I missed it 🙂

mkvlr14:10:00

all notebooks referenced there should run

mkvlr14:10:06

working on fixing up the rest now

yuhan15:10:05

Looks great! How does this compare to https://github.com/scicloj/notespace? I haven't used much of either but their goals look very similar.

Jakub Holý19:10:07

Yeah, I would like to know that too. I would appreciate it if https://nextjournal.com/mk/clerk-preview had a short section about the "syntax", i.e. what the comments rendered by Clerk look like, and a link to the API docs (with fns such as show! and the vl one). I am very happy to see this, thanks for open-sourcing!

mkvlr19:10:00

Clerk does static analysis to build a dependency graph for each form and caches results between subsequent evaluations so it only recomputes things that changed. This allows it to eliminate hidden state issues and a fast feedback loop with file save events as the interface. I believe notespace takes a different approach here receiving commands via the repl on what to evaluate but maybe @U066L8B18 can say more?

👍 1
mkvlr19:10:32

besides there seems to be some differences regarding the format (markdown line comments in Clerk vs vectors of strings in Notespace) and the viewer api differs, compare https://github.com/scicloj/notespace/blob/master/test/notespace/v3_experiment1_test.clj with https://github.com/nextjournal/clerk-demo/blob/main/notebooks/viewer_api.clj

👍 1
mkvlr19:10:43

(btw the notebook format used by Clerk is from https://www.maria.cloud)

❤️ 3
mkvlr19:10:20

and I’ll add the viewer functions to the readme

mkvlr19:10:45

(there’s currently html, vl, plotly, tex, table, md, code, with-viewer and with-viewers. https://github.com/nextjournal/clerk-demo/blob/main/notebooks/viewer_api.clj is the best reference until then

jerger_at_dda11:10:32

Just released our new c4k-jira module. A k8s setup for small jira installations on a cheap single app cluster. We use this installation in production. Provider independent backup is included - there is no lock in 🙂 https://gitlab.com/domaindrivenarchitecture/c4k-jira #k8s #devops #jira

🎉 4
borkdude13:10:33

babashka 0.6.2 babashka https://github.com/babashka/babashka/blob/master/CHANGELOG.md#062 Various bugfixes and a few new features!

babashka 22
👍 5
🎉 7
ericdallo13:10:31

cool, I was about to report something similar to #45

Karol Wójcik13:10:55

Cool. I have already stumbled upon the cider hanging bug.