Re:Babashka: A quick example
by Whatitat90 on Saturday February 22, 2020 @12:57PM
(#22392296)
Why do you think asciidoc is better than Markdown? Serious question as quick skim over the homepage (https://asciidoctor.org/) and it looks just like Markdown with different sigils.
Re:Babashka: A quick example
by cmroanirgo on Saturday February 22, 2020 @01:52PM
(#22392596)
One of the main failings of markdown (for me) is it's lack of expressiveness, always forcing us to revert to html to get certain things done.
Markdown's great for simple readme, or if you don't need to (say) right align an image, of apply a class to a paragraph (eg. To turn it into an inset).
While I personally prefer textile (which is a deader dodo than asciidoc), they are both able to do significantly more than markdown.
I look at the problem as: if markdown forces me to write html, then I may as well use html...
(Ps: in textile "> hello world" at the start of a line sets right alignment, "=" for justified, "p.inset#my_id hello world" applies an "inset" class to the para and gives it the id "my_id". Asciidoc is similar, but I'm not familiar enough with it to write it on my phone just now)
Re:Babashka: A quick example
by type0 on Saturday February 22, 2020 @11:21AM
(#22391751)
babashka scripting could be overkill if you just want to rerun your generator every time some file changes. There's Entr is for that. What sort of automation can babashka do that isn't easier done with Python or Lua?
Re:Babashka: A quick example
by Borkdude on Saturday February 22, 2020 @11:33AM
(#22391829)
Babashka's target audience is primarily Clojure developers that just want to keep writing Clojure instead of switching to a language like Bash or Python for shell scripts. It's not a matter of better, just more familiar.
Re:Babashka: A quick example
by malcolmjuxt on Tuesday February 25, 2020 @01:10PM
(#22415539)
Some of our documents contain confidential details (personal data, client confidential details). Keybase provides a filesystem (kbfs), accessible by authorized individuals, with team management, and git repositories for recording history.
Unfortunately, as worse is better, markdown is on the way to win.
https://www.ericholscher.com/blog/2016/mar/15/dont-use-markd...
https://dev.to/practicalprogramming/we-need-a-new-document-m...
https://mister-gold.pro/posts/en/asciidoc-vs-markdown/
Markdown's great for simple readme, or if you don't need to (say) right align an image, of apply a class to a paragraph (eg. To turn it into an inset).
While I personally prefer textile (which is a deader dodo than asciidoc), they are both able to do significantly more than markdown.
I look at the problem as: if markdown forces me to write html, then I may as well use html...
(Ps: in textile "> hello world" at the start of a line sets right alignment, "=" for justified, "p.inset#my_id hello world" applies an "inset" class to the para and gives it the id "my_id". Asciidoc is similar, but I'm not familiar enough with it to write it on my phone just now)