So this is like medium + org-babel-mode/jupyter but for clojure content?
It's a good idea with a good execution (especially the idea around literate programming). I also like that I always have a copy of my own content in my fork.
I would just need some more convincing though to post content here instead of just posting it on my own blog?
Maybe it is good to use both the personal blog and public spaces like this. It is great that finally we have a common space for posting Clojure namespaces as notebooks, where different authors can be conveniently visible to each other, respond and follow up each other, and contribute to a somewhat unified set of knowledge.
Think of Civitas as a "static site generator" that uses the GH pages for the project as the public hosting for all the content -- a centralized, Clojure-specific blog if you like.
So this is like medium + org-babel-mode/jupyter but for clojure content?
It's a good idea with a good execution (especially the idea around literate programming). I also like that I always have a copy of my own content in my fork.
I would just need some more convincing though to post content here instead of just posting it on my own blog?
Maybe it is good to use both the personal blog and public spaces like this. It is great that finally we have a common space for posting Clojure namespaces as notebooks, where different authors can be conveniently visible to each other, respond and follow up each other, and contribute to a somewhat unified set of knowledge.
I liked this demo by Timothy Pratley (the creator of Clojure Civitas): https://www.youtube.com/watch?v=lceazLPcSZg
How is this different from https://github.com/nextjournal/clerk?
Think of Civitas as a "static site generator" that uses the GH pages for the project as the public hosting for all the content -- a centralized, Clojure-specific blog if you like.
Reminds me of https://github.com/bhauman/devcards
another attempt to get a defibrillator on the last remaining lisp-like
just move on folks
We cannot, the WebAssembly crowd decided that Lisp like was exactly the best textual representation for WebAssembly.
Since it is the best thing since sliced bread, as long as WebAssembly is around we won't need a defibrillator.
Lisp has a guaranteed life (albeit low stakes) in configuring and extending Emacs, which like Vim is unkillable!
(jeez, OPs account is pure trolling...)