programming-2022 VS clerk

The latest thing the system can do is run interactive 3d mathematical visualizations. Here are some physics examples: https://twitter.com/sritchie/status/1503220063264026629, with code living here: https://github.com/sritchie/programming-2022

- multiple stories about the same piece of code, but all with the ability to IMPORT the story as a library

I've been writing sicmutils[0] as a "literate library"; see the automatic differentiation implementation as an example[1].

A talk I gave yesterday at ELS demos a much more powerful host that uses Nextjournal's Clerk to power physics animations, TeX rendering etc, but all derived from a piece of Clojure source that you can pull in as a library, ignoring all of these presentation effects.

Code should perform itself, and it would be great if when people thought "LP" they imagined the full range of media through which that performance could happen.

[0] sicmutils: https://github.com/sicmutils/sicmutils

[1] autodiff namespace: https://github.com/sicmutils/sicmutils/blob/main/src/sicmuti...

[2] Talk code: https://github.com/sritchie/programming-2022

[3] Clerk: https://github.com/nextjournal/clerk

Yes, for these examples SICMUtils is handling the state updates and gives new coordinates to Mathbox to render.

The library works in both JS and the JVM, so I was able to generate an unevaluated code form for the equations of motion (simplified, optimized!), which clerk sends over the wire for the JS build of sicmutils to run.

Here is the code for that demo: https://github.com/sritchie/programming-2022/blob/main/src/p...

The api is settling, of course this is all quite playful! I will add instructions on how to get this building when I’m back at the keyboard.

Another way this will all get more powerful is via the in-progress https://github.com/ChristopherChudzicki/mathbox-react project. When that’s settled we can send a data structure representing a full scene across the wire, and build stuff like www.math3d.org , but with the full power of Clojure augmenting the UI equation editor. Dreamy stuff!

Something I really like in the Clojure data science stack that isn't mentioned is Clerk* — an interesting take on notebooks. I think it's a good gateway into Clojure for those coming from a Python or R background.

*https://clerk.vision/

Clojure's lazy sequences by default are wonderful ergonomically, but it provides many ways to use strict evaluation if you want to. They aren't really a hassle either. I've been doing Clojure for the last few years and have a few grievances, but overall it's the most coherent, well thought out language I've used and I can't recommend it enough.

There is the issue of startup time with the JVM, but you can also do AOT compilation now so that really isn't a problem. Here are some other cool projects to look at if you're interested:

Malli: https://github.com/metosin/malli

Babashka: https://github.com/babashka/babashka

Clerk: https://github.com/nextjournal/clerk

I'm really enjoying using Clojure with Clerk: https://github.com/nextjournal/clerk

It's a bit like a Jupyter notebook, but you get to use your own editor, you still have a normal Clojure REPL, it's stored in git like "normal" code, etc.

Hey all, I'm new to Clojure and would appreciate your help with a few questions I had getting started. I'm using Leiningen to setup my projects and manage my packages as recommended in Brave & True. So far I've been able to add any dependencies I've needed without much issue, Neanderthal, tech.v3.dataset, etc. I'm interested in data science, and was hoping to set up a notebook environment to be able to quickly produce data visualizations on the fly since I'm used to working with Jupyter. I came across Clerk, but I'm having some trouble adding it to my project. Here's what I tried:

Clojure also has Clerk, which is like Jupyter, but more befitting Clojure's overall philosophy: https://clerk.vision/

If I were working long enough with gnarly enough equations I'd look into using Clerk to visualize the equations with MathJax or similar, probably following Sam Ritchie's footsteps with SICMUtils. To me this is the true readability answer: lisp notation for precise implementations, compiling to a rich & familiar visual representation.