3 ms·

Huh? The core/reference implementation was python-only. (Was python2-only for a while, actually--I helped change that.) Asciidoctor (ruby) is a prominent imp

Huh? The core/reference implementation was python-only. (Was python2-only for a while, actually--I helped change that.) Asciidoctor (ruby) is a prominent implementation, granted, but afaik there are quite a few other implementations in other languages.

sandGorgon 6y ago
I'm talking about where the momentum is. Sure I can use asciidoctor (through docker,etc)..but what I'm really talking about is the adoption in the wider ecosystem. Which needs javascript, tooling, support,etc. Asciidoc as a community has not gone down that path.
- SevereOverfl0w 6y ago
  You might be interested in asciidoctor.js and asciidoctorj
mbeex 6y ago
Not so much. And the original Python variant is a) slowly growing old in features, b) the Python3 variants are unfinished and are missing support. I don't remember exactly in what respect, but I evaluated things some months ago and reluctantly installed the ruby gem of AsciiDoctor. I would have prefered a Python solution very much in my Python-driven environment. Also, a 'pip install asciidoc' would be very welcome.
- mbeex 6y ago
  > the Python3 variants are unfinished and are missing support. I stand corrected: https://asciidoc.org/CHANGELOG.html https://asciidoc.org/CHANGELOG.html (Version 9.0.0 (2020-06-02))