This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-20
Channels
- # adventofcode (72)
- # aleph (8)
- # announcements (21)
- # beginners (43)
- # calva (10)
- # cider (2)
- # cljdoc (12)
- # cljsrn (3)
- # clojure (9)
- # clojure-android (1)
- # clojure-europe (38)
- # clojure-norway (2)
- # clojure-romania (1)
- # clojure-uk (2)
- # clojurescript (58)
- # cursive (8)
- # datomic (29)
- # deps-new (2)
- # depstar (2)
- # fulcro (3)
- # java (20)
- # leiningen (11)
- # luminus (2)
- # off-topic (13)
- # sci (1)
- # shadow-cljs (3)
Why do a lot of clojure folks prefer adoc to markdown? Just because is better? Prior book publishing know-how carry-over?
I’ve just made the switch for simple reasons like table of contents support, and embedded TIP, NOTE, WARNING callouts
I would not be surprised if the actual correlation would be based on years in tech, and thus carry-over. Currently working on a few years old Java project and surprised to see adoc docs. But setup by people with 10+ years experience.
I spent a lot of time evaluating both and decided asciidoc was just clearly better
I have a strong preference for adoc. It offers a richer set of elements than md. Where I sometimes find myself embedding html in md I can almost always just express what I want in adoc. Adoc can also do nice things like auto-generate a table of contents for your section headings, and supports replacement variables.
I think that's a reasonably fair executive summary :)
I'm looking for a specific blog post about a fictional job interview, in which the interviewee (lisper) implements C in Clojure (IIRC) and solves the interview questions in it. Writing was very well, if I'm not mistaken the author also wrote articles on writing.
https://aphyr.com/posts/353-rewriting-the-technical-interview
Thank you very much.
I only recently got into Clojure but this was enough to explode my brain a bit. Laughed out loud when I realized what they were doing